# Oracle Transportation Management with JD Edwards: Freight Planning Integration

> Source: https://netray.co/stack/oracle-transportation-management-jd-edwards
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

Oracle Transportation Management (OTM) plans freight, selects carriers, rate shops and supports freight payment. Oracle's implementation guide documents JD Edwards integration points for sales orders, purchase orders, ship confirmation and freight vouchers, using staging tables and XML (GLogXML) over HTTP. It is a substantial implementation and suits manufacturers with real multi-leg or multi-carrier freight, not simple parcel shipping.

## Erp

Oracle JD Edwards EnterpriseOne

## Erp Key

jd-edwards

## On Prem

true

## Product

Oracle Transportation Management (OTM)

## Vendor

Oracle

## Category

Freight and TMS

## Integration

**Method:** JDE staging tables and GLogXML over HTTP

**Detail:** Per Oracle's guide, JDE writes transportation data to staging tables and the integration sends it to OTM as GLogXML over HTTP. Planned shipment results come back to JDE the same way, then ship confirm and freight vouchers close the loop.

**Method:** Fusion alternative

**Detail:** For Oracle Fusion Cloud ERP, Oracle documents that Fusion Shipping integrates natively with Fusion Cloud Transportation Management and Global Trade Management, so the staging pattern applies to JDE rather than Fusion.

## Data Flows

**From:** JD Edwards sales and purchase orders

**To:** OTM

**Data:** Order releases with ship-from, ship-to, weights and dates

**Trigger:** Order ready for transportation planning

**From:** OTM

**To:** JD Edwards

**Data:** Planned shipment, carrier and route

**Trigger:** Planning run completes

**From:** JD Edwards

**To:** OTM

**Data:** Ship confirmation

**Trigger:** Shipment confirmed in JDE

**From:** OTM

**To:** JD Edwards

**Data:** Freight voucher for carrier payment

**Trigger:** Freight settlement approved in OTM

## Setup

### Decide the planning scope

**Detail:** Define which order types, plants and lanes OTM will plan and which stay manual.

### Align location and item master

**Detail:** Make sure ship-from and ship-to locations, item weights, volumes and freight classes exist and agree between JDE and OTM.

### Configure the JDE staging and outbound processing

**Detail:** Set up the JDE transportation integration objects per Oracle's guide, and test the HTTP endpoints between the two systems.

### Load rates and carrier contracts

**Detail:** Enter carrier rate tables, service levels and accessorials in OTM.

### Map ship confirm and freight vouchers

**Detail:** Define how settlement lines map to JDE vouchers, accounts and business units.

### Run end-to-end tests

**Detail:** Walk orders through plan, tender, ship confirm and payment, including split shipments and cancellations.

## Pitfalls

- Missing or wrong item weights and volumes lead to bad plans and carrier invoice disputes.
- Order changes after planning not propagated, leaving OTM planning a shipment that no longer exists.
- Location code mismatches between JDE address book and OTM locations.
- Freight accruals and vouchers posted to the wrong account because of weak mapping.
- Integration failures that sit unseen in staging tables or HTTP logs.
- Customisation of JDE shipping that bypasses the documented integration points.

## Ai Layer

### Stuck shipment diagnosis

**Description:** A private assistant can compare the JDE staging records with OTM shipments and say where an order stopped and why.

### Freight invoice reconciliation

**Description:** It can explain differences between planned cost, carrier invoice and the JDE freight voucher, line by line.

### Logistics questions in plain language

**Description:** Planners can ask which orders shipped late by carrier lane, with the SQL shown and read-only access.

## Alternatives

- For parcel and simple LTL, a multi-carrier shipping tool such as ShipConsole may be enough without a full TMS.
- JDE's own transportation and carrier management may cover modest freight needs.
- A third-party TMS with a prebuilt JDE connector can shorten the project if you do not need OTM's depth.

## Faq

### How does JD Edwards connect to OTM?

**Answer:** Oracle's implementation guide describes staging tables in JDE and XML in the GLogXML format sent over HTTP. It covers sales and purchase orders, ship confirmation and freight vouchers. Read the guide for your JDE release, because object names and supported flows depend on the version you run.

### Is OTM overkill for a mid-size manufacturer?

**Answer:** Often yes. OTM earns its cost with multi-leg, multi-carrier or regulated freight and heavy rate shopping. If you ship mostly parcel and a few LTL lanes, a lighter shipping tool or JDE's native features may do the job with far less implementation effort.

### What can a private AI do for freight data?

**Answer:** It can read JDE and OTM records on your own infrastructure to explain why a shipment stalled, reconcile freight invoices and answer logistics questions. It does not change plans or vouchers by itself; any write-back goes through a person, so planners stay in control of freight decisions.

## Source

https://docs.oracle.com/cd/E16582_01/doc.91/e15120/introduction.htm

## Search terms

oracle transportation management jd edwards integration, otm jd edwards, jde tms integration, glogxml jd edwards, jd edwards freight voucher, jd edwards transportation management

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json