ReleaseInstruction XML Updates Existing Release Instruction Instead Of Creating New One
(Doc ID 1457073.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.0 to 6.3.0 [Release 6 to 6.3]Information in this document applies to any platform.
Symptoms
A Release Instruction is provided via XML. This is updating an existing Release Instruction instead of creating a new Release Instruction.
The original Release Instructions were created via the UI (e.g. Ready to Ship action). When creating the release instruction this way, the DB Sequence named OB_RELEASE_INSTRUCTION_SEQUENC is not modified. However, when the Release Instruction is provided via XML, the DB Sequence is being checked for the LAST_NUMBER. If a Release Instruction exists with this LAST_NUMBER, it is the one updated. Since the sequence is never modified via UI actions, this LAST_NUMBER is never matching the actual values used. Furthermore, there is only one Sequence, so this LAST_NUMBER can not be maintained for multiple Orders.
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 |