Inventory dimensions, costing and the warehouse-management transition
How AX 2012's storage and tracking dimension groups, item model groups, inventory close and warehouse-management architecture carry forward to D365 — including the structural break between legacy WMS I/II and current advanced warehouse management that the data upgrade cannot bridge.
What you will be able to do
Confirm which storage and tracking dimension group configurations are identity-mapped and which require post-upgrade validation
Explain how item model groups and costing methods carry forward structurally while the inventory-close algorithm has evolved
Describe the boundary between legacy warehouse management (WMS I/II) and current advanced warehouse management and what that means for a programme that used the older module
Trace on-hand inventory semantics through InventSum, InventTrans and InventDim and confirm their structural survival
Sequence inventory-position loading within the canonical wave model and identify the reconciliation gates
Introduction
Inventory is the domain where AX 2012's same-lineage advantage is most visible on the surface and most deceptive beneath it. The tables are the same: InventDim, InventTrans, InventSum, InventTable, InventModelGroup, EcoResStorageDimensionGroup. The key structures are the same: ItemId + InventDimId identifies an on-hand position;
Storage and tracking dimension groups
Storage dimension groups define which dimensions describe where stock is held. In AX 2012, the storage dimensions available were:
Item model groups and costing methods
Item model groups define the costing method and inventory-posting behaviour for each released product. The supported costing methods in both AX 2012 and D365 are:
The warehouse-management boundary
Basic warehousing (WMS I) carries forward without structural change. Products tracked by site and warehouse only continue to work exactly as they did. No redesign is needed.
On-hand inventory: tables and semantics
InventDim. A dimension-combination table. Each row holds a unique combination of dimension values (site, warehouse, location, batch, serial, licence plate, inventory status, owner). Rows are identified by a surrogate key (InventDimId). The table grows as new combinations are encountered.
Reconciliation and validation
For Mode A (in-place upgrade), the comparison is simpler: AX 2012 pre-upgrade on-hand versus D365 post-upgrade on-hand. The check is still required — the data upgrade occasionally encounters data issues (orphaned InventDim references, zero-quantity records, dimension mismatches) that cause records to be excluded silently.
Wave sequencing for inventory
Inventory positions are canonical Wave 4 in this site's eight-wave model. The dependency chain:
Knowledge check
Summary
Inventory is the domain where same-lineage fidelity is highest at the record level and most deceptive at the behaviour level. The tables, keys and relationships survive the data upgrade intact.