How to translate LN's single multi-view item record — with its item types, item groups, item-site and item-warehouse data, and generic-item configurator — into D365 shared products, released products per legal entity, product dimension groups, and product categories.
The item master is the foundation on which all supply-chain and manufacturing processes stand. Get it wrong and every downstream flow — BOMs, purchase orders, production orders, inventory positions — is built on incorrect assumptions. In LN the item is a single record with multiple views;
The item group in LN is a multi-purpose classification that simultaneously controls: IMS posting-account resolution (which GL accounts receive inventory receipts, issues, and adjustments for this item), MRP parameters (planning horizons, lot sizes, safety stock), and operational classification (ABC analysis, cycle count frequency).
LN stores planning and stocking parameters at three levels: the base item record, the item-site record, and the item-warehouse record. This layered structure allows the same item to have different reorder points, lead times, costing methods, and procurement sources across different sites and warehouses in the same Logistic Company.
LN groups related units of measure into unit sets and defines the conversion factors between them. A typical unit set for a discrete mechanical item might define: kg (the stocking unit), each (sales and purchase unit), and pallet (goods-receipt unit), with the conversion factors between them.
LN's generic item is a template item without a fixed BOM or routing. When a customer places an order for a generic item, a product configurator session generates an order-specific set of specifications — typically a variant code, an order-specific BOM, and an order-specific routing — from a predefined configuration model.
The item master migration is deceptively broad. It is not just about moving item records — it is about correctly mapping LN's multi-purpose item group into D365's distributed object model, translating per-site and per-warehouse parameters into site-scoped default order settings, and deciding whether LN generic items become…