1.

Step:
  
Number that determines the sequence of the conditions with in a procedure. It indicates the position of the condition type in pricing procedure. Ex.: 10, 15 etc.

2. Counter:
  
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance. Access number of the conditions with in a step in the pricing procedure. During automatic pricing, the system takes into account the sequence specified by the counter.

3. Condition Type:
 
It represents pricing element in pricing procedure as a base price, discount, freight and tax. The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.

Ex.: PR00 - Price, K004 - Material Discount, K005 - Customer/Material Discount, K007 - Customer Discount.

4. Description:

System copies description of condition type from its description (V/06).

5. From and 6. To:
1. From: This can be used as a base to the condition type for calculating further value. 2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.

7. Manual:
     
This indicator specifies whether the specific condition type can be determined manually during sales order processing. If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic. For Base Price and Taxes, the entry should be automatic. For Discounts and Freights, The entry should be manual. If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it. If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.

If we check the box. Ex. then in VA01 at the header/item level in the conditions tab. If we uncheck the box. It is used only for information purposes only.Cost (Moving average price/Standard Price). Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. 11. we will take the example of the Rebates.e. These condition amounts or subtotals are used as a starting point for further calculations. Mandatory:      This indicator specifies that particular condition type is mandatory in the pricing procedure. . want a subtotal of all the discounts included in the pricing of a sales order. By defining Requirement in condition technique we can restrict the access of condition type. If the same fields are used to store different condition amounts. then in VA01 at the header/item level in the conditions tab. This is commonly used for condition types SKTO . 9. without giving any error. Statistical:       This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation. Requirement:    It is a routine that is written by an ABAP consultant according to the business requirement. Rebates are to be included during the billing document processing and not in the sales document processing. and in the Requirement column we give the value 24 which is "Only in Billing Document". If the condition type is checked with mandatory option.8. MWST. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).  For rebates we use the condition types BO01 to BO05. then value should be maintained for that condition type. the system totals the individual amounts. if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error. for example. This indicator causes a surcharge or discount to be set in the document statistically (that is. Subtotal:     The value of this field determines where the values of subtotals to be captured i. To understand the concept. 12. You may.Cash Discount VPRS . without altering the value). Controls whether and in which fields condition amounts or subtotals (for example. otherwise the system will not allow the user to process the document. in which table and which field.: PR00. if we delete the value in the condition type and try to save the document then system will allow us to save it. 10. Print:  The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed. a customer discount or the cost of a material) are stored.

Maintain Requirements & Formulas Click on the "Formulas" and then on the "Condition Values".Accruals:     The values of the Sales Revenues.    In this column we can mention the value as 12 . Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. If new Requirements are to be defined we follow the procedure given below. For example. Ex. And we assign the application type.Net Weight. Freight Revenues. And we assign the application type like V .Account Key/ Accrls . and Rebate Accruals etc.Gross Weight or 13 . and not on the base price. AcyKy . the system will consider the value that is mentioned in this column and determine the freight based on this value.KF00. AltCty .: 950 0 Profit Margin 11. 15.Maintain Requirements & Formulas Click on the "Requirements" in the top menu and then click on "pricing". The classification shown below. If new routines are to be defined we follow the procedure given below. It is an alternative formula for the condition type that can be used instead of standard formulas.Sales/Distribution etc. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. In order to do this we assign account keys/ accruals to the different condition types based on their classification. ERB Rebate sales deduct. volume etc. let us take the Profit Margin which can be both + / . We have a list of routines. We have a list of requirements. so here this routine will help us in generating the value which can be either + or -. Go to T. 14. It is again a Routine that is written by ABAP Consultant. Ex.Code: VOFM.      This Requirement will ensure that these condition types will appear only during the billing document processing.Alternative formula for condition base value:      Formula for determining the condition basis as an alternative to the standard. AltCBV . . So we assign 11 .Condition formula for alternative calculation type:            It is again a Routine that is written by ABAP Consultant. . We have to get the value from the Material master. Tax Revenues. we can ask ABAP consultant to create new requirement based on the client requests. It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column. Freight is calculated based on weight. Go to T. we can ask ABAP consultant to create new routines based on the client requests.: Freight .Profit Margin. During pricing. are going to be posted in the respective G/L accounts in Fi Module. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs. 16. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06. ERF Freight revenue . Sales Deductions.Code: VOFM..

Freight Revenues. For all Rebates condition types BO01 to BO05 we assign in Account key ERB . This also one of the areas of SD . For all Price condition types like PR00 etc. For all Discount condition types like K004. we assign ERL .Sales Deductions.          ERL Revenue ERS Sales deductions ERU Rebate accruals For Ex. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Fi Integration.Rebate Accruals. So the system posts respective values in respective G/L accounts in Fi-Co Module. we assign ERS . This account keys and accruals are in turn assigned to respective G/L accounts.Revenue.Code:VKOA. . K005 etc..Rebates Sales deductions and for Accruals ERU . we assign ERF . For all Freight condition types KF00 etc.