I have a fundamental question about Domain structure in OTM.

[runinord]

Today we have 1 parent domain XY and all our customers are sub-domains to this domain, i.e. XY/CUST1, XY/CUST2 and so forth. All our buy shipments are built in the parent domain XY and none of the sub domains can see these shipments. We are having issues with visibility when we have a customer, say XY/CUST1 who has 20 DC and wants 100% visibility to his orders, sell and buy shipments. The question is should we create a third domain level for this customer in the structure below and try to build this costumers buy shipments in his sub domain or should we create a new parent domain CUST1 on the same level as XY with 20 sub-domains so that the customer has 100% visibility to his orders, sell and buy shipments? See diagrams below, first diagram is our current structure, second diagram adding an third domain level, third diagram creating a new parent domain.
XY
|
____________________________________________...... ...........
| | | |
CUST1 CUST2 CUST3 CUST4
Current structure

XY
|
________________________.......................
|
CUST1
|
__________________________________
| | | | |
DC1 DC2 DC3 ….. DC20
Current structure with a third level of sub domains

XY CUST1
| |
_________................____ ________................._________
| | | | | |
CUST2 CUSTZ DC1 DC2 DC19 DC20
New structure with several parent domains for customers with several DC.

Does any one have any experience in setting up several parent domains and are there any implications in doing so for locations, carrier rates, Agents and so forth? Any thoughts on complications in the different setups would be highly appreciated.
Thanks,
Runi

[runinord]

Sorry about the first diagram all the spaces got removed, here "`" is space


`````````````````````````````````````````XY
```````````````````````````````````````````|
`````````_________________________________________ ___.................
`````````|```````````````````|``````````````````|` ```````````````````|
`````CUST1``````````CUST2````````CUST3```````````` CUST4
Current structure

`````````````````````````````````````````````````` ``````XY
`````````````````````````````````````````````````` ````````|
````````````````````````________________________.. .....................
```````````````````````|
```````````````````CUST1
```````````````````````|
```__________________________________
```|``````````|```````````|``````````````|```````` `````|
DC1`````DC2``````DC3`````````…..````````DC20
Current structure with a third level of sub domains

`````````````````````````XY``````````````````````` ``````````````CUST1
```````````````````````````|`````````````````````` `````````````````````|
`````````_________................______`````````` ________................._________
`````````|````````````````````````````````````|``` ```````|````````````|`````````````|``````````````|
`````CUST2````````````````````````CUSTZ`````DC1``` ```DC2```````DC19````````DC20
New structure with several parent domains for customers with several DC.

Where ` is space

[samuellevin_mavenwire]

I think I may have a better solution to your issue. There is a property that you can enable that will create your shipments in the domain of the order. I think based on readying your model that it will give you the visibility that you need from the parent domain while maintaining customer information at the sub domain level. I did not ask but would hope that you are on OTM version 5.0 or 5.5 as this is when the properties came available. They can be found under help if you search for glog.process.Properties and the propert is glog.process.execAsEnabled.agent I have pasted below the details on this property from OTM Help
This property will force planning actions to run as either the logged-in user or the domain of the business object when the execAsEnabled.planning property is set to False.

True - will use the domain of the logged-in user when planned through the user interface, but use the domain of the business object when planned through an agent.

False - will use the domain of the logged-in user

[runinord]

Thanks for you sugestion Samuellevin,
We are on 5.0 and moving to 5.5.2 in weeks.
If I understand the documentation in the G-Log help right then this will change the behaviour for all domains. I.e. if you set glog.process.execAsEnabled.planning=true then all buy shipments will be build in the same domain as the order release for all domains. We are a 3PL and do ship several orders from different domains on the same buy shipments (in a case with 3 orders from 3 different domains where would the buy be built?), i.e. that is why we have the Buy shipment in the parent domain and the sell shipment in the same domain as the order release.
Thanks,
Runi