CR02 — Change Work Center

CR02 changes an existing work center, which is a plant-specific master object holding capacities, scheduling parameters (queue time, move time), default values, formulas for standard value keys, and a cost center assignment used for activity costing. The structural fact behind most confusion: several of these attributes are time-dependent intervals, not single values. Capacity records and cost center assignments each carry a validity period. A change made today does not overwrite history; it either extends an existing interval or requires a new one starting from a chosen date. Consultants who simply edit the current row instead of opening a new validity period end up silently rewriting the past, which then shows up weeks later as a costing or capacity discrepancy on orders that were already settled.

CR02 is used any time an existing work center needs correction after go-live: a shift pattern changes, a cost center is reassigned due to an org restructure, a formula key is fixed, or queue/move time needs tuning to match actual shop floor behaviour. It sits upstream of routing maintenance and order scheduling; the work center itself is maintained once per plant and then referenced by many routings and orders. Consultants reach for CR02 rather than CR01 (create) whenever the work center key already exists, and reach for CA02 instead when the actual operation sequence or standard values on a specific routing need adjusting rather than the work center's own defaults. A Fiori work center app exists for basic list and edit scenarios, but detailed capacity interval and formula work is still typically done in CR02.

Start in SE16 on CRHD filtered by plant and work center to confirm the record and usage indicator exist as expected. Check CRCO for the same work center and read the validity start and end dates against the order or costing date in question; a gap or an unexpected end date there explains a wrong or missing activity price. For capacity issues, pull KAKO for the capacity category and cross-check KAZY intervals against the date the MRP run or capacity evaluation used; an expired interval reads as zero available capacity even though the work center itself looks fine.

The work center object model and its underlying tables are unchanged on S/4HANA. CR02 remains the primary transaction for detailed capacity interval and formula maintenance. A Fiori app is available for browsing and light editing of work centers, but complex capacity or costing validity work is still commonly done through classic CR02, so no functional migration is required for this transaction specifically.

This is primarily a PP functional problem. Cost center and activity type assignments on the Costing tab need sign-off from a CO consultant, since they affect activity pricing and settlement. Basis involvement is limited to authorization objects for plant-specific work center maintenance. A good handover states the plant, work center key, which tab and field changed, the effective date used, and which open orders or routings are affected.

Read CR01 and CR03 alongside this page to understand creation and pure display of the same object, and to compare a suspect record against a known-good one. CA02 is the natural next stop since routing operations reference the work center by key and often explain why a work center change does not appear to take effect. CO02 is useful for checking whether a specific order picked up the corrected capacity or cost center data after the change was saved.