Advanced SD Scenarios, Integration and Production Support

SD / O2Cintermediate

Advanced SD Scenarios Part 2: Mapping Configuration, Document Flow and Integration Architecture

Key takeaway

Build an integration map for SD: which configuration objects control each step, which documents are created in SD, MM and FI, which interfaces (IDoc, APIs, GTS, EWM, carriers) are involved, and how to use the map for design reviews, testing and production support.

Explanation

📌 KEY POINTS
✅ An integration map shows per process step: controlling configuration, documents created, postings and interfaces.
✅ It supports design reviews (gaps), test design (end-to-end cases) and support (where to look).
✅ Interfaces (IDoc/API to EWM, GTS, carriers, EDI partners, e-invoicing) need monitoring and ownership.
✅ Keep the map current as a living document per scenario.
⚠️ Undocumented integrations turn every incident into an investigation from scratch.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 explained why integration and support matter. Now building the map.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PROCESS STEPS

Order → ATP/credit → delivery → picking/PGI → billing → FI → payment.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONFIGURATION PER STEP

Document/item/schedule line types, copy control, determinations.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DOCUMENTS AND POSTINGS

SD documents, material documents, accounting documents per step.

━━━━━━━━━━━━━━━━━━━━
▶ 4. INTERFACES

EWM (deliveries/tasks), GTS (compliance), EDI (orders, ASN, invoices), carriers, e-invoicing.
Monitoring tools and owners.

━━━━━━━━━━━━━━━━━━━━
▶ 5. USING THE MAP

Design reviews, test scripts, support runbooks.

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

Draw the map for a standard order.
Add one special scenario (e.g. third-party).
Add interfaces and monitoring.

✅ CHECKPOINT: for any failure, the map tells you which configuration, document or interface to check.

Code example

ABAP Code

===== STEP 1: map excerpt =====Step         | Config                        | Documents          | Interfaces/monitorOrder        | VOV8, VOV7, OVKK, credit      | sales order         | EDI ORDERS (WE02)Delivery     | VTLA, route, shipping point   | delivery            | EWM (queues)PGI          | movement type (VOV6)          | material + FI doc   | –Billing      | VTFL, VKOA, output            | invoice + FI doc    | INVOIC / e-invoiceCompliance   | GTS integration               | block/release       | GTS status ===== STEP 2: usage =====Design review checklist | end-to-end test cases | support runbook sections per step

Real project scenario

A retail distribution company running a hybrid landscape (S/4HANA, external WMS, EDI hub) had long incident resolution times because nobody knew which system owned which step. Building an integration map with monitors and owners per interface cut average resolution time by half.

Common mistakes

No integration documentation.
Interfaces without owners.
Tests covering only SD steps.
Outdated maps.
No monitoring per interface.

Best practices

Maintain a living integration map.
Assign owners and monitors.
Derive tests from the map.
Update with every change.
Use it in onboarding.

Interview angle

Questions: "How would you document SD integration?", "Which interfaces does O2C typically have?", "How does the map help support?"
Strong answer: per-step configuration, documents, postings, interfaces with monitoring and owners; used for design reviews, tests and runbooks.

Practice this lesson

Quick check

1. Which document is created at post goods issue in a standard O2C flow?

2. An intermediate-level architectural map connecting sales document configuration, document flow control, and the key integration handoffs to FI, MM, and logistics execution that underpin advanced SD scenarios and production support work. A production team now has to make a design decision in Mapping the Configuration, Document Flow and Integration Architecture. Which option best preserves reliability and supportability?

3. A hybrid landscape (S/4HANA, external WMS, EDI hub) has slow incident resolution. What helps most?

Interview questions

1. You are designing copy control for a complex order-to-cash flow involving variant-configured materials where sales orders are decoupled from deliveries via EWM, and configuration data must remain consistent from order through delivery and billing. What copy control considerations are critical?

Answer it in your own words first, then compare.

2. In an intercompany sales process, explain how billing between the selling company code and the delivering plant's company code is triggered, and which documents are generated.