ORDER TO CASH · TRACE
How does SAP document flow work?
Document flow is the connected evidence trail that shows how one customer requirement became logistics activity, financial value, and—eventually—cleared cash.
PROCESS ROLE
Document flow is a network of purpose-built records
The sales order, delivery, material document, billing document, and FI document are not sections of one giant record. References and status updates connect documents with different owners, quantities, values, dates, and control responsibilities.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Start from the business question
Choose the customer requirement, delivery, invoice, or accounting item closest to the issue instead of assuming the order is always the best entry point.
Follow predecessors and successors
Copy control, reference fields, material documents, accounting references, and clearing documents connect each part of the story.
Compare planned and actual state
Overall and item statuses distinguish open, partial, complete, blocked, rejected, reversed, and not-yet-due work.
Match quantity, value, and timing
A coherent flow explains what was ordered, confirmed, delivered, posted, billed, paid, reversed, or left open.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Reference creation
Copy requirements, quantity rules, update logic, and reference fields determine whether successors are created and how their relationship is recorded.
Status reliability
Item-level status, rejection, completion rules, blocks, and asynchronous updates must reflect the actual document and interface state.
Correction trace
Cancellations, returns, credit memos, reversals, rebilling, and clearing changes should extend the trail rather than erase the original event.
DIAGNOSTIC EVIDENCE
Use three lenses when a successor looks missing
A missing document is often a symptom. Determine whether the issue is eligibility, execution, or evidence linkage before changing configuration.
Is the item relevant, due, complete enough, unblocked, and within the correct date and organizational selection?
Did the due-list job, user, interface, warehouse step, accounting transfer, or clearing process actually run and succeed?
Was the successor created without the expected reference, summarized elsewhere, reversed, archived, or traced through a subledger document?
PROJECT MOMENT
The invoice is not missing—it is not due
A sales order has a delivery, but PGI is incomplete. Delivery-related billing therefore has no eligible item. The document flow and status explain the absence; creating another invoice rule would treat the symptom.
- Reference chain is intact
- Blocking status is explicit
- Quantity and value agree
- Correction preserves history
See how these module capabilities connect across fulfilment branches, logistics documents, accounting entries, billing, and clearing.