MD06 — Collective Display of MRP Lists
MD06 is used to display MRP lists for multiple materials collectively and prioritize exception messages from the last planning run. It is most useful when planners need a worklist of MRP exceptions captured at planning-run time rather than the live MD04 situation. 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 MD06 — Collective Display of MRP Lists. 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· 583 words
Esta página ainda não está disponível em português.
Purpose
display MRP lists for multiple materials collectively and prioritize exception messages from the last planning run. MD06 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
MD06 is typically used when planners need a worklist of MRP exceptions captured at planning-run time rather than the live MD04 situation. 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
- Select plant and MRP controller or a focused material set.
- Use traffic lights/exception groups to identify priorities.
- Open individual MRP lists for materials with relevant exceptions.
- Compare with current MD04 before acting because MD06 is a planning-run snapshot.
- Correct master/planning data and rerun planning where needed.
Key data objects
These are the fields and objects that most often explain the result in MD06. Record them in test evidence and support handovers.
- plant/MRP controller — verify the exact value, status, validity and relationship to the source or follow-on document.
- material — verify the exact value, status, validity and relationship to the source or follow-on document.
- MRP list creation date — verify the exact value, status, validity and relationship to the source or follow-on document.
- exception group — verify the exact value, status, validity and relationship to the source or follow-on document.
- planning 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 explicitly identifies MD06 as Collective Display of MRP Lists; S/4HANA also offers material-coverage Fiori apps. 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
- Treating MD06 as a live stock/requirements view. Check the source and follow-on document statuses before applying a workaround.
- Acting on an old MRP list after requirements changed. Check the source and follow-on document statuses before applying a workaround.
- Processing every exception without understanding its business significance. 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/md06ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.