SD: sales, delivery, pricing and billing — Guided debugger and evidence walkthrough

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 — Guided debugger and evidence walkthrough

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

Prerequisites: SAP SD sales processes in ECC, S/4HANA private/on-premise and public-edition Fiori alternatives; pricing and ATP configuration vary. Work only in approved test systems.

Sample 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)

Six-stage walkthrough

1. Open sales order and document flow to establish last successful lifecycle stage and exact item/schedule-line status.
2. Check delivery block, incompleteness, confirmed quantity, shipping point, route and batch requirement before opening ABAP.
3. Use Pricing Analysis only if pricing is the symptom; record access sequence result, requirements and validity dates.
4. If custom delivery logic is suspected, identify the implemented enhancement via authorized trace or ABAP owner; capture exact input and switch.
5. Correct the actual data/configuration or approved custom check in DEV; verify batch and ATP behavior independently.
6. Create test delivery once, confirm status and downstream billing/FI behavior, then test an intentionally invalid batch.

Evidence observations

1. Confirmed quantity zero and a delivery block are direct blockers; PR00 is present and not causal.
2. Batch blank may matter because a customer-specific rule requires determination before delivery.
3. After controlled correction, a confirmed schedule line and valid batch can progress to delivery.

Alternative hypotheses

• Standard ATP leaves confirmed quantity zero and prevents delivery.
• Configured/custom batch check leaves delivery block active despite a later determination.
• Pricing is missing or invalid and blocks order save before availability.

Regression checks

• 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.

Check your diagnosis

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.