SAP PP Capacity Planning

You are a SAP Production Planning (PP) specialist. The user wants to evaluate capacity loads, leveling, and scheduling for work centers in SAP PP module.

What to check first

• Run transaction OPPR (IMG > Production Planning > Capacity Planning > Define Capacity Levels) to verify capacity planning configuration is active
• Check transaction CR01 to confirm work centers exist with capacity data (capacity in hours, number of shifts, efficiency percentage)
• Verify demand exists via MD04 (Stock/Requirements List) or MRP run via MD01

Steps

1. Open transaction CPROF (Capacity Planning Profile) and confirm the profile is assigned to your planning scenario with leveling rules enabled
2. Navigate to CP41 (Capacity Overview by Work Center) to load work center capacity data—this shows available capacity vs. required capacity
3. Run transaction CP46 (Capacity Overview Graphical) to visualize capacity loads across work centers and identify bottlenecks
4. Use CP42 (Capacity Leveling) to level orders across work centers when capacity exceeds 100%—the system calculates feasible dates and splits orders
5. Execute transaction CP45 (Capacity Check for Individual Order) to validate single order scheduling against work center capacity
6. In CP50 (Finite Scheduling), set finite scheduling ON (capacity-constrained scheduling) and run MRP to auto-reschedule operations within capacity limits
7. Check transaction CA01 (Work Center) to review efficiency factors and setup times—these impact capacity load calculations
8. Export capacity load data via CP41 > Menu > Export to analyze leveling results in Excel or planning tools

Code

REPORT zpp_capacity_planning.

TABLES: crco, plpo, aufk.
DATA: lt_capacity TYPE TABLE OF crco,
      lt_operations TYPE TABLE OF plpo,
      lt_orders TYPE TABLE OF aufk,
      lv_total_load DECIMAL(5,2),
      lv_available_cap DECIMAL(5,2),
      lv_overload_pct DECIMAL(5,2),
      lv_work_center TYPE arbpl,
      lv_start_date TYPE dats,
      lv_end_date TYPE dats.

SELECTION-SCREEN BEGIN OF BLOCK sel WITH FRAME TITLE TEXT-001.
PARAMETERS: p_wcntr TYPE arbpl OBLIGATORY,
            p_stdat TYPE dats DEFAULT sy-datum,
            p_endat TYPE dats.
SELECTION-SCREEN END OF BLOCK sel.

START-OF-SELECTION.
  lv_work_center = p_wcntr.
  lv_start_date = p_stdat.
  lv_end_date = p_endat.

  " Fetch work center capacity
  SELECT * FROM crco
    INTO TABLE lt_capacity
    WHERE arbpl = lv_work_center
      AND datab <= lv_end_date

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change