OTM Inbound Integrations (XML)

There are several ways of bringing in data into OTM system. Below are some of the methods:

  • via XML that follows Glog XML schema posted from a middleware applications like Oracle SOA, webMethods, Mulesoft, etc
  • Manaul XML uploads by OTM users
  • CSV Uploads
  • DB.XML Uploads
  • REST-API Calls
  • HTTP Post Requests from programming languages like PLSQL, etc

XML Inbound Integrations:

Most common way of receiving OTM Inbound data is via XML files from middleware applications. OTM can read XML files which are in the format specified by GlogXML Schema(OTM Standard XML Schema). You can download this schema from :

Business Process Automation > Integration > Integration Manager > Retrieve Schemas > GlogXML.xsd

This file will describe the data structure for each OTM element like ‘Location’, ‘Order Release’, ‘Shipment’, etc along with some documentation.

Say, if we want to upload a new location to OTM, you follow below steps:

1. Read the GlogXML.xsd and identify the XML structure for element “Location”. Once you map your input data values to OTM XML elements, you will end up coming with XML file similar to one below:

DBA.ADMIN CHANGEME Y IU ABC TEST SH OTM CORPORATION-45769 TEST SH OTM COR,CLUTE,TX,USA
1 1039 EAST PLANTATION CLUTE TX 32830 USA
ORIGIN CUSTOMER CUSID 1130 CUSNM MOORE SUPPLY CO CUSTOMER OTM CORPORATION
  1. Save this file with extension ‘.xml’

  2. Once you have XML ready, you can upload to OTM as below: Goto Business Process Automation -> Integration -> Integration Manager -> Upload XML/CSV Transmission and Browse XML File.

  3. Click Upload.

5. You will see following log:

  1. Note the transmission number from the log

  2. Navigate to Business Process Automation -> Integration -> Transmission Manager

  3. Query for transmission and you should see transmission status as ‘PROCESSED’.

In case of errors Report button displays error reasons like foreign key reference missing etc.

Posting XML from Other middleware applications like Oracle SOA/BPEL, webMethods, Mulesoft, etc

Middleware applications can post XML using below details:

Method: POST

OTM Servlet: https:///GC3/glog.integration.servlet.WMServlet

Body Type: Raw

File format: XML

Authorization: Basic Auth (Get domain INTEGRATION username and password credentials from OTM Admin)

Sample Payload to update VOUCHER status:

HTTPPOST

ERROR

VOUCHER

DPSCM

20240823-00001310

IU

DPSCM

PAYMENT STATUS

DPSCM

PAYMENT_RECEIVED

Sample Response from OTM for above request:

<otm:TransmissionAck xmlns:otm=“http://xmlns.oracle.com/apps/otm/transmission/v6.4" xmlns:gtm=“http://xmlns.oracle.com/apps/gtm/transmission/v6.4">

otm:EchoedTransmissionHeader

otm:TransmissionHeader

otm:ReferenceTransmissionNo311245595</otm:ReferenceTransmissionNo>

otm:AckSpec

otm:ComMethodGid

otm:Gid

otm:XidHTTPPOST</otm:Xid>

</otm:Gid>

</otm:ComMethodGid>

otm:AckOptionERROR</otm:AckOption>

</otm:AckSpec>

</otm:TransmissionHeader>

</otm:EchoedTransmissionHeader>

</otm:TransmissionAck>

Using Reference Transmission Number, you can query OTM transmission screen to see if the message is posted to OTM without any errors.

Other methods:

Review below topics for loading data into OTM using other methods:

https://www.oracle-otm.com/2026/03/csv-data-uploads.html

https://www.oracle-otm.com/2026/03/posting-data-to-otm-using-http-request.html

Note: Please post corrections(if any) to ’learnotm@outlook.com