OTM organises all of its data using a domain model. Understanding domains, the database schema, and how business objects are identified is foundational for anyone working with OTM data — whether you are building integrations, writing reports, or troubleshooting transactions.
Domains:
What is a domain? A domain is a logical grouping of OTM data for a business unit. A corporation with multiple shipping divisions — say, Merchandise and Food & Beverage — would typically have one domain per division. Users and roles are tied to a domain, so a user in one domain cannot see or modify data in another.
Domain hierarchy: Domains can be nested — a parent domain at the corporate level with child domains under each business unit. Configuration defined at the parent level (e.g. Item Numbers, Agents, Rate Offerings) is shared across all child domains, while each child domain can also maintain its own configuration.
DOMAIN_NAME column: Every table in OTM includes a
DOMAIN_NAME column that ties each row to its domain. This is how OTM isolates data between business units within a single database instance.GID and XID — How OTM Identifies Business Objects: