New: Supaflow Claude Plugin -- let Claude create, edit, and monitor your data pipelines. Try the plugin
Oracle Transportation Management (OTM) logo

Oracle Transportation Management (OTM) Connector

Sync Oracle Transportation Management shipments, orders, costs, locations, allocation, and audit data into your warehouse.

SourceGold

Evaluating against Fivetran? See how Supaflow handles Oracle Transportation Management (OTM) pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Load Oracle Transportation Management (OTM) into Snowflake

Dedicated pages for destination-specific setup, buyer questions, and Snowflake sync behavior.

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

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 credentials or OAuth 2.0. The integration user must have Data Export and Data Integration permissions.

Sync and Async Export Modes

Use direct OTM exports for smaller datasets or Object Storage handoff for large-volume extraction.

Incremental Logistics Updates

Syncs new and changed logistics records after the initial load, with a configurable lookback window for late-arriving OTM updates.

Operational OTM Coverage

Covers shipments, order releases, shipment costs, status history, stops, locations, reference numbers, items, contacts, allocation, and audit data.

Supported Objects

Core Logistics Data

Shipments

Shipment records containing logistics and transportation data.

Locations

Facility, address, and site information.

Location references

Location reference numbers and external identifiers.

Items

Product and material master data.

Contacts

Person and organization contact information.

Orders

Order releases

Customer orders for fulfillment.

Order status history

Order release status history and tracking.

Shipment Details

Shipment costs

Freight charges and accessorials.

Shipment status history

Shipment milestones and status tracking.

Shipment stops

Pickup and delivery stop locations.

Ship units

Handling units and containers.

Cost attributes

Cost qualifiers, references, remarks, and notes.

Reference Data

Adjustment reasons

Reason codes for inventory and cost adjustments.

Allocations

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 an application in your Oracle identity provider.

2

Enter server and authentication details

Provide the OTM server base URL, select Basic Auth or OAuth 2.0, and enter the corresponding credentials.

3

Configure export mode

Choose direct export for smaller datasets or Object Storage handoff for large-volume extraction.

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 required export and data integration permissions are available.
When should I use async export mode?
Use async mode when exporting large data volumes. It stages exports through Oracle Object Storage, which avoids timeouts on large OTM exports.
Why do some tables not appear in schema discovery?
OTM objects are discovered dynamically. If an object has no data, it may not appear during 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