MD07 — Collective Stock/Requirements Overview
MD07 is used to monitor stock/requirements situations for multiple materials and work with exception-oriented planning lists. It is most useful when planners need a collective view of shortage, rescheduling and MRP exception situations rather than one MD04 material. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
This ERPClimb practitioner page covers MD07 — Collective Stock/Requirements Overview. It focuses on the transaction's real operational role, the parameters that matter, the evidence needed to diagnose problems, S/4HANA context, and the mistakes that cause most support rework.
Published 19 Sept 2026· 630 words
Purpose
monitor stock/requirements situations for multiple materials and work with exception-oriented planning lists. MD07 is most useful when treated as part of an end-to-end process rather than a shortcut. The object status you see here is usually influenced by upstream master data, configuration, planning or document history, so capture those inputs before changing anything.
When it is used
MD07 is typically used when planners need a collective view of shortage, rescheduling and MRP exception situations rather than one MD04 material. It is also valuable during project testing because it exposes a repeatable state that can be compared before and after configuration or master-data changes. In production, narrow the population first and distinguish display/analysis from actions that post, approve, replicate or change status.
How to use it in practice
- Select plant and MRP controller or a focused material population.
- Use exception groups to prioritize real planning issues.
- Drill into the material stock/requirements list.
- Validate source master data before changing dates or quantities.
- Re-run planning only after understanding whether the exception is stale or genuine.
Key data objects
These are the most useful anchors when working in MD07. Capture them in screenshots, test evidence and incident handovers so another consultant can reproduce the same result and identify whether the issue is data, configuration, status or integration.
- plant/MRP controller — verify the exact value, validity/date context and relationship to the affected process.
- material selection — verify the exact value, validity/date context and relationship to the affected process.
- exception groups — verify the exact value, validity/date context and relationship to the affected process.
- stock/requirements elements — verify the exact value, validity/date context and relationship to the affected process.
- days' supply — verify the exact value, validity/date context and relationship to the affected process.
How to prove it in the data
Build an evidence chain rather than relying on one message: identify the source requirement or master record, show the transaction status or worklist entry, then show the resulting document, posting, warehouse object, planning element or replication log. Use the same date and organizational scope throughout. That makes the diagnosis repeatable and separates a true fix from a coincidental retry.
ECC vs S/4HANA
MD07 remains useful in S/4HANA, while MRP Live and Fiori MRP apps provide additional planner worklists. Where a Fiori app or cloud service becomes the strategic user experience, the SAP GUI transaction can still remain valuable for support, migration and deep technical analysis, but it should not be used to justify a legacy design for new work.
Common pitfalls and how to diagnose them
- Treating every exception message as an error. Return to the exact object status and chronology before applying a workaround.
- Changing planned receipts without checking pegged requirements. Return to the exact object status and chronology before applying a workaround.
- Using broad collective lists without planner/plant filters. Return to the exact object status and chronology before applying a workaround.
Whose problem this is
Primary ownership is the PP M2D team, with adjacent functional, Basis, Security or integration teams joining when the evidence crosses system boundaries. Escalate with the object/document number, organization, date/time, expected result, actual status 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/md07ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.