Understanding Planned Orders: Purpose, Structure, and Lifecycle
Introduces what a planned order is, why MRP generates it, its key data structure, and how it moves through its lifecycle from creation to conversion or deletion.
Explanation
A planned order is a planning element created by Material Requirements Planning (MRP) or manually by a planner to cover a net requirement for a material that is either produced in-house or procured externally. It is not yet a legally binding document like a purchase order or a released production order; instead, it is an internal proposal that tells the planning system 'this quantity of this material is needed by this date, and this is how we intend to cover it.' Why planned orders matter: without them, MRP would have no intermediate mechanism to represent proposed supply before committing to procurement or production. They allow planners to review, adjust, firm, or delete proposals before they become costly, hard-to-reverse execution documents. This buffer is essential in real manufacturing environments where demand signals change frequently (forecast revisions, sales order changes, engineering changes) and where premature commitment to purchase requisitions or production orders would create waste, expediting costs, or excess inventory. Structure: Every planned order carries a header with material number, plant, MRP area (if activated), planned quantity, order start date, order finish date, and order type (in-house production vs. external procurement, indicated by the special procurement key or the requirements class). For in-house production, the planned order references a routing (or master recipe in process industries) and a bill of material (BOM) that MRP or the system explodes to determine component requirements — visible as dependent requirements. For externally procured materials, the planned order instead points toward a source of supply (vendor, info record, or scheduling agreement) that will be used when it is converted to a purchase requisition. Lifecycle: MRP creates planned orders during a planning run (in ECC/S/4HANA classic MRP, this is typically triggered via the MRP run transaction/job; in PP/DS, the heuristic or optimizer creates similar planning elements). Planned orders are unfirmed by default, meaning MRP is free to change their date, quantity, or even delete them automatically on the next planning run as demand changes. Planners can firm a planned order (locking it against automatic changes) when they want to protect a commitment — for example, once procurement has informally confirmed vendor capacity. Eventually, a planned order is converted: in-house production planned orders convert into production orders (or process orders), while procurement planned orders convert into purchase requisitions. Conversion can be manual (planner reviews and converts individually or in a collective conversion transaction) or automatic (via a conversion indicator that allows MRP to auto-convert without planner review, typically used only for stable, low-risk materials). It is important to understand that planned orders exist only in the planning/logical layer — they do not post any goods movements, do not consume budget, and do not trigger vendor commitments. They are visible in stock/requirements list and MRP list transactions alongside other elements like purchase requisitions, production orders, and sales orders, giving the planner an integrated view of supply and demand. In S/4HANA, the same fundamental concept applies, though the underlying data model (MATDOC-based tables, simplified order structures) and the Fiori-based apps for monitoring planned orders differ from the classic ECC GUI transactions, and PP/DS in S/4HANA offers additional planned order handling through the advanced planning and optimization heuristics.
Real project scenario
A mid-size discrete manufacturer runs weekly MRP for a family of assembled products. During Monday's planning run, MRP creates dozens of new planned orders and adjusts dates on existing unfirmed ones because a large customer order was rescheduled. The production planner reviews the MRP list, firms three planned orders whose components have already been kitted on the shop floor floor (protecting them from further automatic rescheduling), and leaves the rest unfirmed so MRP can continue optimizing dates as new sales orders arrive later in the week. On Thursday, the planner runs a collective conversion for planned orders falling within the current production horizon, generating production orders that are released to the shop floor.
Common mistakes
• Assuming a planned order is a firm commitment — it can be changed or deleted by the next MRP run unless explicitly firmed. • Confusing planned orders with purchase requisitions or production orders; they are a distinct, earlier-stage planning object. • Firming every planned order out of caution, which defeats the purpose of MRP's automatic replanning and leads to excess inventory or missed schedule optimizations. • Not understanding that dependent requirements from a planned order's BOM explosion disappear if the planned order is deleted, potentially causing unexpected shortages downstream. • Overlooking that planned order conversion behavior (manual vs automatic) is controlled by settings on the material master and MRP group, not a universal system default.
Best practices
• Leave planned orders unfirmed by default so MRP can continue to optimize dates and quantities as demand changes. • Firm planned orders only when there is a real business reason (materials already procured, capacity already reserved, engineering change lock). • Review the MRP list or stock/requirements list regularly rather than relying solely on automatic conversion for critical or expensive materials. • Align conversion indicator settings on the material master with the actual planning strategy for that material (make-to-stock vs make-to-order). • Educate planners that deleting a planned order also removes its dependent requirements, which can cause a hidden shortage if not re-evaluated.
Interview angle
Interviewers often ask candidates to explain the difference between a planned order, a purchase requisition, and a production order, and why MRP uses an intermediate object at all. Strong answers emphasize the firm/unfirm concept, the review-before-commit business value, and the conversion mechanics (manual vs automatic) tied to material master settings such as the conversion indicator or MRP group behavior.