CR03 — Display Work Center Master Data

CR03 shows the master record of a work center: basic data, default values passed to routing operations, capacity categories (machine, labor, setup), scheduling formulas, cost center assignment, and technical data such as usage indicators. The structural fact that explains most confusion is that a work center is not a single flat record but a header (CRHD) with several dependent sub-objects, each with its own validity period. Capacities, cost center links, and formulas can each have a different valid-from date, so a work center that looks fine on the basic data tab can still fail scheduling or costing because one of its dependent objects expired or was never extended. CR03 lets a consultant confirm exactly what is live on a given date, without the risk of accidentally changing it.

CR03 is reached for whenever a production order, routing, or capacity evaluation behaves unexpectedly and the work center is a suspect: scheduling produces zero or absurd durations, a capacity load doesn't show up in leveling, or an order fails to cost because no cost center is found. It sits upstream of CA01/CA02/CA03 (routing) and CO01/CO02/CO03 (order), since both reference the work center by key and plant. A consultant uses CR03 to inspect before escalating a change request through CR02, and uses it instead of the order or routing transaction when the question is specifically about capacity, formula, or cost center configuration rather than the sequence of operations.

In SE16, query CRHD filtered on plant and the work center's object ID to confirm the record exists and its status. Take the object ID into CRCA to list which capacity categories are actually allocated, then follow the capacity category key into KAKO and KAZY to check the interval dates cover the order or requirement date. Separately query CRCO on the same object ID to check the cost center and its valid-from/valid-to; a gap here is the most common cause of costing failures traced back to the work center.

CR03 is unchanged on S/4HANA; the underlying work center master data model was not restructured. A Fiori app for displaying or managing work centers exists as a modern alternative, but the classic transaction remains fully functional and is still the faster path for checking capacity intervals or cost center validity during an incident. Nothing about the diagnostic approach differs between ECC and S/4HANA for this object.

Functional PP ownership for the work center configuration itself; a Controlling colleague should be looped in when the issue is the cost center assignment or its validity, since that touches CO master data conventions. Basis involvement is limited to authorization for CR02 change access. A good handover states the work center key, plant, the exact tab and field where the discrepancy was found, and the order or date the problem was observed against.

CR01 and CR02 are the create and change counterparts and are where any fix identified through CR03 actually gets made. CA01, CA02, and CA03 show how the work center is consumed inside a routing operation, which is the next place to check once the work center itself is confirmed correct. CO01, CO02, and CO03 show the production order side, where a bad work center setup surfaces as a scheduling or costing error.