S/4HANA SD Transformation, Migration, Public Cloud and Architecture

SD / O2Cbeginner

S/4HANA SD Part 1: What S/4HANA Changes in Sales and Distribution

Key takeaway

The main S/4HANA changes for SD: business partner as mandatory master data, simplified data model (status and pricing tables), SAP Credit Management, settlement management instead of rebates, new output management, RAR instead of SD revenue recognition, advanced ATP, Fiori apps, and what this means for projects.

Explanation

📌 KEY POINTS
✅ Business partner is the single entry point for customers (customer-vendor integration).
✅ Data model simplified: document status fields moved into header/item tables (VBUK/VBUP removed), pricing results in PRCD_ELEMENTS.
✅ Functional replacements: SAP Credit Management, settlement management (condition contracts), RAR for revenue recognition, output management with BRF+.
✅ Advanced ATP and Fiori apps change availability and user experience.
⚠️ The simplification list defines what must change — ignoring it causes conversion blockers.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: What S/4HANA changes in SD
Part 2: Choosing and sequencing a migration approach

━━━━━━━━━━━━━━━━━━━━
▶ 1. MASTER DATA

Business partner with customer roles; CVI synchronization.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DATA MODEL

Status fields in VBAK/VBAP/LIKP…; PRCD_ELEMENTS replaces KONV.
Custom code reading old tables must be adapted.

━━━━━━━━━━━━━━━━━━━━
▶ 3. FUNCTIONAL REPLACEMENTS

Credit management → SAP Credit Management.
Rebates → settlement management.
SD revenue recognition → RAR.
Output → S/4HANA output management (NAST still possible on-premise).

━━━━━━━━━━━━━━━━━━━━
▶ 4. NEW CAPABILITIES

Advanced ATP (product allocation, BOP), Fiori apps, embedded analytics.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PROJECT IMPACT

Simplification items, custom code adaptation, data migration, training.

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

Review simplification items for SD.
Map each to your current processes.
Plan replacements and custom code changes.

✅ CHECKPOINT: you can list the SD simplification items that affect your system and their replacements.

Code example

ABAP Code

===== STEP 1: key changes =====Customer master → BP (CVI) | VBUK/VBUP → status in VBAK/VBAP | KONV → PRCD_ELEMENTSClassic credit (FD32, VKM1) → SAP Credit Management | Rebates (VBO1) → condition contractsSD revenue recognition (VF44) → RAR | NAST → output management (BRF+, Adobe) ===== STEP 2: tools =====Readiness check | simplification item checks | custom code checks (ATC)

Real project scenario

A distribution company started conversion planning assuming SD would remain "as is". The readiness check showed open rebates, classic credit management, VF44 revenue recognition and custom reports on VBUK. Treating these as separate workstreams with owners prevented late surprises.

Common mistakes

Assuming SD is unchanged.
Ignoring custom code on old tables.
Late BP/CVI preparation.
Forgetting rebates and revenue recognition.
No readiness check.

Best practices

Run readiness checks early.
Plan BP/CVI cleanup.
Handle functional replacements as workstreams.
Adapt custom code with ATC.
Train users on Fiori.

Interview angle

Questions: "What changes in SD with S/4HANA?", "What happens to rebates and credit management?", "What is CVI?"
Strong answer: BP/CVI, data model simplifications, SAP Credit Management, settlement management, RAR, output management, aATP and Fiori; simplification items and custom code impacts.

Practice this lesson

Quick check

1. Which S/4HANA solution replaces classic SD rebate agreements?

2. Which master data object is mandatory for customers in S/4HANA?

3. Interviewers at this level often ask you to explain, in plain business language, why a company would migrate SD to S/4HANA and what functional risks exist. In the S/4HANA SD Transformation, Migration, Public Cloud and Architecture context, which answer shows the strongest practical judgment?

Interview questions

1. During an ECC to S/4HANA conversion, why must every customer and vendor master record be converted into a Business Partner, and what is the role of the Customer/Vendor Integration (CVI) framework in this process?

Answer it in your own words first, then compare.

2. As part of an S/4HANA conversion readiness assessment, several SD-relevant simplification items are flagged, including changes affecting EWM integration for outbound deliveries. How would you approach interface monitoring during the conversion to ensure delivery-related EWM interfaces continue functioning correctly?