Lesson 2 of 6
Release and availability checks
9 min
Listen to this lesson
A created order is a plan. Release turns it into work. Until an order is released, SAP S/4HANA will not let anyone post a goods issue, a confirmation or a goods receipt against it. Release changes the system status from CRTD (created) to REL (released) and, depending on configuration, prints shop papers and sends the order to a manufacturing execution system.
- CreatedCRTDOrder exists; can be changed and rescheduled; no execution postings allowed
- ReleasedRELShop papers can print; goods issue, confirmation and goods receipt are allowed
- Partly confirmedPCNFSome work reported; remaining quantity still open
- ConfirmedCNFAll operations finally confirmed
- DeliveredPDLV → DLVPartially, then fully received into stock
- Technically completeTECOLogistics closed; reservations and capacity requirements removed
How orders get released
- Individually: release one order (or single operations) from the order itself, for example an urgent order.
- Collectively: select many orders by plant, production supervisor, release date or material and release them together, for example in the Manage Production Orders app or the classic mass processing transaction
COHV. - In the background: a scheduled job releases orders whose release date has arrived.
- At creation: some order types are set to release immediately when the order is created or converted.
You can also release single operations rather than the whole order. Releasing the whole order releases all operations; releasing operations follows the operation sequence. Complex orders with long routings sometimes release operation by operation so later steps cannot be reported early.
The availability checks
Before or at release, the system can check whether the order can actually run. There are three checks, each switched on per order type and plant in configuration.
| Check | What it compares | What you see when it fails |
|---|---|---|
| Material availability | Component requirements against available stock and planned receipts, using a checking rule | A missing-parts list and status MSPT (material shortage) |
| Capacity availability | Load from the order's operations against free capacity at each work center | A capacity check log; the order may need rescheduling |
| Production resources/tools | Tools or fixtures needed by operations against their availability | A PRT check log |
Availability checks on production orders.
Configuration also decides what happens when a check fails: release anyway, block release, or let the user decide. That setting is one of the most important things to test, because it decides whether a shortage stops the line before work starts or surfaces later at the workbench.
- Are all components available for the requirement dates?Yes → release · No → next question
- Does configuration allow release with missing parts?No → order stays CRTD with status MSPT; expedite parts · Yes → next question
- Can the line start with what is there?Yes → release; stage what is available and track the shortage · No → hold the order and reschedule
What would you do?
The Detroit supervisor tries to release the order for 200 alternators. The check shows 40 stators (CMC-STA-300) missing; the configuration lets the user decide. A replenishment of stators arrives tomorrow. The first operation, stator winding, needs the stators. What should the supervisor do?
- Release changes CRTD to REL; no goods issue, confirmation or receipt can be posted before it.
- Orders are released individually, collectively, in the background or automatically at creation.
- Material, capacity and PRT checks are configured per order type and plant.
- Test what happens on a failed check: release, block or user decides.
Check your understanding · not graded
Lesson check
1. Which status change does release cause?
2. A material availability check finds a shortage. Which status appears on the order?
3. What decides whether an order with missing parts can still be released?
4. Which statement about committed quantities is true?