Data transfers to / from Oracle Transportation Management

Datetime:2016-08-23 02:24:30          Topic: Oracle  XML  Web Service           Share

Oracle Transportation Management (OTM) manages all transport activity across the supply chain cycle. It provides features to enable users to manage master data like location, corporation, equipment, item, commodity, rates, etc., and also monitor transaction data like order release and shipment data. However, OTM cannot work as a standalone system, as most organizations maintain their master / transaction data in enterprise resource planning (ERP) systems. Integration helps bring ERP systems and OTM consolidate data, which is critical for a comprehensive logistics system. 

OTM exchanges information in the form of XML (GLogXML), thus making it mandatory for the interacting system to process XML also. An ERP system, on the other hand, has its own methodology to store and communicate information. For example, Oracle E-Business Suite (EBS) stores data in an Oracle Database, SAP stores it in the 'Pivot' format, and Electronic Data Interchange (EDI) stores data in a predefined format. For these systems to interact with OTM and exchange messages, a middleware that can appropriately translate messages between them is required.

Exchange information from ERP systems to OTM

Exchange information from OTM to ERP systems

Although OTM is compatible with most middleware software's currently available in the market, Oracle Fusion Middleware is recommended for integrations. Additionally, Oracle also offers its Process Integration Pack (PIP), which seamlessly integrates EBS and OTM using Fusion Middleware.

The GLogXML schema is the back bone for integration and consists of the 'Transmission Element,' which is the primary document for inbound / outbound integration. The 'TransmissionAck' element represents acknowledgement from OTM for the sent / received transmission. Transmission Report presents the summary of errors encountered during the integration process.

Transferring Information from ERP systems to OTM

Messages can be posted to OTM in one of the following four ways:

  • ·          HttpPost

o    WMServlet: Default servlet to post transmission to OTM

http://hostname/GC3/glog.integration.servlet.WMServlet

o    TransformerServlet:  Applies XSL transformation to XML data in order to generate a valid transmission XML and upload it to OTM.  The XSL file should be uploaded in OTM, which will be used for inbound transmission

http://hostname/GC3/glog.integration.servlet.TransformerServlet

o    DirLoadServlet: Bypasses application server to upload data into OTM. This will be used when data is loaded into OTM and processed later

http://hostname/GC3/glog.integration.servlet.DirLoadServlet

  • ·         Web service: OTM supports Simple Object Access Protocol (SOAP) Web Services (IntXmlService) for inbound transmissions. The web service is deployed in the application server
  • ·          Oracle Advanced Queue (OAQ): OTM supports Oracle Advanced Queue (OAQ) for sending and receiving XML transmission to/from OTM. The advantage of using OAQ is that it guarantees message delivery.
  • ·          Manual upload: Upload the XML file from OTM's front end. This is predominantly used for testing

OTM authenticates the username and password specified in the transmission XML.

Username and password can be specified in the HTTP header, when GLogXML is posted via HTTP post to WMServlet.

When GLogXML is posted via web service, username and password can be specified in the web service security token.  

Transaction Code in GLogXML helps OTM identify the operation to be performed on the received transmission. Transaction Code I (Insert) creates a new record; II (Insert Ignore) creates a new record if the record does not exist; U (Update) updates the existing record; D (Delete) deletes the record; NP (No Persist) does not persist data in the database; and R (Replace) replaces the parent and child objects.

Transferring data from OTM to ERP systems

A message can be posted from OTM in any one of the following ways:

  •             Automatically as part of workflow notifications
  •             Manual Scheduling outbound transmissions

At the same time, an external system can be configured to post data from OTM to:

  •           FTP server
  •           HTTP/HTTPS
  •           Queue
  •           Web service

Out XML Profiles help exclude portions of XML while posting out of OTM. This also reduces the size of the XML file and improves performance.

Although OTM provides multiple options to send / receive information, a web service is the recommended approach to interact with OTM as it is highly scalable, can handle huge volumes of data, and supports multi-threading.

Be a part of our sessions at the OTM SIG Conference 2016 in Philadelphia. Join our experts at the Infosys booth and we will be delighted to walk you through our solutions.

Written by: Ravi Kiran Gurujala





About List