Domains, Standard Schema and Data Dictionary

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:

Inbound Integrations (XML)

OTM supports several methods for receiving data from external systems. This topic covers XML-based integrations, which are the most common approach in OTM implementations.

Integration Methods Overview:

GlogXML via Middleware: XML files following the GlogXML schema, posted to OTM from middleware platforms such as Oracle SOA/BPEL, webMethods, or MuleSoft. This is the most common approach for production integrations.
Manual XML Upload: OTM users manually upload a GlogXML-formatted XML file through the OTM Integration Manager screen. Useful for testing, one-time loads, or small data corrections.
CSV Upload: Uploading data using comma-separated value files for supported OTM entities. See the CSV Data Uploads topic for details.
DB.XML Upload: A method for loading data directly using database-level XML files, typically used in implementations or data migrations.
REST API: Newer versions of OTM support REST API-based integrations for querying and updating OTM data without using GlogXML format.
HTTP Post from Code: Custom programs written in PL/SQL, Java, or other languages can post GlogXML directly to the OTM WMServlet endpoint. See the Post Data via HTTP Request topic for details.

GlogXML Schema: