Study guide

18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages

Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Product Master and Released Products

1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups

2 Chapter 2: Bills of Materials (BOM) and Formulas

2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling

3 Chapter 3: Product Prerequisites and Dimension Groups

3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups

4 Chapter 4: Additional Product Details and Warehouse Fit

4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions

5 Chapter 5: Inventory Costing and Pricing

5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding

6 Chapter 6: Inventory Journals and Core Transactions

6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals

7 Chapter 7: Inventory Operations, Blocking, and Closing

7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification

8 Chapter 8: Quality Management and Nonconformance

8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders

9 Chapter 9: Asset Management: Setup and Maintenance

9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption

10 Chapter 10: Procurement and Sourcing Configuration

10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal

11 Chapter 11: Purchase Order Lifecycle and Consignment

11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders

12 Chapter 12: Landed Cost and Inbound Logistics

12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances

13 Chapter 13: Sales Management and Order Processing

13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates

14 Chapter 14: Warehouse Setup and Core Infrastructure

14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences

15 Chapter 15: Warehouse Execution Processes

15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization

16 Chapter 16: Transportation Management and Logistics

16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation

17 Chapter 17: Warehouse Management Mobile App

17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation

18 Chapter 18: Master Planning and Planning Optimization

18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management

18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages

Key Takeaways Explain This Topic AI

Item coverage overrides broad Coverage group rules at the released product level, enabling discrete minimum/maximum, lead time, and planned order types per Site and Warehouse.

Positive days dictate how far into the future on-hand inventory or incoming receipts can satisfy upcoming demand; Negative days specify how long master planning will wait for an existing scheduled receipt before creating a duplicate planned order.

Time fences define planning horizons: Coverage fence calculates requirements, Freeze fence locks planned orders, Firming fence auto-converts planned orders, and Explode fence governs multi-level BOM explosion.

Action messages generate real-time operational advice (Advance, Postpone, Increase, Decrease) to align existing purchase, production, and transfer orders with fluctuating demand.

Period templates divide the planning horizon into structured time buckets (days, weeks, months) for consolidated supply and demand visualization in Net Requirements and Supply Schedule forms.

Last updated: September 2026

18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages

Quick Answer: While Coverage groups define baseline planning policies across groups of items, Item coverage ( Product information management > Released products > Plan tab > Item coverage ) allows supply chain consultants to override parameters at the discrete product, site, and warehouse levels. Master planning schedules supply by evaluating Positive days (how long existing inventory can satisfy future demand) and Negative days (how long master planning will wait for an open receipt before generating a new order). Time fences establish execution horizons (Coverage, Freeze, Firming, Explode, Capacity, Action messages), while Action messages recommend advancing, postponing, increasing, or decreasing existing orders.

1. Item Coverage Architecture and Hierarchy

Organizations rarely maintain uniform replenishment rules across all distribution nodes. A product distributed from a central warehouse may require a Min/max policy with a 30-day coverage horizon, while regional transit cross-docks operate on a strict 2-day Requirement basis.

Item Coverage Configuration

Navigation : Product information management > Released products > Plan tab > Item coverage .

Item coverage records are created for specific combinations of inventory dimensions (typically Site and Warehouse ). +-------------------------------------------------------------------------+

  • | ITEM COVERAGE HIERARCHY |
  • +-------------------------------------------------------------------------+
  • | 1. Item Coverage: Specific Item + Site + Warehouse (Highest Priority) |
  • | │ |
  • | ▼ |
  • | 2. Item Coverage: Specific Item + Site (All Warehouses in Site) |
  • | │ |
  • | ▼ |
  • | 3. Item Coverage: Specific Item (All Sites / Global Item Level) |
  • | │ |
  • | ▼ |
  • | 4. Coverage Group assigned to Released Product |
  • | │ |
  • | ▼ |
  • | 5. Master Plan Default Coverage Settings (Lowest Priority) |
  • +-------------------------------------------------------------------------+
  • Core Overrides on Item Coverage

General FastTab : Override the default Coverage group, Coverage code, and Minimum/Maximum inventory levels.

Planned Order Type : Specify whether master planning should generate a Planned purchase order , Planned production order , or Planned transfer order for that specific warehouse.

Replenishment Warehouse : When Planned transfer order is selected, define the source shipping warehouse (e.g., Warehouse 11 transfers stock from Warehouse 10).

Lead Time Overrides : Specify warehouse-specific purchase, production, or transfer lead times.

2. Mechanics of Positive Days vs. Negative Days

The interaction between Positive Days and Negative Days represents one of the most mathematically critical concepts on the MB-330 exam. Both settings can be defined on Coverage groups or overridden on Item coverage. +-------------------------------------------------------------------------+

  • | POSITIVE DAYS VS. NEGATIVE DAYS |
  • +-------------------+-----------------------------------------------------+
  • | Parameter | Operational Definition & Impact |
  • +-------------------+-----------------------------------------------------+
  • | Positive Days | The number of days into the future that on-hand |
  • | | inventory or expected receipts can satisfy a demand |
  • | | requirement before master planning creates a new |
  • | | planned order. Defines receipt viability. |
  • +-------------------+-----------------------------------------------------+
  • | Negative Days | The number of days past a requirement date that |
  • | | master planning will accept an existing scheduled |
  • | | receipt (e.g., purchase order) rather than ordering |
  • | | an expedited, duplicate planned order. |
  • +-------------------+-----------------------------------------------------+
  • Mathematical Deep Dive: Negative Days and the Duplicate Order Trap

Consider a company with the following scenario:

  • Today : January 1
  • Demand : Sales order for 100 units required on January 10

Existing Supply : Open Purchase Order for 100 units scheduled to arrive on January 14 (4 days late relative to the demand)

  • Purchase Lead Time : 5 days Timeline: Today (Jan 1) -------- Demand (Jan 10) ---- PO Receipt (Jan 14)
  • ▲ ▲
  • └────── 4 Days ───────┘
  • Outcome A: Negative Days = 5 (Greater than the 4-day delay)

Master planning evaluates the gap: Delay = 4 days . Because Negative days (5) >= Delay (4) , master planning considers the existing Purchase Order acceptable.

Result : Master planning does not create a new planned purchase order. It pegs the sales order to the existing PO arriving on January 14 and generates an Action message (Advance) requesting the buyer pull the PO delivery date forward to January 10.

Outcome B: Negative Days = 2 (Less than the 4-day delay)

Master planning evaluates the gap: Negative days (2) < Delay (4) . The existing PO is deemed too late to fulfill the demand.

Result : Master planning creates a NEW Planned Purchase Order for 100 units to meet the demand on January 10 (or earliest lead-time date). The existing PO of 100 units arriving January 14 remains open as excess inventory!

Consequence : The organization now has 200 units of supply for 100 units of demand. Setting negative days too low causes widespread duplicate planned orders and excess inventory accumulation.

Note

Dynamic Negative Days in Planning Optimization : Planning Optimization can calculate dynamic negative days by comparing the item's purchase lead time against the scheduled arrival. If the scheduled receipt arrives sooner than placing a brand-new order from scratch, the existing receipt is used, preventing duplicate orders.

3. Master Planning Time Fences

Time fences establish operational horizons (expressed in days from today's date) that regulate what master planning is allowed to calculate, lock, or execute. Time fences can be configured on the Master Plan , the Coverage Group , or the Item Coverage record. +-----------------------------------------------------------------------------------+

  • | MASTER PLANNING TIME FENCES |
  • +-----------------------------------------------------------------------------------+
  • | [ Today ] ──► [ Freeze ] ──► [ Firming ] ──► [ Explode ] ──► [ Coverage Fence ] |
  • | │ │ │ │ │ |
  • | │ No changes Auto-convert Explode BOMs Net requirements |
  • | │ permitted planned orders down levels horizon ends |
  • +-----------------------------------------------------------------------------------+
  • Comprehensive Time Fence Reference

Time Fence Primary Purpose What Happens Inside Fence What Happens Outside Fence

Coverage time fence Defines the total planning horizon. Master planning calculates net requirements, evaluates demand, and generates planned orders. Demand (sales orders, forecasts) is completely ignored by master planning.

Freeze time fence Prevents system nervousness and preserves planned schedule stability. Existing planned orders cannot be deleted, rescheduled, or modified by regeneration runs. Master planning dynamically reschedules and adjusts planned orders as demand shifts.

Firming time fence Automates transition from planning to execution. Planned orders are automatically converted (firmed) into actual Purchase Orders, Production Orders, or Transfer Orders during batch runs. Planned orders remain suggestions awaiting planner intervention.

Explode time fence Governs multi-level Bill of Materials (BOM) decomposition. Production BOMs are exploded down through all sub-assembly levels, creating planned orders for raw materials. Sub-assemblies are treated as purchased/discrete end-items; lower BOM levels are not exploded.

Capacity time fence Controls finite resource capacity scheduling. Production orders are scheduled against actual finite resource capacity and resource group limits. Production orders are scheduled assuming infinite capacity .

Action message fence Generates operational rescheduling recommendations. Master planning generates Advance, Postpone, Increase, and Decrease action messages. No action messages are generated, reducing notification clutter.

4. Action Messages and Margin Tolerances

As business conditions shift, existing purchase orders, production orders, and transfer orders can drift out of alignment with customer demand dates. Rather than creating new orders, master planning issues Action Messages advising planners how to synchronize existing supply.

Navigation : Master planning > Setup > Coverage > Coverage groups > Action message tab . +-------------------------------------------------------------------------+

  • | ACTION MESSAGE TYPES |
  • +-------------+-----------------------------------------------------------+
  • | Action Type | Operational Meaning & Business Trigger |
  • +-------------+-----------------------------------------------------------+
  • | Advance | Move the delivery date of an existing open order forward |
  • | | (earlier) to satisfy an expedited demand or avoid stockout|
  • +-------------+-----------------------------------------------------------+
  • | Postpone | Delay the delivery date of an existing open order to |
  • | | prevent carrying unnecessary inventory holding costs. |
  • +-------------+-----------------------------------------------------------+
  • | Increase | Increase the order quantity on an existing order to cover |
  • | | newly created demand without issuing a new order. |
  • +-------------+-----------------------------------------------------------+
  • | Decrease | Reduce the order quantity on an existing order to avoid |
  • | | over-stocking caused by cancelled customer demand. |
  • +-------------+-----------------------------------------------------------+
  • Action Message Tolerances and Margins

To prevent planners from suffering alert fatigue from minor, inconsequential date shifts, consultants configure Action message margins :

Advance margin : Minimum number of days an order must be advanced before generating an action message. If Advance margin is set to 2 days, a 1-day advance requirement will not trigger an alert.

Postpone margin : Minimum number of days an order must be delayed before recommending postponement.

Basis : Action messages can be calculated based on Requirement date , End of coverage period , or Today's date .

5. Period Templates

Period templates segment the continuous master planning timeline into discrete visual time buckets (e.g., daily buckets for the first 2 weeks, weekly buckets for the next 2 months, and monthly buckets for the remainder of the year).

Navigation : Master planning > Setup > Coverage > Period templates .

Structure and Application

Planners define a sequence of periods with specific period lengths: Day , Week , Month , Quarter , or Year .

Where Used : Period templates govern the time-phased grid displays in the Supply Schedule , Net requirements , and Capacity reservations forms.

Operational Benefit : Provides executive and material planners with clear visibility into projected on-hand balances, aggregated gross requirements, and scheduled receipts without scrolling through thousands of individual transaction lines.

6. Implementation Scenarios and Exam Traps

Important

Exam Tip — The Negative Days Duplicate Order Trap: Whenever an MB-330 exam question presents an issue where "master planning generates unnecessary duplicate planned purchase orders even though open purchase orders already exist for the required items," immediately inspect the Negative days parameter. If Negative days is smaller than the supplier delivery delay, master planning assumes the existing order is invalid and generates a redundant order.

Warning

Exam Trap — Freeze vs. Firming Time Fences: Do not confuse Freeze with Firming. The Freeze time fence freezes planned orders as untouchable planned orders (status remains planned, but regeneration cannot alter them). The Firming time fence converts planned orders into actual transactional documents (Purchase Orders or Production Orders).

Tip

Best Practice — Explode Time Fence Tuning: Keep the Explode time fence shorter than the total Coverage time fence for complex manufacturing BOMs. Exploding 10-level BOMs out 365 days severely degrades planning performance and clutters raw material schedules with speculative requirements.