CA01 — Create Routing for Production Operations
CA01 creates a routing (task list) that defines the operations, work centers, and standard values needed to manufacture a material. The routing itself is identified by a group and group counter, independent of any material; the material is linked to it separately through a task list-material allocation, which is the source of most confusion about why a routing does not show up on an order.
CA01 is the create transaction for standard routings in Production Planning, used to define operation sequences, work centers, and standard values before production orders can be released. This page covers the header/group structure, the tables the save populates, and the diagnostic sequence for the recurring failure where an order cannot find or selects the wrong routing.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,202 words
Purpose
CA01 creates a routing, also called a task list, which lists the operations required to produce a material along with the work center, control key, and standard values (time, quantity) for each step. The structural fact that trips up most consultants coming from a BOM background is that a routing is not keyed by material. It is keyed by a plan group and group counter. The material is attached afterward through a separate allocation record, which means one routing group can legitimately serve several materials, and a single material can have several competing routings distinguished by usage, status, and lot-size validity. Confusion during order creation almost always traces back to this separation, not to the operation data itself.
When it is used
CA01 is used during production engineering setup, after the BOM exists and before the first production or process order is created against the material. It is the natural companion to CS01 for the same material and plant: the BOM says what goes in, the routing says how it gets made and what it costs to make. Consultants reach for CA01 specifically to create a brand-new routing; CA02 is used to change an existing one and CA03 to display it read-only. In S/4HANA, Fiori apps exist for browsing and reporting on routings, but the bulk of routing creation and detailed operation maintenance in most implementations still happens through this transaction or its equivalents for rate routings and reference operation sets.
How to use it in practice
- Start CA01 and enter material, plant, and a key date, or go directly to a group and group counter if creating a routing not yet tied to a material.
- On the header screen, set routing usage, status, and the lot-size validity range (from-to quantity) that governs when this routing is eligible for selection.
- Move to the operation overview and add operations in sequence, each with a control key, work center, and standard values for setup, machine, and labor time.
- Maintain alternative or parallel sequences if the process branches, and assign components to specific operations if backflush or phase-based issue is required.
- Confirm the material assignment (or add additional materials to the same group if the routing is shared).
- Save. The system assigns the group and group counter if this is a new routing.
Key data objects
- PLKO - routing header: group, group counter, usage, status, lot-size validity range, planner group.
- PLPO - operation details: work center, control key, standard value fields, base quantity, formulas.
- PLFL - sequence relationships when alternative or parallel sequences exist between operations.
- MAPL - task list allocation: the link between the routing (group/counter) and the material and plant, including priority and validity dates.
- PLMZ - assignment of BOM components to specific operations, used when components are issued or backflushed at the operation level rather than at order header level.
How to prove it in the data
Start in MAPL filtered on material and plant to find the plan group, group counter, and priority for every routing allocated to that material. Note the validity dates and status there. Take the group and counter into PLKO to check usage, status, and lot-size validity range. Take the same key into PLPO to list the operations, work centers, and control keys in sequence. If more than one row comes back from MAPL for the same material and plant with overlapping validity, that is the ambiguity the order creation logic is struggling with.
ECC vs S/4HANA
CA01 and its underlying tables (PLKO, PLPO, PLFL, MAPL, PLMZ) are unchanged in structure on S/4HANA; the transaction still runs in SAP GUI and is still the primary route for detailed routing creation in most implementations. Fiori apps exist for routing overview and reporting, giving a more readable, filterable view of existing routings, but they are largely read-oriented rather than full replacements for the creation screens. No renaming or data model consolidation happened here as part of the S/4 move.
Common pitfalls and how to diagnose them
- Routing not found at order creation: the order type looks for a routing matching a specific usage code and a released status. Check MAPL for the allocation and PLKO for status; a routing sitting in 'created' or 'locked' status, or carrying the wrong usage code for that order type, will simply be invisible to CO01/CO02.
- Wrong routing selected among several valid ones: when MAPL has multiple rows for the same material and plant, the system picks by priority and lot-size range. Check the priority field first, then check whether the order quantity falls inside the lot-size validity of the routing you expected; if it falls outside, a lower-priority or unwanted routing wins instead.
- Lot-size mismatch causing manual assignment: if the order quantity does not fall inside any routing's lot-size range, the system either defaults to the first available routing or forces manual selection, which is often mistaken for a missing routing entirely.
- Costing or confirmation errors traced to the operation, not the header: a work center not extended to the order's plant, or a control key not flagged for costing/confirmation, produces errors during order release or settlement that look like a routing problem but are actually a work center master data problem. Check CR03 for the work center's plant extension before touching the routing.
- Component issue behaves unexpectedly: if PLMZ assignments are missing, components intended for operation-level backflush get issued at the order header instead, which shows up later as a goods movement discrepancy rather than a routing error at creation time.
- Engineering change number confusion: a routing maintained under a change number with a future validity date will not appear on orders created today; check the change number's valid-from date before assuming the routing itself is broken.
Whose problem this is
Functional problem, owned by the PP or process engineering master data team that maintains routings alongside BOMs. ABAP involvement is rare and limited to custom checks on save (user exits or BAdIs on the routing). A clean handover states material, plant, routing group and counter, usage code, order type involved, and whether the issue is at order creation, costing, or confirmation, with the MAPL/PLKO/PLPO extract attached rather than a screenshot alone.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ca01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.