OTM Integration

Inbound Data Methods

• HTTP

1. WMServlet is the default servlet used when sending the Transmission http://hostname/GC3/glog.integration.servlet.WMServlet 
2. Large Transmission Servlet
3. Transformer Servlet(XSL Files)
4. DirLoad Servlet(The DirLoadServlet does not raise events (like shipment - created for ActualShipment) so automation agents cannot be triggered)

• Send Via Web Interface to Application Tier
• Oracle Advanced Queuing
• Manually Upload XML
• Direct XML Insert into transmission table(pkg/proc name --> pkg_integration_util. insert_transmission).

XML documents being sent inbound to Oracle Transportation Management are not required to specify the namespace in the XML. OTM will automatically generate XID based on BN generators in OTM

Data Queues:

The inbound data queue events reside in the Q_INTEGRATION_IN Data Queue table. 

The outbound data queue events reside in the Q_INTEGRATION_OUT Data Queue table.

By default the PUBLIC queues are inactive. To activate the queues, login as DBA.ADMIN and edit the Data Queue records via the Data Queue Manager (under Business Process Automation à Integration menu). 

Transactions:

You can send many transactions in or out of Oracle Transportation Management in one transmission

but to separate the transactions, every transaction must be wrapped in a GLogXMLElement.

A Transmission Body element wraps one or more GLogXMLElement elements in a Transmission

Transmission Status:

• STAGED: Indicates that the Transmission is initially stored in the transmission tables, and is awaiting some pre-preprocessing steps such as sequencing of the Transactions for processing.
• STAGING: Indicates that the Transmission has been staged and is waiting on a condition to be released for processing. Additional transactions can be added to it prior to processing.
• FRESH: Indicates that the Transmission is waiting to complete processing. The individual transactions may still be processing.
• ERROR: Indicates that the Transmission had completed processing and there were errors in the processing.
• PROCESSED: Indicates that the Transmission successfully completed processing.
• REDO: Indicates that the Transmission is waiting for the REDO logic to initiate re-processing.
• MESSAGE: Indicates that the Transmission is a Message

Blank Out Certain Fields: To delete (null out) values from certain fields in a record (without deleting the whole record), you can specify the (~) character in the element.

Integration Saved Queries:

• Arg Values: The queries are written as SQL statements that contain references to the information in the incoming XML transmission 
• XPath Reference: The queries can also be written using XPath expressions to search for values from specific elements in the XML

Transaction Code  DR (Delete Reference)  will only delete reference between objects and not the object.

Transaction Code RC (Replace Child)  will update the parent element and delete and replaces the child elements.

Processing Codes for TransOrder XML

• NOPLN: Instructs OTM not to plan shipments
• PLN: Instructs OTM to plan shipments from OR assuming transorder setup to create order release already exists

Outbound XML Profiles:  Out XML Profiles are used to exclude portions of outbound XML with a high degree of control.

OTM can automatically change text to upper case when processing the inbound XML by setting the below property to true.

glog.integration.enableCaseChange=true