How to carry a QAD inventory position into D365 at full dimension granularity while keeping valuation defensible and lot and serial genealogy intact.
Inventory is where three workstreams have to agree simultaneously. Finance needs a value that reconciles to a control account. Operations needs a position accurate enough to pick against on day one. Compliance needs genealogy and disposition state intact enough to answer a recall query.
The storage and tracking dimension groups were designed in the Product & Item Modelling module. This is where the consequences land.
Inventory value has to arrive in the target with a defensible basis, and defensible means a controller can explain it to an auditor.
Genealogy is the part of this module that cannot be fixed afterwards, so it gets the most attention.
Every position carries a state as well as a quantity, and the state is what determines whether it can be used.
The posting rules record the inventory adjustment, cycle count and quarantine family as mapped with medium collapse risk and a high version sensitivity, with the note that life-sciences and automotive programmes often require reason-code and audit-trail preservation.
Three position types cause disproportionate trouble because they sit at the edge of what "our inventory" means.
The gate is inventory value agreeing to the inventory control account within an agreed tolerance. Reaching it requires more than one comparison.
Inventory migration has to satisfy finance, operations and compliance at once, and only the finance requirement is expressed in the wave gate. Load at operational granularity rather than extract convenience, carry a per-position cost basis so that value reconciles by construction, and reflect the source's real valuation method mix rather…