Integrations on Learn Oracle OTM

Inbound Integrations (XML)

Fri, 15 Apr 2016 18:20:00 +0000

OTM supports several methods for receiving data from external systems. This topic covers XML-based integrations, which are the most common approach in OTM implementations.

Integration Methods Overview:

GlogXML via Middleware: XML files following the GlogXML schema, posted to OTM from middleware platforms such as Oracle SOA/BPEL, webMethods, or MuleSoft. This is the most common approach for production integrations.

Manual XML Upload: OTM users manually upload a GlogXML-formatted XML file through the OTM Integration Manager screen. Useful for testing, one-time loads, or small data corrections.

CSV Upload: Uploading data using comma-separated value files for supported OTM entities. See the CSV Data Uploads topic for details.

DB.XML Upload: A method for loading data directly using database-level XML files, typically used in implementations or data migrations.

REST API: Newer versions of OTM support REST API-based integrations for querying and updating OTM data without using GlogXML format.

HTTP Post from Code: Custom programs written in PL/SQL, Java, or other languages can post GlogXML directly to the OTM WMServlet endpoint. See the Post Data via HTTP Request topic for details.

GlogXML Schema:

Post Data to OTM via HTTP Request

Wed, 04 Mar 2026 21:37:00 +0000

If your source system is an Oracle database — such as Oracle E-Business Suite (EBS) — you can post GlogXML data directly to OTM using PL/SQL without requiring a middleware layer. This is done using Oracle’s built-in UTL_HTTP package, which allows a PL/SQL program to make HTTP requests to external URLs.

This approach is useful for simple, direct integrations where installing or configuring a middleware platform is not practical. For more complex scenarios involving multiple source systems or non-XML formats such as EDI or flat files, a dedicated middleware tool such as Oracle SOA/BPEL, webMethods, or MuleSoft is a better fit — see the Inbound Integrations (XML) topic for an overview of all available methods.

CSV Data Uploads

Wed, 04 Mar 2026 21:48:00 +0000

OTM supports loading data using CSV (comma-separated values) files. This is a practical method for bulk data uploads during initial implementation or data migrations — especially when the source data is available in spreadsheet form.

The approach works by first exporting a sample record from OTM in CSV format, which gives you the exact column structure OTM expects. You then populate that template with your data and upload it back. The steps below use a Location record as an example — the same process applies to any OTM business object such as Order Release, Shipment, Service Provider, Invoice, and more.

Outbound Integrations

Fri, 15 Apr 2016 20:21:00 +0000

OTM can generate outbound XML data for any business object — Order Release, Shipment, Invoice, and more — and send it to an external system such as a carrier platform, ERP, or middleware. This can be triggered manually using the Send Interface Transmission action, or automatically from an OTM Agent (workflow). OTM Agents are covered in a later topic.

There are three things you need to set up before OTM can send outbound data: