SD Pricing Part 10: Enterprise Pricing Architecture — Governance, Extensibility and S/4HANA Migration

📌 KEY POINTS
✅ Pricing architecture = few procedures, a catalogue of condition types with owners, a clear price hierarchy, and governed extensions.
✅ Record ownership and data processes (price approval, upload, validity) matter as much as configuration.
✅ Extensions (new fields, routines, BAdIs) must be registered, reviewed and performance-tested.
✅ S/4HANA changes: document conditions in PRCD_ELEMENTS (not KONV), SD rebates replaced by condition contracts in settlement management, extended field lengths.
⚠️ Legacy pricing migrated 1:1 carries years of unused condition types, tables and routines into the new system.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–9 covered the technique end to end. This part is the enterprise design view.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PROCEDURE STRATEGY

• Few procedures: domestic, export, intercompany, special (e.g. rebate-relevant or free goods variants).
• Country differences via condition types/records, not separate procedures, where possible.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONDITION TYPE CATALOGUE

• Each type: purpose, class, calculation, access sequence, owner, account key.
• Clear price hierarchy (contract price > customer price > list price > base price).

━━━━━━━━━━━━━━━━━━━━
▶ 3. EXTENSIBILITY GOVERNANCE

• Field catalog extensions only with business case.
• Routine register (VOFM 9xx) and BAdI inventory with performance tests.
• Prefer standard features before code.

━━━━━━━━━━━━━━━━━━━━
▶ 4. INTEGRATION

• CRM/CPQ or e-commerce pricing: decide system of record and synchronization (API, IDoc).
• Rebates: S/4HANA uses condition contract settlement (Settlement Management).
• Analytics: pricing elements from PRCD_ELEMENTS via CDS views.

━━━━━━━━━━━━━━━━━━━━
▶ 5. MIGRATION

• Inventory legacy procedures, condition types, tables, routines, usage.
• Rationalize; migrate only valid, future-relevant condition records.
• Convert rebate agreements to condition contracts.
• Regression test pricing with real order samples before cutover.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Build the condition type catalogue and price hierarchy.
2. Reduce procedures to the needed set.
3. Register extensions; retire unused ones.
4. Define record ownership and processes.
5. Plan migration with rationalization and sample-based regression.

✅ CHECKPOINT: any price on any order can be explained from the catalogue and hierarchy without reading code.

A global manufacturer entered its S/4HANA migration with 23 pricing procedures, 140 condition types and 60 custom routines accumulated over 15 years. The architect ran a usage analysis on two years of documents: 60% of condition types had no values in recent orders. The target design had 5 procedures and 38 condition types with a catalogue and owners; rebate agreements were converted to condition contracts. Pricing regression tests with 5,000 real orders from each country confirmed identical net values within tolerance before cutover.

• Migrating legacy pricing 1:1.
• Creating procedures per country instead of per business pattern.
• Extensions without registry or performance tests.
• No owner for condition records.
• Ignoring rebate conversion to condition contracts in S/4HANA.

• Keep few procedures and a documented condition type catalogue.
• Define a price hierarchy with business.
• Govern extensions like code.
• Assign record ownership and data processes.
• Rationalize and regression-test pricing during migration.

Questions: "How would you design pricing for a global template?", "What changes in pricing with S/4HANA?", "How do you migrate pricing?"
Strong answer: few procedures, condition type catalogue with owners, price hierarchy, governed extensions; S/4HANA PRCD_ELEMENTS, condition contract settlement instead of SD rebates, CDS analytics; migration with usage-based rationalization, record cleanup and sample-based regression testing.