MD01N — MRP Live
MD01N is used to run HANA-optimized Material Requirements Planning for selected plants, materials, product groups or MRP controllers. It is most useful when S/4HANA planners need a regenerative or net-change planning run using MRP Live. Start with the exact document, material, organizational scope and business date, then follow status and document flow before changing configuration or master data.
Verified practitioner reference for MD01N — MRP Live. It covers purpose, practical use, key data, proof-in-data checks, S/4HANA context, common errors and related objects so the transaction can be used as part of an end-to-end SAP investigation.
Published 19 Sept 2026· 571 words
Esta página ainda não está disponível em português.
Purpose
run HANA-optimized Material Requirements Planning for selected plants, materials, product groups or MRP controllers. MD01N should be understood in the surrounding business flow: source document or requirement, master data, determined status and follow-on document. Capturing that chain is more reliable than treating the transaction as an isolated screen.
When it is used
MD01N is typically used when S/4HANA planners need a regenerative or net-change planning run using MRP Live. It is also valuable in project testing because it provides a repeatable point in the process. In production, narrow the document/material scope first and capture the before-state before mass actions or configuration changes.
How to use it in practice
- Define the smallest scope that meets the planning objective.
- Choose regenerative planning only when required.
- Run MRP Live and review the planning log.
- Analyze uncovered materials/exceptions in MD04 or Fiori coverage apps.
- Correct master data and rerun only the affected scope where possible.
Key data objects
These are the fields and objects that most often explain the result in MD01N. Record them in test evidence and support handovers.
- plant/material scope — verify the exact value, status, validity and relationship to the source or follow-on document.
- MRP controller/product group — verify the exact value, status, validity and relationship to the source or follow-on document.
- planning parameters — verify the exact value, status, validity and relationship to the source or follow-on document.
- regenerative option — verify the exact value, status, validity and relationship to the source or follow-on document.
- planning log/result — verify the exact value, status, validity and relationship to the source or follow-on document.
How to prove it in the data
Prove the scenario through chronology and document flow. Start with the source order, delivery, requirement or master record; capture the transaction status; then follow the resulting delivery, billing, production or procurement object. Reconcile quantities, dates and statuses using the same organizational scope. A correct diagnosis explains why SAP selected or rejected the object, not just what message appeared.
ECC vs S/4HANA
SAP Help documents MD01N as the S/4HANA MRP Live transaction and provides Fiori scheduling/coverage apps alongside it. For new S/4HANA designs, use current strategic applications and clean-core guidance even when a classic SAP GUI transaction remains available for support.
Common pitfalls and how to diagnose them
- Using regenerative planning routinely when net-change planning is sufficient. Check the source and follow-on document statuses before applying a workaround.
- Comparing MD01N results with old MRP runs without identical scope/settings. Check the source and follow-on document statuses before applying a workaround.
- Treating every planning exception as a program error rather than master/data demand behavior. Check the source and follow-on document statuses before applying a workaround.
Whose problem this is
Primary ownership is the PP/M2D team, with MM, warehouse, Finance or Basis involved when the document flow crosses those components. A strong escalation includes document/material, plant or sales area, date, status, expected result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/md01nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.