MD13 — Display Planned Order
MD13 is used to display a planned order, including material, quantity, dates, procurement type and component/quantity-structure context. It is most useful when planners or support teams need read-only evidence for a supply proposal before conversion. 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 MD13 — Display Planned Order. 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· 548 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
display a planned order, including material, quantity, dates, procurement type and component/quantity-structure context. MD13 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
MD13 is typically used when planners or support teams need read-only evidence for a supply proposal before conversion. 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
- Open the planned order number from MD04 or another planning list.
- Review quantity and basic dates.
- Check procurement type and source/production data.
- Inspect components where relevant.
- Compare with current requirements and conversion status.
Key data objects
These are the fields and objects that most often explain the result in MD13. Record them in test evidence and support handovers.
- planned order — verify the exact value, status, validity and relationship to the source or follow-on document.
- material/plant — verify the exact value, status, validity and relationship to the source or follow-on document.
- quantity — verify the exact value, status, validity and relationship to the source or follow-on document.
- basic dates — verify the exact value, status, validity and relationship to the source or follow-on document.
- procurement/production details — 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 references MD13 as Display Planned Order in current S/4HANA navigation and planning documentation. 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
- Assuming an old planned order still reflects current MRP demand. Check the source and follow-on document statuses before applying a workaround.
- Confusing planned order with a released production or purchase commitment. Check the source and follow-on document statuses before applying a workaround.
- Ignoring firming/deletion indicators. 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/md13ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.