SAP Capacity Planning Tutorial (Part 1)

Capacity planning exists because a materially feasible MRP plan is not automatically a physically feasible one. Material Requirements Planning determines what quantities are needed and when, but it does not natively guarantee that the machines, labor, or production lines involved have enough available hours to execute that plan. Capacity planning closes that gap by comparing the capacity requirements generated by planned orders, production orders, and process orders against the capacity supply defined on work centers or resources.

At the foundation is the work center (or resource in process industries, or production line in repetitive manufacturing). Each work center can carry one or more capacity categories, most commonly machine capacity and labor/personnel capacity, though setup, teardown, or other categories can also be modeled. Each capacity category has a capacity header defining the base unit of measure for capacity (hours is typical), and an intervals record specifying the operating time pattern: start time, end time, breaks, number of individual capacities (parallel machines or workers), utilization percentage, and a factory calendar reference so the system knows which days are working days.

Capacity requirements are generated at the operation level of routings. When a planned order or production order is created with a routing, each operation carries standard values (setup time, machine time, teardown time) that, combined with the formulas assigned to the work center's capacity category, produce a calculated capacity requirement in hours, distributed across the operation's scheduled dates. This requirement is what appears in capacity evaluation transactions.

Capacity evaluation is typically done in two complementary views: the load-oriented view showing cumulative capacity requirements versus available capacity per work center over a time axis (day, week, or period), and the order-oriented or pegged view showing which specific orders and operations make up that load. A work center's capacity situation can be color-coded or numerically flagged as underloaded, adequately loaded, or overloaded, letting a planner quickly triage bottlenecks.

It is important for beginners to understand the distinction between capacity requirements and capacity leveling. Requirements evaluation is read-only diagnostics: it shows the mismatch but does not fix it. Leveling (covered in a later lesson) is the active process of shifting, splitting, or reassigning operations to smooth the load. Also critical is understanding the planning horizon layering: in early planning stages (sales and operations planning, rough-cut planning), capacity checks are often simplified using rate-based or resource-based rough-cut profiles rather than full routing-based detailed capacity, because detailed routings may not yet be finalized or maintaining them at that level of granularity would be too costly. As the plan matures toward execution, detailed capacity from actual routings becomes the basis for scheduling and leveling decisions.

In S/4HANA, the same underlying work center and capacity category concepts persist, but capacity evaluation can also be performed through Fiori apps that present the same load and backlog information with more modern visualization, and in PP/DS-enabled scenarios capacity is evaluated live against the liveCache-resident planning data rather than only through batch-oriented reports. Regardless of deployment, the conceptual anchor is the same: capacity supply (from work center intervals) versus capacity demand (from order operations), evaluated over a calendar-aware time axis.

A discrete manufacturing client running MRP weekly found that several work centers were consistently flagged red (overloaded) in the capacity evaluation report two weeks out, yet production always seemed to catch up. Investigation revealed the work center's capacity intervals had not been updated after a shift pattern change from two shifts to three, so the available capacity in the system was understated by roughly 33 percent even though real capacity had increased. Correcting the capacity header and interval maintenance eliminated the false overload signal and restored planner trust in the evaluation report.

• Failing to update work center capacity intervals when shift patterns, calendars, or headcount change, leading to phantom over- or under-load.
• Assuming capacity evaluation numbers reflect leveled, feasible schedules when they are only a diagnostic snapshot of requirements versus supply.
• Ignoring the factory calendar assignment on the capacity category, causing requirements to fall on non-working days and distort the load picture.
• Mixing rough-cut and detailed capacity checks without understanding which planning stage each is appropriate for.
• Overlooking the utilization percentage field, which can silently reduce effective available capacity below the nominal operating time.

• Establish a periodic review cadence to reconcile work center capacity intervals against actual shift patterns and headcount.
• Use factory calendars consistently and verify they are assigned correctly at the capacity category level, not only at the plant level.
• Communicate to planners that capacity evaluation reports are diagnostic, and pair them with a defined leveling or escalation process.
• Document which capacity category (machine vs labor) drives the bottleneck for each critical work center to speed up troubleshooting.
• Validate standard values and formulas on new routings against real observed run times before relying on the resulting capacity requirements for decisions.

Interviewers commonly ask candidates to explain the difference between capacity requirements and capacity leveling, and to describe how a work center's available capacity is derived from capacity category intervals, factory calendar, and utilization percentage. A strong answer distinguishes diagnostic evaluation from corrective leveling and explains why rough-cut and detailed capacity checks serve different planning horizons.