You are on page 1of 2

All the Steps of Calculation Schema or Pricing Procedure Step: It indicates the step number of condition type in pricing

procedure. Ex: 10, 20, 30, and etc. It is possible to number the steps in intervals of 1, but this can make changing the procedure in the future very difficult. Counter: System uses the counter while accessing the condition types in our pricing procedure. This is used to show a second mini step within an actual step. For example, you may have all your freight surcharges assigned to step 100; however, there may be three condition types, each representing a different freight surcharge. Thus, you can assign a freight condition type to step 100, counter 1; another to step 100, counter 2; another to step 100, counter3; and so on. Condition type: The condition type is the link from the access sequence all the way to the actual condition record. We specify condition types (pricing elements) that are participating to calculate net value in our pricing procedure. Ex: PR00 Description: System copies the description of the condition type from definition of condition type. From and To: These two columns serve two purposes. (A) As a range between the condition types of some conditions we can specify the same condition type within one range. So that all values of condition types added together and deducted or added to the base value. (B) As a base to calculate further value of condition type. We can specify the base for condition type. So that system takes the base (step). Manual: It determines how the condition type is going to be determining in our pricing procedure manually or automatically. Ex: Some condition types that do not have any access sequence should/can be determined manually. That means they do not directly come to the pricing procedure automatically. Ex: Item conditions can be determined automatically through access sequence and Header conditions should be entered manually. Mandatory: Mandatory indicates that the particular condition type is mandatory in pricing procedure. So that the end user should maintain the value of a particular condition type in condition records. Otherwise system will not allow the document to be process for further move. Ex: Condition types Base price and Taxes are mandatory conditions. Statistical: It indicates the purpose of condition type is only for information purpose. The value of condition type will not be reflected onto the G/L Accounts. Ex: Condition type VPRS

As this VPRS copies cost of the material from the material (master) and deducts the value from net value for items to calculate profit margin. So the purpose of having VPRS is only to copy the cost of the material. So that it should be a statistical. Print: It indicates the value of the condition type can be printed in a document. Sub total: The value of this field determines where the value of the sub totals is going to be stored in the database. Sub total 1 = KOMP KZWI 1 and Sub total 2 = KOMP KZWI2 Requirement: Requirement is nothing but a routine that has been written by ABAPers according to the client requirement. Requirement is used for condition type that excludes particular condition type while determining the net value. Ex: Routine No: 23 and 24 can be used only in billing document with condition type BI01, BI02, and BI03 (condition types for rebates) as these condition types should be activated only in the billing document level. We include these condition types in our pricing procedure and system deactivates at sales order level and activates in billing document level. System takes this requirement into consideration and activates or deactivates accordingly. PR00: As it is quite possible some items are not relevant for pricing, it is advisable to assign a requirement indicating this condition type is not necessary for items not relevant for pricing. Assigning the requirement 002 to the requirement column can do this. Alternative formula for calculation type: We can specify the alternative formula instead of standard one as a condition type in the form of routines. Ex: Routine No: 11 profit margins can be used as a alternative formula for condition type to calculate profit margin as there is no standard condition type to calculate profit margin. Alternative formula for condition base value: Instead of using from column as a basis to calculate further value for particular condition type we can use a formula in the form of routine to use base. Ex: Routine No: 12 or 13 gross weight or net weight can be used with Freight condition type to calculate fright charges. As for freight charges always weight of the material taken as a base. Accounting keys and accruals: We can define and assign accounting keys for each and every pricing element groups. So that, the values of the pricing elements (condition types) can be posted in the respective G/L accounts, through this accounting keys. Ex: ERL = Sales revenues (Ex: PR00) ERS = Sales deductions (Ex: K004, K005, K007, and etc) ERF = Freight revenues (Ex: KF00) MWS = Tax revenues (Ex: MWST) ERU = Rebate accruals (Ex: BI01, BI02, and BI03)