My Oracle Support Banner

Issue with Direct XML Insert (Doc ID 1493965.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Transportation Management - Version 6.2.7 and later
Information in this document applies to any platform.

Symptoms


Legacy application is being integrated with OTM using interface layer(middle-ware) using Direct XML Insert feature for incoming messages into OTM (to improvise the performance due to huge number of transactions involved per day.) Upstream application pushes messages having transmission no (alphanumeric character) through interface layer to OTM. Here they invoke the Direct XML related PL/SQL API: pkg_integration_util package to insert messages directly into DB. The integration fails because of they are sending transmission no with alphanumeric character.

While they upload the same XML message directly using upload feature through UI, that works fine and SAW shipment gets created. Here we observe that SENDER TRANSMISSION NO is updated against the SENDER_TRANSMISSION_ID column in I_TRANSMISSION table instead of SENDER_TRANSMISSION_NO column so it accepts any data-type and max upto 200 characters VARCHAR2(200)



Cause

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
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.