18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture
Key Takeaways
- Planning Optimization is a cloud-native, in-memory multi-tenant Azure microservice that calculates material requirements in minutes or seconds without placing transactional table locks on the core ERP SQL database.
- The classic built-in SQL-based master planning engine is deprecated for cloud deployments of Dynamics 365 Supply Chain Management, making Planning Optimization the mandatory standard for exam MB-330.
- Organizations configure a single-plan strategy (pointing both static and dynamic plans to the same plan) or a two-plan strategy (maintaining a static plan for execution stability and a dynamic plan for real-time order promising).
- Coverage codes dictate net requirements logic: Period combines requirements over a time bucket, Requirement performs discrete 1:1 lot-for-lot planning, Min/max orders up to maximum stock when minimum thresholds are breached, and Manual bypasses calculation.
- Safety stock fulfillment policies (Today's date, Today's date + purchase time, First issue, Coverage time fence) define the exact timing and urgency with which replenishment orders are scheduled to restore minimum inventory.
18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture
Quick Answer: In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), Master Planning translates sales demand, forecasts, safety stocks, and production requirements into actionable planned purchase, production, and transfer orders. Modern D365 SCM relies on Planning Optimization, a cloud-native, multi-tenant in-memory Azure microservice that replaces the deprecated SQL-based classic planning engine. Master planning behavior is governed globally by Master planning parameters (
Master planning > Setup > Master planning parameters), partitioned operationally through Coverage groups (Master planning > Setup > Coverage > Coverage groups), and executed across Static and Dynamic master plans.
1. Planning Optimization Add-in: Microservice Architecture & Performance
Historically, Microsoft Dynamics AX and early versions of Dynamics 365 SCM utilized an in-application MRP calculation engine. This legacy engine executed heavy, long-running batch jobs directly against the transactional relational database (ReqCalc and SQL Server tables). For enterprise environments with hundreds of thousands of items, multi-level Bills of Materials (BOMs), and high transaction velocity, classic MRP runs took 4 to 12 hours, consumed massive database compute, created table locks, and had to be restricted to overnight batch windows.
The Cloud-Native Microservice Architecture
To solve these operational bottlenecks, Microsoft introduced Planning Optimization, an external microservice hosted in Microsoft Azure. Planning Optimization operates outside of the core ERP database runtime, delivering near-real-time performance.
+-----------------------------------------------------------------------------------+
| PLANNING OPTIMIZATION CLOUD MICROSERVICE ARCHITECTURE |
+-----------------------------------------------------------------------------------+
| |
| [ Dynamics 365 SCM Core ERP ] [ Azure Microservice ] |
| |
| +---------------------------+ +---------------------------+ |
| | Master Data & Transactions| | In-Memory High-Speed | |
| | - Released Products | | Calculation Cache | |
| | - Sales / Transfer Orders | --- Data Push ---> | | |
| | - Inventory On-Hand | (Change Tracking | - Multi-level BOM explode | |
| | - Coverage Settings | & Sync Engine) | - Net requirements logic | |
| +---------------------------+ | - Lead time scheduling | |
| +---------------------------+ |
| │ |
| +---------------------------+ │ |
| | Planned Orders & Pegging | <--- Result Stream --------------┘ |
| | - ReqPO (Purch / Prod) | (Delta Planned Orders |
| | - ReqTrans (Pegging) | written in seconds) |
| +---------------------------+ |
+-----------------------------------------------------------------------------------+
Architectural Characteristics and Performance Gains
- In-Memory Calculation: The planning algorithm runs entirely in high-speed cloud memory using optimized C++ microservices rather than executing recursive SQL stored procedures.
- Zero Transactional Locking: Because calculations occur in Azure microservice memory, master planning places no read or write locks on operational tables (such as
InventTrans,SalesLine, orPurchLine). Users can process shipments, post invoices, and register receipts while planning runs. - Near Real-Time Execution: Planning runs that previously required hours complete in seconds or minutes. Planners can execute intraday planning multiple times per day (e.g., hourly or upon receiving major customer orders) rather than waiting for nightly batch cycles.
- Deprecation of Classic Planning Engine: Microsoft has officially deprecated the classic built-in planning engine for cloud deployments. Transitioning to Planning Optimization is required for functional support and is heavily emphasized on the MB-330 certification exam.
Enabling Planning Optimization
- Prerequisites: Lifecycle Services (LCS) or Power Platform Admin Center environment management; installation of the Planning Optimization Add-in for Microsoft Dynamics 365 Supply Chain Management.
- Navigation:
Master planning > Setup > Planning Optimization > Planning Optimization parameters. - Toggle Use Planning Optimization to
Yes. The form includes a Fit Analysis tool that validates whether the active legal entity uses any specialized legacy features not yet supported by the microservice.
2. Master Planning Parameters and Master Plan Strategies
Global parameters dictate how master planning operates across legal entities and determine how planned orders are generated, numbered, and segregated.
- Navigation:
Master planning > Setup > Master planning parameters.
+-------------------------------------------------------------------------+
| MASTER PLANNING PARAMETERS OVERVIEW |
+-----------------------+-------------------------------------------------+
| Parameter Tab | Core Functional Configurations |
+-----------------------+-------------------------------------------------+
| General | Current static master plan, Current dynamic |
| | master plan, Master plan update mode |
+-----------------------+-------------------------------------------------+
| Number sequences | Number sequence codes for Planned purchase, |
| | Planned production, and Planned transfer orders |
+-----------------------+-------------------------------------------------+
| Standard update | Default update parameters for firming orders |
+-----------------------+-------------------------------------------------+
Static Plan vs. Dynamic Plan Strategy
Dynamics 365 SCM supports two primary master planning deployment models: a Single-plan strategy and a Two-plan strategy.
| Operational Dimension | Static Master Plan | Dynamic Master Plan |
|---|---|---|
| Primary Role | Operational execution baseline for buyers, production schedulers, and material controllers. | Real-time simulation and customer service order promising (Available to Promise / Capable to Promise). |
| Update Frequency | Regenerated periodically (e.g., once daily at night or start of shift) to prevent order nervousness. | Regenerated continuously or updated upon net change as new sales orders or inventory receipts arrive. |
| Planned Orders | Planned orders remain stable until planners review, modify, approve, or firm them. | Planned orders shift dynamically with every sales entry, reflecting immediate operational reality. |
| Firming Target | The plan from which actual Purchase Orders, Production Orders, and Transfer Orders are firmed. | Typically used strictly for scheduling insight and order promising rather than direct firming. |
Single-Plan vs. Two-Plan Configuration
- Two-Plan Strategy:
Current static master planis set to Plan A (e.g.,Static), andCurrent dynamic master planis set to Plan B (e.g.,Dynamic). When a sales representative checks delivery dates during customer order entry, the system evaluates the dynamic plan. Planners work out of the static plan to execute purchase and production orders without their workspace shifting mid-day. At the scheduled interval, the static plan can be copied from or refreshed by the dynamic plan. - Single-Plan Strategy: Both
Current static master planandCurrent dynamic master planpoint to the same master plan (e.g.,Plan-10). With the advent of Planning Optimization's extreme execution speed, Microsoft increasingly recommends the single-plan strategy for organizations that execute frequent, automated intraday regeneration runs, eliminating data duplication.
3. Coverage Groups and Coverage Codes
Coverage Groups categorize items according to their replenishment behavior, requirement grouping, and planning horizons. Every released product evaluated by master planning must belong to a coverage group (either inherited from item defaults or specified directly).
- Navigation:
Master planning > Setup > Coverage > Coverage groups.
The Four Coverage Codes
The Coverage code is the most critical setting on the coverage group, determining how net requirements calculate replenishment order quantities and timing:
+-------------------------------------------------------------------------+
| COVERAGE CODE COMPARISON |
+-------------+-----------------------------+-----------------------------+
| Coverage | Net Requirements Logic | Ideal Business Use Case |
| Code | | |
+-------------+-----------------------------+-----------------------------+
| Period | Aggregates all net demand | High-volume consumables, |
| | occurring within a defined | fasteners, raw materials |
| | period window into a single | with predictable vendor |
| | planned order. | delivery schedules. |
+-------------+-----------------------------+-----------------------------+
| Requirement | Generates a discrete 1:1 | High-cost components, MTO |
| | planned order for every | (Make to Order), custom |
| | single demand transaction. | sub-assemblies, traceable. |
+-------------+-----------------------------+-----------------------------+
| Min/max | When projected inventory | Safety stock buffers, retail|
| | dips below Minimum, orders | distribution replenishment, |
| | quantity up to Maximum. | standard shelf inventory. |
+-------------+-----------------------------+-----------------------------+
| Manual | Bypasses master planning; | Non-stocked supplies, MRO |
| | no planned orders are ever | items, obsolete items, or |
| | created automatically. | vendor-managed inventory. |
+-------------+-----------------------------+-----------------------------+
Detailed Behavior of Coverage Codes:
- Period:
- When demand occurs, master planning creates a planned order on the date of the first requirement. It then looks ahead by the number of days specified in the Coverage period field (e.g., 7 days).
- All subsequent demands occurring within that 7-day bucket are consolidated into that single planned order. The order quantity equals total demand across the period.
- Requirement (Lot-for-Lot):
- Master planning treats every requirement individually. If three sales orders require 10 units each on Friday, master planning creates three separate planned purchase/production orders of 10 units each.
- Maximizes pegging visibility and isolates customer order costs, but can cause order proliferation if used for generic fasteners or bulk liquids.
- Min/Max:
- Driven by two boundary values: Minimum (reorder trigger threshold) and Maximum (target stock ceiling).
- Calculation: When projected on-hand inventory drops below the Minimum level, master planning creates a planned order for:
Order Quantity = Maximum - Projected On-Hand.
- Manual:
- Excludes the item from automated calculation. The item appears in net requirements for informational visibility, but the engine will never generate planned purchase, production, or transfer orders.
4. Safety Stock Fulfillment Policies
Safety stock (minimum inventory) serves as a risk buffer against demand spikes and vendor delays. On the Coverage group FastTab Other, the Fulfill minimum parameter dictates when and with what priority master planning schedules replenishment to restore safety stock.
+-------------------------------------------------------------------------+
| SAFETY STOCK FULFILLMENT POLICY TIMING |
+-------------------------------+-----------------------------------------+
| Fulfill Minimum Setting | Master Planning Scheduling Logic |
+-------------------------------+-----------------------------------------+
| Today's date | Minimum inventory must be met today. |
| | Planned orders are dated today or lead- |
| | time constrained to earliest date. |
+-------------------------------+-----------------------------------------+
| Today's date + purchase time | Minimum inventory must be met on today's|
| | date PLUS the item's purchase lead time.|
| | Prevents unrealistic expedited orders. |
+-------------------------------+-----------------------------------------+
| First issue | Minimum inventory is fulfilled on the |
| | date of the first outbound transaction. |
| | Idle items do not trigger replenishment.|
+-------------------------------+-----------------------------------------+
| Coverage time fence | Minimum inventory is fulfilled on the |
| | last day of the coverage time fence. |
| | Low-priority long-term buffer. |
+-------------------------------+-----------------------------------------+
Strategic Analysis of Fulfillment Settings
- Today's date: If safety stock is breached, the system demands inventory immediately. If lead time prevents delivery today, master planning flags the planned order with a delay (or action message to expedite). This setting is essential for critical Class-A parts where zero stock is unacceptable.
- Today's date + purchase time: Acknowledges real-world vendor constraints. If an item has a 14-day purchase lead time, master planning schedules the safety stock replenishment for
Today + 14 days, eliminating artificial advance warnings and expediting alerts on routine stock breaches. - First issue: Ideal for seasonal or slow-moving items. If an item drops below safety stock in January, but no sales orders exist until April, master planning will not order inventory in January. It schedules receipt for the April date of the first issue, saving holding costs and working capital.
- Coverage time fence: Delays safety stock replenishment to the outer boundary of the planning horizon. Rarely used for finished goods; occasionally applied to long-horizon strategic raw materials.
5. Implementation Scenarios and Exam Traps
[!IMPORTANT] Exam Tip — Planning Optimization Microservice Prerequisites: On the MB-330 exam, if a scenario asks how to eliminate performance degradation during master planning runs without altering BOM complexity or purchasing hardware, the answer is installing and activating the Planning Optimization Add-in. Remember that Planning Optimization runs out-of-process in Azure memory and eliminates database locking.
[!WARNING] Exam Trap — Single vs. Two-Plan Order Promising: If an organization uses a two-plan strategy, sales order entry (ATP/CTP delivery date calculation) must point to the Dynamic master plan to reflect current open inventory transactions. If pointing to the static plan, delivery dates will be calculated against stale overnight data, leading to inaccurate promises to customers.
[!TIP] Best Practice — Coverage Group Assignment Hierarchy: Coverage settings follow a strict inheritance model: Item Coverage (Warehouse level) > Item Coverage (Site level) > Item Coverage (Item level) > Coverage Group > Master Plan default. Always configure broad policies on Coverage Groups, and reserve Item Coverage records exclusively for exceptions.
A multinational manufacturing company runs master planning nightly in Dynamics 365 Supply Chain Management. The current planning process takes over six hours to complete, causes severe SQL table locking, and prevents warehouse workers from registering inbound purchase order receipts during the batch window. Management requires that master planning run multiple times during the day without locking transactional tables or disrupting warehouse execution. Which solution should the functional consultant recommend?
A company produces custom industrial machinery using a Make to Order (MTO) manufacturing model. High-value engineered sub-assemblies are built specifically for individual customer orders and must never be combined or shared across different customer projects. Conversely, common hardware items like bolts, washers, and packaging boxes should be consolidated across all production jobs and ordered in weekly batches. Which combination of Coverage Codes should the functional consultant assign to the respective coverage groups?
A supply chain planner notices that master planning consistently generates planned purchase orders for safety stock replenishment with delivery dates scheduled for today, accompanied by urgent delay alerts and action messages to expedite. The supplier has a contractual lead time of 15 business days, making immediate delivery impossible. The planner wants master planning to automatically take supplier lead times into account when scheduling safety stock replenishment so that artificial delays and expediting warnings are eliminated. Which Safety stock fulfillment policy (Fulfill minimum) should be configured on the coverage group?