Advanced SD Scenarios, Integration and Production Support

SD / O2Cbeginner

Advanced SD Scenarios Part 1: Why Integration and Support Skills Matter

Key takeaway

An orientation to advanced SD: special business processes (returns, third-party, consignment, intercompany, foreign trade, settlement, revenue recognition), their integration with MM, FI, WM/EWM and external systems, and the support skills — document flow analysis, logs, root cause thinking — that distinguish senior consultants.

Explanation

📌 KEY POINTS
✅ Advanced SD scenarios reuse the same building blocks (document types, item categories, schedule lines, copy control) in special combinations.
✅ Each scenario crosses modules: MM (stock, purchasing), FI (postings), logistics execution, external partners.
✅ Support skills matter as much as configuration: reading document flow, logs, status and determination analyses.
✅ Root cause analysis prevents repeated incidents; workarounds hide design gaps.
⚠️ Debugging code before checking configuration and master data wastes time in most SD incidents.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Why integration and support skills matter
Part 2: Mapping configuration, document flow and integration architecture
Detailed tracks: Returns, Third-Party, Consignment, Intercompany, Advanced Intercompany, Foreign Trade, Settlement, Revenue Recognition.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SPECIAL SCENARIOS

Returns, third-party, consignment, intercompany, foreign trade, rebates/settlement, revenue recognition.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SHARED BUILDING BLOCKS

Order type, item category, schedule line (movement types, purchasing data), copy control, billing relevance.

━━━━━━━━━━━━━━━━━━━━
▶ 3. INTEGRATION POINTS

MM: stock, special stock, PR/PO, invoice verification.
FI: AR, revenue, accruals, intercompany.
External: EDI, GTS, carriers.

━━━━━━━━━━━━━━━━━━━━
▶ 4. SUPPORT SKILLS

Document flow, status, incompletion, determination analyses, logs.
Reproduce, isolate, fix root cause, prevent.

━━━━━━━━━━━━━━━━━━━━
▶ 5. SENIOR MINDSET

Explain business impact; propose design fixes, not only workarounds.

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

Pick a scenario and list its building blocks.
Trace a document flow across modules.
Practice a root cause analysis on a failing case.

✅ CHECKPOINT: you can describe any special scenario as a combination of standard building blocks.

Code example

ABAP Code

===== STEP 1: building blocks per scenario =====Returns: RE / REN / DN (651) | Third-party: TAS / CS (PR, item cat 5) | Consignment: KB/KE/KA/KR, special stock WIntercompany: plant of other company, IV billing, PI01 | Settlement: condition contracts | Rev rec: RAR ===== STEP 2: support toolkit =====Document flow | status overview | incompletion log | pricing/output determination analysis | billing/IDoc logs | application log

Real project scenario

A support team repeatedly fixed stuck consignment issues by manual stock postings. A senior consultant traced the flow and found a copied item category missing special stock W. Fixing configuration and correcting stock ended the recurring tickets, saving hours each week.

Common mistakes

Treating scenarios as unrelated.
Debugging before checking configuration.
Repeated workarounds.
Ignoring cross-module effects.
Not explaining business impact.

Best practices

Learn building blocks deeply.
Use standard analysis tools first.
Fix root causes.
Document scenarios and runbooks.
Communicate impact clearly.

Interview angle

Questions: "How do advanced SD scenarios differ from standard sales?", "What is your approach to a production incident?", "How do you prevent recurring issues?"
Strong answer: same building blocks in special combinations, cross-module integration, analysis toolkit (document flow, logs, determination), root cause and prevention, business impact communication.

Practice this lesson

Quick check

1. Which statement best describes advanced SD scenarios like third-party or consignment?

2. A team proposes debugging ABAP first for every SD incident. What is the better first step?

3. A problem affects only one user while others can process the same document. Where should you look first?

Interview questions

1. During hypercare after go-live, users report that certain materials are unexpectedly blocked from being added to sales orders for specific customers, though pricing works fine. How would you investigate and resolve this as a listing/exclusion issue?

Answer it in your own words first, then compare.

2. You join a support team for a retail distributor with frequent SD incidents in returns, consignment and intercompany. How do you approach incidents and reduce their number?