This article opens a series on SAP S/4HANA supply chain and manufacturing, written from the shop-floor side: planning and production execution, materials and inventory, warehouse management, quality, and the points where production meets costing. I am starting with a hand-over that every manufacturing process goes through and almost nobody documents: the moment a planned order becomes a production order. It looks like a formality, one click in the stock/requirements list, but it is the moment S/4HANA decides which master data the order will live with for the rest of its life, and most "why does my order look like that" questions trace back to it.
Cheap object, expensive object
Planning and execution use different objects on purpose. A planned order is cheap: MRP creates, moves, resizes and deletes it on every run without asking anyone. A production order is expensive: it carries reservations, operations, capacity requirements, a cost estimate and a settlement rule, and once people confirm and issue against it, the system protects it from change. One rule explains almost everything: some data is read fresh at conversion, some is copied from the planned order, and nothing is read again afterwards unless somebody asks for it.
What a planned order actually contains
MRP Live (the Schedule MRP Runs app, classic MD01N) creates a planned order with a short list of content: the quantity from lot sizing, the basic start and finish dates, the production version it selected, the component list, and an opening date. The component list is the part people underestimate. MRP explodes the bill of material during the planning run, through the production version, and stores the result as dependent requirements. In S/4HANA this is not optional: MRP Live selects the BOM only through a production version (C223, or the production versions button in the material master), so a manufactured material without a valid one is planned without its components, and nothing flags that until somebody opens an order.
What the planned order does not contain matters just as much. It has no operations. MRP Live schedules planned orders with basic dates only, from the in-house production time in the material master (the MRP 2 view, or the lot size dependent times in the Work Scheduling view if maintained), plus the floats from the scheduling margin key. It never reads the routing, so it creates no capacity requirements and carries no costs.
Two more fields matter for conversion. The opening date is the basic start minus the opening period from the scheduling margin key: it is the date from which the planner is expected to convert, and collective conversion (CO41) selects planned orders by it. And the planned order has two firming flags, one for the order (quantity and dates) and one for its components; the first is set when you change the order by hand or a planning time fence firms it, the second when you edit its component list. MRP leaves firmed values alone, which is what you want when you meant to firm, and what hurts when a planner moved a date "just to see".
What happens at the moment of conversion
Whether you convert from the Manage Material Coverage app, from the classic stock/requirements list (MD04, then MD14 for one order or MD15 for several), from CO40 and CO41 on the production side, or partially with CO48, the same sequence runs, and its order explains the surprises.
- The order type is determined, from the production scheduling profile in the material's Work Scheduling view if that names one, otherwise from the MRP group or the plant parameters. With it come the order type dependent parameters (
OPL8): costing variants, settlement profile, routing selection. - Header data is copied from the planned order: quantity, basic dates, production version, and the planned order number as a reference.
- The component list is copied, not re-exploded. The dependent requirements of the planned order become the components of the production order, and from them the system creates reservations. The BOM is not read again.
- The routing is read now. This is the one piece of master data that conversion reads fresh: the routing behind the production version is selected, and its operations are copied into the order with their work centres, standard values and control keys.
- The order is scheduled. With operations in place, lead time scheduling runs according to the scheduling parameters for production orders (
OPU3); more on those below. - Capacity requirements are created, if the scheduling parameters say so. This is the first time the order shows up in any capacity evaluation.
- The availability check runs, if the checking control (
OPJK) asks for it at creation; it is configured separately for creation and for release. - The order is costed. Preliminary costing values the components at their planned prices and the operations at the activity rates of their cost centres, and stores the result as the planned costs; the settlement rule is generated at the same time.
- The order is saved with status
CRTD(orRELat once if the production scheduling profile releases on creation). In the stock/requirements list the receipt changes fromPlOrdtoPrdOrd, and the dependent requirements become order reservations.
The components are copied, and that changes how you work
Of all the steps above, the third causes the most trouble. A BOM change lands in three different places depending on timing. An unfirmed planned order picks it up on the next MRP run, because MRP re-explodes it. A planned order with firmed components keeps the old list until someone re-explodes it by hand in the planned order (MD12). And a production order never picks it up on its own: its components are its own data from the moment it was created. The same is true for the routing.
The tool for the production order side is Read PP master data in the order (the Manage Production Orders app, or classic CO02 under Functions). It re-reads BOM and routing, replaces the component list and the operations, and lets you pick a different production version while doing so. It is an all or nothing replacement, and only possible while the order is untouched: once anything has been confirmed or issued against it, you are into manual changes instead. That is why I tell planners to convert as late as the opening period allows. Every day an order spends in status CRTD is a day in which a master data change silently misses it.
The routing is read fresh, and that is why the dates move
The second most common complaint is that "conversion changed my dates". It did, and it was right to. The planned order dates came from the in-house production time in the material master; the production order dates come from the routing. The two stay consistent only if somebody keeps them consistent, which is what the scheduling update from the routing (CA97) is for: it writes the times calculated from the routing back into the material master, so that MRP plans with numbers that resemble what the routing will later produce.
The OPU3 settings decide how the surprise shows. The scheduling type is normally backwards from the basic finish date. With "adjust basic dates" the order header follows the scheduled operation dates; with "do not adjust" it keeps the planned order dates and the operations float inside them, which can hide an operation that ends after the basic finish. And the "start in the past" tolerance is behind the sudden jump: if the backward scheduled start lies further in the past than the tolerance allows, the system switches to forward scheduling from today, and the finish date moves out by the whole lead time. A planned order that sat unconverted past its start date does this every time.
Capacity is the quieter version of the same effect. Planned orders from MRP Live carry no load, so a capacity evaluation shows only the converted orders, and a planner who converts on Monday for the whole week sees the load appear in one jump. If you need load before conversion, plan those materials with embedded PP/DS, which schedules planned orders with real operation times; otherwise convert within the opening period rather than in weekly batches.
What the order is born with
Everything else conversion gives the order is a snapshot too. The reservations exist from creation, but a goods issue to a CRTD order fails because the order is not released, by design. The planned costs reflect the quantity structure and prices at the moment of costing; a component added later shows in the cost analysis only after the order is costed again. And the production version is now fixed in the order: if you wanted the alternative line, the place to change it was the planned order before conversion, or Read PP master data immediately after.
If you come from Dynamics 365
This hand-over is the firming step in D365 Supply Chain Management: firming creates the production order and copies the BOM and route lines into it at that moment, and estimation is where the costs appear. The mistakes are the same on both sides: firm too early and you freeze stale master data, firm too late and you have no load picture.
What goes wrong
- The order has last month's components. The BOM changed after the planning run and nobody re-exploded. Use Read PP master data if the order is untouched; otherwise correct the components by hand and ask why the planned order was converted so early.
- The finish date jumped at conversion. Either the material master times disagree with the routing (run the scheduling update after routing changes) or the planned order start was already in the past and forward scheduling kicked in; the scheduling log of the order shows which.
- Capacity looks empty until the planner converts. Planned orders from MRP Live carry no load. Decide between PP/DS for the bottleneck resources and conversion inside the opening period.
- The wrong production version. MRP picks the first valid production version by number unless a quota arrangement says otherwise. Make the choice in the planned order, not in the production order after the fact.
- Planned orders firmed by habit. A planner who drags dates in the planning list firms every order he touches, and MRP stops moving them. Teach the team what the firming flag means and reset it where it was set by accident.
A routine that keeps the hand-over clean
None of this needs a project; it needs habits. Keep production versions valid for every manufactured material and let MRP select them. Run the scheduling update whenever routings change. Convert within the opening period, not weeks ahead and not in Monday batches. Treat a firmed planned order as a decision, not a side effect. And when a master data change goes live, list the orders in status CRTD for the affected materials and re-read their master data before the shop floor sees them. Do that, and the order the operator opens is the order the planner meant.
Next time I will look at order release: what the REL status actually unlocks, from the availability check and printing to goods movements and confirmations, and why releasing on creation is not always the shortcut it looks like.