This document provides an overview of pricing conditions master data in ERP SD, including main transactions for maintaining condition tables and records, key tables used for conditions, dealing with inconsistencies, and generation of condition maintenance objects. The main transactions are for creating, changing, and displaying condition tables and records. Key tables include the condition table, conditions header, and conditions item tables. Reports are used for generating condition tables and reports, and finding and repairing inconsistencies.

1. source: http://wiki.scn.sap.com/wiki/display/SD/ERP+SD+Condition+Maintainance
ERP SD Condition Maintenance
Purpose
The purpose of this page is to provide an overview about pricing conditions master data.
Overview
In the following sections you will find information about the main transactions, main tables, dealing
with inconsistencies, and generation in condition maintenance.
Main transactions
The following figure shows the main transactions in condition maintenance:
Maintain condition tables (Customer namespace is between 501 and 999):
 V/03 Create Condition Table (or general transaction VK03)
 V/04 Change Condition Table (or general transaction VK04)
 V/05 Display Condition Table (or general transaction VK05)
Maintain condition records:
 VK11 or VK31 Create Condition Record
 VK12 or VK32 Change Condition Record
 VK13 or VK33 Display Condition Record* *
 VK14 or VK34 Create Condition Record with Reference

2. source: http://wiki.scn.sap.com/wiki/display/SD/ERP+SD+Condition+Maintainance
Main tables
The following figure shows the main tables in condition maintenance.
Condition Table (e.g. A304)
Key: Client, Application, Condition Type, VAKEY, Validity end date (optional), Release Status
(optional)
VAKEY: Variable key fields (fields like Sales Organization, Material Number, Ship-To Party) must be
part of the field catalog (table T681F) and structure KOMG.
Non-Key: Validity start date (optional), VADAT (Variable data portion), KNUMH (Link to KONH and
KONP, almost unique)
Conditions (Header)
Key: Client, KNUMH
Contains additional header information (created by, created on, sales deal or promotion number,…)
and the VAKEY as string.
Conditions (Item)
Key: Client, KNUMH, KOPOS (if condition supplements exists)
Contains important pricing information (rate, unit, calculation type, deletion indicator...)
Quantity Scales (KONM) (optional)
Value Scales (KONW) (optional)
The following figure shows an example of a condition record in tables A304, KONH and KONP:

3. source: http://wiki.scn.sap.com/wiki/display/SD/ERP+SD+Condition+Maintainance
When the user creates a new condition record in VK11 with the same keys and same validity period,
the system issues a pop-up warning that the existing condition record will be deleted when saving. If
the user clicks on ‘OK’, the entry in table Axxx is deleted. The entry in tables KONH and KONP
remains. They can be removed by archiving.
When the user creates a new condition record in VK11 with the same keys and validity period
overlapping the existing condition record, the system splits the existing condition record in table
Axxx.
For further information please see SAP Note 66943: Validity periods in condition records.
The deletion modus depends on the field ‘delete fr. DB’ (V_T685A-KDELE) in the customizing of
condition type (transaction V/06). If it is ‘ ‘ (space), when the user deletes a condition record in
VK12, the deletion indicator is set in table KONP (KONP-LOEVM_KO). The entries in table Axxx, KONH
and KONP remain. Conditions marked for deletion can be removed from database by archiving.
Dealing with inconsistencies
When error message VK067 occurs in condition maintenance, this is due to inconsistency. Report
VK+C can be used to find inconsistencies in condition tables. Example of inconsistency: entry exists in
table Axxx but not in table KONH or KONP.
To repair, you can overwrite the inconsistent record by creating a new condition record with the
same key and same validity period.
For further information, please see SAP Note 94443.
Generation in condition maintenance

4. source: http://wiki.scn.sap.com/wiki/display/SD/ERP+SD+Condition+Maintainance
SAP Note 886771 : Generation in condition maintenance explains the three generation reports in
condition maintenance:
Report RV12A001: generates condition tables, fast entry screens, selection reports.
Report RV12D001: generates the reports to “Display Condition Records”
Report RV14ALLE: generates the pricing reports
In VK12 for example, the program name contains the table number: RV13Axxx where xxx is the table
number.
In the fast entry screen of VK12 for example, the screen number contains the table number: 1xxx
where xxx is the table number. You can check the screen number by going to menu System -> Status.
Related Content
Related Documents
SAP Library path:
SAP ERP Central Component -> Logistics -> Sales and Distribution (SD) -> Pricing and Conditions (SD-
BF-PR) -> Condition records
Related Notes
SAP Note 886773: FAQ: General condition technique
SAP Note 66943: Validity periods in condition records
SAP Note 94443: Inconsistencies in condition master data (Termination VK067)
SAP Note 886771: Generation in condition maintenance