# Capacity Leveling in SAP PP, with an Example > Source: https://netray.co/erp-help/capacity-leveling-in-sap-pp-with-example > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System sap ## Erp SAP ECC / S/4HANA ## Module PP / Capacity Planning ## Query capacity leveling in sap pp with example ## Alternate Queries - sap capacity leveling cm21 cm25 - how to do capacity leveling in sap - sap capacity planning overload work center - sap dispatching planning table ## Applies To SAP ECC 6.0 and S/4HANA on-premise production planning with routings, work centers and capacity categories. ## Steps ### How to level an overloaded work center **Items:** Make 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. Run 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. Open 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. In 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. Check 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. Save. The system reschedules the affected orders. Re-run the evaluation (CM01) to confirm the load now fits under 100 percent. Release the orders (CO02 or CO05N or mass release) once the schedule is acceptable. ## Sections ### Worked example: a machining center with a 20 percent overload **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### What is capacity leveling in SAP PP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms capacity leveling in sap pp, capacity leveling in sap pp with example, sap cm21 capacity leveling, sap cm25 capacity planning table, sap capacity evaluation cm01, sap work center overload, sap dispatch capacity planning, sap infinite scheduling vs finite, sap pp capacity planning steps --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json