Capacity Header Configuration and Available Capacity Setup
Learn how to configure the capacity header (capacity category, shift definitions, intervals of capacity, and overload behavior) on a work center so that capacity evaluation, finite scheduling, and MRP capacity checks produce reliable results.
Explanation
Every work center that is meant to be capacity-relevant for detailed scheduling, capacity evaluation, or finite/infinite capacity checks must carry at least one capacity category (typically machine or labor) configured on the Capacities tab. The capacity header stores the base unit of measure for capacity (for example H for hours), the formula that will be used to compute capacity requirements, the shift sequence or grouping (referencing a shift definition maintained in customizing or via a factory calendar), and the available capacity intervals. Available capacity is not a single static number; it is time-phased. A work center can have a base available capacity (e.g., 8 hours/day, 5 days/week) plus intervals with start and end dates that override the base value for known changes such as planned overtime, a second shift added temporarily, machine downtime for maintenance, or a plant shutdown period. Getting this time-phasing correct is essential because capacity evaluation reports (capacity load, capacity leveling) and PP/DS heuristics compare requirements against these intervals, and a wrong interval silently produces incorrect overload or underload signals that planners will not question unless they know to check it. The overload percentage field allows a controlled tolerance above 100 percent utilization before the system flags the work center as overloaded in capacity evaluation transactions; setting this too high hides real bottlenecks, setting it to zero can generate excessive noise for capacities that always run slightly over due to rounding in formula results. The capacity planner group assigned on the capacity header determines which planner is responsible for resolving overloads and is used to filter worklists in capacity leveling. Long-term planning and finite scheduling both read this same capacity data, so a work center used in both a live production plan and a simulative long-term planning scenario must have available capacity defined far enough into the future; a common production issue is a capacity interval that was only maintained for the current fiscal year, causing next year's MRP run to see zero or default available capacity and generate false overload messages. In S/4HANA, when a work center is also exposed as a PP/DS resource (either through the classic resource generation report or, in cloud contexts, through the resource maintenance apps), the capacity data feeds resource-level bucket or single-mode capacity used by optimizer and heuristic runs; discrepancies between the ERP work center capacity and the generated PP/DS resource capacity are a frequent root cause of planning mismatches between the two planning engines, so any change to available capacity intervals in the work center should be followed by a resource regeneration or synchronization check in integrated PP/DS landscapes. Distinguish capacity category (machine vs labor vs generic) from capacity utilization: a single work center commonly carries two capacity categories, one for the machine and one for the operator, each with its own available capacity and formula, because a machine may run unattended for part of a shift while the operator capacity is constrained differently.
Real project scenario
A discrete manufacturing client complained that capacity leveling showed severe overload on a CNC work center every December even though production volumes were normal. Investigation of the capacity header showed the available capacity intervals had been maintained only through the prior fiscal year-end by a data load during initial go-live, so the system fell back to a much lower default capacity for the new year. The consultant corrected the process by adding available capacity as a rolling multi-year interval maintained via a periodic batch job instead of a one-time load, and added a data-quality check to the monthly master data audit.
Common mistakes
• Maintaining available capacity intervals for only a limited date range, causing false overloads once the range expires • Setting the overload percentage arbitrarily high to silence warnings instead of investigating true bottlenecks • Forgetting to define both machine and labor capacity categories when both constrain output independently • Not aligning the work center's factory calendar with the shift definitions used in the capacity header, causing capacity to be planned on non-working days • Failing to regenerate or resynchronize PP/DS resources after changing ERP work center capacity, leading to planning engine divergence
Best practices
• Maintain available capacity as rolling intervals extended periodically well beyond the current planning horizon • Use separate capacity categories for machine and labor when both are independent constraints • Set overload tolerance based on actual measured variability, not to suppress alerts • Align factory calendar, shift definitions, and capacity intervals consistently • Establish a governance process to regenerate PP/DS resources whenever ERP work center capacity changes
Interview angle
Interviewers assess whether candidates understand that available capacity is time-phased data requiring ongoing maintenance, not a one-time setup value, and whether they can explain the relationship between capacity category, formula, and capacity evaluation results, plus the ERP-to-PP/DS resource synchronization consideration in integrated landscapes.