Open orders¶
Open orders represent incoming, outgoing, transfer, or production commitments that still affect the future. They complement observed inventory and keep the plan from proposing something already contracted or in execution.
Execution against an order is recorded separately in Deliveries. Keeping the order and its delivery lines separate allows the remaining open quantity to be reconciled instead of overwritten.
Firm operational production is maintained in the dedicated Production orders dataset. It identifies routing, bill of materials, planned output, effective output, and completion state rather than an origin-destination commercial flow.
The Order flows area groups distinct physical operations. The selected dataset — purchase, sales, transfer, or delivery — determines the order type; the user does not classify it through free interpretation.
Path in the platform¶
Data > Data Operations > Transactional Data > Orders > Order Flows > Order flows
Grain and key¶
One row represents an order item. The key combines document identifier and item number. If the source system has no item number, use a stable composition that distinguishes material, origin, destination, and date.
Required fields¶
| Logical field | Meaning |
|---|---|
orderId |
Document identifier |
orderItemId |
Line identifier within the document |
materialId |
Material being moved |
quantity |
Quantity still relevant to planning |
uomId |
Quantity unit |
expectedDate |
Expected availability or fulfillment date |
status |
Operational status used to decide whether the line remains open |
Origin and destination are required according to the flow: a purchase needs a destination; a transfer needs both; a sale needs the fulfillment point and the customer or destination when identified.
Optional fields¶
| Logical field | Meaning | Default Value When Not Provided |
|---|---|---|
originLocationId |
Flow origin where applicable | No origin location |
destinationLocationId |
Flow destination where applicable | No destination location |
confirmedDate |
Date confirmed by supplier or operation | expectedDate remains the reference date |
lotId |
Lot assigned to the order | No specific lot reservation |
deliveredQuantity |
Quantity already delivered | No delivered-quantity value |
Dependencies¶
- Materials.
- Locations.
- Units of Measure.
- Transportation network for transfers.
- Production resources and routings for production orders.
- Production orders for firm productive commitments.
- Status and closing rules defined by the source system.
Used by¶
- Supply Planning data model;
- Supply Plan generation and recalculation;
- projected inventory and backlog;
- DRP, Deployment, and Load Building;
- S&OE and Line Sequencing;
- Inventory Policy Optimization;
- service, delay, occupation, and Cost-to-Serve analysis.
- Deliveries, which reduce the open balance and position quantities in picking, transit, or completed.
- Production orders, which enter Supply Planning and Line Sequencing as firm productive commitments.
Validations¶
- origin or destination may be empty only when the selected order type does not require that side of the flow;
- open quantity is calculated only after delivered quantity has been reconciled;
- no duplicate document and item;
- canceled or closed rows excluded according to source rules;
- open quantity equals ordered quantity minus valid deliveries;
- confirmed dates are not replaced by requested dates;
- origin and destination match the flow;
- historical orders are not used as additional demand.