CR01 — Create Work Center
CR01 creates a work center master record in a plant, defining the capacity, scheduling formulas, and cost center assignment that routings and production orders reference. The structural trap is that capacity and costing data live in separate time-dependent segments from the header, so a work center can look active in display while its costing validity period has actually expired or not yet started.
This page covers CR01, the transaction used to create work center master data in Production Planning. It focuses on how the header, capacity, and costing segments interact, why time-dependent validity periods cause errors that look like routing or costing problems, and how to trace a failure back to the correct table.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,203 words
Purpose
CR01 creates a work center master record for a specific plant, capturing the resource that performs operations in a routing: a machine, a labor group, or a combination. The record carries basic data, default values for operations, capacity definitions, scheduling formulas, and a cost center assignment for costing. The structural fact that drives most confusion is that the header (plant, key, category, description) is a single static record, but the capacity and costing information sit in separate time-dependent segments with their own valid-from and valid-to dates. A work center can display normally in CR03 and still fail during order release or costing because the relevant segment's validity window does not cover the order's basic dates.
When it is used
CR01 is used during initial plant build, when commissioning a new machine or labor pool, or during a data migration project ahead of routing creation, since a routing operation cannot reference a work center that does not yet exist. It is also used mid-project when a new resource type is introduced that does not fit any existing work center's category or standard value key. Consultants use CR02 instead once the record exists and only a parameter needs adjusting, and CR03 for read-only investigation. For bulk creation during migration, LSMW or a direct table-driven load is more common than manual CR01 entry screen by screen, though CR01 remains the reference transaction for validating field behavior before scripting a mass load.
How to use it in practice
- Enter the plant and a work center key on the initial screen; the key is entered manually, there is no internal number range by default.
- Select the work center category (for example, a production category) on entry, since this determines which tabs and default views appear afterward.
- Maintain Basic Data: description, person responsible, usage indicators for task list types.
- Maintain Default Values: control key and other operation defaults that routings will inherit unless overridden.
- Maintain Capacities: assign a capacity category, formula, shift definition, and factory calendar.
- Maintain Scheduling: assign the formulas used to calculate setup, processing, and teardown time from standard values.
- Maintain Costing: assign a cost center and activity type or types with an explicit validity period.
- Save; this writes the header, text, capacity, and cost center assignment records in one transaction.
Key data objects
- CRHD - work center header: plant, work center key, category, standard text key, person responsible, deletion flag.
- CRTX - language-dependent work center description texts.
- CRCO - assignment of the work center to a cost center and activity type, carrying its own valid-from and valid-to dates independent of the header.
- KAKO - capacity header segment: capacity category, formula used for available capacity, shift and factory calendar reference.
- PLPOD - default value assignment linking the work center to a task list type for control key defaulting (uncertain on exact table name, verify before quoting to a client).
How to prove it in the data
In SE16 on CRHD, filter by plant and work center to confirm the header exists and check the deletion flag field is blank. Then check CRCO for the same work center key: read the valid-from and valid-to dates on the cost center assignment and compare them against the order's basic start or finish date; if the order date falls outside that window, costing or release will fail even though the header looks fine. Separately check KAKO for a populated formula field; a blank formula there is what produces zero or default durations during scheduling rather than an actual routing defect.
ECC vs S/4HANA
The work center object model is unchanged on S/4HANA; CR01, CR02, and CR03 remain the transactions for creation, change, and display, and the underlying table structure for header, capacity, and cost center assignment is preserved. A Fiori app for managing work centers exists for display and limited editing, but mass creation during migration or project setup is still typically done through the classical transactions or migration tooling rather than the Fiori app.
Common pitfalls and how to diagnose them
- Deletion or validity flag set: the work center header shows a deletion indicator or has passed its overall validity, so new routings or orders referencing it fail while existing ones already saved may continue to function until reprocessed. Check CRHD first, before touching capacity or costing.
- Costing segment gap: CRCO's valid-from/valid-to window does not cover the order's basic dates, usually because the cost center assignment was created later than the work center itself or was end-dated during a reorganization. This produces a costing error that looks like a missing cost center when the cost center itself is perfectly valid.
- Capacity or formula missing: KAKO has no capacity header, or the formula field is blank, so scheduling silently defaults to zero or minimal duration instead of erroring loudly. This surfaces as orders finishing instantly or capacity evaluations showing no load, not as an explicit error message.
- Standard value key mismatch: the standard value key assigned in Basic Data does not match the parameters the routing operation's formula expects, producing a formula-parameter-not-maintained error at costing or scheduling time. Confirm the key on the work center matches what the routing operation was built against before assuming the routing is broken.
- Change not reflected downstream: changing a formula or cost center assignment on an existing work center via CR02 affects future scheduling and costing runs immediately because both read live master data, but it does not retroactively correct cost estimates or confirmations already posted, which is often mistaken for the change not having saved.
- Category mismatch: the work center category chosen at creation restricts which capacity categories and views are available; picking the wrong category early forces a later rebuild rather than a simple field change.
Whose problem this is
Functional PP ownership for the master data setup itself, with CO involvement wherever a cost center or activity type assignment is in question, since costing segment validity is a shared boundary. Basis involvement is limited to authorization or transport issues. A good handover includes the plant, work center key, the exact error message, and the order or routing number that reproduces the failure, not just a description of the symptom.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cr01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.