Capacity Leveling in SAP PP, with an Example
capacity leveling in sap pp with example
Also searched as
- sap capacity leveling cm21 cm25
- how to do capacity leveling in sap
- sap capacity planning overload work center
- sap dispatching planning table
Short answer
Capacity leveling moves operations from overloaded periods to periods with free capacity so a work center is not scheduled beyond what it can do. You first evaluate load in the capacity evaluation (CM01 for the work center view), then level with the capacity planning table (CM25, graphical) or the leveling list (CM21), and finish by checking the new dates and releasing the orders.
Applies to: SAP ECC 6.0 and S/4HANA on-premise production planning with routings, work centers and capacity categories.
How to level an overloaded work center
- 1Make sure capacity requirements exist: the work center needs a capacity category and available capacity (work center master, Capacities tab, CR02) and the routing operations need standard values that generate capacity requirements. Scheduling of orders creates the requirements.
- 2Run the capacity evaluation for the work center: CM01 (work center view) or CM02 (order view). Select the period and the work center, and look for load above 100 percent.
- 3Open capacity leveling for that work center: CM21 (leveling, work center view) for the variable overview or CM25 for the graphical capacity planning table. Both start from a planning profile and selection profile that define what is shown.
- 4In the planning table, select the overloaded operations and dispatch them. Options include move to another date, move to another period, and 'dispatch' to the next free capacity. Backward and forward dispatch decide which direction the tool searches for free capacity.
- 5Check the result against the due date. If an order now finishes after its basic finish date, decide whether to accept the delay, add shifts or overtime in the work center, or move the operation to an alternative work center.
- 6Save. The system reschedules the affected orders. Re-run the evaluation (CM01) to confirm the load now fits under 100 percent.
- 7Release the orders (CO02 or CO05N or mass release) once the schedule is acceptable.
Worked example: a machining center with a 20 percent overload
Work center MACH-10 has 40 hours available per week (one shift, 5 days, 8 hours). Week 22 has orders requiring 48 hours (120 percent load) while week 23 requires 20 hours (50 percent) and week 24 requires 10 hours.
In the planning table you see the week 22 operations stacked above the capacity line. You select the lowest priority order with 8 hours of load and dispatch it with the forward direction. The system places it into week 23, where it fits (28 hours of 40). Week 22 is now at 40 hours or 100 percent, week 23 at 70 percent. The order's finish date moves by one week.
If this order is critical, you would not move it. Instead you would level other orders, add overtime in week 22 (a shift sequence on the work center or an extra capacity version) or split the operation across a second work center with an alternative sequence in the routing. Leveling is a planner's decision tool, not an optimizer.
Leveling versus finite scheduling, and what leveling does not do
Standard SAP scheduling is infinite: it calculates dates from lead times and does not care that a work center is overloaded. Leveling is the manual (or semi-automatic) step that resolves overloads afterward. It does not change quantities and it does not know about material availability unless you check it before release.
For automated finite scheduling and sequencing across many orders, companies usually need Advanced Planning (PP/DS in S/4HANA or APO) or an external scheduler. Capacity leveling in PP remains useful for a small number of critical work centers where a planner can decide.
Settings that decide what you see
Capacity planning profiles (selection profile, planning table profile, dispatch function profile) control the time scale, the lines shown and the dispatching strategies. If the planning table is empty, usually the selection profile does not match the work center, plant or period, or no capacity requirements exist because orders were never scheduled.
Available capacity depends on the factory calendar, shift sequence and capacity version. A load of 120 percent may simply reflect a work center with the wrong shift definition, so check the master data before moving orders.
Try it here, free
SAP PP Work Center Available Capacity and Load Calculator
Compute available capacity per week from operating time, utilization rate and number of individual capacities, then see load percent and overload.
Common pitfalls
- !Leveling orders that are already released and partly confirmed changes remaining work only, so results may look odd. Level before release when possible.
- !No capacity requirements appear because the routing operation has no capacity category, no standard value or the capacity is not flagged relevant to finite scheduling.
- !Dispatching to a later period silently pushes an order past its customer date. Always compare to the due date.
- !Using the wrong selection profile hides work centers; the table looks empty although load exists.
- !Using leveling to fix master data errors: a wrong factory calendar or shift gives a fake overload.
How an ERP-grounded AI assistant handles this
Planners spend most of the time finding which work centers are overloaded and which orders can move without hurting a customer date. An assistant grounded in your SAP data (ERPray, read-only, runnable on-prem) can list work center load by week, the orders inside it and their due dates, so the person doing CM25 knows where to look. The moves themselves stay with the planner or a PP/DS tool.
Frequently asked questions
What is capacity leveling in SAP PP?
It is the process of moving operations from overloaded periods to periods with free capacity so the planned load on a work center fits what it can deliver. You analyze load with CM01 and level in CM21 or the CM25 planning table.
What is the difference between CM21 and CM25?
CM21 is the list based leveling view of a work center. CM25 is the graphical capacity planning table with drag and drop and dispatch functions. Both use planning and selection profiles and update the same capacity requirements.
Does SAP PP do finite scheduling?
Standard PP scheduling is infinite. Leveling is the manual correction. For automatic finite scheduling you need PP/DS (S/4HANA) or an APS tool, or an external scheduler fed by your SAP orders.
Why does the capacity planning table show nothing?
Most often the orders are not scheduled, so no capacity requirements exist, or the selection profile excludes the plant or work center. Check CM01 first. If load shows there, the planning table profile is the next suspect.
Related
Planning Strategy 40 in SAP PP, with a Worked Example
Planning strategy 40 is 'planning with final assembly'. You enter planned independent requirements (PIRs) for the finished product, MRP plans the finished product and all components from that forecast, and incoming sales orders consume (reduce) the PIR instead of adding to it. Final assembly is triggered by the sales order, not by the plan, so components are ready but the finished good is not built on spec.
How-toHow to Read MD04 Exception Messages in SAP
The exception indicator in MD04 flags procurement elements whose date or quantity no longer matches the current demand situation - it is SAP's built-in change signal, read element by element in the detail screen, not just the header icon. Triage by exception group first, then decide to reschedule, cancel, or accept each one.
Error fixSAP CO11N Confirmation Errors and How to Fix Them
CO11N (time ticket confirmation for production/process orders) throws several distinct errors: deviation from the standard value is too large, goods movement not possible for a component, or the order/operation status does not allow confirmation. Each has a specific cause in order status, routing tolerance settings, or component availability, not a single generic fix.
Error fixSAP CO01 Error: No Production Version Found for Material
SAP cannot pick a production version for the order quantity and date, so it cannot determine the BOM and routing. Fix it in C223 or on the MRP 4 view of the material: create a version for the plant, make its validity dates and lot size range cover the order, link a valid BOM alternative and routing, and remove the lock indicator.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI Agents for SAP Production Planning, MRP, and Exception Triage
AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
AI for ERPAI for SAP S/4HANA in Industrial Machinery: Project Structures, Variant BOMs and Aftermarket Parts
AI on SAP S/4HANA for machinery builders: project WBS, variant BOMs, engineering changes and spare parts answered from your live data, on-prem and read-only.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP PP Work Center Available Capacity and Load CalculatorCompute available capacity per week from operating time, utilization rate and number of individual capacities, then see load percent and overload.
- SAP Work Center Capacity Planning CalculatorCalculate available capacity, capacity requirements and load percent for a work center from shifts, utilization, setup and run times.
- SAP Work Center Master Data Request TemplateA request form for creating or changing an SAP PP work center, covering basic data, capacity, scheduling and costing so master data gets it right the first time.
ERP fixes and how-tos
- SAP PP Standard Reports: COOIS, CO46, MD04, CM01, CS12 and PPIO_ENTRYThe standard SAP PP reports and transactions planners use: COOIS, CO46, MD04, CM01, CS12 and PPIO_ENTRY, with what each shows and when to use it.
- SAP Table for Routing and Work Center, Work Orders and CapacitySAP PP tables for routing, work center, capacity and production orders: PLKO, PLPO, CRHD, KAKO, AFKO, AFPO, with join keys and SE16N queries to start from.
- SAP PP End to End Configuration: Steps, IMG Paths and Process FlowSAP PP end to end configuration in order: organizational structure, master data, MRP, order types, confirmation, costing and settlement, with IMG paths and tcodes.
Runs with your ERP
- Just Plan It and SAP Business ByDesign: finite-capacity scheduling for production ordersHow Just Plan It adds finite-capacity scheduling to SAP Business ByDesign through a BTP Integration Suite connector, with setup steps, pitfalls and AI options.
- Prometheus Planning & Scheduling with SAP Plant MaintenanceHow Prometheus Planning and Scheduling works with SAP Plant Maintenance work orders on S/4HANA and ECC: data flows, setup, pitfalls and a private AI layer.
- Asprova APS and SAP ECC: Finite-Capacity SchedulingHow Asprova finite-capacity scheduling complements SAP ECC and S/4HANA: flat file or OLE DB exchange, data flows, setup, pitfalls and a private AI layer.
Guides
- Machine Shop Scheduling for CNC Job Shops: Why Schedules Break and How to Fix ThemMachine shop scheduling for CNC job shops: why schedules break, finite versus infinite capacity, the data it needs, and where AI helps daily.
- Die Casting Scheduling: Machine, Die and Changeover CapacitySchedule die casting by machine tonnage, die availability, alloy, changeover and trim capacity, and see why spreadsheets break and how finite scheduling fixes it.
AI on your ERP
- AI Production Scheduling on Top of Your ERP: Explain, Triage and Re-Plan Without Replacing the SchedulerHow AI helps planners and schedulers explain late jobs, fix bad routing data and draft reschedules on top of ERP work orders, without replacing the finite scheduler.
- AI for PlanetTogether APS: Explain the Schedule, Compare Scenarios, Reconcile with the ERPAdd private AI to PlanetTogether APS: explain schedule changes, compare scenarios, and reconcile ERP orders with the plan, on-prem and read-only by default.