Entity or Country First

motorwaygn

Hello,

We're considering launching into a new country, how would be best to structure this in the organisational hierarchy?

Country first, then entities; or entities, then countries.

For reference both entities will be trading in both countries.

e.g. Total Company > UK, Germany > Entity 1 - UK, Entity 2 - UK, Entity 1 - Germany, Entity 2 - Germany

OR

Total Company > Entity 1, Entity 2 > Entity 1 - UK, Entity 2 - UK, Entity 1 - Germany, Entity 2 - Germany

Thanks!

rob_marshall

@motorwaygn

Why not have two different lists, one for countries and one for Entities?

TristanS

Agree with Robs comment above. The use case will determine which organisational hierarchy you will use.

if you have user input modules, will the data be entry users be more geography specific than entity specific. Scenario 1 (most common scenario): User is restricted to Germany but can enter data for multiple entities. In this case I would recommend the 1st structure you provided below

Total Company > UK, Germany > Entity 1 - UK, Entity 2 - UK, Entity 1 - Germany, Entity 2 - Germany

Scenario 2: User is restricted to Entity 1 but can enter data for data for multiple countries then I would recommend the 2nd structure

Total Company > Entity 1, Entity 2 > Entity 1 - UK, Entity 2 - UK, Entity 1 - Germany, Entity 2 - Germany

Scenario 3: Combination of both 1 and 2.

I would take a profile of which one has the higher usage rather implementing both hierarchies in separate data input modules as reconciling both modules is likely prove difficult later

Anmol14

@motorwaygn

I think it depends on the architecture of your modules and lists. If your earlier architecture is:
Total Company > UK, Germany > Entity 1 - UK, Entity 2 - UK, Entity 1 - Germany, Entity 2 - Germany

Then, I believe this can be a possible structure.

Here, entity names can be kept the same with unique codes(as it is a numbered list).

It depends on the way you wish to see the data. No way is wrong if it serves the purpose.