Data Model on Learn Oracle OTM

Domains, Standard Schema and Data Dictionary

Mon, 02 May 2016 16:34:00 +0000

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:

Order Management Data Structure

Tue, 03 May 2016 17:42:00 +0000

OTM models order management across three levels: the Purchase Order (what was ordered), the Order Release (a confirmed booking for movement), and Order Movements (the planned legs of that movement). Understanding this hierarchy and the underlying tables is essential for integration work and troubleshooting.

Purchase Order (Order Base):

A Purchase Order represents the commercial transaction — what items are being moved, from where, to where, and under what terms. POs are typically created in an ERP system (e.g. Oracle E-Business Suite) and sent to OTM via inbound integration. Note that POs often lack exact weight and volume details, which are required for shipment planning — those are defined on the Order Release.

Shipment Management Data Structure

Tue, 03 May 2016 20:01:00 +0000

A shipment in OTM consists of one or more Equipment records (containers or trailers), Shipment Ship Units loaded into each equipment, and Shipment Ship Unit Lines that link back to the original Order Release lines. Understanding this structure is essential for troubleshooting planning results, writing integration queries, and working with carrier tracking events.

Shipment Structure:

When OTM plans an Order Release to a shipment, it creates Shipment Ship Units and assigns them to equipment. If a Bulk Plan splits an order across two containers — say 60 units in one and 40 in another — that split is recorded at the Shipment Ship Unit Line level. This line is the critical link between the shipment and the originating order: it ties back to a specific item, Order Release Line, Order Release, and Order Base.

Contract & Rate Management Data Structure

Fri, 06 May 2016 17:29:00 +0000

OTM models carrier contracting across five layers: Service Provider (who moves the freight), Rate Service (transit time commitments), Rate Distance (how mileage is calculated), Rate Offering (the contract), and Rate Records (the actual cost lanes). Understanding this structure is essential for rate setup, planning troubleshooting, and freight cost analysis.

Service Provider:

A Service Provider (carrier) is the party that physically moves freight. They own or manage trucks, containers, trailers, and drivers. They receive tender requests from OTM specifying origin, destination, weight, volume, and shipment dates — and issue invoices once delivery is complete.

Business Process Automation Data Structure

Fri, 06 May 2016 20:15:00 +0000

The Business Process Automation (BPA) module handles the technical configuration layer of OTM — workflows, notifications, outbound integrations, reports, and transmission logging. The tables below are useful when troubleshooting agent behaviour, auditing integration traffic, or diagnosing report failures.

Contacts:

A Contact in OTM defines a communication endpoint — an email address, fax number, or integration URL — that OTM can reach when sending notifications or outbound data. Contacts can be associated with: