MD11 — Create Planned Order
MD11 is used to create a planned order manually with material, plant, quantity and dates before conversion to procurement or production. It is most useful when planners need a controlled supply proposal outside an automatic MRP run or for testing planning behavior. 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 MD11 — Create Planned Order. 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· 644 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
create a planned order manually with material, plant, quantity and dates before conversion to procurement or production. MD11 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
MD11 is typically used when planners need a controlled supply proposal outside an automatic MRP run or for testing planning behavior. 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
- Enter material and plant and confirm planning parameters.
- Set quantity and basic dates based on the actual requirement.
- Review procurement type and source/production data.
- Save the planned order and record its number.
- Check MD04 to confirm requirements and receipts balance as expected.
Key data objects
These are the most useful anchors when working in MD11. 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.
- material and plant — verify the exact value, validity/date context and relationship to the affected process.
- planned-order quantity — verify the exact value, validity/date context and relationship to the affected process.
- basic dates — verify the exact value, validity/date context and relationship to the affected process.
- procurement type — verify the exact value, validity/date context and relationship to the affected process.
- BOM/production version context — 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
Planned orders remain central to S/4HANA MRP, including MRP Live scenarios; Fiori planning apps may supplement SAP GUI. 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
- Creating manual supply that duplicates an MRP proposal. Return to the exact object status and chronology before applying a workaround.
- Using dates that ignore lead time and capacity realities. Return to the exact object status and chronology before applying a workaround.
- Treating a planned order as a released production commitment. 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/md11ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.