M3 item master to D365 released product: decoding MITMAS, status codes, and variants
How M3's three-tier item master (MITMAS / MITFAC / MITBAL), multi-position status code, style–colour–size matrix, and product configurator translate into D365's shared product, released product per legal entity, product dimension groups, and lifecycle states.
What you will be able to do
Describe the three-tier M3 item master and what splits at each tier
Explain how M3 item status codes map to D365 product lifecycle state, item model group flags, and blocking controls
Map the M3 style–colour–size grid to D365 product dimensions and explain the volume implications
Describe M3 lot and serial control and their D365 tracking-dimension equivalents
Identify the key design decisions in the D365 storage and tracking dimension group configuration
Introduction
M3's item master is not a single table — it is a three-tier hierarchy that spreads item attributes across MITMAS (global item identity), MITFAC (facility-level planning and manufacturing parameters), and MITBAL (warehouse-level stock and replenishment).
The M3 item master — three tiers
MITMAS holds the attributes that are true of an item regardless of where it is planned or stocked:
The M3 status code — a multi-position gate
M3's item status is a multi-position code stored on MITMAS. Each character position gates a distinct operational capability:
The style–colour–size grid
CloudSuite Fashion extends MITMAS with a style–colour–size (SCS) grid. A style master is the top-level item; colours and sizes are attribute dimensions; every unique (style, colour, size) combination is a distinct stockable variant.
Lot control, serial control, and tracking dimensions
M3 controls lot and serial traceability at the MITMAS level with flags that apply globally across all facilities and warehouses. D365 uses tracking dimension groups assigned per released product, which are similarly item-level configurations.
Product configurator
M3's product configurator (PCT/CFG) generates configured variants at order entry time based on option selections. Each order entry triggers a configuration session; the resulting variant is either a new item or an existing one matched by attribute combination (exact program codes release-dependent — verify against M3 documentation).
Vertical CloudSuite extensions and what must survive
M3 CloudSuite verticals add data-model detail that is easy to lose if the item migration only loads MITMAS/MITFAC/MITBAL. The extensions are not decorative; they often drive costing, compliance and warehouse behaviour.
Knowledge check
Summary
M3's three-tier item master — MITMAS / MITFAC / MITBAL — maps onto D365's shared product, released product per legal entity, and inventory dimension model. The fan-out is structural: MITMAS is the product identity, MITFAC is the per-site operational settings, and MITBAL becomes default order settings plus opening inventory positions.