Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Creating production orders

10 min

Listen to this lesson

0:00 / 5:59

A production order is the instruction to make a specific quantity of a product by a specific date, in a specific way. MRP does not create production orders. It creates planned orders, which are proposals: nobody can issue stock to them or confirm work against them. A production planner turns a proposal into an executable order by converting it, or creates an order manually when there is no proposal.

At Contoso Motor Co., MRP in plant 1710 Detroit has proposed a planned order for 200 alternators (CMC-ALT-100) to cover a replenishment requirement. The planner reviews it in the stock/requirements list (MD04) or the Fiori material coverage apps, then converts it to a production order of order type PP01, the standard production order type in many systems.

  1. DemandPlanned independent requirements or sales orders for CMC-ALT-100
  2. MRP runCreates a planned order for 200 pc in plant 1710 with dependent requirements for components
  3. ConversionPlanner converts the planned order; the planned order disappears and a production order takes its place
  4. Production orderOrder type PP01, status CRTD, with components, operations, dates and planned costs
  5. ReleaseCovered in the next lesson; until then nothing can be issued, confirmed or received
From MRP proposal to production order.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-204

Ways to create an order

MethodWhereWhen to use it
Convert one planned orderCO40, or from MD04 / the material coverage appsThe planner wants to review each proposal before it becomes firm
Convert planned orders collectivelyCO41Many proposals for a production line or MRP controller at once
Partial conversionFrom the planned orderConvert part of the quantity now and leave the rest as a proposal
Create manuallyCO01 or the Fiori production order appsRework, trial runs or demand that MRP has not planned

Conversion and creation options. Names of Fiori apps vary by release; check the SAP Fiori apps reference library for yours.

Conversion copies the planned order's quantity, dates and production version into the order. Creating an order manually asks you for material, plant, order type and quantity, and the system then reads master data itself. Either way, the order is firm: MRP will not change it or delete it the next time it runs, which is why planners convert only what they are ready to build.

Every route to a production order ends in a firm document MRP will not touch; only partial conversion leaves part of the proposal for MRP to keep adjusting.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-204

What the order copies from master data

When the order is created, SAP S/4HANA selects the production version, which points to one bill of material (BOM) and one routing. It explodes the BOM into a component list and copies the routing into operations, each assigned to a work center. It then schedules the operations and, if the order type is set up for it, calculates planned costs and creates a settlement rule.

HeaderMaterial CMC-ALT-100, plant 1710, quantity 200 pc, basic dates, order type PP01, statuses
Operations0010 Stator winding at WIND-10 · 0020 Final assembly at ASSY-10 · 0030 End-of-line test at TEST-10
ComponentsRotor CMC-RTR-200, stator CMC-STA-300 and housing CMC-HSG-400, each assigned to the operation that consumes it
CostsPlanned costs from the BOM and routing at standard prices and activity rates
Settlement ruleReceiver: the material, so variances settle to inventory or price-difference accounts at period end
The layers of a Contoso production order. Work center and stator/housing numbers are fictional examples.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-204

Each component is linked to the operation where it is consumed: the stator goes to stator winding, the rotor and housing to final assembly. That link matters later, because backflushing posts consumption when the operation that uses the component is confirmed.

Inside the order, each component reservation hangs off the operation that consumes it, which is what lets backflushing post at the right confirmation.
The Sign-Off Table · thesignofftable.com/academy/sap-pp-204

If the component list or operations look wrong, the cause is almost always master data: a BOM with the wrong validity date, a routing without the new work center, or a production version that points to an old BOM. Changing the order by hand fixes this order only. Fix the master data too, or the next order will carry the same error.

What would you do?

Grace asks why the Detroit planner converted only 120 of the 200 alternators on the planned order. What is the most likely reason?

In the Fiori launchpad, supervisors work with apps such as Manage Production Orders and Manage Production Operations, which list orders and operations with their issues (missing parts, delays) and let them release, reschedule or confirm. In SAP S/4HANA Cloud Public Edition these apps are the way to work; SAP GUI transactions such as CO01, CO40 and CO41 exist only in on-premise and Private Edition.

Key points
  • MRP creates planned orders; production needs a production order before anything can be posted.
  • Convert one planned order (CO40), many (CO41), part of one, or create an order manually (CO01).
  • The order copies BOM and routing through the production version into components and operations.
  • A created order is firm: MRP no longer changes it, so convert only what you are ready to build.

Check your understanding · not graded

Lesson check

  1. 1. What happens to a planned order when it is fully converted?

  2. 2. Which object tells the order which BOM and routing to use?

  3. 3. Why is each component assigned to an operation?

  4. 4. What makes a converted production order different from the planned order it came from?