Master planning runs in Dynamics 365 Finance and Operations

Master planning is the F&O engine that turns demand (sales orders, transfers, forecasts) and existing supply (on-hand, purchase orders, production orders) into a coherent supply plan — planned purchase orders, planned production orders, planned transfer orders, and action messages on existing supply. Master planning runs are a daily or hourly rhythm in most production deployments.

Two engines.

• Classic master planning — the legacy engine, runs on the F&O SQL database, batch-processes the whole plan.
• Planning Optimization — the newer in-memory service, runs in Azure, much faster, supports incremental runs.

Both follow the same conceptual model. Planning Optimization is the strategic direction; new deployments should start there unless they need a feature that classic supports but PO doesn't (still a shrinking list).

The master plan record. A master plan defines the run:

• Time fence — how far into the future planning suggests orders.
• Coverage codes inheritance — defaults if items don't specify.
• Calculations to include — sales orders, forecasts, transfers, BOMs, kits.
• Filters — items, sites, warehouses to include.

A typical setup has two plans:

• Static plan — read-only, used by procurement to firm purchase orders.
• Dynamic plan — recalculated frequently, used by planners for what-if and short-term decisions.

Some teams run a third simulation plan for scenario analysis.

Regenerative vs net-change.

• Regenerative — recalculates everything for every item in scope. Heavier; usually nightly.
• Net change — recalculates only items whose net requirement changed since last run. Lighter; hourly.

Planning Optimization handles incremental more efficiently than classic. Regenerative every weekend, net-change every hour or even continuously is the typical cadence.

What the engine produces.

• Planned orders — suggestions: planned purchase, planned production, planned transfer, planned kanban.
• Action messages — recommendations on existing supply: advance, delay, increase, decrease, cancel.
• Futures messages — alerts that promised dates can't be met.
• Capacity warnings — if scheduling reveals overload.

Planners review in the Planned Orders workspace. Firming a planned order converts it to the real order (purchase, production, transfer); action messages drive amendments to existing orders.

Pegging. The link from supply to demand. Every planned order traces to the demand it covers, and every demand traces to its supply. The Pegging tree view shows: this sales order → this planned production → this planned purchase. Pegging visibility is invaluable for impact analysis when a vendor delays.

BOM explosion. For manufactured items, master planning recursively explodes BOMs:

1. Demand for finished good → planned production order.
2. Production order needs components per BOM → demand for each component.
3. Each component → existing supply or new planned order (purchase, production, transfer).
4. Multi-level BOMs recurse until raw materials.

The explosion respects:

• Production routes for lead time calculation.
• Production calendars for capacity.
• BOM versions active on the planned production date.

Forecast consumption. As real sales orders land in forecast periods, they consume the forecast. Master planning sees the net demand (max of forecast remaining, actuals). Without consumption, demand doubles.

Lock periods and frozen zones.

• Time fence — the window within which the engine doesn't change existing orders without explicit planner intervention.
• Action message time fence — the window within which the engine doesn't even produce action messages.

These prevent constant rescheduling of imminent operations.

Performance.

• Classic master planning on 10K+ items can run for hours. Mitigations: index tuning, batch parallelism, scoped plans.
• Planning Optimization on the same volume runs in minutes — orders of magnitude faster because it's an in-memory service.

For large supply chains, PO performance often justifies the migration from classic by itself.

Common pitfalls.

• Stale forecasts. Engine produces precise suggestions for a forecast nobody believes any more.
• Lead times wrong. Suggested orders due dates miss reality; planners override constantly.
• Coverage codes default-only. No item-level tuning; one-size-fits-all suggestions.
• Ignoring action messages. Hundreds of action messages every day; planners triage by ignoring most. Build a discipline of working messages or accept that the engine will inflate exception backlogs.
• Pegging not used. Planners override without understanding downstream consequences; supply chain becomes opaque.

The operational rhythm. Daily morning planner stand-up: review last night's regenerative results, work the top action messages, firm the next 24 hours of planned orders. Master planning is a tool for the planning rhythm — not a substitute for planner judgement, but a force-multiplier for it.