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+overview
http://wiki.scn.sap.com/wiki/display/SD/Group+Conditions
http://wiki.scn.sap.com/wiki/display/SD/ERP+SD+Pricing

1.

ERP SD

2.

3.

ERP SD Pricing

SD Pricing overview
Skip to end of metadata

Attachments:10
Added by Kelly Ynoue, last edited by Kelly Ynoue on Nov 05, 2012 (view change)
show comment
Go to start of metadata

Purpose
The purpose of this page is to provide an overview about the SD Pricing functionality.

Overview
The following sections will explain how condition technique works, the main pricing customizing and how to analyze the
pricing in the sales order.

Condition technique
The 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 for Division/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.
8.

The system finds a condition record in the first access (searching for Incoterms Part 1 + 2).
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 customizing
The 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: RVA001
Related notes:
SAP Note 388112: Change of pricing procedures in the production system

Customizing: 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 order

The 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 Note 834174: How are 'value-related' condition bases determined?
SAP Note 1007110: How is the KWERT determined in a subtotal?
SAP Note 791944: How is the KBETR determined in a subtotal?
The following figure shows the analysis button:

Related notes:
SAP Note 363212: 'Pricing analysis' mode of operation
SAP Note 859876: Condition is missing: Message VE 108 or VE 008
SAP Note 156230: 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 Note 24832: Pricing rules / TVCPF

Related Content
Related Documents
SAP Library on path:
SAP ERP (Central Component) -> Logistics -> Sales and Distribution (SD) -> Pricing and Conditions (SD-BF-PR)

Related Notes
SAP Note 388112 : Change of pricing procedures in the production system
SAP Note 834174 : How are 'value-related' condition bases determined?
SAP Note 1007110 : How is the KWERT determined in a subtotal?
SAP Note 791944 : How is the KBETR determined in a subtotal?
SAP Note 363212 : 'Pricing analysis' mode of operation
SAP Note 859876 : Condition is missing: Message VE 108 or VE 008
SAP Note 156230 : Requirements: What is permitted, what is not?
SAP Note 24832 : Pricing rules / TVCPF

Pricing Relevant Customizing - Tables, Structures, Transactions,

Userexits
created by Csaba Soltesz on May 16, 2014 1:36 PM, last modified by
2, 2014 9:45 AM

Csaba Soltesz

on Jul

Version 2
inShare

General path:
SPRO > Sales and Distribution > Basic Functions > Pricing

Objects

Tables

Transaction codes

V/06 for Sales,

Condition type
(KSCHL)

M/06 for Purchasing

T685, T685A

or SM30 with View Cluster V_T685A

T682, T682I,
Access sequence

V/07 for Sales,

Objects

Tables

Transaction codes

M/07 for Purchasing

(KOZGF)

T682Z

or SM34 with View Cluster V_T682

V/08 for Sales,

M/08 for Purchasing

Pricing procedure
(KALSM)

T683, T683S

or SM34 with View Cluster V_T683

hardcoded in include LV61AA12 and

Pricing type
(KNPRS)

Condition exclusion groups

Default condition sales overview

Internal table
STEU

FORM USEREXIT_PRICING_RULE

T684

SM30 with View Cluster VV_T684_VA

T684G

SM30 with View Cluster VV_T684G_VA

T684S

SM34 with View cluster VVC_T683A_VA

T683V

OVKK

Pricing type used in copy control

of documents

VTAA, VTFA, VTFL, etc.

Pricing relevant master data <-> Pricing condition records

Condition master data tables

How to maintain
condition
master data ?

Pricing relevant master data <-> Pricing condition records

This table is used for the condition access. If

access is successful a condition

Axxx (e.g. A004)

(Data field KNUMH)

record number is found (KNUMH).

KONH

This table contain administrative data of the

condition record, e.g.

(Key field KNUMH)

ERNAM, ERDAT, ...

KONP

This table contains the actual information of the

condition recrod, e.g.

(Key field KNUMH)

9,50 EUR per 1 PC

Transaction

VK11 - VK13

(or VK31 - VK33)

for SD condition records

Quantity scales, e.g.

KONM
(Key field KNUMH)

From 1 PC 9,50 EUR per 1 PC

Transaction

10 PC 8,50 EUR per 1 PC

MEK1 - MEK3
Value scales, e.g.

KONW
(Key field KNUMH)

From 50,00 EUR 5,00 EUR

for MM condition records

100,00 EUR 15,00 EUR

Preparation of pricing
calls in

TKOMK (header) and TKOMP (item) structures

are prepared in

Purchasing
Header data: FUNCTION ME_FILL_KOMK_PO (include LMEKOU24)

Preparation of pricing
calls in

TKOMK (header) and TKOMP (item) structures

are prepared in

Item data: FUNCTION ME_FILL_KOMP_PO (include LMEKOU25)

FORM PREISFINDUNG_VORBEREITEN
Sales
Billing

in include FV45PF0P_PREISFINDUNG_VORBEREI

FORM PREISFINDUNG_VORBEREITEN in include LV60AA58

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

debugging mode

(T)KOMK

(T)KOMP

XKOMV

TKOMV

Structure (internal table) with header data.

Structure (internal table) with item data.

Internal 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.

Internal table with the total pricing result of the document. It contains no subtotal lines.

KOMT1

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

KOMT2

Internal table which contains the customizing of the relevant access sequences and

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

debugging mode
accesses (T682, T682I, T682Z).

Userexits in calling programs

Header data: FUNCTION EXIT_SAPLMEKO_001 (include

LXM06U14)
Preparation of pricing calls in
'Purchasing'

Item data: FUNCTION EXIT_SAPLMEKO_002 (include LXM06U15)

Header data: FORM USEREXIT_PRICING_PREPARE_TKOMK (include

MV45AFZZ)
Preparation of pricing calls in
'Sales'

Item data: FORM USEREXIT_PRICING_PREPARE_TKOMP (include

MV45AFZZ)

FORM USEREXIT_NEW_PRICING_VBAP (include MV45AFZB)

Additional triggering of
pricing calls in 'Sales'

FORM USEREXIT_NEW_PRICING_VBKD (include MV45AFZB)

Header data: FORM USEREXIT_PRICING_PREPARE_TKOMK (include

RV60AFZZ)
Preparation of pricing calls in
'Billing'

Item data: FORM USEREXIT_PRICING_PREPARE_TKOMP (include

RV60AFZZ)

Userexits in pricing itself

include RV61AFZA:
FORM USEREXIT_PRICING_RULE
FORM USEREXIT_PRICING_COPY

include RV61AFZB:
FORM USEREXIT_PRINT_ITEM
FORM USEREXIT_PRINT_HEAD
FORM USEREXIT_XKOMV_BEWERTEN_INIT
FORM USEREXIT_XKOMV_BEWERTEN_END
FORM USEREXIT_XKOMV_ERGAENZEN
FORM USEREXIT_XKOMV_ERGAENZEN_MANU
FORM USEREXIT_XKOMV_FUELLEN
in the pricing processing logic (program
SAPLV61A)

FORM 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):

.
.
2546 ViewsProducts: sap_erp_sales_and_distribution Tags: sales, pricing, sap_sd, pricing_procedure, pricing_con
dition, pricing_billing;,pricing_sales_order, pricing_analysis