MTS 202 ยท OBJECT MODEL
How does availability check turn general stock into a customer promise?
In Make to Stock, forecast demand replenishes general stock before a customer is known. When a sales order arrives, availability checking evaluates the supply picture and writes a confirmed quantity and date to the schedule line.
THE DEFINING CONTROL
Availability check is the promise engine; forecast consumption protects the demand signal
ATP or advanced ATP checks the stock and receipt elements included by the checking group, checking rule, and scope of check. Separately, consumption reduces relevant planned independent requirements so the sales order does not duplicate forecast demand. Transfer of requirements can still expose unconfirmed sales demand to planning, but it is not the availability check itself.
CONTROL LAYERS
One customer request, four connected layers
The promise is explainable only when demand policy, ATP scope, confirmation, and fulfilment remain connected.
Strategy and consumption
Strategy group, requirements type, PIR version, consumption mode, and consumption periods define how forecast and sales demand coexist.
General stock and receipts
ATP considers the stock, planned receipts, and issues selected by checking group, checking rule, and scope of check.
Schedule-line confirmation
Requested quantity and date are checked; confirmed quantity and date are stored at schedule-line level and may change after rescheduling or backorder processing.
Delivery and goods issue
Confirmed schedule lines become delivery-relevant. Picking and post goods issue reduce the common stock that supported the promise.
SYSTEM BEHAVIOR
How MTS converts forecast supply into a promise
Forecasting, replenishment, availability, and fulfilment are related controls with different owners and evidence.
Create forecast demand
PIRs express expected demand and MRP proposes replenishment into general stock.
Recognize the sales order
The sales order consumes applicable PIRs so expected and actual demand are not planned twice.
Calculate availability
ATP nets included stock and time-phased receipts against included requirements and determines confirmation.
Deliver from common stock
The confirmed order is delivered from the shared inventory pool and goods issue updates availability.
DIAGNOSTIC EVIDENCE
Diagnose the control that owns the result
A missing confirmation can originate in demand configuration, ATP scope, an absent receipt, competing requirements, allocation, or delivery scheduling. Inspect the evidence in that order instead of treating every shortage as an MRP failure.
Material strategy group, PIR version and dates, requirements type, consumption mode, consumed and unconsumed forecast quantities.
Checking group, checking rule, scope of check, stock/requirements list, ATP elements, product allocation or backorder result, requested and confirmed schedule-line quantities and dates.
Delivery relevance, delivery quantity, picking status, goods issue, material document, remaining stock, and updated confirmation.
PROJECT MOMENT
Forecast exists, but the promise comes from availability
A fan forecast drives production into unrestricted stock. A June sales order consumes the June PIR, while ATP confirms the customer from current stock plus receipts included in the scope of check. The delivery then issues from general stock.
- PIR consumption is visible
- ATP elements explain the date
- Schedule-line confirmation matches the check
- Delivery and stock movement reconcile
Connect this object model to execution, accounting impact, and exception handling.