CRCA table — Work Center Capacity Category Assignment Table

One row in CRCA represents the assignment of a single capacity category to a capacity-relevant object, most commonly a work center. When a work center is created or changed on the capacity header tab in CR01 or CR02, each capacity category defined there, typically machine, labour and setup, gets its own capacity header record in KAKO, and CRCA is the join record that ties that KAKO entry back to the work center. A single work center normally produces several CRCA rows, not one, because each category is a separate capacity object with its own interval and shift data. The row also carries a usage indicator that tells the system whether that particular capacity assignment is relevant for scheduling, capacity planning, or costing.

CRCA is client-dependent and physically small compared to movement or requirement tables, but it should never be read unrestricted because it covers every capacity-relevant object in the client, not just work centers. Always restrict on OBJTY and OBJID, resolved first from CRHD by plant and work center code, since OBJID itself is an internal number with no business meaning. Do not filter on VERWE as if it were a plant or category label; it is a usage flag with a small fixed value range and needs to be checked against its domain, not guessed. Exclude rows with LOEKZ set if the question is about currently active capacity assignments, but do not assume every deleted assignment is physically removed.

Symptom: a work center's requirements do not show up in capacity evaluation even though the routing clearly references it. Look up the work center in CRHD by plant and work center code to get OBJID, then select CRCA where OBJTY matches the work center object type and OBJID equals that value. If no row carries a VERWE relevant to capacity planning, or the relevant row has LOEKZ set, the capacity category needed for evaluation was removed or deactivated on the work center's capacity header tab, and that, not a scheduling or DS integration issue, is the root cause.

CRCA is retained in S/4HANA and continues to be maintained through the same work center transactions and the capacity header tab in CR01, CR02 and CR03. Classic capacity planning based on CRHD, CRCA, KAKO and KAZY has not been restructured in the way that some logistics document tables were, since work center master data and capacity assignment remain part of the core production planning model rather than the redesigned document layer. No compatibility view replacing CRCA is generally required because the table shape and usage are unchanged.

This is a production planning master data question, owned by whoever maintains work centers, since the rows are a direct side effect of what is configured on the capacity header tab. Capacity planning key users get involved when the question is about whether a category is actually being evaluated, but the fix, if there is one, is made in the work center master, not by touching the table directly.

CRHD holds the work center header that CRCA points back to, CRTX carries the readable work center description, KAKO and KAZY hold the actual capacity numbers behind each CRCA row, and CRCO handles the separate cost center assignment for the same work center. All of these are maintained together through CR01, CR02 and CR03, so a change on any tab of the work center master can touch several of these tables in a single save.