The tenant/site/plant hierarchy re-projected onto legal entities, sites and warehouses

How to determine whether each Plex site becomes a D365 legal entity or a site and warehouse under one shared legal entity — the highest-impact, least-reversible decision on this migration path.

What you will be able to do

Introduction

The Plex Smart Manufacturing Platform models a customer's entire manufacturing operation inside one tenant. Every site, every plant, every warehouse exists within that single logically isolated slice of Rockwell's shared multi-tenant codebase. Reporting rolls up across sites within the tenant. Security is tenant-scoped.

The Plex organisational model

Plex's organisational model is simpler to state than D365's — and that simplicity is exactly what creates the translation challenge.

The D365 organisational model

D365 has one first-class posting boundary: the legal entity. All other organisational constructs exist below it, above it, or alongside it — but none of them partition the general ledger the way the legal entity does.

The mapping bridge: Plex to D365

The single question that determines whether a Plex site should become a D365 legal entity:

The cost of getting it wrong

Both directions of error are permanent and expensive. Understanding the cost is what makes the decision framework robust.

Fiscal calendars, currencies and number sequences

Each D365 legal entity owns its fiscal calendar. If two Plex sites have the same fiscal year (say, calendar year January–December), they can share one legal entity without conflict.

Master-data consequences

In a single-legal-entity design, the customer and vendor masters are simpler (no deduplication needed) and products are released once. In a multi-legal-entity design, master-data governance becomes a permanent workstream.

Preserving Plex's roll-up reporting capability

Plex provides cross-site roll-up reporting within one tenant. When the D365 design places sites under one legal entity, this capability is preserved naturally through financial-dimension filtering: run a trial balance filtered by Site=A or Site=B or remove the filter for the consolidated view.

Worked topology examples

A Plex tenant has four manufacturing plants in Germany. All plants share one tax registration (Steuernummer), one fiscal year and one functional currency (EUR). They produce different product lines and have separate cost rolls and management P&Ls.

The decision governance process

The topology decision must be signed off before Wave 1 configuration begins. The governance process should involve:

Knowledge check

Summary

The Plex tenant/site model projects onto D365's legal-entity/site/warehouse model through a decision framework, not a mechanical mapping. The statutory test — does this site file its own return, hold its own banks, sign its own contracts? — determines which Plex sites become legal entities and which become sites.