SHIPMENT_COST_REF — Oracle Transportation Management Reference

Shipment cost reference numbers and external identifiers.

This page documents the SHIPMENT_COST_REF table in Oracle Transportation Management (OTM) -- columns, primary key, incremental cursor, and the exact REST API endpoints used to extract it. This is one of 18 OTM tables that Supaflow's Oracle Transportation Management connector syncs natively into Snowflake, Databricks, BigQuery, Redshift, or Postgres.

Overview

Attribute	Value
OTM export table name	SHIPMENT_COST_REF
OTM metadata resource name	shipmentCostRefs
Primary key	SEQNO
Incremental cursor field	UPDATE_DATE
Category	Shipment children

OTM REST API endpoints

OTM exposes every table through the logistics REST API. Paths depend on the authentication method you use.

Export API (fetch rows)

POST one of the following URLs, depending on your OTM authentication mode:

• OAuth 2.0 (IDCS): https://{your-otm-host}/logisticsRestApi/data/v1/exportRequests/
• Basic Auth: https://{your-otm-host}/logisticsRestApi/data-int/v1/exportRequests/

Example request body for SHIPMENT_COST_REF:

{
  "schema": "PRIMARY",
  "contentType": "text/plain",
  "tables": {
    "items": [
      { "tableName": "SHIPMENT_COST_REF", "partSize": 5000 }
    ]
  }
}

To pull only rows updated after a given timestamp (the recommended pattern for incremental sync), add a rangeAfter block:

{
  "schema": "PRIMARY",
  "contentType": "text/plain",
  "rangeAfter": { "value": "2026-04-01T00:00:00Z" },
  "tables": {
    "items": [
      { "tableName": "SHIPMENT_COST_REF", "partSize": 5000 }
    ]
  }
}

The response is a CSV payload with the table name on line 1, column headers on line 2, and data rows starting on line 3.

Metadata catalog (fetch schema)

GET the schema for SHIPMENT_COST_REF:

• OAuth 2.0: https://{your-otm-host}/logisticsRestApi/resources/v2/metadata-catalog/shipmentCostRefs
• Basic Auth: https://{your-otm-host}/logisticsRestApi/resources-int/v2/metadata-catalog/shipmentCostRefs

note

The OTM metadata-catalog endpoint returns HTTP 400 for several tables. If you receive a 400 here, fall back to data-driven type inference by sampling rows from the Export API. See the OTM integration guide for the full pattern.

Columns

Column	Type	Nullable	PK	Foreign key
SEQNO	NUMBER()		Yes
SHIPMENT_COST_SEQNO	NUMBER()			SHIPMENT_COST
SHIPMENT_GID	VARCHAR2(101)			SHIPMENT
COST_REFERENCE_GID	VARCHAR2(101)
SHIPMENT_COST_QUAL_GID	VARCHAR2(101)			SHIPMENT_COST_QUAL
IS_PICKUP	CHAR(1) Y/N	Yes
IS_DROPOFF	CHAR(1) Y/N	Yes
DOMAIN_NAME	VARCHAR2(50)
INSERT_USER	VARCHAR2(128)
INSERT_DATE	DATE
UPDATE_USER	VARCHAR2(128)	Yes
UPDATE_DATE	DATE	Yes

Column list source

The column list above is extracted from Oracle's OTM data dictionary included with the February 2025 release snapshot of this connector. Oracle publishes an updated dictionary with every Transportation and Global Trade Management release; for the current version, consult Oracle's Transportation and Global Trade Management documentation.

Incremental sync

The SHIPMENT_COST_REF table supports incremental sync via the UPDATE_DATE cursor. Supaflow's connector handles:

• Server-side clock skew -- measured once from OTM's RFC 1123 Date header and applied to every cursor comparison.
• Late-arriving updates -- configurable lookback window (recommended 300-600 seconds in production) re-scans the tail of the previous window.
• Identical-timestamp batches -- tracks record count at the maximum cursor timestamp so batch updates that stamp thousands of rows with the same UPDATE_DATE don't cause missed or duplicated rows.

Full pattern: The Complete Guide to Oracle Transportation Management Integration.

Sync SHIPMENT_COST_REF with Supaflow

Supaflow's Oracle Transportation Management connector syncs SHIPMENT_COST_REF -- along with 17 other OTM tables -- into your cloud data warehouse with:

• Sync and async (Object Storage PAR) export modes
• Proactive OAuth token refresh (60-second safety margin on IDCS tokens)
• Composite primary key preservation for tables with multi-field keys
• Automatic handling of the five OTM-specific data quirks (metadata 400s, "0" temporal sentinels, Z-suffixed date fields, 1 MB sync-mode truncation, _TEXT / _COMMENT column type overrides)
• Predictable connector-based pricing -- not per-row, not per MAR

Next steps:

• Book a 15-minute demo to see the OTM connector against a live instance
• Set up the OTM source in your Supaflow workspace
• Read the full OTM integration guide