http://wiki.scn.sap.com/wiki/display/SD/ERP+Sales+and+Distribution (tres bon site sur sd custo et analyse des erreures)http://wiki.scn.sap.com/wiki/display/SD/SD+Pricing+overviewhttp://wiki.scn.sap.com/wiki/display/SD/Group+Conditionshttp://wiki.scn.sap.com/wiki/display/SD/ERP+SD+Pricing

1. ERP SD2. 3. ERP SD PricingSD Pricing overviewSkip to end of metadata Attachments:10 Added byKelly Ynoue, last edited byKelly Ynoueon Nov 05, 2012(view change) show commentGo to start of metadataPurposeThe purpose of this page is to provide an overview about the SD Pricing functionality.OverviewThe following sections will explain how condition technique works, the main pricing customizing and how to analyze the pricing in the sales order.Condition techniqueThe figure shows how the condition technique works in the background to produce the pricing information. The diagram shows how the various elements in the condition technique work together.1. The system determines the pricing procedure according to information defined in the sales document type and the customer master record.2. The pricing procedure defines the valid condition types and the sequence in which they appear in the sales order. In the example, the system takes the first condition type (PR00) in the pricing procedure and begins the search for a valid condition record.3. Each condition type in the pricing procedure can have an access sequence assigned to it. In this case, condition type PR00 is assigned to access sequence PR00. The system checks the accesses until it finds a valid condition record. (Although you cannot see this in the diagram, each access specifies a particular condition table. The table provides the key with which the system searches for records).4. In the example, the first access (searching for a customer-specific material price) is unsuccessful. The system moves on to the next access and finds a valid record.5. The system determines the price according to information stored in the condition record. If a pricing scale exists, the system calculates the appropriate price. In the example, the sales order item is for 120 pieces of the material. Using the scale price that applies to quantities from 100 pieces and more, the system determines a price of USD 99 per piece.The system repeats this process for each condition type in the pricing procedure determines a final price.1. The system takes the next condition type (K007) in the pricing procedure and begins the search for a valid condition record.2. Condition type K007 is assigned to access sequence K007. The system checks the accesses until it finds a valid condition record.3. The system finds a condition record in the first access (searching forDivision/Customer).4. The system determines the discount according to information stored in the condition record. In this case, the condition record found has a rate of 5,000 %.5. The system takes the next condition type (KF00) in the pricing procedure and begins the search for a valid condition record.6. Condition type KF00 is assigned to access sequence KF00. The system checks the accesses until it finds a valid condition record.7. The system finds a condition record in the first access (searching forIncoterms Part 1 + 2).8. The system determines the discount according to information stored in the condition record. In this case, the condition record found has an amount of 20,00 USD.Pricing customizingThe main pricing customizing are: Customizing of Pricing procedure (tcode V/08), customizing of Condition type (tcode V/06) and customizing of Access sequence (tcode V/07). The condition master data for pricing belongs to component SD-MD-CM, as shown in the following figure.

Customizing: SD Pricing Procedure Transaction V/08

A pricing procedure is a set of condition types that can be prices, discounts, surcharges, taxes, and freights, in a particular sequence.Example of standard pricing procedure: RVA001Related notes:SAP Note388112: Change of pricing procedures in the production systemCustomizing: SD Condition type Transaction V/06

A condition type is a representation in the system of some aspect of the daily pricing activities.For example, a different condition type can be defined for each kind of price, discount or surcharge that occurs in the business transactions.Customizing: Access sequence Transaction V/07

An access sequence is assigned to the condition types that are determined automatically.It consists of a sequence of condition tables.The sequence of the accesses establishes which condition records have priority over others.The accesses tell the system where to look first, second, and so on, until it finds a valid condition record.Pricing in Sales orderThe following figure shows the item conditions in the sales order.

You can access the item pricing screen by going to menu Goto Item -> Conditions.Related notes:SAP Note834174: How are 'value-related' condition bases determined?SAP Note1007110: How is the KWERT determined in a subtotal?SAP Note791944: How is the KBETR determined in a subtotal?The following figure shows the analysis button:

Related notes:SAP Note363212: 'Pricing analysis' mode of operationSAP Note859876: Condition is missing: Message VE 108 or VE 008SAP Note156230: Requirements: What is permitted, what is not?The following figure shows the pricing types that can be used to update the pricing in the sales order item. They are also used in the copy control to define which pricing the system will carry out when creating an SD document with reference to another.

Related note:SAP Note24832: Pricing rules / TVCPFRelated ContentRelated DocumentsSAP Library on path:SAP ERP (Central Component) -> Logistics -> Sales and Distribution (SD) -> Pricing and Conditions (SD-BF-PR)Related NotesSAP Note388112: Change of pricing procedures in the production systemSAP Note834174: How are 'value-related' condition bases determined?SAP Note1007110: How is the KWERT determined in a subtotal?SAP Note791944: How is the KBETR determined in a subtotal?SAP Note363212: 'Pricing analysis' mode of operationSAP Note859876: Condition is missing: Message VE 108 or VE 008SAP Note156230: Requirements: What is permitted, what is not?SAP Note24832: Pricing rules / TVCPF

Pricing Relevant Customizing - Tables, Structures, Transactions, Userexitscreated byCsaba Solteszon May 16, 2014 1:36 PM, last modified byCsaba Solteszon Jul 2, 2014 9:45 AMVersion 2inShareGeneral path:SPRO > Sales and Distribution > Basic Functions > Pricing

ObjectsTablesTransaction codes

Condition type(KSCHL)T685, T685AV/06 for Sales,M/06 for Purchasingor SM30 with View Cluster V_T685A

Access sequence(KOZGF)T682, T682I, T682ZV/07 for Sales,M/07 for PurchasingorSM34 withView Cluster V_T682

Pricing procedure(KALSM)T683, T683SV/08 for Sales,M/08 for PurchasingorSM34 withView Cluster V_T683

Pricing type(KNPRS)Internal table STEUhardcoded in includeLV61AA12 andFORM USEREXIT_PRICING_RULE

Condition exclusion groupsT684T684GT684SSM30 with View Cluster VV_T684_VASM30 with View Cluster VV_T684G_VASM34 with View cluster VVC_T683A_VA

Default condition sales overviewT683VOVKK

Pricing type used in copy control of documentsVTAA, VTFA, VTFL, etc.

Pricing relevant master data Pricing condition records

ConditionmasterdatatablesHow to maintain conditionmaster data ?

Axxx(e.g. A004)(Data field KNUMH)This table is used for the condition access. If access is successfula conditionrecord number is found (KNUMH).TransactionVK11 - VK13(or VK31 - VK33)for SD condition records

KONH(Key field KNUMH)This table contain administrative data of the condition record, e.g.ERNAM, ERDAT, ...

KONP(Key field KNUMH)This table contains the actual information of the condition recrod, e.g.9,50 EUR per 1 PC

KONM(Key field KNUMH)Quantity scales, e.g.From 1 PC 9,50 EUR per 1 PC 10 PC 8,50 EUR per 1 PCTransactionMEK1 - MEK3for MM condition records

KONW(Key field KNUMH)Value scales, e.g.From 50,00 EUR 5,00 EUR 100,00 EUR 15,00 EUR

Preparation of pricing calls inTKOMK (header) and TKOMP (item) structures are prepared in

PurchasingHeader data: FUNCTION ME_FILL_KOMK_PO (include LMEKOU24)Item data: FUNCTION ME_FILL_KOMP_PO (include LMEKOU25)

SalesFORM PREISFINDUNG_VORBEREITENin include FV45PF0P_PREISFINDUNG_VORBEREI

BillingFORM PREISFINDUNG_VORBEREITEN in include LV60AA58

Relevant structures and tables in SAPLV61A (Functions for pricing) in debugging mode

(T)KOMKStructure (internal table) withheader data.

(T)KOMPStructure (internal table) with item data.

XKOMVInternal table with the pricing result of the item processed (conditions and subtotal lines).When pricing is called this table is always refreshed and built up again.

TKOMVInternaltable with the total pricing result of the document. Itcontains no subtotal lines.

KOMT1Internal table which contains the customizing data of the pricing procedure and the condition types (T683S, T685, T685A).

KOMT2Internal table which contains the customizing of the relevant access sequences and accesses (T682, T682I, T682Z).

Userexits in calling programs

Preparation of pricing calls in 'Purchasing'Header data: FUNCTION EXIT_SAPLMEKO_001 (include LXM06U14)Item data: FUNCTION EXIT_SAPLMEKO_002 (include LXM06U15)

Preparation of pricing calls in 'Sales'Header data: FORM USEREXIT_PRICING_PREPARE_TKOMK (include MV45AFZZ)Item data: FORM USEREXIT_PRICING_PREPARE_TKOMP (include MV45AFZZ)

Additional triggering of pricing calls in 'Sales'FORM USEREXIT_NEW_PRICING_VBAP (include MV45AFZB)FORM USEREXIT_NEW_PRICING_VBKD (include MV45AFZB)

Preparation of pricing calls in 'Billing'Header data: FORM USEREXIT_PRICING_PREPARE_TKOMK (include RV60AFZZ)Item data: FORM USEREXIT_PRICING_PREPARE_TKOMP (include RV60AFZZ)

Userexits in pricing itself

in the pricing processing logic (program SAPLV61A)include RV61AFZA:FORM USEREXIT_PRICING_RULEFORM USEREXIT_PRICING_COPYinclude RV61AFZB:FORM USEREXIT_PRINT_ITEMFORM USEREXIT_PRINT_HEADFORM USEREXIT_XKOMV_BEWERTEN_INITFORM USEREXIT_XKOMV_BEWERTEN_ENDFORM USEREXIT_XKOMV_ERGAENZENFORM USEREXIT_XKOMV_ERGAENZEN_MANUFORM USEREXIT_XKOMV_FUELLENFORM USEREXIT_XKOMV_FUELLEN_O_KONP

in the pricing screen logic (program SAPLV69A)include (LV69AFZZ)

[custom] requirements (KOBED)include LV61ANNN [RV61ANNN]

[custom] scale base formula (KOFRS)include FV62ANNN [RV62ANNN]

[custom] condiiton basis formula (KOFRA)include FV63ANNN [RV63ANNN]

[custom] condition value formula (KOFRM)include FV64ANNN [RV64ANNN]

[custom] grouping key routines (GRLNR)include FV65ANNN [RV65ANNN]

Pricing procedure with custom requirement, condition value formula and condition basis formula (Number >= 600):

..2546ViewsProducts:sap_erp_sales_and_distributionTags:sales,pricing,sap_sd,pricing_procedure,pricing_condition,pricing_billing;,pricing_sales_order,pricing_analysis