SD / O2Cintermediate

SD Output Management Part 4: Output Design for Orders, Deliveries and Invoices

Key takeaway

Design output per SD document: order confirmations and change notices, delivery notes, picking lists and labels, invoices, credit memos and EDI messages — who receives what, when, through which channel — and how to avoid duplicates, missing output and inconsistent layouts.

Explanation

📌 KEY POINTS
✅ Each document needs a defined set of outputs: who (partner), what (form/message), when (timing), how (channel).
✅ Order confirmations may need change output rules (resend only on relevant changes).
✅ Delivery outputs serve warehouse (picking list), carrier (labels) and customer (delivery note, DESADV).
✅ Billing outputs must match legal requirements (invoice, credit memo, e-invoicing).
⚠️ Undefined repeat-output rules send customers duplicate confirmations or invoices.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 2–3 covered both frameworks. Now designing the output landscape per document.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SALES ORDER

Order confirmation to sold-to (print/email/EDI ORDRSP).
Change confirmation only for relevant changes (dates, quantities, prices).

━━━━━━━━━━━━━━━━━━━━
▶ 2. DELIVERY

Picking list to warehouse (or EWM tasks instead).
Delivery note to ship-to, labels (SSCC), DESADV/ASN via EDI.

━━━━━━━━━━━━━━━━━━━━
▶ 3. BILLING

Invoice to bill-to/payer, credit/debit memos.
EDI INVOIC, e-invoice formats, copies for internal archive.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CUSTOMER PREFERENCES

Channel per customer (email, portal, EDI).
Language and number of copies.
Maintained centrally (BP data or determination tables).

━━━━━━━━━━━━━━━━━━━━
▶ 5. RULES

Timing (immediate vs batch).
Repeat output only when needed; archive originals.
Output relevance conditions (e.g. no invoice output for internal customers).

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

Build an output matrix per document type.
Configure determination per framework.
Test changes for repeat behavior.
Validate legal content of invoices per country.

✅ CHECKPOINT: every customer gets exactly the agreed outputs once, through the agreed channel.

Code example

ABAP Code

===== STEP 1: output matrix (example) =====Document  | Output               | Receiver   | Channel        | TimingOrder     | Confirmation         | sold-to SP | email / EDI    | on save, repeat on date/qty changeDelivery  | Delivery note        | ship-to SH | print          | on PGIDelivery  | Label (SSCC)         | carrier    | print (label)  | on packingDelivery  | DESADV               | ship-to    | EDI            | on PGIBilling   | Invoice              | bill-to BP | email / e-inv. | on posting ===== STEP 2: EDI messages =====ORDRSP order response | DESADV dispatch advice | INVOIC invoice

Real project scenario

A retailer received up to four order confirmations per order because every change (including internal text changes) triggered output. The team restricted change output to confirmed date, quantity and price changes, and added an output relevance condition to suppress confirmations for internal replenishment orders. Customer complaints about duplicate mails stopped.

Common mistakes

No output matrix.
Change output on every modification.
Ignoring EDI partners in design.
Different layouts per sales team.
No suppression for internal documents.

Best practices

Define an output matrix with business.
Control repeat output precisely.
Centralize customer channel preferences.
Standardize forms.
Suppress irrelevant output.

Interview angle

Questions: "Which outputs does a delivery need?", "How do you avoid duplicate confirmations?", "How do customer channel preferences work?"
Strong answer: output matrix per document (receiver, form/message, timing, channel), change output rules, delivery outputs for warehouse/carrier/customer, billing legal outputs and EDI, customer preferences and suppression rules.

Practice this lesson

Quick check

1. What is the purpose of an output matrix per document type?

2. Customers receive several order confirmations for small internal changes. How should this be fixed?

3. Which EDI message type is typically used for a dispatch advice to the customer?

Interview questions

1. Shipping point determination is functioning correctly, but for a subset of shipping points routed through a third-party logistics warehouse, shipment notification and packing list outputs are not triggering, so invoices reach the customer before the ASN, causing FI-AR payment disputes. How would you architect a fix connecting shipping point determination with output management and FI-AR timing?

Answer it in your own words first, then compare.

2. A customer requires that route determination results trigger different output types (e.g., different carrier labels) for domestic versus export shipments. How would this integration be designed between route determination and output management?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.