MD16 — Collective Display of Planned Orders
MD16 is used to list planned orders collectively for a plant/material/planner selection and navigate to individual proposals. It is most useful when planners need a worklist of planned orders for review, conversion or exception analysis. 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 MD16 — Collective Display of Planned Orders. 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· 544 words
Purpose
list planned orders collectively for a plant/material/planner selection and navigate to individual proposals. MD16 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
MD16 is typically used when planners need a worklist of planned orders for review, conversion or exception analysis. 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
- Restrict plant and planner/material scope.
- Review order dates, quantities and procurement type.
- Separate in-house from external procurement proposals.
- Navigate to individual orders requiring adjustment.
- Use dedicated collective conversion transactions for controlled mass conversion.
Key data objects
These are the fields and objects that most often explain the result in MD16. Record them in test evidence and support handovers.
- plant — verify the exact value, status, validity and relationship to the source or follow-on document.
- MRP controller/material — verify the exact value, status, validity and relationship to the source or follow-on document.
- planned order — verify the exact value, status, validity and relationship to the source or follow-on document.
- dates/quantity — verify the exact value, status, validity and relationship to the source or follow-on document.
- conversion/firming status — 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 lists MD16 as Collective Access/Display of Planned Orders. 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
- Converting a broad selection without checking dates/material availability. Check the source and follow-on document statuses before applying a workaround.
- Treating every planned order as firm demand. Check the source and follow-on document statuses before applying a workaround.
- Ignoring duplicate proposals created by manual planning. 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/md16ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.