MAKE TO ORDER · PROMISE
How is a feasible MTO delivery date promised?
The requested date is the customer ask; the confirmed schedule-line date is the system promise. ATP and MRP contribute to one end-to-end story, but they answer different questions.
PROCESS ROLE
Read the promise decision
ATP checks the eligible stock and receipt picture against included requirements to confirm quantity and date. It does not by itself create the production or procurement supply that may later be needed. MRP evaluates planning demand and creates proposals; it can change the supply picture that a later ATP or rescheduling process sees. Delivery scheduling adds material availability, production, loading and goods-issue timing. Product allocation, backorder processing, capacity integration and advanced ATP can be deliberate extensions, but they are not mandatory characteristics of an MTO promise.
DECISION MODEL
Separate the controls that determine the result
Each layer owns a different part of the MTO outcome. Diagnose the layer that made the decision.
ATP scope
Checking group, checking rule, plant, included stocks, receipts, requirements and replenishment lead time determine confirmation.
Scheduling model
Calendars, transit, pick/pack, loading, goods issue, procurement and in-house production times explain the dates.
Optional promise services
Use allocation, backorder processing, aATP or capacity integration only when their business rules are approved and tested.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Capture the customer ask
The schedule line records requested quantity and date.
Calculate ATP confirmation
ATP applies the checking group, rule and scope to eligible stock, receipts and competing requirements.
Build fulfilment dates
Material availability, production, loading and goods-issue dates form the delivery schedule.
Respond to change
Order changes or supply changes can require new MRP proposals, ATP confirmation or approved rescheduling.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
ATP scope
Checking group, checking rule, plant, included stocks, receipts, requirements and replenishment lead time determine confirmation.
Scheduling model
Calendars, transit, pick/pack, loading, goods issue, procurement and in-house production times explain the dates.
Optional promise services
Use allocation, backorder processing, aATP or capacity integration only when their business rules are approved and tested.
DIAGNOSTIC EVIDENCE
What proves the result
Use document, planning, logistics and Finance evidence together; one screen rarely tells the full MTO story.
Requested and confirmed schedule-line quantity/date, checking group/rule, ATP elements and competing requirements.
Material availability, production, loading and goods-issue dates; calendars and lead-time assumptions.
MRP proposals and exception messages, kept distinct from the ATP result.
MTO SCENARIO
Trace one customer requirement
A component shortage moves the confirmed date. ATP shows why the original date cannot be confirmed; MRP then creates or reschedules a customer-specific proposal. A later supply change can improve the confirmation, but the order retains both requested and confirmed evidence.
- ATP result is not called MRP
- Each date has an explanation
- Rescheduling is controlled
See how the customer reference moves across Sales, planning, production, inventory, delivery and Finance.