Part 1 - Routings, Operations & Confirmations in Production Planning

Discrete manufacturing in SAP S/4HANA is governed by a tightly coupled set of master data objects — routings, work centers, and production versions — that together determine how production orders are scheduled, executed, costed, and closed. This paper documents the full technical architecture of that system: how routings are structured and linked to bills of material through production versions, how operations and control keys govern scheduling and cost collection, how work centers connect PP execution to CO-PC actual cost accumulation, and how the confirmation event drives goods movements, activity postings, and progressive cost visibility on the production order. The paper also covers capacity requirements planning, mass processing, and the reporting transactions that give planners and controllers real-time insight into order execution. The intended audience is SAP S/4HANA production planners, manufacturing controllers, and solution architects implementing or optimizing discrete manufacturing in S/4HANA.

SAP S/4HANA discrete manufacturing inherits the conceptual architecture of SAP ERP PP but introduces several structural simplifications that have meaningful operational consequences. The most significant is the elimination of all BOM and routing selection methods except selection by production version. In SAP ERP, multiple selection strategies existed on the MRP tab of the material master; in S/4HANA, only production version selection survives — SAP refers to this as simplified sourcing. Every in-house-manufactured material must therefore have at least one production version that explicitly links a BOM and a routing before planned orders or production orders can be created.

A second S/4HANA simplification affects goods movement transactions. The legacy transaction family MB1A, MB1B, MB1C, MB31, and the broader MB0*/MB1* set are deprecated in S/4HANA. MIGO is the required alternative for all inventory postings against production orders. Practitioners migrating from ERP environments or following legacy documentation must account for both of these changes.

A routing defines the ordered sequence of production steps through which a material is transformed from components into a finished or semi-finished product. It is the operational backbone of a production order: when an order is created, the system reads the routing to determine which operations to perform, at which work centers, in which sequence, and at what standard activity quantities. Without a valid routing, neither scheduling nor activity-based cost collection is possible.

The routing header carries data that applies to the entire task list:

• Material and Plant — the material being produced and the plant in which the routing is valid. The plant defaults to all operations but can be overridden at the operation level; all plants in a routing must belong to the same company code.
• Task List Type — for standard discrete manufacturing routings, this is N (Routing). Rate routings (repetitive manufacturing) and master recipes (process industries) use separate task list types.
• Group and Group Counter — the Group identifies routings that contain different production steps for the same material (e.g., a high-efficiency standard method and a lower-efficiency high-demand fallback). The Group Counter uniquely identifies a task list within the group — for example, to distinguish different lot-size ranges for manufacturing the same material. The combination of Group + Group Counter uniquely identifies a task list.
• Usage — assigns the routing to a work area. Setting Usage = 1 (Production) makes the routing available for production order creation, MRP, S&OP, and cost estimates. The system applies task list usage during automatic task list selection at order creation.
• Status — a status of 4 (Released) makes the routing available for production orders; a status of 1 (Being Created) withholds it from order creation.

Routings are time-dependent. The Key Date (Valid From date) entered at routing creation determines when the routing becomes effective. A routing created with a key date of March 2025 will not be available when creating a production order dated January 2025. If no key date is entered, the system assigns the creation date automatically.

Transactions: CA01 (create), CA02 (change), CA03 (display).

The production version is the object that joins a BOM and a routing into a complete manufacturing master data set. Given S/4HANA’s simplified sourcing rule, it is non-negotiable: every in-house-manufactured material must have at least one production version with both a BOM and a routing assigned. For subcontracting, a production version is required but needs only a BOM — no routing, because the subcontracting purchase order carries only the component list provided to the vendor.

The production version carries:

A practical efficiency: multiple materials that follow the same production process can be assigned to a single routing via the Material Assignment function on the routing header. This avoids redundant routing data and reduces database load.

An operation is the smallest schedulable and confirmable unit in a routing. Each operation represents a discrete production step performed at a specific work center. A routing consists of one or more operations that process and assemble BOM items into subassemblies and final assemblies.

Each operation carries standard values defined by the Standard Value Key (SVK) assigned to the work center:

Standard values are defined with a unit of measure and a reference quantity. They drive three downstream calculations simultaneously: scheduling (operation start and finish dates), capacity requirements (work center load), and costing (standard values × activity price = planned operation cost).

The control key assigned to an operation governs its behavior across multiple functional dimensions:

The control key is therefore the primary switch that determines whether an operation participates in scheduling, in costing, in confirmation, or in external procurement — making it one of the most consequential configuration objects in discrete manufacturing.

Sub-operations sit beneath a parent operation within the routing structure, inheriting the parent’s scheduling context while allowing finer-grained decomposition of work. They relate to the parent for both scheduling and costing purposes.

Inspection characteristics can be assigned at the operation level to integrate Quality Management. This embeds quality inspection steps directly in the production process, triggering inspection lots and results recording at the appropriate operation.

The standard sequence is the default linear chain of operations executed one after another in numerical order (0010, 0020, 0030, …). Two additional sequence types extend this baseline:

Parallel sequences allow operations to run concurrently at different work centers — for example, machining a housing while a subassembly is being prepared on a separate line. The scheduling engine calculates total order duration based on the critical path (the longest parallel branch), not the sum of all operations.

Alternative sequences define different production paths for the same material — a primary high-efficiency process and a fallback used during capacity constraints or machine downtime. Only one sequence is executed per production order; selection occurs at order creation or during capacity leveling.

The choice of sequence directly shapes both the scheduled order duration and the distribution of capacity load across work centers.

The work center is the organizational unit at which operations are performed — a machine, a production line, a machine group, or a person. Its master record is structured across several functional areas:

Basic Data defines the work center category and plant assignment. The work center category determines the application areas for which the work center is relevant (production, plant maintenance, etc.).

Default Values carries the defaults that flow into every routing operation assigned to this work center: the control key, the standard value key (SVK), and the units of measure for each standard value.

Scheduling defines the formulas used to convert standard values into scheduled operation duration.

Capacity defines available capacity across capacity categories. The governing formula is:

Available Capacity = Operating Time × Utilization Rate × Number of Resources

The two primary categories in discrete manufacturing are machine capacity and labor capacity.

Costing is the integration point between PP and CO-PC. It requires a validity-dated assignment of one cost center and one or more activity types (e.g., SETUP1, Machine, Labor). The constraint is strict: a work center can be assigned to only one cost center at a time, though one cost center can serve multiple work centers.

When a confirmation is posted against an operation, the system multiplies the confirmed actual activity quantity (e.g., actual machine hours) by the planned activity price maintained in CO for the cost center / activity type combination. This posts a debit to the production order and a credit to the cost center — the mechanism by which shop floor execution translates into financial cost accumulation on the order. The CO team must ensure that cost center / activity type price planning is complete before confirmations are entered, otherwise the system cannot calculate meaningful actual costs.

At period end, if actual costing (Material Ledger) is active, the actual activity price is recalculated and production orders are revalued accordingly.

Transactions: CR01 (create), CR02 (change), CR03 (display).

MRP produces planned orders as proposals carrying planned quantity, dates, and a link to the production version. Conversion to a production order can be executed via:

• CO40 — single planned order conversion
• CO41 — collective conversion
• MD04 (Stock/Requirements List) — inline conversion from the planning view

On conversion, the system explodes the BOM into order components, copies the routing into order operations, calculates planned costs, and generates a settlement rule (typically settling order variances to the material’s inventory account).

Once the order is technically complete, it is settled via KO88 (individual) or CO88 (collective). Settlement clears any WIP balance and posts production variances to CO, completing the financial lifecycle of the order.

flowchart TD
    classDef planning fill:#fff3e0,stroke:#e65100
    classDef execution fill:#e8f5e9,stroke:#2e7d32
    classDef financial fill:#e3f2fd,stroke:#1565c0
    classDef closing fill:#f3e5f5,stroke:#6a1b9a

    MRP["MRP Run<br>(MD01/MD02)"]:::planning
    PLO["Planned Order<br>(CRTD)"]:::planning
    CONV["Convert to Production Order<br>(CO40 / CO41 / MD04)"]:::planning
    ORD["Production Order<br>(CRTD)"]:::execution
    REL["Release Order<br>(CO02)"]:::execution
    GI["Goods Issue — Components<br>(MIGO / Mvt 261)"]:::execution
    OPS["Operation Execution<br>(Shop Floor)"]:::execution
    CONF["Operation Confirmation<br>(CO11N / CO15)"]:::execution
    GR["Goods Receipt — Finished Good<br>(MIGO / Mvt 101)"]:::execution
    TECO["Technical Completion<br>(TECO — CO02)"]:::closing
    SETTLE["Order Settlement<br>(KO88 / CO88)"]:::financial
    CLSD["Order Closed<br>(CLSD)"]:::closing

    MRP --> PLO
    PLO --> CONV
    CONV --> ORD
    ORD --> REL
    REL --> GI
    GI --> OPS
    OPS --> CONF
    CONF --> GR
    GR --> TECO
    TECO --> SETTLE
    SETTLE --> CLSD

CO11N — Operation-Level Confirmation is the primary confirmation transaction for discrete manufacturing. The operator or planner selects the order and operation and enters:

• Yield quantity — successfully produced units at this operation
• Scrap quantity — rejected units
• Rework quantity — units requiring rework
• Actual activity quantities — actual machine hours, labor hours, setup hours (defaulted from routing standard values and adjustable)
• Posting date

CO15 — Order-Level Confirmation confirms the production order at the header level without operation-by-operation detail. It suits environments where operation-level tracking is not operationally required.

A partial confirmation records progress without closing the operation. Each partial posting charges actual activity quantities to the production order and credits the cost center — giving real-time, progressive cost visibility against the planned cost. The operation moves to status PCNF.

Setting the Final Confirmation indicator on CO11N closes the operation (status CNF) and, if configured, triggers automatic goods movements (backflush GI at movement type 261, automatic GR at movement type 101). When all operations reach CNF, the order header status advances to CNF.

When a control key carries the milestone confirmation flag, confirming that operation automatically confirms all preceding unconfirmed operations up to that point. This is used where intermediate operations are not individually tracked on the shop floor — only the milestone requires an explicit confirmation entry.

Scrap is posted by entering a scrap quantity on CO11N. Components and activities consumed to produce scrapped units are charged to the order with no corresponding yield — directly inflating the order’s actual cost and widening the variance at settlement.

Rework is handled via two distinct S/4HANA best-practice scenarios:

BJN — Rework Processing (Stock-Manufactured Material): A dedicated rework production order is created. The process runs: create rework order → goods issue rework components → confirm rework production activities (CO11N) → manage production operations → post goods receipt for rework order (MIGO, movement type 101) → preview goods receipt slip.

BJQ — Rework Processing (Work-in-Process): Rework is handled within the original production order via a reference operation set added to the routing (CA02). The production operator confirms the defect (CO11N), confirms the rework operation (CO11N), and then confirms the subsequent operation including the reworked quantity (CO11N). The reference operation set is removed from the routing after completion (CA02).

COHV (Mass Processing for Production Orders) enables bulk execution of confirmation-related functions across large order populations. Orders are selected by plant, order type, system status, and date range; available actions include mass technical completion, mass release, and mass confirmation. In high-volume discrete manufacturing environments, COHV is the operationally practical alternative to order-by-order processing.

When a production order or planned order exists, the system calculates capacity requirements for each operation by applying the routing’s standard values against the order quantity using the formulas on the work center. These requirements are placed on the work center for the scheduled operation dates, building a load profile across the planning horizon.

Overloaded work centers are addressed through the manual dispatch board (planner-driven rescheduling) or automated leveling (system-driven redistribution within constraints). Both operate in infinite capacity mode within standard MRP/CRP.

For finite scheduling, SAP S/4HANA integrates with PP/DS (Production Planning and Detailed Scheduling), now embedded within S/4HANA. PP/DS applies finite capacity constraints during scheduling, ensuring work center capacity is not exceeded when generating the detailed production schedule. The MRP-based transactions CM01 and CM04 reflect infinite capacity; PP/DS applies the finite layer.

All goods movements posted against a production order — every goods issue (261) and goods receipt (101) — are visible within the order via:

CO03 → More → Documented Goods Movements

Each material document is displayed with quantity, movement type, posting date, and material, giving the planner a complete audit trail of physical inventory activity against the order.

The itemized cost view is accessed via:

CO03 → Costs → Itemization

This displays planned costs (calculated at order creation from BOM quantities × material prices plus routing standard values × activity prices), actual costs (updated progressively with each confirmation and each goods movement), and the variance between them. The cost overview reflects the current state of the order at any point in time — partial confirmations and partial goods issues are reflected immediately.

The confirmation is the primary integration event between PP execution and CO-PC actual cost collection. When CO11N is posted, the system creates a CO document that debits the production order and credits the cost center, based on actual activity quantities × the activity price for the cost center / activity type combination. If the Material Ledger and actual costing are active, the actual activity price is recalculated at period end and production orders are revalued, ensuring that actual — not standard — costs are carried through to inventory valuation.

The discrete manufacturing execution layer in SAP S/4HANA is architected around three interlocking objects: the routing (what work is done and in what sequence), the work center (where it is done and at what cost), and the confirmation (the event that records that it was done and triggers all downstream financial and inventory consequences). The production version is the mandatory link that makes these objects operational — without it, neither planned orders nor production orders can be created in S/4HANA.

Several design principles govern how this system should be implemented and maintained. First, control key configuration is not peripheral — it is the switch that determines whether an operation participates in scheduling, costing, confirmation, and external procurement. Misconfigured control keys are a common root cause of cost collection gaps and scheduling anomalies. Second, the work center costing tab is the physical boundary between PP and CO-PC; CO teams must maintain cost center / activity type price planning before production orders are confirmed, or actual cost accumulation will be meaningless. Third, S/4HANA’s deprecation of legacy goods movement transactions and its mandate for production version selection are not cosmetic changes — they require deliberate remediation for organizations converting from SAP ERP, both in master data completeness (every manufactured material needs a production version) and in user training (MIGO replaces the MB* family throughout).

For organizations running high-volume discrete manufacturing, COHV-based mass processing and milestone confirmation design are not optional enhancements — they are operational necessities that determine whether the system can realistically be confirmed and settled at period end without manual bottlenecks. Capacity Requirements Planning through CM01/CM04 provides the infinite-capacity visibility layer; PP/DS integration extends that into finite scheduling when operational precision demands it.

Taken together, this architecture gives a well-configured S/4HANA environment end-to-end traceability from MRP-generated demand through physical execution to confirmed actual costs on the production order — the foundation on which variance analysis, product cost controlling, and manufacturing performance management are built.