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

SD / O2Cintermediate

S/4HANA SD Part 2: Choosing and Sequencing a Migration Approach

Key takeaway

Compare new implementation, system conversion and selective data transition from an SD perspective: impact on processes, history, custom code and organizational structure, how to sequence SD-specific preparations (BP/CVI, open documents, rebates, credit, output), and cutover considerations.

Explanation

📌 KEY POINTS
✅ New implementation: redesign processes, migrate master data and open items (e.g. with the migration cockpit) — no history.
✅ System conversion: keep configuration, history and custom code; adapt to simplification items.
✅ Selective data transition: combine redesign with selected data/history (e.g. per company code).
✅ SD preparation items: BP/CVI, open orders/deliveries/billing, rebates, credit data, output, revenue recognition.
⚠️ Choosing conversion to "save time" while processes need redesign moves problems into S/4HANA.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 listed what changes. Now how to get there.

━━━━━━━━━━━━━━━━━━━━
▶ 1. NEW IMPLEMENTATION

Standard-based redesign, clean data.
Migrate BPs, materials, prices, open orders/items.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SYSTEM CONVERSION

Technical conversion with preparation (CVI, custom code, simplification items).
History retained.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SELECTIVE DATA TRANSITION

Shell/mix approaches; selected org units and history.

━━━━━━━━━━━━━━━━━━━━
▶ 4. SD PREPARATION

CVI and BP cleanup, closing old documents, rebate settlement or migration, credit data, output strategy, RAR.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CUTOVER

Open documents, pricing and credit data, blocked documents, output switch.

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

Evaluate process fit and data needs.
Choose approach with business and IT.
Plan SD preparation items.
Rehearse cutover.

✅ CHECKPOINT: the chosen approach is justified by process, data and custom code needs, not only by timeline.

Code example

ABAP Code

===== STEP 1: comparison =====New implementation : redesign, no history, migration cockpit for master/open dataSystem conversion  : keep config/history, fix simplification items, adapt custom codeSelective          : mix, per org unit or time slice ===== STEP 2: SD preparation checklist =====CVI/BP | close old open documents | rebates settle or migrate | credit data → BP | output strategy | revenue recognition → RAR

Real project scenario

A mid-size discrete manufacturer with heavy SD customizations wanted a quick conversion. Analysis showed most custom code compensated for poor process design that S/4HANA standard (aATP, settlement management) now covered. The company chose a selective approach: new processes in SD with migrated history for finance, reducing custom code by 60%.

Common mistakes

Choosing by timeline only.
Underestimating CVI.
Leaving open documents unmanaged.
Ignoring rebates/credit replacements.
No cutover rehearsal.

Best practices

Evaluate approaches with facts.
Start CVI early.
Clean open documents.
Plan replacements as workstreams.
Rehearse cutover.

Interview angle

Questions: "Greenfield vs brownfield for SD?", "What SD items must be prepared for conversion?", "How do you handle open documents?"
Strong answer: approach comparison with process/data/custom code criteria, SD preparation (CVI, open docs, rebates, credit, output, RAR), cutover planning.

Practice this lesson

Quick check

1. Which migration approach keeps configuration, history and custom code?

2. During production readiness for S/4HANA SD Transformation, Migration, Public Cloud and Architecture, the team is validating Choosing and Sequencing an S/4HANA SD Migration Approach: New Implementation vs System Conversion vs Selective Data Transition. Given the scenario "A distribution company on ECC with private cloud target decides on system conversion because they have extensive custom pricing routines tied to rebate agreements they are not ready to redesign", which choice best prevents a repeat failure?

3. Learn how SD-relevant decisions differ across the three main S/4HANA migration approaches, what to validate during each, and how integration and cutover risks show up specifically in sales processes. A production team now has to make a design decision in Choosing and Sequencing an S/4HANA SD Migration Approach: New Implementation vs System Conversion vs Selective Data Transition. Which option best preserves reliability and supportability?

Interview questions

1. A global template rollout requires migrating sales data (open orders, contracts) for a new country while ensuring output management triggers correctly for the migrated documents, and these documents must also feed PP for make-to-order scenarios. What migration sequencing and validation steps would you follow?

Answer it in your own words first, then compare.

2. During cutover for sales data migration, you discover that several customer master records were converted to Business Partners but their corresponding MM info records and purchasing views are inconsistent, causing intercompany sales order creation to fail. What is your troubleshooting approach?