SD: sales, delivery, pricing and billing — Concepts and mental models

Training simulation: All sample identifiers, logs, requests, transactions, values and cases are fictional. Tools and permissions vary by SAP release; perform any changes only in approved DEV/QA environments.

SD: sales, delivery, pricing and billing — Concepts and mental models

Outcome: Trace the business document chain and isolate configuration, master-data and custom-code causes.

Environment: SAP SD sales processes in ECC, S/4HANA private/on-premise and public-edition Fiori alternatives; pricing and ATP configuration vary.

Mental models

1. Understand the boundary

An SD document's lifecycle joins sales order, schedule line, availability, batch determination, picking, goods issue, billing and accounting. The correct investigation starting point is document flow and statuses, not a breakpoint guessed from a message. An order that saves successfully may still be unready for delivery.

2. How this investigation works

Pricing Analysis reveals which condition access was attempted, skipped, excluded or successfully found. Copy control, incompleteness, ATP/aATP, credit, route/shipping point and item category rules decide different transitions. Read business rule and master data before assuming a custom exit.

3. Evidence-based decisions

When a functional check proves the standard process should continue, hand off the smallest reproducible case to ABAP: relevant user exit/BAdI, enhancement switch, active filter and exact field values. Return the fix to SD for end-to-end validation.

Three common false diagnoses

• No delivery can be an expected delivery block, unavailable quantity or schedule-line deficiency rather than a code crash.
• A missing PR00 condition can be an invalid access/condition record, not necessarily VOFM routine failure.
• Creating a billing document does not prove FI transfer succeeded; reconcile downstream accounting status.

Synthetic evidence

SO DEMO-SD-901: material M-TEST, qty 10, delivery date +7 daysSchedule line: confirmed qty 0 | delivery block 'Z1'Batch CHARG: blank | item batch determination required by demo ruleVL01N proposal: nonePricing PR00: valid condition found (unrelated to delivery block)

Diagnostic flow

1. Trace sales order, delivery, billing and status flow
2. Inspect pricing/ATP/credit and copy-control evidence
3. Test corrected determination on representative document

Tools

VA03 · VL03N · VF03 · Document flow · Pricing analysis

Check your understanding

Question: An order has no delivery; schedule line confirmed quantity is 0 and batch block exists. What is the first step?

A. Inspect ATP and block prerequisites separately in document status.
B. Debug VF01 billing immediately.
C. Update LIKP directly.

Correct: A. Multiple business prerequisites must be established before attributing failure to custom code.

Safety: Use standard supported transactions and approved SD customizing; never direct-update core document tables or force PGI to resolve a training scenario.

Synthetic case: A sales order cannot progress to delivery or billing; prices or credit blocks differ.

The featured fictional case has both zero confirmed quantity and a delivery block tied to mandatory batch determination. Both prerequisites must be independently resolved before delivery can be created.

• No delivery can be an expected delivery block, unavailable quantity or schedule-line deficiency rather than a code crash.
• A missing PR00 condition can be an invalid access/condition record, not necessarily VOFM routine failure.
• Creating a billing document does not prove FI transfer succeeded; reconcile downstream accounting status.

Verify stock/ATP and determine permitted batch, then remove a custom block only through the approved business rule. Never directly update VBAP/LIKP/VBEP or status tables in production.

• Positive: Valid stock and valid batch produce one delivery with correct document flow.
• Negative: Missing/expired batch remains blocked with a clear business message.
• Cross-process: A pricing-only condition change does not accidentally clear delivery blocks or bypass credit approval.

Use standard supported transactions and approved SD customizing; never direct-update core document tables or force PGI to resolve a training scenario.

SD debugging questions: incompletion logs, pricing analysis in the condition screen, availability and schedule lines, copy control between documents, output determination, credit blocks and billing errors — always comparing working vs failing documents.