MD12 — Change Planned Order

change an existing planned order's quantity, dates or permitted planning data. MD12 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.

MD12 is typically used when a planner must manually adjust an MRP-generated or manually created 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.

These are the fields and objects that most often explain the result in MD12. Record them in test evidence and support handovers.

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.

MD12 remains the standard planned-order change transaction in classic and S/4HANA MRP processes. For new S/4HANA designs, use current strategic applications and clean-core guidance even when a classic SAP GUI transaction remains available for support.

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.

Use ERPClimb's related SAP objects to follow the process upstream and downstream. This makes MD12 useful as part of a diagnostic path rather than as a memorized shortcut.