How Oracle Transportation Management (OTM) connects to Oracle JD Edwards EnterpriseOne
JDE staging tables and GLogXML over HTTP
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.
Fusion alternative
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.
What data moves
| From | To | Data | When |
|---|---|---|---|
| JD Edwards sales and purchase orders | OTM | Order releases with ship-from, ship-to, weights and dates | Order ready for transportation planning |
| OTM | JD Edwards | Planned shipment, carrier and route | Planning run completes |
| JD Edwards | OTM | Ship confirmation | Shipment confirmed in JDE |
| OTM | JD Edwards | Freight voucher for carrier payment | Freight settlement approved in OTM |
Setting it up
- 1Decide the planning scopeDefine which order types, plants and lanes OTM will plan and which stay manual.
- 2Align location and item masterMake sure ship-from and ship-to locations, item weights, volumes and freight classes exist and agree between JDE and OTM.
- 3Configure the JDE staging and outbound processingSet up the JDE transportation integration objects per Oracle's guide, and test the HTTP endpoints between the two systems.
- 4Load rates and carrier contractsEnter carrier rate tables, service levels and accessorials in OTM.
- 5Map ship confirm and freight vouchersDefine how settlement lines map to JDE vouchers, accounts and business units.
- 6Run end-to-end testsWalk orders through plan, tender, ship confirm and payment, including split shipments and cancellations.
What usually breaks
- !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.
A private AI layer across both systems
Stuck shipment diagnosis
A private assistant can compare the JDE staging records with OTM shipments and say where an order stopped and why.
Freight invoice reconciliation
It can explain differences between planned cost, carrier invoice and the JDE freight voucher, line by line.
Logistics questions in plain language
Planners can ask which orders shipped late by carrier lane, with the SQL shown and read-only access.
Try it here, free
JD Edwards EnterpriseOne AI Assistant Sizing and Value Calculator
Estimate peak load, GPUs, index size, hours saved and payback for an on-prem AI assistant on JD Edwards EnterpriseOne.
When something else fits better
- 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.
Frequently asked questions
How does JD Edwards connect to OTM?
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?
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?
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.
Pairing documented at docs.oracle.com/cd/E16582_01/doc.91/e15120/introduction.htm . Oracle Transportation Management (OTM) is a product of Oracle; Netray is independent and not affiliated with either vendor.