CO01 — Create Production Order

CO01 creates a new production order directly, without a preceding planned order. On save, the system reads the material master, selects a BOM and routing (via the production version or the standard selection ID), explodes both, and writes the result into the order as a fixed set of operations, components, and dates. The structural fact that causes most confusion: this explosion happens once, at creation. The order is a snapshot, not a live pointer to the BOM and routing. If engineering changes the routing or BOM after the order exists, the order keeps the old version until someone opens it in CO02 and runs the explicit recompute function. Consultants who expect automatic propagation of master data changes into open orders are the ones who end up debugging why a corrected component list is not showing up on the shop floor.

CO01 sits at the point in discrete manufacturing where an order is needed but there is no planned order to convert, or the planning result is being bypassed deliberately: a rework order, a one-off repair job, a prototype build, or a test order in a sandbox client. In a normal MRP-driven process, planned orders generated by MD01/MD02 are converted to production orders through the conversion transactions, not created fresh in CO01. Reach for CO01 specifically when someone needs to create an order outside the planning run, or when reproducing an issue that a planner reports and it needs to be isolated from the MRP logic. In S/4HANA, the same manual-creation need is also served by a Fiori app, but CO01 remains the transaction most consultants use for troubleshooting because it exposes every screen and tab the Fiori app abstracts away.

In SE16, pull AUFK filtered on the order number to get the object number and status; cross-check against AFKO on the same order number for basic dates, production version, and BOM/routing group and counter. For component questions, filter AFPO and RESB on the same order number and compare quantities against what the BOM in CS03 shows for the version referenced in AFKO. If the order looks wrong, check whether the production version field in AFKO is blank or points to an alternative the planner did not expect.

CO01 is still available in S/4HANA and the underlying explosion, scheduling, and costing logic are unchanged from ECC. S/4HANA adds a Fiori app for creating production orders that covers the same core fields with a simplified layout; consultants working incidents still tend to reproduce them in CO01 because it shows every tab, including production version and scheduling parameters, that the Fiori app hides behind defaults. No table or field structure behind the order changed with the move to S/4HANA.

This is a PP functional consultant's transaction end to end: material master, BOM, routing, order type customizing, and scheduling parameters all sit in PP configuration. ABAP gets involved only if a user-exit or BAdI on order creation is suspected of altering component or date logic. A good handover includes the order number (or exact material/plant/order type combination if the order never saved), the error message text, and confirmation of whether the same inputs reproduce the issue in a quality system.

CO02 and CO03 are the natural next stops for changing or displaying an order created here, including running the BOM/routing recompute that CO01 will not do automatically. COOIS gives the list-view way to find and filter orders instead of pulling them one at a time. CO11n is where the order's operations get confirmed once released. COR1 is the process-order equivalent of CO01 for process industries, useful to compare when a process manufacturing site reports a similar creation issue.