ERPTwin
Menu
PPCM01CM21advanced

Capacity Evaluation and Levelling (CM01, CM25)

MRP plans without looking at capacity, so a work center can end up overloaded. Capacity evaluation shows the load against what is available; levelling dispatches orders into periods that have room, respecting their due dates.

Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.

Digital twin

Docs
SAP DOCUMENTSVisualization of Capacity Evaluation and Levelling (CM01, CM25). All information shown in the scene is also available in the caption and the panels next to it.
Demo data

01Orders scheduled into week 42

Orders A (40 h), B (30 h) and C (50 h) all fall into week 42: 120 h against 80 h available.

Business scenario

Assembly line 1 has 80 hours in week 42. Three orders are scheduled there: 40, 30 and 50 hours — 120 hours in total.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

  1. 01

    Orders scheduled into week 42 open in twin

    Orders A (40 h), B (30 h) and C (50 h) all fall into week 42: 120 h against 80 h available.

    Standard MRP assumes infinite capacity, so overloads are normal until levelled.

  2. 02

    Capacity evaluation (CM01) open in twin

    Week 42: load 120 h, available 80 h — 150% utilised.

    The overload is visible before it becomes a missed date.

  3. 03

    Resolve the overload open in twin

    Week 42 is 40 hours over. Which order moves?

    Move work that has slack, not work that would then be late.

  4. 04

    Order A now late open in twin

    Order A is due in week 42. Moving it makes it late while C, which had slack, still overloads week 42 (80 h).

    Dispatching sequences and strategies (CM25 profiles) encode such rules.

  5. 05

    Dispatch order C to week 43 (CM25) open in twin

    Week 42: 70 h (88%). Week 43: 70 h (88%). All orders on time.

    Dates on the order are updated; dependent requirements move with it.

  6. 06

    Load balanced open in twin

    Evaluate → decide → dispatch. No stock or accounting involved.

    In S/4HANA, Fiori apps (e.g. capacity scheduling board) and PP/DS offer finite scheduling — scope dependent.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

This part of the process does not change stock.

Accounting impact

No accounting impact in the steps shown.

Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.

Movement type

This flow spans several documents rather than a single movement type.

Matches planned work to the capacity actually available, so orders can be finished on time.

Transactions & Fiori apps

  • CM01 — Capacity Evaluation — Work Center Load
  • CM21 — Capacity Levelling — Graphical
  • CM25 — Capacity Levelling — Variable
  • CR02 — Change Work Center (capacity)
  • Manage Work Center CapacityAvailability depends on release and scope
  • Capacity Scheduling BoardAvailability depends on release and scope

Differences by SAP version

CM01 / CM21 / CM25.

Configuration

  • Overall profile for levelling

    Configuration dependent

    Time profile, strategy and list profiles used by CM21/CM25.

  • Finite scheduling

    Configuration dependent

    Whether dispatching respects available capacity strictly.

Prerequisites

  • Work center with capacity header (shifts, utilisation)
  • Routings with standard values and formulas
  • Orders scheduled with capacity requirements

Master data

Work center capacity
Available hours per day.
Routing
Load per operation.

Organizational structure

  • Plant 1000
  • Work center ASSY-01

Tables

TableDescription
KBEDCapacity requirements
KAKOCapacity header

Integration

    Common errors

    • “No capacity requirements shown”

      Likely causes: Order not scheduled with capacity requirements; Missing formulas on the work center

      Where to look: Order scheduling parameters · Work center formulas

    Troubleshooting

    Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

    1. CHECK 1

      Load

      • Capacity requirements created?
      • Correct capacity category on the work center?

    Interview questions

    • Why is capacity levelling needed after MRP?

      Classic MRP plans with infinite capacity, so work centers can be overloaded. Capacity evaluation (CM01) shows load vs available capacity; levelling (CM21/CM25) dispatches operations into periods with free capacity, respecting due dates and priorities.

    Quiz

    Q1 · Multiple choice

    Which transaction shows the load on a work center?

    References

    • SAP SE — SAP Help Portal: Capacity Planning (source)
    • SAP SE — SAP Help Portal: Capacity Levelling (source)

    Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

    Version history

    VersionChange
    1.0.0Initial version.