Order Management
The Order Management domain tests order capture through fulfillment: order structure, pricing, processing constraints, holds, orchestration, shipping, and returns. Questions often hinge on how one order line becomes several fulfillment lines.
Order structure
- An order header contains order lines; each order line can split into multiple fulfillment lines for partial shipments, different warehouses, or different supply sources.
- Processing constraints block or warn on actions such as cancel or change; hold codes pause fulfillment without deleting the order.
Pricing and orchestration
- Pricing strategies apply price lists and discounts through qualification and precedence rules.
- Orchestration processes define fulfillment steps such as reservation, shipping, and invoicing, and can invoke Supply Chain Orchestration for back-to-back or drop-ship supply.
Fulfillment
- Shipment sets, pick waves, packing, and ship confirm move the order to shipped status.
- Ship confirm reduces on-hand inventory and feeds costing; invoicing flows through the Receivables interface.
Worked example: A customer orders 10 units of item A. The default warehouse has 4 on hand. The orchestration process creates one fulfillment line for 4 units from inventory and, because the item is back-to-back enabled, a second fulfillment line for 6 units linked to a purchase order. A volume pricing strategy applies a 5% discount because the order qualifies. The reasoning is that fulfillment lines, not order lines, drive supply and shipping, and pricing is evaluated by strategy precedence.
Traps: treating processing constraints as pricing rules; assuming a hold cancels the order; confusing order lines with fulfillment lines; forgetting that pricing strategy precedence must be defined; assuming ship confirm posts directly to the general ledger.