Planned Order Firming, Exception Messages, and MRP Regeneration Behavior
Understand how MRP treats existing planned orders during regenerative and net change planning runs, how firming protects manually adjusted orders, and how to interpret and act on exception messages tied to planned orders.
Explanation
When MRP runs repeatedly against a material, it does not simply delete and recreate every planned order from scratch. Instead, the MRP logic evaluates existing planned orders against current requirements and either keeps them unchanged, adjusts their quantity or date, or deletes and recreates them, depending on firming status and the planning parameters on the material master (MRP1-MRP4 views) and the plant-level MRP control parameters. A planned order is 'unfirmed' by default when generated by the system. Unfirmed orders are fully within MRP's control: if requirements shift, MRP can freely reschedule, resize, or delete these orders during the next run. This is the normal behavior planners rely on for a self-adjusting supply plan. A planned order becomes 'firmed' when a planner manually changes its date or quantity, or when firming is explicitly set (for example through a firming horizon defined in the material master or via manual firming action). Firmed orders are largely protected from automatic deletion; MRP will instead generate exception messages when a firmed order no longer matches current requirements, rather than silently changing it. This protects planner decisions (e.g., a deliberately front-loaded production run) from being overwritten by the next MRP run, while still surfacing the resulting supply/demand mismatch for review. The firming horizon is a critical configuration lever. It is a number of workdays from the MRP run date within which the system will not automatically reschedule or delete planned orders, treating them as if firmed, even if the planner did not manually firm them. This is commonly used to stabilize the near-term production schedule while allowing the system to freely re-plan further out. Setting this horizon too long can cause the system to accumulate stale, unadjusted orders that do not reflect real demand; setting it too short can cause excessive schedule churn on the shop floor as MRP reshuffles orders daily. Exception messages relevant to planned orders include indications that a firmed order's date is earlier or later than required, that a receipt element should be brought forward or pushed back, that a planned order falls before the opening period, or that a planned independent requirement can no longer be covered. These exception messages are surfaced in the MRP list and stock/requirements list and must be triaged by planners, since MRP does not auto-resolve firmed order conflicts. In S/4HANA, the same underlying firming and exception logic applies functionally, but the MRP Live engine (running on HANA) recalculates faster and the newer Fiori-based apps for Material Coverage and MRP monitoring present exceptions in a more consumable, filterable format than the classical exception lists. The core planning behavior around firmed vs. unfirmed orders is unchanged, but architects should verify whether a given landscape still uses classical MRP or MRP Live, since scheduling precision and performance characteristics differ, and this affects how quickly a planner sees the impact of a firming decision. A common design decision is whether to rely on manual firming (planner discretion, requires diligence) or a configured firming horizon (systematic, but blunt across all orders for a material). Many production support teams combine both: a modest firming horizon to protect the next few days of the schedule, supplemented by manual firming for orders the planner has specifically committed to, such as ones already communicated to a work center or subcontractor.
Real project scenario
A discrete manufacturing client experienced daily schedule instability: production supervisors complained that today's dispatch list differed from what was communicated yesterday. Investigation showed the material master had no firming horizon set, so every nightly MRP run freely rescheduled all planned orders, including ones already staged for the next shift. The fix was to configure a short firming horizon (a few workdays) on the relevant MRP1 view for the affected material group and to train planners to manually firm any order already communicated to production, resolving the churn while preserving MRP's ability to re-plan further out.
Common mistakes
• Assuming a firmed planned order will still be automatically resized by MRP; firming suppresses automatic changes and instead raises exception messages that require planner action. • Setting a firming horizon so long that MRP effectively stops adjusting near-term supply even when real demand has changed significantly. • Ignoring exception messages in the MRP list, allowing supply/demand mismatches on firmed orders to persist for multiple planning cycles. • Confusing manual firming (planner action on an individual order) with the firming horizon (a systemic date-based protection) and assuming they behave identically in all cases. • Not distinguishing classical MRP exception handling from S/4HANA Fiori-based monitoring apps when documenting procedures for a mixed-skill planning team.
Best practices
• Use a firming horizon judiciously to stabilize only the near-term schedule, not the entire planning horizon. • Establish a clear planner routine for reviewing exception messages on firmed orders during each planning cycle rather than letting them accumulate. • Document for each material or material group why a firming horizon value was chosen, tying it to lead times and communication commitments to production or vendors. • Train planners on the distinction between manually firming an individual order and relying on the systemic firming horizon. • When migrating to S/4HANA, verify whether MRP Live is active and validate that firming behavior and exception visibility meet the same operational expectations as the legacy process.
Interview angle
Interviewers assess whether a candidate understands the difference between unfirmed and firmed planned orders, what triggers firming (manual action vs. firming horizon), and why MRP raises exceptions instead of silently overriding firmed orders. Strong candidates can explain a real scenario where firming was used to stabilize a schedule and describe the trade-off between planner control and MRP's ability to self-adjust.