How to setup Stores in a Multi Org Environment
By default, the design for iStore is geared towards single operating unit installations:
- One Store Admin responsibility (IBE_ADMIN),
- One Customer responsibility (IBE_CUSTOMER)
- One Guest User responsibility (IBE_GUEST)
- One Operating Unit
- One Item Validation Organization (usually Master, but any Inventory Org will suffice)
To perform a Multi-Operating Unit iStore setup correctly, we need to create separate responsibilities for each of the Operating Units. In effect, the design discards the default responsibilities
Assume that Operating Unit 1 (OU1) has under it Inventory Orgs IO1, IO2, IO3
Similarly, Operating Unit 2 (OU2) has under it Inventory Orgs IO3, IO4, IO5
The correct setup would be
Define an OU1_iStore Administrator responsibility, copied from iStore Administrator
Define a OU1_IBE_CUSTOMER, copied from IBE_CUSTOMER
Define a OU1_IBE_GUEST, copied from IBE_GUEST
In the profile options,
IBE: Item Validation Organization needs now to be setup at the responsibility level for
OU1_iStore Administrator
OU1_IBE_CUSTOMER
OU1_IBE_GUEST
The value can be any of the Inventory Organizations (IOs) belonging to the Operating Unit (IO1, IO2, IO3)
Similarly, the Profile Option MO: Operating Unit needs to be OU1 for each of the above responsibilities
The correct setup would be
Define an OU2_iStore Administrator responsibility, copied from iStore Administrator
Define a OU2_IBE_CUSTOMER, copied from IBE_CUSTOMER
Define a OU2_IBE_GUEST, copied from IBE_GUEST
In the profile options,
IBE: Item Validation Organization needs now to be setup at the responsibility level for
OU2_iStore Administrator
OU2_IBE_CUSTOMER
OU2_IBE_GUEST
The value can be any of the Inventory Organizations (IOs) belonging to the Operating Unit (IO4, IO5, IO6)
Similarly, the Profile Option MO: Operating Unit needs to be OU2 for each of the above responsibilities
These responsibilities need to be created under the CRM HTML Administrator responsibility. NOTE: The sysadmin username needs to be used
Furthermore, Registration templates need to be created for each Operating Unit. These can be copied from the existing registration templates.
