Pricing and the Condition Technique
The condition technique in five parts
Pricing is configuration found by a search, not code:
- Condition table - the key fields of a condition record (customer, material, sales organization, and so on).
- Access sequence - the ordered list of tables searched until a record is found; individual accesses can be flagged exclusive.
- Condition type - the calculation rule (percentage, fixed amount, quantity-dependent), the condition class, plus/minus sign, scales, and whether it is statistical.
- Pricing procedure - the ordered steps of condition types with from/to levels, subtotal lines, requirements and alternatives.
- Pricing procedure determination - sales area + customer pricing procedure (from the customer master) + document pricing procedure (from the sales document type).
Condition records are maintained with VK11 or the Manage Prices – Sales app and are valid for a period; the pricing date decides which records apply. Condition exclusion groups let the system keep only the best or cheapest of competing conditions. Condition supplements let a procedure fall back to another condition type when a record is missing.
Traps
- Statistical conditions (such as VPRS, the cost) appear in the procedure but never change the net value.
- Header conditions are calculated once for the whole document; item conditions are calculated per item.
- Deleting a condition record does not reprice existing documents; a new pricing run is required.
- Condition types that are inactive or blocked by a requirement silently produce no value.
Rule of thumb - debug in this order
Is the condition type in the procedure? Was the procedure found using the sales area and both pricing procedures? Does a condition record exist and is it valid on the pricing date? Does the access sequence actually reach that table? Is the step deactivated or excluded?