Diagnosing Capacity Overload on a Work Centre
Capacity overload on a work centre means the sum of required hours from planned and production orders in a period exceeds the available capacity defined on the work centre. It shows up as red load bars in the planning table or overdue confirmations. Most cases trace to wrong capacity header data, bad formulas on standard values, or scheduling that never runs finite capacity checks, not to an actual shortage of machine hours.
This page covers how a reported capacity overload on a work centre is actually diagnosed: whether it is a master data defect in the capacity header or routing formula, a scheduling customizing gap, or a genuine bottleneck that needs a planning decision rather than a system fix. It gives the check sequence, the branching resolution path, and the reflex fix that hides the problem instead of solving it.
Published 16 Sept 2026· 1,089 words
The business symptom
Production scheduling calls in saying a machine or work group is 'booked solid three weeks out' or that the graphical planning table shows the same work centre red across every period. Shop floor supervisors report they cannot physically fit the confirmed orders into a shift, or that planned start dates keep sliding because the same resource is double-booked. Sometimes it surfaces as MRP proposing dates that operations says are unachievable, or as a scheduler manually splitting an order into two operations just to spread the load. Expediters escalate specific orders as 'stuck behind the bottleneck' even though components and capacity for other resources look fine. Nobody has yet distinguished whether the machine is truly out of hours or whether the system is simply mis-stating how much capacity it has or how much each order actually consumes.
The configuration behind it
- Capacity header on the work centre understated or wrong: shift sequence missing a shift, utilization percentage left at 100 instead of a realistic figure, or available capacity formula referencing the wrong base unit, so the denominator in the load calculation is too small.
- Standard values or the work centre formula for setup or machine time overstated: a formula multiplies by the wrong parameter, or the base quantity on the routing operation does not match the order quantity unit, inflating required capacity far beyond reality.
- One work centre modeled to represent several physical machines or operators as if it were a single resource, so requirements that could run in parallel are summed as if they compete for the same hours.
- Finite scheduling never actually runs: standard MRP and order scheduling by default do infinite scheduling, so overloads are visible in the load report but never trigger a reschedule or a capacity check during order creation or release.
- Factory calendar or shift changes not reflected: a plant shutdown, reduced Saturday shift, or holiday is not updated on the capacity, so available hours drop while requirements stay the same.
- Individual capacity category confusion: labor and machine capacity on the same work centre both marked relevant to scheduling, causing the same operation time to be counted twice against available hours.
- A real bottleneck: order volume genuinely exceeds what the resource can produce in the period, which is a production planning fact, not a data defect.
What to check
- CM01 or the graphical capacity planning table for the plant and work centre to confirm the overload period and its magnitude.
- CR02 to open the work centre and check the capacity header: shift sequence, utilization percentage, available capacity formula, and whether the correct capacity category is flagged relevant to finite scheduling.
- The routing operation feeding the order (via the order or CA03) to check the standard values and the formula assigned for setup, machine, and labor time, and whether the base quantity unit matches the order.
- CM25 or the capacity evaluation to see the requirement breakdown by order, distinguishing whether one large order or many small ones are driving the load.
- Scheduling parameters for the order type (transaction OPU5 or equivalent customizing) to confirm whether finite scheduling and capacity leveling are active or capacity checks are switched off entirely.
- The factory calendar assigned to the work centre to confirm shifts, holidays, and shutdown periods are current.
How to prove it in the data
Run the capacity evaluation for the work centre, plant, and the disputed period, and pull the required versus available capacity per period bucket rather than the cumulative total. Cross-check the required hours against the routing standard values and order quantities for the two or three largest contributing orders; if required hours per order look disproportionate to the produced quantity, the formula or base unit is the defect, not the plant's real throughput.
Resolution path
If the capacity header is wrong, shift missing, utilization percentage incorrect, wrong formula reference, the fix is a master data change in CR02, no transport required, but it must be checked against costing and lead time scheduling since the same capacity feeds those. If the routing standard values or formula are inflating requirements, correcting the routing is also a data fix, but it changes planned lead times and standard cost, so it needs sign-off from both planning and costing before saving. If the work centre is modeled as one resource for multiple physical machines, splitting it into separate work centres with their own capacities is a structural master data project, touching routings, work centre hierarchies, and historical order history, and should be scoped rather than patched. If finite scheduling or capacity checks are simply switched off in the order type or scheduling parameters, turning them on is a configuration change requiring a transport and testing across all order types that use the same scheduling profile. If the overload is real, the resolution is not technical: capacity leveling in CM25 or CM27, adding a shift, subcontracting, or replanning order dates, decided by production planning, not by IT.
The fix people try first (and why it fails)
The first reflex is to raise the available capacity or push the utilization percentage above realistic levels, or to widen the capacity interval, just to turn the red load bars green. This does not add a single physical hour to the machine. Orders still cannot be produced on time, but the planning table now looks clean, so the underlying shortage stops being visible until confirmations are late and the real cause has to be rediscovered under pressure, usually after a shipment has already slipped.
Whose problem this is
The work centre capacity header and routing standard values belong to production planning master data maintenance. Scheduling parameters and finite scheduling activation belong to the PP configuration owner and require change control. The handover note should state the work centre, plant, period of overload, whether the load report shows a data defect or a genuine volume excess, and which orders were used as evidence.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-functional-issues/capacity-overload-on-the-work-centreERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.