My Oracle Support Banner

Wrong SenderTransactionId Is Used in Tender XML When Using HTTPOST Communication Method (Doc ID 2207042.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Transportation Management - Version 6.0 to 6.4.3 [Release 6 to 6.4]
Information in this document applies to any platform.

Symptoms

A Service Provider is configured to send Tenders via HTTPPOST. When a tender is sent, two Transmissions are created (one with the External System and one without). As per Note 1384278.1, the two transmissions is expected behavior and only one is actually sent.

However, if the XML reviewed from the XML that was actually sent, the "SenderTransactionID" on that XML is the wrong Transaction ID. The one seen is the Transaction ID from the Transmission that was NOT sent.

Note: The XML correctly identifies the "SenderTransmissionNo" with the Transmission ID of the transmission actually sent.

Changes

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.