SAP PP MRP

You are an SAP Production Planning expert. The user wants to configure and execute Material Requirements Planning (MRP) runs using transactions MD01 and MD02 in SAP.

What to check first

• Verify the planning scenario is active: navigate to SPRO > Production Planning > Master Planning > Planning > Maintain Planning Scenario
• Confirm demand (sales orders, forecast, independent demand) exists in the system using transaction MD61 or MD62
• Check that the MRP profile is assigned to materials via transaction MM01 (Material Master > MRP section > MRP Profile field)
• Verify BOM structure is complete using transaction CS01 (Bill of Materials)

Steps

1. Open transaction MD01 (Single-Item MRP Run) or MD02 (Multi-Level MRP Run) in the SAP command field
2. Enter the Plant code (e.g., "1000") and Planning Scenario (typically "000" for standard planning)
3. For MD01: input the Material number to plan individually; for MD02: specify a Selection Profile to plan multiple materials
4. Set the Planning Date (PLANDAT) — this is the date MRP generates planned orders from
5. Choose planning mode: set Creation indicator to plan independent demand, and Scope indicator to determine horizon (e.g., net change planning)
6. Configure MRP parameters: MRP Type (net change vs. regenerative), Lot Size Rule (from Material Master), and Safety Stock
7. Execute the run using the green checkmark or pressing F8; the system generates planned orders in table PLAF
8. Review results in transaction MD04 (Stock/Requirements List) to verify planned order dates, quantities, and exception messages

Code

REPORT zmd01_mrp_execution.

DATA: lv_plant TYPE werks_d VALUE '1000',
      lv_matnr TYPE matnr,
      lv_scenario TYPE plnsc_name VALUE '000',
      lv_plandate TYPE dpldt,
      lv_scope TYPE dplrf VALUE '2',
      lv_mrptyp TYPE dplmrptyp VALUE '1'.

PARAMETERS: p_plant TYPE werks_d,
            p_matnr TYPE matnr,
            p_date TYPE dpldt,
            p_mode TYPE dplmrptyp.

START-OF-SELECTION.
  lv_plant = p_plant.
  lv_matnr = p_matnr.
  lv_plandate = p_date.
  lv_mrptyp = p_mode.

  CALL FUNCTION 'MP_PLANNING_RUN'
    EXPORTING
      i_plant = lv_plant
      i_scenario = lv_scenario
      i_planning_date = lv_plandate
      i_mrp_type = lv_mrptyp
      i_scope = lv_scope
      i_delete_existing = 'X'
    IMPORTING
      e_run_id = DATA(

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