Introduction
This document explains the basic concept of organizations of the Intershop Order Management. This document is aimed at business users, project developers, and operators.
References
Guide - IOM Basic Business Configuration | Create an Organization Structure
Overview - IOM Database Documentation (
OrganizationDO)
In General
An organization is a single tree structure on shops and suppliers to manage dedicated tasks easily, for example user and permission management or stock handling.
Organizations are used to:
present/map organizations' structures within the IOM
manage user allocation and permission handling
manage hierarchical stock visibility
The organizations must observe the following rules:
There can be organizations without a shop or supplier
Each shop instance is mapped to one organization instance
Each supplier instance is mapped to one organization instance
A supplier can only have another supplier as a child
A shop can only have another shop as a child
Sub-trees defined in
SupplierDOorShopDOalso exist in the organization tree
Reserved/Predefined and Required Organizations
The IOM initial database dumps come with predefined/required organizations:
OmsSystem is the required root organization (internal id=1)
OMS internal Supplier is a required dummy supplier that is used before order positions get assigned to real suppliers. Do not modify it!
There must beShop2SupplierDOmapping between all real shops and this internal supplier.OMS internal Shop is an internal shop that is used in a few places for default shop assignments,
but it may get removed in a future version. Do not consider it.All Shops is a predefined shop that was originally meant as a placeholder to assign users/roles automatically to all existing and future shops.
You should not consider or use it as it will probably be removed in a future version.All Supplier is a predefined supplier similar to the “All Shops”.
You should not consider or use it as it will probably be removed in a future version.