3.1 Product, Storage, and Tracking Dimension Groups
Key Takeaways
- Product dimensions define item variants (Configuration, Size, Color, Style, Version), Storage dimensions establish physical and logical location hierarchy (Site, Warehouse, Location, Inventory status, License plate), and Tracking dimensions govern traceability and ownership (Batch number, Serial number, Owner).
- The 'Financial inventory' parameter determines the costing boundary; enabling it tracks costs, running averages, and inventory settlements per dimension value (e.g., per warehouse), whereas disabling it pools inventory costs across dimension values (e.g., across warehouses within a site).
- Enabling 'Use warehouse management processes' on a storage dimension group requires Site, Warehouse, Location, Inventory status, and License plate to be active, and mandates assigning a reservation hierarchy to released products.
- Serial numbers can be registered at receipt, at issue, or specifically during sales picking, where sales picking capture eliminates scanning overhead during inbound receiving and internal bin transfers.
- Tracking number groups automate batch number generation via number sequences and calculate expiration, best-before, and shelf-advice dates from manufacturing dates and item shelf life parameters.
3.1 Product, Storage, and Tracking Dimension Groups
[!NOTE] In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), inventory dimensions provide the structural backbone for tracking item variations, physical storage locations, costing boundaries, and regulatory traceability. Every transaction recorded in the inventory transaction table (
InventTrans) carries an inventory dimension identifier (InventDimId) pointing to a unique combination of product, storage, and tracking dimensions.
The Three Dimension Groups: Architecture and Scope
Dynamics 365 Supply Chain Management categorizes inventory dimensions into three distinct groups. A released product inherits its operational behavior by associating with one group from each category:
- Product Dimension Groups (
Product information management > Setup > Dimension and variant groups > Product dimension groups) - Storage Dimension Groups (
Product information management > Setup > Dimension and variant groups > Storage dimension groups) - Tracking Dimension Groups (
Product information management > Setup > Dimension and variant groups > Tracking dimension groups)
+---------------------------------------------------------------------------------+
| RELEASED PRODUCT |
+------------------------+--------------------------------+-----------------------+
| |
v v
+----------------------------------+ +-------------------------------------------+
| STORAGE DIMENSION GROUP | | TRACKING DIMENSION GROUP |
| - Site, Warehouse, Location | | - Batch number, Serial number, Owner |
| - Inventory status, License plate| | - Capture at receipt/issue/sales picking |
| - WMS processes flag | | - Shelf life & expiration calculation |
+----------------------------------+ +-------------------------------------------+
|
v (If Product Master)
+---------------------------------------------------------------------------------+
| PRODUCT DIMENSION GROUP |
| - Configuration, Size, Color, Style, Version |
| - Defines variant combinations and Engineering Change Management revisioning |
+---------------------------------------------------------------------------------+
1. Product Dimensions
Product dimensions define physical and functional variations of a product master. When assigned to a product master, they enable the creation of Product Variants. The five supported product dimensions are:
- Configuration (
ConfigId): Distinguishes functional or structural alternatives (e.g., standard vs. deluxe electronics). - Size (
InventSizeId): Captures dimensional variations (e.g., Small, Medium, Large, or numeric dimensions). - Color (
InventColorId): Identifies aesthetic or material color variations. - Style (
InventStyleId): Distinguishes design cuts or fashion models. - Version (
InventVersionId): Activated primarily through Engineering Change Management (ECM). It allows discrete manufacturers to enforce revision control, track engineering change orders (ECOs), and manage distinct lifecycles for successive iterations of a manufactured item.
2. Storage Dimensions
Storage dimensions specify the physical and logical location hierarchy where inventory is received, stored, picked, and issued. The five storage dimensions are:
- Site (
InventSiteId): The top-level physical, geographical, or operational entity. In multi-site setups, Site is mandatory and represents an independent operational and costing boundary. - Warehouse (
InventLocationId): A physical or virtual facility nested under a single Site. - Location (
wmsLocationId): The exact bin, rack, shelf, or floor staging area inside a warehouse. - Inventory status (
InventStatusId): A logical classification in advanced Warehouse Management (WMS) indicating commercial availability (e.g., Available, Damaged, Quality Hold, Blocked). - License plate (
LicensePlateId): A unique mobile tracking identifier assigned to a pallet, container, box, or tote in advanced WMS.
3. Tracking Dimensions
Tracking dimensions enforce legal custody, batch traceability, and serialized equipment management. The three tracking dimensions are:
- Batch number (
InventBatchId): Identifies a distinct production run, lot, or chemical formulation. - Serial number (
InventSerialId): Assigns an individual, unique identity to each physical piece of inventory. - Owner (
InventOwnerId_RU): Identifies the legal owner of goods, critical in Consignment Inventory where vendor-owned stock resides in a company warehouse prior to consumption.
Dimension Parameters and Tracking Behaviors
Each dimension row within a dimension group exposes configuration checkboxes that govern system behavior:
| Parameter | Description | Operational Impact |
|---|---|---|
| Active | Activates the dimension in the inventory subsystem. | The dimension is tracked in InventTrans and must be validated across transactional tables. |
| Active in sales process | Activates tracking on sales lines only. | Enables entering dimension values (such as serials) on sales orders without tracking physical inventory in warehouse bins. |
| Active in purchase process | Activates tracking on purchase lines only. | Captures vendor batch or serial information on inbound documents without maintaining internal subledger tracking. |
| Active in transfer process | Activates tracking on transfer orders. | Allows recording tracking numbers during transit without requiring granular bin-level tracking at receiving. |
| Physical inventory | Tracks on-hand quantity per dimension. | Maintained in InventSum. The system verifies physical availability and enforces physical negative inventory controls at this dimension level. |
| Financial inventory | Segregates inventory valuation and costing. | Running average costs, standard costs, and Inventory Close settlements are calculated independently per dimension value. |
| Coverage plan by dimension | Master planning (MRP/Planning Optimization) scope. | Master planning calculates gross requirements and generates planned purchase/production orders per dimension value. |
| Blank receipt allowed | Permits receipt posting without a dimension value. | If checked, an item can be received without specifying this dimension (e.g., unassigned location). |
| Blank issue allowed | Permits issue posting without a dimension value. | If checked, an item can be picked/shipped without specifying this dimension. |
Physical vs. Financial Inventory: Critical Costing Impacts
On the MB-330 exam, understanding the Financial inventory flag is essential. While Physical inventory controls whether on-hand stock quantities are tracked in InventSum per dimension, Financial inventory dictates how cost prices are calculated and settled.
Cost Pooling vs. Cost Segregation
Consider an organization operating two warehouses (Warehouse 11 and Warehouse 12) under Site 1:
SCENARIO A: Financial Inventory Enabled at Warehouse Level
+-------------------------------------------------------------------------+
| Site 1 |
| +------------------------------+ +-------------------------------+ |
| | Warehouse 11 | | Warehouse 12 | |
| | On-hand: 100 pcs @ $10/unit | | On-hand: 50 pcs @ $14/unit | |
| | Financial Cost Pool: $1,000 | | Financial Cost Pool: $700 | |
| +------------------------------+ +-------------------------------+ |
+-------------------------------------------------------------------------+
Result: Distinct running average cost prices. Transferring 10 units from
Warehouse 11 to Warehouse 12 creates financial ledger adjustments.
SCENARIO B: Financial Inventory Disabled at Warehouse Level (Site Only)
+-------------------------------------------------------------------------+
| Site 1 (Single Unified Cost Pool) |
| Total On-hand: 150 pcs | Total Valuation: $1,700 | Average Cost: $11.33 |
| +------------------------------+ +-------------------------------+ |
| | Warehouse 11 (100 pcs) | | Warehouse 12 (50 pcs) | |
| | Cost: $11.33/unit | | Cost: $11.33/unit | |
| +------------------------------+ +-------------------------------+ |
+-------------------------------------------------------------------------+
Result: Both warehouses share an identical cost price. Transferring units
between Warehouse 11 and 12 produces $0 financial adjustment.
- Site Level: The Site dimension must always have Financial inventory enabled. Cost pooling cannot cross sites.
- Warehouse Level: If Financial inventory is unchecked, costs are pooled at the Site level. Moving goods between warehouses on the same site produces zero financial variance and generates no financial inventory settlements during Inventory Close.
- Location and License Plate: D365 SCM strictly prohibits enabling Financial inventory for Location or License plate. Tracking financial cost pools at the individual bin or pallet level would cause exponential ledger table bloat and performance degradation.
The "Use Warehouse Management Processes" (WMS) Flag
Located on the Storage Dimension Group (Product information management > Setup > Dimension and variant groups > Storage dimension groups), the Use warehouse management processes toggle switches an item from basic warehouse handling to advanced Warehouse Management (WMS / WAX):
- Mandatory Dimension State: Once enabled, the storage dimension group enforces that Site, Warehouse, Inventory status, Location, and License plate must all be marked as Active.
- Blank Rules:
Blank receipt allowedandBlank issue allowedare locked to disabled for Location and License plate, ensuring absolute inventory integrity. - Reservation Hierarchy Prerequisite: Every released product associated with a WMS-enabled storage dimension group must have a Reservation Hierarchy assigned before transactions can be created.
- Immutability Warning: Once an item has associated inventory transactions (
InventTrans), its storage dimension group cannot be switched from non-WMS to WMS (or vice versa) through standard form edits. Administrators must execute the specialized Enable warehouse management processes migration utility.
Serial Number Registration Strategies
Tracking high-value items via serial numbers introduces warehouse scanning overhead. D365 SCM provides three operational strategies on the Tracking Dimension Group:
+---------------------------------------------------------------------------------+
| SERIAL NUMBER CAPTURE STRATEGIES |
+-----------------------+---------------------------------+-----------------------+
| 1. Capture at Receipt | 2. Capture at Issue | 3. Sales Picking |
| - Serial scanned at | - Serial scanned at packing | - Serial scanned only |
| dock upon PO | slip or production pick. | during outbound |
| receiving. | - Inbound receiving unburdened. | sales picking work. |
| - Full traceability | - Requires blank receipt | - Zero scanning on |
| through every bin. | allowed. | inbound/internal. |
+-----------------------+---------------------------------+-----------------------+
- Capture at Receipt: The serial number must be entered or scanned when goods first enter the warehouse (purchase order product receipt, production report-as-finished). This provides end-to-end traceability but slows dock receiving.
- Capture at Issue: Goods are received without serial numbers (
Blank receipt allowed = Yes). Serial numbers are registered only when items are issued from inventory. - Capture during Sales Picking: Serial numbers are captured specifically when warehouse workers execute sales picking work via the Warehouse Management mobile app or confirm a sales packing slip. Inbound receiving, internal transfers, cycle counting, and replenishment proceed without scanning individual serials, protecting warehouse throughput while fulfilling customer warranty tracking.
Batch Number Groups and Shelf Life Management
Tracking number groups (Inventory management > Setup > Dimensions > Tracking number groups) automate batch numbering and date calculations for perishable and regulated goods.
1. Number Sequence vs. Manual Batch Generation
- Manual: Workers must manually key in vendor batch numbers upon arrival.
- Automatic: When linked to a number sequence code, D365 SCM automatically assigns a unique batch ID when purchase orders are received, transfer orders arrive, or production orders are created.
- Only for inventory transactions: Restricts automatic batch generation to physical inventory movements rather than sales quotation lines.
2. Shelf Life Date Calculations
Perishable goods require dynamic date calculation based on manufacturing dates. In the released product form (Manage inventory FastTab), four shelf life parameters operate in conjunction with batch groups:
- Shelf life period in days: Defines the operational lifespan. After this date, the batch cannot be reserved or sold.
- Shelf advice period in days: Triggers quality re-testing or vendor inspection before expiration.
- Best before period in days: Alerts order processing that the product has passed peak quality.
- Batch disposition codes: Applied manually or automatically to a batch. A disposition code specifies whether inventory with that code is Available or Blocked for reservation, picking, or master planning.
Exam Watch: Critical Traps and Configuration Tips
[!WARNING]
- Trap 1: Believing Location or License plate can have Financial inventory enabled. They cannot. Only Site, Warehouse, and Product dimensions can participate in financial inventory valuation.
- Trap 2: Confusing Active in sales process with true serial inventory tracking. Marking a tracking dimension as active only in the sales process records the number on the sales order document, but does not track inventory quantity or valuation in
InventTrans.- Trap 3: Forgetting the WMS prerequisite. You cannot assign a WMS-enabled storage dimension group to a product without also assigning a Reservation Hierarchy.
- Trap 4: Assuming an inter-warehouse transfer always posts financial ledger adjustments. If Financial inventory is unchecked on the Warehouse dimension, inter-warehouse transfers within the same site produce zero financial adjustments.
A distribution company operates two warehouses under a single physical site: Warehouse 11 (Main Logistics Hub) and Warehouse 12 (Express Delivery Center). The finance director discovers that when items are transferred between Warehouse 11 and Warehouse 12, no financial ledger entries are created and the cost price remains identical across both facilities. The business requires each warehouse to maintain its own independent cost price and inventory close valuation. How must the Storage Dimension Group be configured to achieve this requirement?
A wholesale distributor of high-end commercial electronics wants to capture serial numbers only during sales order fulfillment to verify warranty registration upon customer delivery. The warehouse director mandates that receiving dock workers and putaway forklift operators must not be prompted to scan or register serial numbers during purchase order receipts or internal warehouse transfers. How should the Tracking Dimension Group be configured?
A food and beverage manufacturer packages perishable ingredients with a 180-day shelf life. The quality assurance team requires that whenever a purchase order product receipt or production order report-as-finished journal is posted, the system must automatically generate a batch number from a dedicated sequence and calculate the batch expiration date as exactly 180 days after the manufacturing date. Which configuration combination is required to satisfy this requirement?