Design the D365 legal entity, operational site and warehouse structure from a SYSPRO estate whose organisational master decomposition is the highest-rated discovery gap on this path.
Organisational design is the first gate on a SYSPRO programme, and it is also the one where this path's evidence is thinnest. That combination is uncomfortable, so it is worth naming immediately.
D365 expresses organisational structure through a small set of constructs that do different jobs. Confusing them is the root of most organisational rework.
Start from the SYSPRO company list, then interrogate it rather than transcribing it.
In the target, an operational site is a boundary that inventory, production and financial dimension defaulting all recognise. It is where production happens, where costing behaviour can be differentiated, and where a financial dimension typically defaults from.
Every organisational meaning that is not a statutory boundary and not a physical location is a candidate for a financial dimension. Division, branch, business unit, product line, customer segment, channel, cost centre — all of these are analytical, all of them belong in named dimensions, and all of them are easier to change as dimensions…
SYSPRO companies are separated in a way that lets divergent conventions survive indefinitely. Company A can call an item one thing, Company B can call it another, and nothing ever forces the conversation, because the two never have to agree on anything.
Because the evidence base cannot answer the organisational questions, the deliverable of this module is a discovery pack rather than a mapping. A sufficient pack contains:
Organisational design is the first gate and the least documented domain on this path.