M3 organisational model: unbundling CONO, DIVI, FACI, and WHLO

How M3's four-level organisational hierarchy — Company, Division, Facility, Warehouse — maps to D365's legal entity, financial dimensions, sites, and warehouses, and how to avoid the Facility-as-legal-entity trap that derails most M3 migrations.

What you will be able to do

• Map each of the four M3 org codes to its D365 equivalent
• Apply the statutory test to determine whether a Facility should become a D365 legal entity or a site plus financial dimension
• Explain the consequences of running multiple Divisions inside one Company
• Describe the customer and supplier deduplication challenge in multi-CONO tenants
• Design a financial dimension set that preserves the reporting capability M3 delivered through the org hierarchy

Introduction

M3's organisational model is simple to state but difficult to project onto D365. Four nested codes — Company (CONO), Division (DIVI), Facility (FACI), and Warehouse (WHLO) — are first-class keys in M3's data model. They appear on nearly every transactional table.

The four M3 org codes

M3's hierarchy is strict in the metadata and porous in operational reality. Each code has a defined parent-child relationship, but M3 tenants routinely use FAM functions to simulate cross-DIVI and cross-CONO flows within the same instance.

The D365 equivalents

D365 F&O has one hard posting boundary — the legal entity (DataAreaId) — and treats every other organisational dimension as either an inventory attribute or a financial dimension.

The mapping bridge

The single most common architectural error in M3 migrations is promoting every Facility with a separate cost roll to a D365 legal entity. The temptation is understandable: the FACI runs a management P&L, it has its own planners, and it raises internal "billing" through FAM functions configured for inter-facility pricing.

Multi-DIVI tenants and dimension semantic drift

Where a CONO runs multiple DIVIs, the DIVI maps to a financial dimension value. The DIVI master for CONO 100 might carry values APPAREL, FOOTWEAR, ACCESSORIES; those become dimension values on the D365 BusinessUnit or custom Division dimension.

Customer and supplier structures in multi-CONO tenants

M3 customer master (OCUSMA) and supplier master (CIDMAS) are both scoped per CONO. The same legal customer, such as a large distributor trading with two of your legal entities, appears as two separate OCUSMA rows in M3 — one per CONO — each potentially with different addresses, payment terms, and CO codes, diverged through years of…

Worked organisational bridge examples

The CONO/DIVI/FACI/WHLO bridge becomes easier to apply when it is tested against concrete tenants. Treat the following as design exercises rather than formulas.

Knowledge check

Summary

M3's four-level hierarchy — CONO, DIVI, FACI, WHLO — projects onto D365's legal entity, financial dimensions, site, and warehouse model through a many-to-few collapse. Each decision has permanent structural consequences.