MD15 — Collective Conversion of Planned Orders to Purchase Requisitions
MD15 is used to convert multiple externally procured planned orders into purchase requisitions in a controlled selection. It is most useful when planners/buyers need mass conversion of eligible MRP proposals for external procurement. 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 MD15 — Collective Conversion of Planned Orders to Purchase Requisitions. 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· 540 words
Esta página aún no está disponible en español.
Purpose
convert multiple externally procured planned orders into purchase requisitions in a controlled selection. MD15 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
MD15 is typically used when planners/buyers need mass conversion of eligible MRP proposals for external procurement. 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
- Build a focused plant/planner/material selection.
- Review eligible planned orders before conversion.
- Exclude proposals that need manual correction.
- Run conversion and inspect failures individually.
- Reconcile generated requisitions in MD04/ME5A.
Key data objects
These are the fields and objects that most often explain the result in MD15. 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.
- planned orders — 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.
- dates/quantity — verify the exact value, status, validity and relationship to the source or follow-on document.
- conversion result/log — 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 MD15 as collective conversion of planned orders into purchase requisitions. 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
- Mass-converting stale or duplicate proposals. Check the source and follow-on document statuses before applying a workaround.
- Ignoring failed lines because most of the batch succeeded. Check the source and follow-on document statuses before applying a workaround.
- Converting before source/planning master data is corrected. 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/md15ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.