Study guide
3.3 Reservation Hierarchies and Unit Sequence Groups
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
3.3 Reservation Hierarchies and Unit Sequence Groups
Key Takeaways Explain This Topic AI
Reservation hierarchies separate high-level commercial reservations (dimensions above Location) from granular physical warehouse allocations (dimensions below Location), eliminating the legacy bin-locking bottleneck.
In advanced Warehouse Management (WMS), Site, Warehouse, and Inventory status are strictly mandatory above Location, while Location and License plate must always remain below Location.
A Batch-Above reservation hierarchy requires batch selection at sales order entry to satisfy customer-mandated specifications, whereas Batch-Below defers batch selection until warehouse wave release to automate FEFO/FIFO picking.
Unit sequence groups establish the packaging hierarchy (e.g., Each -> Box -> Pallet) and determine which packaging units generate and track distinct license plate handling units.
A reservation hierarchy can only be assigned to a released product if its storage dimension group has 'Use warehouse management processes' enabled, and the hierarchy cannot be modified once inventory transactions exist.
Last updated: September 2026
3.3 Reservation Hierarchies and Unit Sequence Groups
Note
In advanced Warehouse Management (WMS), inventory allocation cannot function like legacy ERP systems. Reserving inventory at sales order entry cannot lock specific physical storage bins or pallets weeks before shipment. To decouple commercial order promises from granular floor execution, Dynamics 365 Supply Chain Management utilizes Reservation Hierarchies ( Warehouse management > Setup > Inventory > Reservation hierarchy ) and Unit Sequence Groups ( Warehouse management > Setup > Units > Unit sequence groups ).
The Architecture of Reservation Hierarchies: Solving "Bin-Locking"
In legacy warehouse management, when a sales order line reserved 50 units of an item, the system immediately reserved a specific Location (e.g., Aisle 04, Shelf 02, Bin 01) and a specific License plate (pallet). This created the infamous "bin-locking" problem :
Forklift drivers could not consolidate or replenish inventory in that bin because the stock was reserved.
Other urgent customer orders could not pick from that bin, even if the reserved order was not scheduled to ship for another three weeks.
Warehouse floor agility was crippled.
The Reservation Hierarchy Solution
A Reservation Hierarchy defines the exact sequence in which inventory dimensions are reserved during the order lifecycle. It splits dimensions into two structural zones: Dimensions Above Location and Dimensions Below Location : +---------------------------------------------------------------------------------+
- | RESERVATION HIERARCHY ARCHITECTURE |
- +---------------------------------------------------------------------------------+
- | DIMENSIONS ABOVE LOCATION |
- | - Reserved at: Sales Order Entry / Order Promising / Master Planning |
- | - Scope: Site, Warehouse, Inventory status (and Batch if Batch-Above) |
- | - Role: Guarantees commercial availability without locking physical bins |
- +---------------------------------------------------------------------------------+
- | ========================= PHYSICAL LOCATION BOUNDARY ======================== |
- +---------------------------------------------------------------------------------+
- | DIMENSIONS BELOW LOCATION |
- | - Reserved at: Wave Processing / Work Creation / Mobile Device Picking |
- | - Scope: Location, License plate (and Batch if Batch-Below) |
- | - Role: Determines optimal picking bin via Location Directives & FEFO/FIFO |
- +---------------------------------------------------------------------------------+
- Mandatory Dimension Placement Rules
Above Location (Mandatory Minimum) :
- Site
- Warehouse
Inventory status Rationale : The sales order must know which geographical site and facility will fulfill the shipment, and must reserve stock with an Available inventory status rather than blocked or damaged stock.
Below Location (Mandatory Minimum) :
Location
License plate Rationale : Location directives allocate the specific bin when the wave executes. License plate represents the physical carrier or pallet, which is scanned or confirmed dynamically by the warehouse picker.
Architectural Invariants : Site, Warehouse, and Inventory status can never be moved below Location. License plate and Location can never be moved above Location.
Batch-Above vs. Batch-Below Reservation Hierarchies
When tracking perishable, chemical, or regulated goods with batch numbers, the consultant must make a critical architectural decision: Should Batch number reside Above Location or Below Location ?
Architectural Attribute Batch-Above Location Batch-Below Location
Hierarchy Sequence Site > Warehouse > Status > Batch > Location > LP Site > Warehouse > Status > Location > Batch > LP
Reservation Timing Sales Order Entry / Document Creation Wave Processing / Work Execution / Picking
Order Taker Experience Must specify or reserve a batch on the sales line Reserves quantity; no batch required at order entry
Primary Business Driver Customer-mandated batches, specific potency/formula Automated warehouse optimization, FIFO/FEFO picking
Picking Flexibility Picker is strictly directed to the reserved batch Location directives dynamically pick earliest expiry
Order Promising (ATP) Can promise against a specific batch lifecycle Promises against aggregate warehouse available stock
1. Batch-Above Location Use Cases
Contractual Specifications : An aerospace or defense customer contracts to purchase titanium fasteners exclusively from melt-lot B-9021 .
Potency / Active Pharmaceutical Ingredient (API) : A pharmaceutical customer requires an exact chemical concentration available only in batch LOT-441 .
Customer Approval : The customer inspects and pre-approves batch samples prior to shipment.
2. Batch-Below Location Use Cases
Fast-Moving Consumer Goods (FMCG) : Retail grocery distribution where the customer wants 100 cases of milk, but does not care which batch number is shipped, provided it meets shelf-life requirements.
Automated FEFO (First Expired, First Out) : The sales rep reserves 100 units at Site 1, Warehouse 24, Status Available. When the order is released to the warehouse, the Wave processing engine and Location directives (configured with the Batch FEFO strategy) evaluate all inventory in the warehouse and automatically assign picking work from the bin containing the earliest-expiring batch.
Unit Sequence Groups and Handling Units
Advanced WMS requires knowing how items are packaged and handled on the warehouse floor. Unit Sequence Groups ( Warehouse management > Setup > Units > Unit sequence groups ) define the hierarchy of packaging units and determine which handling units generate unique license plates. +---------------------------------------------------------------------------------+
- | UNIT SEQUENCE GROUP PACKAGING HIERARCHY |
- +---------------------------------------------------------------------------------+
- | PALLET (PL) -> 50 Cases / 600 Eaches | [X] License Plate Grouping enabled |
- | ^ | (Each pallet receives a distinct LP) |
- | | |
- | CASE (CS) -> 12 Eaches | [ ] License Plate Grouping disabled |
- | ^ | (Cases move as un-grouped cartons) |
- | | |
- | EACH (EA) -> Base Inventory Unit | [ ] License Plate Grouping disabled |
- | | (Smallest measurable unit) |
- +---------------------------------------------------------------------------------+
- 1. Structure and Ordering Rules
A unit sequence group defines an ordered sequence from the smallest handling unit (Base unit) to the largest handling unit (e.g., Each -> Box -> Case -> Pallet ).
Every unit transition requires an active Unit conversion record ( Product information management > Setup > Units > Unit conversions ) defining the mathematical relationship (e.g., 1 Box = 10 Eaches; 1 Pallet = 50 Boxes).
2. License Plate Grouping Parameter
The License plate grouping checkbox on a unit sequence group line controls physical containerization:
If checked on the Pallet unit, the system treats a pallet as a discrete handling unit requiring a dedicated License Plate ID upon receipt or movement.
If unchecked on the Case and Each units, workers can pick individual cases or eaches from a pallet without generating new license plate identifiers for each individual box, preventing license plate table bloat.
3. Mobile Device Work Execution Impacts
Unit Restrictability : Mobile device menu items can restrict picking or receiving to specific units defined in the sequence group (e.g., full pallet receiving vs. case break picking).
Replenishment : Min/Max replenishment templates use unit sequence groups to trigger replenishment work in full pallet increments from bulk storage to case-pick forward locations.
Hierarchy Association and Maintenance Rules
Association : A reservation hierarchy is assigned to a released product on the Warehouse management FastTab ( Product information management > Products > Released products ).
Validation : The system validates that the item's storage dimension group has Use warehouse management processes enabled, and that all tracking dimensions enabled on the tracking dimension group are included in the reservation hierarchy.
Immutability : Once inventory transactions ( InventTrans ) have been posted for an item, its reservation hierarchy cannot be modified or changed through standard UI forms. Changing a hierarchy requires zeroing out all on-hand inventory, canceling open warehouse work, or running data upgrade scripts.
Exam Watch: Critical Traps and Configuration Tips
Warning
Trap 1 : Placing Batch number above Location for standard retail items. If you assign a Batch-Above hierarchy to standard goods, sales order entry operators will be forced to manually select or auto-reserve specific batches at order entry, breaking automatic FEFO wave allocation!
Trap 2 : Attempting to put License plate above Location. License plates represent physical containers located within a warehouse location; placing License plate above Location violates D365 SCM core schema rules.
Trap 3 : Forgetting unit conversions before creating unit sequence groups. A unit sequence group cannot be saved or assigned to an item if valid unit conversions between all sequence levels do not exist.
Trap 4 : Changing reservation hierarchies on active items. On the exam, if a question asks how to switch an active item from Batch-Above to Batch-Below, the answer involves closing open transactions and zeroing on-hand inventory, not simply changing a dropdown on the released product form.