Object ID Not Stored Correctly in I_TRANSACTION when Using Integration Saved Queries
(Doc ID 2625180.1)
Last updated on APRIL 07, 2020
Applies to:Oracle Transportation Management Cloud Service - Version 19.3 and later
Information in this document applies to any platform.
When using an integration saved query within an inbound XML to OTM, the OBJECT_GID that is stored in the I_TRANSACTION table for a respective transmission is the result of the first Integration Saved Query (ISQ) that is contained within the XML. The integration saved query itself may not necessarily be querying the respective transaction element, and is querying a child element.
It is expected that the OBJECT_GID of the respective transmission be stored correctly in the I_TRANSACTION table and not stored as the result of the first ISQ contained in the XML.
The issue can be reproduced with the following steps:
1. Send an inbound transmission to OTM containing an integration saved query for a child object. For example, for a Release XML, reference an integration saved query for specifying ship_unit_gid for the order release within the XML.
2. The transmission will process successfully and the object will be created with the expected IDs
3. Review the Transmission Manager for the respective inbound transmission from Business Process Automation -> Integration Manager -> Transmission Manager
4. The object_gid for the transaction (which in this example should be the GID of the order release) will be the result of the integration saved query (which in this example is the GID of the order release ship unit).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document