Hi Kishore,
Details about 16 steps in pricing procedure•
Step: the no that determines the sequence no of a cond type with in a procedure
• Counter: second mini step with in an actual step
• Condition type: specify the cond type
• Description: Description of the condition type, you need not type.
• From & To: if you specify the ref steps in these fields, the cond values of the 2 steps specified and steps in between are totaled
• Manual: If you check this field the condition type is only included in determination either if they are entered manually.
• Mandatory: whether a cond type is mandatory when system carries out pricing. The Mdt column identifies those condition types that are mandatory in the pricing procedure. Mandatory condition types are the sales price or the cost price. Should a mandatory cond typ not be found in the procedure, the system will throw an error in pricing?
• Statistical: the value represented in this step will not alter the overall value. The condition type marked as statistical or Stat will not be included in the net value calculation for that item. The net value is displayed in the item details of the order and invoice, and the total of all items’ net values is displayed on the order and invoice document.
Examples:
 VPRS:- Cost
 PI01 – Inter company price.
 SKTV – Cash discount
 SKTO – Cash discount.
• Print: which cond types should be printed on a doc (order confirmation, invoices)
• Subtotal: controls whether & in which fields the cond amts or subtotals are stored. The subtotal field assigns a subtotal key to a step in the pricing procedure. These subtotal fields are then used in other areas of the system such as in logistics information system (LIS). For example, it is recommended to assign the subtotal field 4 to the total value in the pricing procedure for Freight.
• Requirement: for a cond type to be executed in the sales doc the requirement specified here must be satisfied. (It is a gateway). The requirement is used to assign a requirement to the condition type. This requirement can then be used to exclude the system from accessing the condition type and trying to determine a value.
 2 – Item with pricing used in discounts.
 9 – Cash discount after tax.
 10 – Plant is set, used for Tax condition.
 14 – Discount before tax
 21 – Invoice list control
 24 – Rebates get effect in Billing doc not in sales order
• Alternative Calculation Type: The column AltCty specifies that the system is to use the formula represented in this column as an alternative in finding the value of the condition type, rather than by using the standard condition technique. For example, this can be used to calculate complex tax scenarios.
Alternative formula to the formula in the standard system that determines the cond. In the std SAP system for the cust expected price EDI1, the alt cal type is 9, which means it contains a routine with a logic which states that the difference between the customer expected price & the net value is zero.
 2 – Net value
 6 – Initial price
 8 – Expected value
 9 – Expected price
 11 – profit margin
• Alternative Cond Base Value: alternative formula for determining the cond basis (amt to which the discount or surcharge in a scale refers). The column AltCBV is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value. For example, one can specify a formula that uses a subtotal, such as 4, from the Subtotal field, modify it slightly, such as dividing it by 2, and then using the resultant value as a base value for the condition type.
 2 – Net value
 3 – Net price
 4 – Net value plus tax
 11 – cash discount base
 28 – 100% discount
 29 – Free goods / Inclusive.
• Account Key: this field enables the system to post the sales value to different G/L accounts. ERL: sales revenues, ERS: sales deductions, ERF: freight revenue.
• Accruals: this is exclusively for rebate cond types BO01 & BO02. Key, which identifies various types of G/L accounts for accrual postings.
Note: To maintain your own requirements and routines use the transaction code -- VOFM
VPRS: Cost: Cost pick up from MMD of Accounting view 1.
TAX: MWST
Tax is calculated on the following parameters:
• Plant
• Ship to party region
• Customer tax classification
• Material tax classification
CONDITION SUPPLEMENTS
A Cond Supplement is a supplement for a particular cond type. A cond supplement is a group of conditions that should be applied every time a certain cond is found.
For e.g., if you define a material price, you would enter cond records for every material. If, for one of those materials, you also wanted to include a discount every time the price is determined, you can enter the additional cond type as a cond supplement. When SAP determines the cond record in the pricing proc, it will automatically also include the discount cond record.
Procedure:
• Create the cond type that are to be defined as cond supplements
• V/08: create a new pricing proc & list all the conditions that are to form the cond supplement in this procedure.
• V/06: in the cond type that the supplement applies to, enter the pricing proc one has just defined. Master Data Pricing Proc Field.
• Enter the cond record, select line item & Go To Conditon Supplement or just click on Cond Supplement Icon from tool bar. You can enter the cond supplements for all the cond types defined in the new pricing proc.
• Determination Rule: S.O, Distbn, Div, CuPP, DoPP, New Pricing Proc, Old Cond Type e.g., RDIL, RW, GM, A, 1, NEWPR0, PR00.
• You can only enter a cond supplement if the cond type you are working with has already been defined in Customizing for Sales to include cond supplements.
CONDITION EXCLUSION GROUP
In pricing for sales and billing documents, more than one condition record may apply to a particular item at any one time. You can use the condition exclusion process to compare possible conditions in order to determine such things as the best price for a customer.
SPRO- IMG- SD- Basic Functions- Pricing- Pricing Control- Condition Exclusion- Cond Exclusion for Group of Conditions:
• Define cond exclusion group: OV31
• Assign cond types to the exclusion groups: OV32
• Assign exclusion to pricing procedure: VOK8
A cond exclusion group is merely a grouping of cond types that are compared to each other during pricing & result in the exclusion of particular cond types with in a group or entire groups. The procedure according to which the selection is carried out within or between the condition exclusion groups is defined in the pricing procedure. The following options are possible:
• Selection of the most (least) favorable condition type within a condition exclusion group
• Selection of the most (least) favorable condition record of a condition type, if more valid condition records exist (for example, selection from different condition records of the condition type PR00)
• Selection of the most (least) favorable of two condition exclusion groups (in this case, all condition types of the two groups are cumulated and the totals are compared)
• Exclusion procedure: If a condition type in the first group exists in the document, all condition types in the second group are set to inactive.
Actions
• Create a condition exclusion group by entering an alphanumeric key with a maximum of four characters and a description.
• Allocate the condition types to a condition exclusion group. A condition exclusion group can contain any number of condition types.
• Enter the condition exclusion group in the pricing procedure that you use in pricing (Go to -> Exclusion groups).
• The condition exclusion indicator is not valid for cond supplements. This means if a cond record contains cond supplements they will be taken in to account during pricing.
• After selecting the pricing proc for which you want the cond exclusion to be active, select the button “Exclusion”.
• Deactivate Exclusion in access sequence when ever you active exclusion group.
• Best / Least cond records, with in cond types
• Best / Least cond record, between cond types
• Best / Least cond record, with in exclusion group
• Best / Least cond record, between exclusion groups.
NEW FIELDS IN PRICING
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
• Create the field in the KOMK (header data) & KOMP (item data) tables using the standard include provided for this requirement.
• Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
• When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
• After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Hope this would be more than enough to know.
Award points to encourage members.
Vamsi. P
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.