SAP S/4HANA SD Simplification List: What You Need to Know
If you’re planning a conversion from SAP ECC to S/4HANA, the Sales & Distribution module has some of the most impactful simplification items you’ll encounter. The official Simplification List for SAP S/4HANA 2023 (FPS 1-3) contains 16 SD-specific items spanning data model changes, removed functionality, and replaced solutions.
This post breaks down the key items every SD consultant and developer should understand before, during, and after conversion.
1. SD Data Model Simplification (VBUK/VBUP Elimination)
SAP Note: 2267306 | This is arguably the most significant SD change in S/4HANA.
SAP has eliminated the status tables VBUK (document header status) and VBUP (document item status). Status fields have been moved directly into the document tables:
- VBAK/VBAP for sales documents
- LIKP/LIPS for deliveries
- VBRK for billing documents
Why this matters
In ECC, querying a sales order with its status required joining VBAK with VBUK. In S/4HANA, a single SELECT on VBAK returns everything. This is a direct benefit of SAP HANA’s in-memory architecture — aggregate and index tables are no longer needed.
Additionally, the document index tables VAKPA, VAPMA, VLKPA, VLPMA, VRKPA, VRPMA have been eliminated as redundant.
What you must do
If you have append structures on VBUK or VBUP with custom fields (Z* or Y* namespace), you must add those fields to the corresponding status include structures (VBAK_STATUS, VBAP_STATUS, LIKP_STATUS, LIPS_STATUS, VBRK_STATUS) during the ACT_UPG phase. The automatic data migration will then transfer your custom field data correctly.
Any custom ABAP code that reads directly from VBUK/VBUP must be adapted. Refer to SAP Note 2198647 for the detailed cookbook.
2. Pricing Data Model Changes (KONV to PRCD_ELEMENTS)
SAP Note: 2267308 | Another major data model change that affects virtually every SD implementation.
The pricing result table KONV has been replaced by PRCD_ELEMENTS for data persistence. Key improvements include:
- Direct analytical access to pricing results (no more cluster tables)
- Extended field lengths: condition counter (ZAEHK) from 2 to 3 digits, access sequence entries from 99 to 999
- Customer/document pricing procedure classification extended from CHAR1 to CHAR2
- Condition table keys can now be 255 characters (previously 100)
- The concatenated key field VAKEY has been removed from condition header tables (KONH, NACH, etc.)
What you must do
If you have append structures on KONV, add those fields to PRCS_ELEMENTS_DATA during the ACT_UPG phase. Follow SAP Notes 2188695, 2189301, and 2220005 carefully.
Run the post-processing report PRC_MIG_POST_PROCESSING after conversion to properly fill the document currency field in PRCD_ELEMENTS.
3. SD Rebate Processing Replaced by Settlement Management
SAP Note: 2267377 | SD Rebate Processing is not available in S/4HANA.
The successor is Settlement Management (Condition Contract Settlement), which provides:
- Single point of entry for contract-related conditions
- Flexible data sources and business selection criteria
- Settlement calendar with streamlined contract processing
- Overview of actual business volume including retroactive contracts
Key migration points
- Existing rebate agreements can only be processed until their validity end date
- New agreements must be created as condition contracts
- Transaction VBO1 (Create Rebate Agreement) is no longer available
- Exception: CRM TPM customers can still use SD Rebate Processing (SAP Note 2267344), but this right expires with ECC standard/extended maintenance
Check table KONA with ABTYP = 'A' to determine if your system uses SD Rebate Processing.
4. Credit Management Migration (FI-AR-CR to FIN-FSCM-CR)
SAP Note: 2270544 | Classic Credit Management (FI-AR-CR) is not available in S/4HANA.
The successor SAP Credit Management (FIN-FSCM-CR) offers:
- Automatic calculation of credit scores, risk classes, and credit limits
- Credit events for exception-based management
- Case Management for documented credit decisions
- Higher/lower account relationships for business partners
Key transaction replacements
| ECC Transaction | S/4HANA Replacement | Purpose |
|---|---|---|
| FD32 | UKM_BP | Credit account master data |
| VKM1 | UKM_MY_DCDS | Release blocked sales orders |
| VKM2-5 | UKM_MY_DCDS | SD document processing |
| F.31-F.34 | SAP Credit Management reports | Credit management overview |
Migration scope
You must migrate configuration data, master data, credit exposure data, and credit decision data. SAP provides migration tools in the IMG. Note that the credit limit check types A, B, and C are no longer available — only type D is supported.
5. Foreign Trade (SD-FT) Removed
SAP Note: 2267310 | Foreign Trade functionality (SD-FT) is not available in S/4HANA.
The successor is SAP S/4HANA for international trade (embedded) combined with SAP GTS (side-by-side). This affects:
- Intrastat reporting — replaced by simplified selection reports with multi-user support
- Legal Control — replaced by Trade Compliance Documents
- Classification — enhanced with time-dependent, cross-plant commodity codes
- Preference Management — available via SAP GTS
- Letter of Credit — replaced by Trade Finance integration
Over 100 transactions are removed, including the entire VE*, VI*, VX* transaction families for foreign trade processing.
6. Billing Document Output Management
SAP Note: 2790427 | S/4HANA introduces a new output management framework called SAP S/4HANA output control, while the legacy NAST-based output remains available as default.
You can choose between them via Customizing: SPRO > Cross-Application Components > Output Control > Manage Application Object Type Activation.
Important: The new output control does not support NAST transmission mediums 8 (Special function), 9 (Events/Workflow), A (ALE Distribution), or T (Tasks/Workflow). If you use these, stick with NAST-based output.
7. Revenue Recognition Replaced by RAR
SAP Note: 2267342 | ERP SD Revenue Recognition is not available in S/4HANA. The successor is SAP Revenue Accounting and Reporting (RAR), which supports IFRS 15 compliance.
Transactions VF42-VF48 and OVACT/OVEP are all removed. All active sales orders and contracts using SD Revenue Recognition must be migrated to RAR before conversion.
8. Removed Functionality Summary
Several other SD features are no longer available:
| Feature | SAP Note | Successor |
|---|---|---|
| Internal Sales Representative (ISR) role | 2271150 | SAP Fiori role SAP_BR_INTERNAL_SALES_REP |
| Internet Sales / Web Channel | 2271161 | SAP Commerce Cloud (formerly hybris) |
| Sales Activities (SD-CAS) | 2267375 | SAP CRM on-premise or SAP Cloud for Customer |
| Industry-specific Complaint Handling | 2267398 | Standard SD complaints (CMP_PROCESSING) |
| SD Analytics based on LIS | 2267348 | Embedded Analytics / CDS views |
Practical Conversion Checklist
Here’s a prioritized checklist for your S/4HANA SD conversion:
- Run the Simplification Item Check via the Readiness Check or Maintenance Planner to identify which items affect your system
- Analyze custom code — run the Custom Code Migration Worklist to find direct reads on VBUK, VBUP, KONV, VBFA, and other changed tables
- Inventory append structures on VBUK, VBUP, and KONV — plan the migration to status includes and PRCS_ELEMENTS_DATA
- Assess Credit Management — determine if you’re on FI-AR-CR, FIN-FSCM-CR, or both, and plan migration accordingly
- Evaluate rebate processing — plan the move from SD Rebates to Settlement Management
- Review Foreign Trade processes — coordinate with SAP GTS team if applicable
- Migrate SD Revenue Recognition to RAR before conversion
- Test output management — decide between NAST and S/4HANA output control for billing documents
Conclusion
The SD simplification items in S/4HANA are extensive but well-documented. The data model changes (VBUK/VBUP elimination and KONV to PRCD_ELEMENTS) deliver real performance benefits, while the functional replacements (Credit Management, Rebates, Foreign Trade) modernize processes that were long overdue for an overhaul.
The key to a smooth conversion is early analysis. Run the Readiness Check, inventory your custom code, and plan your migration activities well before the technical conversion begins.
Reference: SAP S/4HANA 2023 Simplification List (Document Version 1.35, February 2025)