ORDER RELEASE - MOD - EDIT SHIPMENT Agent Action in OMD Agent Is Not Triggered To Update Shipment When Adding An Order Release (OR) Line To Exisiting OR Planned On a Shipment
(Doc ID 2200045.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.4.1 to 6.4.2 [Release 6.4]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
An order is created by sending a Release XML inbound to OTM with an order configuration of ONE TO ONE (ex: 2 lines and 2 ship units). The order is planned onto a shipment. A second Release XML is sent to add a line and ship unit with transaction code RC. The order is modified successfully. The ORDER RELEASE - MODIFY agent is active which is triggered by this integration. The agent action ORDER RELEASE - MOD - EDIT SHIPMENT is not triggered as the condition CheckEditableShipment logic still returns false when adding a ship unit, even though it is just a quantity change.
EXPECTED BEHAVIOR
-----------------------
It is expected that the agent action ORDER RELEASE - MOD - EDIT SHIPMENT be triggered to propagate the changes to the respective shipment. This is with the expectation that a quantity change (by adding a line item on the order) should pass the logic of CheckEditableShipment as a true condition.
STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Upload an order xml to create the order
2. Plan the created order onto a shipment
3. Upload an order xml to modify the existing order by adding a ship unit / line.
4. By looking at the logs you will see that the following which indicates that the condition returned false and ORDER RELEASE - MOD - EDIT SHIPMENT was never executed:
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 |