Mastering the Condition Technique in SAP SD Pricing: A Step-by-Step Configuration Guide
The Sales and Distribution (SD) module uses the Condition Technique to develop a comprehensive framework for pricing gross prices, allocating discounts, including freight surcharges, or differentiated tax calculation structures.
For functional consultants and system architects looking to develop scalable Order-to-Cash (O2C) solutions, mastery of the Condition Technique is vital. This step-by-step guide provides you with the technical know-how related to backend customizing (SPRO) and the execution of relevant transactions (VA01 / VL11).
What is the Condition Technique in SAP SD?
The Condition Technique is the algorithm of SAP that evaluates, searches, and determines values (e.g., prices, discounts, taxes, surcharges) based on the prescribed business logic.
To understand the final sales price calculation in a sales order, we need to appreciate the evaluation order of the top-down definition.
[ Pricing Procedure (V/08) ]
ā
āāā> [ Condition Types (V/06) ] (e.g., PR00, K007)
ā
āāā> [ Access Sequence (V/07) ]
ā
āāā> [ Condition Table 1 (501) ] āā> Customer / Material
āāā> [ Condition Table 2 (502) ] āā> Material Group
āāā> [ Condition Table 3 (004) ] āā> Material Only
- The master framework of the sequence of condition types, subtotals, requirements, and accounting keys is referred to as the Pricing Procedure.
- A Condition Type is one of the pricing building blocks (e.g., Base Price PR00, Customer Discount K007, Freight KF00).
- A search sequence for a master data type defines access sequence for SAP.
- A combination of fields that forms part of a condition record key.
- Condition record. Value and validity of master data as well as information on the scale are stored in this record using transaction VK11.
The 5-Step Configuration Roadmap
Follow this step-by-step configuration path to build a custom pricing setup in SAP SD.
Step 1: Create Condition Tables (Transaction V/03, V/04, or V/05)
A Condition Table describes the field combinations of a record for the pricing table.
- Transaction Code: V/03, V/04, or V/05
- IMG Path: Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Tables
Configuration Guidelines:
- Standard Table Range: 001 to 500 (Pre-delivered by SAP).
- Custom Table Range: 501 to 999 (Reserved for customer namespace).
- Select fields from the given field catalog (Sales Organization, Distribution Channel, Customer, Material).
- Technical Note: Saving a Condition Table will automatically generate a database table Axxx (e.g. Table 501 will generate table A501).
Step 2: Define Access Sequences (Transaction V/07)
An Access Sequence is a search path that reads Condition Tables in the order of greatest specification to the least.
- Transaction Code: V/07
- IMG Path: Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Access Sequences
| Step | Table Number | Field Combination | Exclusive |
|---|---|---|---|
| 10 | 501 | Sales Org / Customer / Material | [X] |
| 20 | 502 | Sales Org / Customer Group / Mat. | [X] |
| 30 | 004 | Material Only | [X] |
The "Exclusive" Indicator: If set at [X], SAP stops processing the tables below the step. This indicator speeds up the SAP system during the creation of sales documents.
Transaction Code: V/06
IMG Path: Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types
| Parameter | Base Price (PR00) | Customer Discount (K007) |
|---|---|---|
| Condition Class | B (Prices) | A (Discount/Surcharge) |
| Calculation Type | C (Quantity dependent) or A (Percentage) | A (Percentage) |
| Condition Category | L (Gross Price) | Blank |
| Access Sequence | PR00 / Custom ZPR0 | K007 / Custom ZK07 |
| Manual Entries | C (Manual entry has priority) | C (Manual entry has priority) |
| Item Condition | Set [X] | Set [X] |
Step 4: Create & Maintain the Pricing Procedure (Transaction V/08)
The Pricing Procedure connects different types of condition chains in an organized order.
- Transaction Code: V/08
- IMG Path: Sales and Distribution > Basic Functions > Pricing > Pricing Control > Maintain Pricing Procedures
ZSTANDARD_01 Example Pricing Procedure
Step Cnt CType Description From To Man Req Stat SubT Reqm CalTy BasTy AccKey āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā 10 0 PR00 Base Price [ ] [X] [ ] A 0 0 0 ERL 20 0 K007 Customer Discount 10 [ ] [ ] [ ] 0 2 0 0 ERS 100 0 Net Value 10 20 [ ] [ ] [X] 2 0 0 0 200 0 MWST Output Tax 100 [ ] [ ] [ ] 0 0 0 0 MWS 300 0 Total Amount 100 200 [ ] [ ] [X] 4 0 0 0
Field Explanations:
- Step & Counter: Defines the sequence of lines and sub-sequencing of condition types.
- From / To: Defines the start and end steps for the logic of a calculation (e.g., skill discount step 20 calculates customers from step 10).
- Manual: Prevents automatic operation; the condition must be input manually in VA01.
- Required: If this type of condition is not present, the order cannot be saved.
- Statistical: Calculated value for reporting that does not impact the net order value (e.g., VPRS Cost).
- Subtotal: Assigns step result to the system structure field (e.g., Subtotal A populates KOMP-CMPRE for credit management checks).
- Requirement (Reqm): ABAP routines (e.g., routine 2) ensure an item discount is only calculated when the line item is relevant for pricing.
3. Follow the Pricing Procedure (Transaction OVKK)
| Customer | Material | Amount | Unit | Valid To |
|---|---|---|---|---|
| 1000042 | MAT-A100 | 150.00 | USD | 31.12.2026 |
Transaction VK11: Condition Master Data Record
The purpose of reporting this transaction is focused around scenarios where automatically populating prices fails in VA01.
To capture and analyze this data, start by opening the Sales Order. Click the button on the bottom left of the screen, 'Analysis'. This will open the pricing tree on the left.
Review the search log. SAP provides step-by-step Access Sequence usage, tables checked, and the reason for bypassing a search record (e.g., 'Condition record exists but validity date does not match' or 'Requirement 002 not met').
EVRPVITS: Redefining SAP Career Pathways
One of the more complex SAP SD interview topics involves using the Conditions technique. Domain expertise in designing prices and having in-depth knowledge of S/4HANA Settlement Management (Contracts) and Condition Contracts are highly appreciated by Functional Leads.
ERPVITS has pioneered hands-on, industry-aligned online SAP SD Training for all working professionals and enthusiastic learners.
- Real-time Access to S/4HANA Servers: Create and validate complex configurations in the real world of enterprise IT.
- Industry-Based Instructors: Our instructors are senior SAP architects offering global implementation services.
- Complete Curriculum: Integrate SAP SD with all business processes (MM, FI, and FSCM) across on-premises SAP innovations.
- Career Support Services: Assistance with resume development, practice real-time SAP interview preparations, and SAP certification exams.
Get started on your SAP career path. Check out the available cohorts, and reserve your spot for a live demo at ERPVITS!
FAQs
1. What is the relationship between Condition Type and Condition Records?
A Condition Type is an object used in configuration via V/06 to define a pricing element and how it behaves (e.g. calculation including rules or manual access control). A Condition Record is the master data that consists of prices, rates or percentage values that are defined for specific combinations (e.g., Material A is priced at $100).
2. What is the function of the 'Exclusive' Logical Grouping Indicator in an Access Sequence?
At step level in an Access Sequence (V/07), if the Exclusive checkbox is ticked, SAP will exit the condition record search for the respective table. In case this checkbox is unchecked, SAP continues to evaluate the subsequent steps for values.
3. How does the SAP SD pricing interface with accounts in FI General Ledger?
The pricing steps in the Pricing Procedure assign an Account Key (for example, ERL for gross revenue, ERS for discounts). For the Sales Organization, Account Assignment Group, and Chart of Accounts, the assignment of Account Keys to General Ledger accounts is done in transaction VKOA.
4. Which transaction can be used to address pricing issues in a sales order?
While in transaction VA02 the Analysis button on the Item Pricing tab is available to view search logs, ABAP developers can debug custom pricing routines (Requirements or Formulas) by placing breakpoints in the program RV61AFZA or function module PRICING_CUSTOMIZING.