O2C 606 · PRODUCTION SUPPORT
How do you support Order to Cash when something goes wrong?
Restore the customer-order flow while identifying exactly where the O2C chain broke and why. Use the customer, material, order, delivery, billing document, and accounting evidence to find the first incorrect decision—not merely the last visible error.
O2C DOCUMENT CHAIN
Trace the transaction across commercial, logistics, and financial evidence
A billing, accounting, or collection symptom can originate in the sales order or delivery. Equally, a sales-order block can be an intended credit control. Follow the actual chain and status relationship before changing a rule.
- 01Customer demandIntent
- 02Sales orderCommitment
- 03ConfirmationPromise
- 04Delivery / PGIFulfilment
- 05Billing / FIAccounting
- 06Receivable / paymentSettlement
SUPPORT OPERATING LOOP
Use the same evidence discipline for every O2C incident
Establish business impact
Identify the customer, material, sales order, delivery, invoice, sales organization, plant, market, scope, urgency, process stage, and recent change. Preserve a reproducible example.
Find the failed transition
Locate the last successful O2C document or status, then the failing hand-off and observed message. A delivery failure often starts in the order or schedule line.
Choose the right cause family
Separate transaction data, customer or material master data, configuration, custom logic, integration, authorization, jobs, locks, and operating procedure.
Correct the owning layer
Fix one document when the transaction is exceptional; fix master data, configuration, code, or an interface only when that layer consistently caused the behavior.
Retest end to end
Validate customer, material, quantity, price, promised date, delivery, inventory, billing value, tax, revenue, receivable, and document flow.
Make recurrence visible
Capture symptom, scope, root cause, resolution, validation, and prevention. Turn recurring incidents into data validation, monitoring, tests, guidance, or controls.
FIRST O2C DECISION
Diagnose the specific failure pattern
Start with the issue the business sees, then follow its O2C determination path. These are operational playbooks—not generic system troubleshooting.
Move backward from delivery, PGI, billing, accounting, or payment until the last correct document and status are clear.
Ask what rule produced the result: pricing condition, ATP scope, credit rule, delivery relevance, copy control, or account determination.
Credit, delivery, billing, incompletion, ATP, and authorization stops can be correct controls rather than defects.
O2C DIAGNOSTIC PLAYBOOKS
Follow the path that matches the failing business step
Each case identifies the document relationship and determination evidence that must be understood before correction.
01 · Sales order cannot be created
Trace: Customer → sales area → material sales data → partner → item category → schedule line. Confirm that customer and material are valid for the required organization and transaction.
02 · Price is wrong
Trace: Sales order → pricing procedure → condition type → access sequence → condition record → calculation. Check pricing date, quantity, currency, unit, manual conditions, exclusions, and requirements.
03 · Quantity or date is not confirmed
Trace: Order → schedule line → plant → ATP rule → stock and supply → competing demand → confirmation. Explain the promise; do not force confirmation without evidence.
04 · Order is credit blocked
Trace: Customer or credit account → exposure → limit → risk rule → order → credit check → block. Confirm whether the exposure and rule are correct before treating the block as an error.
05 · Delivery cannot be created
Trace: Order → item category → schedule line → confirmed quantity → delivery relevance → due date → shipping point → blocks or incompletion. Find the first eligibility condition that fails.
06 · PGI cannot be posted
Trace: Delivery → picked quantity → stock → storage location → movement → inventory posting → accounting. Check picking, stock, batch or serial data, periods, movement control, and account determination.
07 · Billing cannot be created
Trace: Sales order or delivery → billing relevance → billing due status → billing type → copy control → pricing → billing document. Check PGI, blocks, dates, and upstream incompletion.
08 · Accounting document is wrong
Trace: Billing document → pricing condition → account key → account determination → G/L → accounting document. Check revenue, discount, freight, tax, reconciliation account, and organization criteria.
09 · Customer payment is not clearing
Trace: Billing → customer open item → payment → reference and amount → matching → clearing. Classify missing payment, mismatch, deduction, partial payment, residual item, or wrong customer assignment.
O2C SUPPORT MOMENT
The sales order exists but delivery cannot be created
Check the item and schedule line first: confirmed quantity, requested and due date, delivery block, credit status, shipping point, incompletion, and document status. The delivery screen may show the problem, while the cause is an earlier sales-order decision.
- Record the known-good step and failing transition.
- Preserve the message, statuses, master data, and expected result before changing anything.
- Correct only the layer that owns the first incorrect decision.
REUSABLE O2C SUPPORT PATTERNS
Keep the process distinctions clear
- 01Document inherited wrong data?Symptom
- 02Check master dataSource
- 03Result determined by a rule?Logic
- 04Trace determinationEvidence
- 05Stop is intentional?Control
- 06Validate the controlProof
Use 101 for process language, 202 for individual capabilities, 303 for the operating day, 404 for determination and configuration, and 505 for implementation context.