Invoice RefNum Set to "One, Updates" is Adding Duplicate RefNum Instead of Updating Existing Value
(Doc ID 2041421.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.2.3 to 6.3.1 [Release 6.2 to 6.3]Information in this document applies to any platform.
Symptoms
A invoice includes a RefNum with a current value. This Refnum Qualifier is defined as "One, Update".
A XML of type GenericStatusUpdate or Payment is created to update an INVOICE and includes the above RefNum Qualifier with a new Value. When the XML is processed, it is found that a new RefNum row is created for the same RefNum Qualifier, therefore creating a duplicate. The existing RefNum row (with original value) remains along with a new row for the same RefNum with the value included on the XML.
It was expected to have the XML update the value of the existing refnum, instead of creating a duplicate.
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 |