This is the second article in my series on SAP S/4HANA supply chain and manufacturing. Last time I followed a planned order through conversion and showed what the production order reads fresh and what it only copies. I ended with an order sitting in status CRTD, fully planned and completely harmless. This time I look at the next click: release. I want to answer two questions that I hear on almost every shop floor. What exactly does the REL status unlock, and why is releasing every order the moment it is created not the shortcut it looks like?
A created order is a plan, a released order is a commitment
An order in CRTD has dates, operations, reservations and planned costs, but nobody can do anything physical with it. You cannot confirm an operation, you cannot issue a component against it, you cannot receive the finished product, and you cannot print the shop floor papers. The system status simply does not allow those business transactions. You can check this yourself in the order header in CO02 or CO03: the status detail screen has a tab that lists every business transaction with a green or red light for the current status combination. I use that tab more than any documentation when someone asks me why a posting is refused.
Release flips those lights. From that moment the order is open for execution, and several things that were waiting for the release start on their own. That second part is the one people forget. Release is not only a permission, it is also a trigger.
How an order gets released
There are more ways than most teams realise, and they do not behave identically:
- Single order. The Release button in the
Manage Production Ordersapp, or the release flag inCO02. The planner sees messages and can react to them. - Collective release. Transaction
CO05Nselects orders by scheduled release date and releases them in one go. Mass processing inCOHVdoes the same with the function Release and can run as a background job with a variant. - Automatic release at creation. The production scheduling profile has an indicator that releases the order as soon as it is saved. The profile is assigned in the Work Scheduling view of the material master or picked up through the production supervisor.
- Operation by operation. You can release single operations instead of the header. The order then shows
PREL, partially released, and only the released operations can be confirmed. Trigger points on an operation can release the following operations when the current one is confirmed, which is a neat way to enforce a sequence.
The scheduled release date deserves a sentence. It is the scheduled start date minus the release period from the scheduling margin key of the material (MRP 2 view). If that period is zero everywhere, CO05N has nothing meaningful to select by, and the team falls back to releasing by feeling. Setting a realistic release period, a day or two for most discrete production, is what turns collective release into a daily routine instead of a judgment call.
What the system checks before it says yes
Release is the second checkpoint in the life of the order, and the checking control for the order type and plant (classic transaction OPJK) has a separate entry for it. Business function 1 is order creation, business function 2 is order release. For each one you decide whether material availability, production resources and tools, and capacity are checked, and what happens when the material check finds a gap.
Two other things can stop a release, and they are less well known:
- User status. If the order type carries a status profile, a user status can forbid the business transaction "release order" until someone sets the next status. This is the clean way to build an approval step, for example for rework orders.
- Settlement rule. The order needs a settlement rule at release at the latest. Normally the default rule in the order type dependent parameters creates it silently. When the default rule is missing or cannot be derived, release fails with a costing message that the planner does not understand and the controller never sees.
The setting that decides what a shortage means
In the checking control, the field for material release has three values, and choosing between them is a process decision more than a configuration detail.
With "user decides", the planner gets a dialog and chooses. That works when a person releases orders one at a time and is of little use for a nightly job. With "release despite missing parts", the order is released and receives the status
MSPT next to REL. With "no release", the order stays in CRTD, also flagged MSPT, and the missing parts information system (CO24) shows what is holding it.
I have a clear preference for anything released in the background: do not release with missing parts unless somebody owns the list of REL MSPT orders every morning. An order that was refused is visible, because it is still on the release list tomorrow. An order that was released with a shortage disappears into execution, the papers reach the line, and the shortage is discovered by the operator who opens the kit.
What REL unlocks
Once the header is released, these become possible:
- Goods issues to the order, whether posted manually or by backflush at confirmation. Technically the reservation items get their "movement allowed" indicator at release, which is why a picker cannot withdraw for a created order even though the reservation exists.
- Confirmations, in
CO11Nfor an operation orCO15for the header, and with them activity postings to the order. - Goods receipt of the finished product.
- Printing of shop floor papers in
CO04N, or automatically if the production scheduling profile says so. - Actual costs. Planned costs exist from creation, but actual debits need a released order, and work in process is only calculated for orders that are released or partially released. For the controller, an order that was never released has no period-end story at all.
What release starts without asking
This is the part that makes early release expensive. Depending on your settings, the release itself can:
- run automatic batch determination for the components, if the production scheduling profile sets it to happen at release;
- create the inspection lot for in-process inspection (inspection type 03), so quality sees a new lot in its worklist;
- print the order papers;
- create purchase requisitions for non-stock components and externally processed operations, if the order is set to generate them from release rather than immediately;
- send a staging request to the warehouse. With embedded EWM this is where the warehouse first hears about the order, and from then on the warehouse can start moving stock to the production supply area.
None of these is wrong. They are simply real work for other departments, and each one is hard to take back.
Why releasing at creation is not a shortcut
The argument for automatic release at creation is always the same: fewer clicks, and nobody has to remember to do it. For short, repetitive orders that start within a day of being created, I agree, and I set it up that way without hesitation. The trouble starts when the same profile is used for orders that are created two or three weeks ahead.
- The availability check answers the wrong question. Checked three weeks before the start, the components are either "available" on the strength of receipts that have not arrived, or missing for reasons that will resolve themselves. Neither result tells you whether the kit will be complete on the day.
- Stock gets taken by the wrong order. A released order can be picked. Warehouses pick what they are allowed to pick, so components leave for an order that starts next month while this week's order waits.
- The order stops listening to master data. As I described last time, a created order can re-read the BOM and routing. A released order cannot; every engineering change after release is a manual change in the order, operation by operation and component by component.
- Batches are chosen too early. Batch determination at release picks from today's stock. By the start date those batches may be consumed, blocked or close to expiry.
- Quality and the warehouse drown in noise. Inspection lots and staging requests for orders that are weeks away fill worklists with items nobody should touch yet.
- Paper goes stale. Printed orders with old quantities and dates are still found on desks long after the order was changed.
Taking a release back is not something to rely on. Where the function to revoke it is available at all, it only works while nothing has been posted or triggered against the order, and by then the papers and the pick list are usually already out.
If you come from Dynamics 365
In Dynamics 365 Supply Chain Management the production order walks through Created, Estimated, Scheduled, Released and Started, and material can only be consumed once the order is started. SAP has no separate start step. REL covers both the release to the floor and the permission to post, which is why the release decision carries more weight here than the similar sounding status does there.
What goes wrong
- Orders in
REL MSPTthat nobody monitors, because release despite missing parts was chosen to keep the nightly job green. - A release period of zero in the scheduling margin key, so collective release by date selects either everything or nothing.
- One production scheduling profile for all materials, with automatic release, printing and batch determination switched on for long lead time orders that did not need any of them yet.
- A release that fails on the settlement rule after an order type was copied without its default rule.
- Partially released orders left in
PRELfor weeks because a trigger point was never reached, with operators unable to confirm the next step. - Operators asking for orders to be released early "so we can book on them", which is usually a sign that the release routine runs too late in the day.
A release routine that holds up
The pattern I come back to is simple. Give materials a release period that matches how far ahead the floor really needs paper and parts. Run collective release once or twice a day for orders whose release date has arrived. In the background, refuse release when parts are missing, and give one named person the missing parts list as a morning task. Keep automatic release at creation for the short-cycle materials where creation and start are practically the same moment, with its own production scheduling profile. And look at the business transaction tab in the status screen before you believe anyone who says the system "should" allow a posting.
Next time I will look at the material availability check inside the production order: checking group, checking rule and scope of check, and why a component that the order shows as committed is not always a component you can put on the line.
In this series: previous article From Planned Order to Production Order: What S/4HANA Reads at Conversion, and What It Just Copies