Oracle Transportation Management (OTM) logo

Oracle Transportation Management (OTM) Connector

Extract shipments, orders, releases, locations, and logistics data from Oracle Transportation Management (OTM) via Export APIs. Supports sync and async export modes with Basic Auth or OAuth 2.0.

SourceBronze

Why Supaflow

All connectors included

No per-connector fees. Every connector is available on every plan.

Pay for compute, not rows

Credit-based pricing. No per-row charges, no MAR surprises.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Basic Auth and OAuth 2.0 Authentication

Connect with OTM username/password (Basic Auth) or OAuth 2.0 via Oracle IDCS. The integration user must have Data Export and Data Integration permissions.

Sync and Async Export Modes

Sync mode uses direct REST API calls for smaller datasets. Async mode offloads exports to Oracle Object Storage via Pre-Authenticated Request URLs for large-volume extraction.

Incremental Sync via UPDATE_DATE

All objects use the UPDATE_DATE field as a cursor for incremental sync. Configurable lookback window (recommended 300-600 seconds) catches late-arriving logistics updates.

Dynamic Object Discovery

Objects are discovered via the Export API. Tables appear in schema discovery once they contain data. Core tables, order tables, shipment child tables, and reference tables are all supported.

Supported Objects

Core Tables

SHIPMENT

Shipment records containing logistics and transportation data.

LOCATION

Facility and address information.

ITEM

Product and material master data.

CONTACT

Person and organization contact information.

Order Tables

ORDER_RELEASE

Customer orders for fulfillment.

ORDER_RELEASE_STATUS

Order release status history and tracking.

Shipment Child Tables

SHIPMENT_COST

Freight charges and accessorials.

SHIPMENT_STATUS

Shipment status history and milestone tracking.

SHIPMENT_STOP

Pickup and delivery stop locations.

SHIP_UNIT

Handling units and containers.

SHIPMENT_COST_QUAL

Additional cost attributes and qualifiers.

SHIPMENT_COST_REF

Cost reference numbers and external identifiers.

SHIPMENT_COST_REMARK

Cost remarks and notes.

Reference Tables

ADJUSTMENT_REASON

Reason codes for inventory and cost adjustments.

ALLOCATION

Inventory and capacity reservations.

AUDIT_TRAIL

Data change and user action audit records.

How It Works

1

Prepare OTM credentials

Create an integration user in OTM with Data Export and Data Integration permissions. For OAuth, register a confidential application in Oracle IDCS with client credentials grant type.

2

Enter server and authentication details

Provide the OTM server base URL (e.g., https://your-instance.otm.us-ashburn-1.ocs.oc-test.com). Select Basic Auth or OAuth 2.0 and enter the corresponding credentials. Do not include paths like /GC3/ in the URL.

3

Configure export mode

Choose Sync (default) for direct REST API export, or Async for large-volume extraction via Oracle Object Storage. Async requires a Pre-Authenticated Request URL for the Object Storage bucket.

4

Test and save

Click Test & Save to verify connectivity and API permissions. Supaflow discovers available OTM objects and their fields.

Use Cases

Transportation analytics

Replicate shipments, stops, costs, and status history into your warehouse to build dashboards tracking on-time delivery, freight spend, and carrier performance.

Order fulfillment reporting

Combine order releases and shipment data with ERP and WMS data in your warehouse for end-to-end fulfillment visibility.

Cost analysis and audit

Load shipment cost records, cost qualifiers, and adjustment reasons into your warehouse for freight audit, accessorial analysis, and cost allocation.

Frequently Asked Questions

Which OTM versions are supported?
Both Oracle Cloud OTM and on-premises OTM instances are supported, provided the Export API and Data Integration REST APIs are accessible.
When should I use async export mode?
Use async mode when exporting large data volumes. Sync mode calls the REST API directly, while async mode writes to Oracle Object Storage first, which avoids API timeouts on large exports.
Why do some tables not appear in schema discovery?
Objects are discovered dynamically via the Export API. If a table has no data, it will not appear in schema discovery but becomes available once data exists in OTM.

Need a connector we don't support yet?

Build one with AI-powered Connector Dev Skills.

Learn More About the Connector SDK