What happens to SAP pricing and KONV when you move to S/4HANA?
The condition technique carries over. The custom code that reads KONV directly is the part that breaks quietly.
The short answer
In S/4HANA the condition technique itself survives: condition types, access sequences, pricing procedures and condition master records work the way your team already knows. What changes is where document-level pricing results are stored. The ECC table KONV, which held the calculated conditions for sales orders, billing documents and purchasing documents, is replaced by PRCD_ELEMENTS, and several fields in the pricing data model were changed or extended. Configuration largely carries over in a system conversion, but every custom report, exit, interface and pricing routine that reads KONV directly has to be found and adapted, and that custom code, not the configuration, is where the migration risk sits.
What actually changes in the pricing data model?
Pricing in SAP has two layers. The first is configuration and master data: condition types, access sequences, condition tables, pricing procedures and the condition records your pricing team maintains. The second is the result: the list of conditions calculated for a specific document, stored per item. In ECC that result lived in KONV.
S/4HANA keeps the first layer and moves the second. Document conditions are stored in PRCD_ELEMENTS, and SAP lists the change as a simplification item, with some fields adjusted or extended in length along the way. For the business user, a sales order prices the same way. For anything that reaches into the database directly, the ground has moved.
Why is custom code the real risk?
Twenty years of ECC tend to accumulate KONV reads in places nobody remembers: margin reports, commission calculations, rebate extracts, pricing outputs, interfaces that send net price to a warehouse or a customer portal, and user exits that inspect conditions before saving an order. Each one was written against KONV, and each one needs to be checked and rewritten against the new model or against the APIs and views SAP provides for it.
The danger is that some of these fail loudly and some do not. A syntax error in a sandbox conversion is easy to catch. A report that runs cleanly but returns incomplete conditions, or an interface that sends a price with the wrong precision because of a changed field length, can pass a shallow test and surface weeks after go-live as a margin or invoicing question.
- Direct SELECTs on KONV in custom programs, function modules and classes.
- Pricing-related user exits, including the sales order and billing exits that inspect or modify conditions.
- Custom pricing requirements and formulas (VOFM routines) that assume the ECC structures.
- Interfaces and extracts that pass condition values to external systems or a data warehouse.
How should you find and triage the affected objects?
Start with the evidence, not a questionnaire. Run the simplification item check and the ABAP Test Cockpit with the S/4HANA readiness checks, which flag objects that use KONV and other changed structures. Pair that with usage data from the production system, because a large share of flagged custom code is often never executed, and retiring it is cheaper than fixing it.
For what remains, read the business rule behind the code before you decide anything. A custom pricing report may be replaceable by standard S/4HANA analytics; a commission calculation may belong side-by-side rather than in the core; a pricing exit may encode a policy that standard condition types can now express. Those are fit-to-standard decisions, and they are the ones that move a clean core score.
What does the configuration side still need?
Configuration usually converts, but it should not be waved through. Pricing procedures built up over many years often contain inactive steps, condition types nobody posts, and statistical conditions added for a report that was retired long ago. A conversion is the moment to rationalize them, because every unnecessary step is one more thing to regression test.
Where the target includes changes to pricing customizing, those changes should travel through normal customizing transports and your change board. Our own approach to agent-assisted configuration follows the same rule: the agent drafts a governed customizing transport in a development system, the change board decides whether it lands, and nothing touches production on its own.
How do you prove pricing still works after conversion?
Price comparison is the most convincing test you can run. Take a representative sample of real orders and billing documents across customer groups, sales organizations, currencies and condition types, re-price them in the converted system, and compare net values, taxes, freight and rebate accruals line by line against ECC. Differences should be explained one by one, not averaged away.
Write the acceptance criteria before the test cycle starts: which document types, which tolerance, who signs off. Pricing defects cost real money and customer trust, so this is one area where finance and sales should own the definition of done, with IT supplying the evidence.
Frequently asked
Do our condition records and pricing procedures need to be rebuilt in S/4HANA?
Not in a system conversion. Condition tables, access sequences, pricing procedures and condition master records carry over; the change is in how document-level results are stored. It is still worth rationalizing unused condition types and procedure steps, because they add test scope without adding value.
Can custom code keep reading KONV after the conversion?
You should not plan on it. Document conditions are stored in PRCD_ELEMENTS in S/4HANA, so code that reads KONV directly has to be adapted to the new model or to the access methods SAP documents for it. Check the current SAP Notes for the simplification item on your target release before choosing the remediation pattern.
How long does pricing remediation usually take?
It depends almost entirely on how much custom code touches pricing and how much of it is still used. An estate with a few dozen active KONV reads is a contained work package; one where pricing logic is spread across exits, reports and interfaces needs dedicated analysis and a full price-comparison test cycle. Measuring that from the system early is what keeps it off the critical path.
See your own Clean Core Score.
Run the free S/4 readiness scan in under a minute — no system access required.
Keep reading