ORDER RELEASE MOD - EDIT SHIPMENT Action Fails with "Cannot update the S_SHIP_UNIT record. [SHIP_UNIT_GID] must reference a valid SHIP_UNIT record" Exception When Replacing Line/Ship Unit and Updating Order
(Doc ID 2436840.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.7 and laterOracle Transportation Operational Planning - Version 6.3.7 and later
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When sending in an order modification for an order planned onto a shipment, the ORDER RELEASE MOD - EDIT SHIPMENT agent action fails with the below error. The modification consists of replacing an order release line/ship unit with a new one, along with updates to the remaining release lines within the order release.
ERROR
---------------
EXPECTED BEHAVIOR
-----------------------
The OMD MOD EDIT SHIPMENT agent action should execute successfully with no errors.
STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Upload a Release XML to create Order Release in OTM with multiple release lines and ship units (one to one configuration)
2. Plan the order release onto a Shipment
3. Upload the second XML (order update) with RC transaction code containing same order release, replacing one OR line/SU with a new one, and updating the remaining release lines within the order release.
4. A previously configured OMD agent with the agent action ORDER RELEASE MOD - EDIT SHIPMENT is triggered upon receipt of the order modification XML.
5. The agent action ORDER RELEASE MOD - EDIT SHIPMENT fails with the above exception.
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 |