Atlas Diagnostic
SAP sales order block diagnosis
A first-pass structure for finding why an order is stopped before delivery, billing, or completion.
Core idea
A blocked sales order is a symptom, not a root cause. The block may be intentional control, incomplete master data, credit exposure, delivery constraints, billing relevance, compliance logic, or custom governance.
The support goal is to identify which control is active and whether it is working as designed.
First split
- Incomplete order: required fields are missing or inconsistent.
- Credit or risk control: release requires commercial or finance review.
- Delivery block: fulfillment is prevented until a condition is cleared.
- Billing block: billing is prevented while delivery or order handling may continue.
- Master data issue: customer, material, partner, plant, shipping, or pricing data does not support the transaction.
- Custom rule: enhancement, workflow, interface, or compliance logic applies in this landscape.
Evidence to collect
A good diagnostic note should capture order number, item, block type, user-visible message, customer, material, sales area, requested delivery date, credit status if relevant, and the business reason the user expected the order to continue.
Retail-specific: ATP mismatch
In retail and omnichannel environments, ATP checks often aggregate inventory across DCs and eligible stores. A mismatch occurs when the system shows stock as available but the assigned fulfillment location cannot actually deliver.
- Check ATP scope of check: confirm whether the ATP configuration includes the store or DC that is being used for fulfillment. A store may be excluded from the scope.
- Check inventory accuracy: the location may show system stock that does not match physical stock due to shrinkage, unrecorded damage, or cycle count delays.
- Check reservation timeout: online orders often create a temporary reservation at the fulfillment location. If the reservation expires before picking is complete, the stock may be sold to another channel.
- Check store receiving backlog: goods may have arrived at the store but not yet been posted as goods receipt, so ATP does not see them.
A useful ATP mismatch ticket should include: order number, material, the location that was checked, the location assigned for fulfillment, current system stock at that location, and whether the issue is recurring for this product or location.
Support takeaway
Do not release blocks blindly. A block is often the only visible control protecting delivery, finance, compliance, or customer communication. Diagnose the control first, then decide whether to correct master data, change configuration, release the order, or escalate the business rule.
Next diagnostic steps
- Order to Cash Map — use this map to see how the sales order block fits into the wider order-to-cash process.
- SAP Delivery Block Analysis — go here when the order can proceed but delivery creation is stopped.
- SAP Billing Block Analysis — use this when the order or delivery is blocked from billing.
- SAP Credit Management Diagnostics — check this if the block reason points to credit exposure or risk control.
Practical checklist
-
Collect order number, item, block reason code, and exact user message. Synthetic example: order 1234567890, item 10, block “Credit check”.
-
Check VA02/VA03 block reason and incompletion log for the order and item.
-
Confirm whether the block is header-level, item-level, credit-related, or manual.
-
Document the business reason the user expected the order to continue and who can approve release.
-
Verify authorization to release the block in SU53 before attempting removal.
-
Safety limit: do not release credit or compliance blocks without written approval from the owning team.