Full-Impact Action on Order Release or Order Movement Errors
(Doc ID 731041.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Transportation Management - Version 5.5.04 to 5.5.04.04 [Release 5.5]
Information in this document applies to any platform.
This problem can occur on any platform.
-- Problem Statement:
On 5.5.04.02, When attempting to unassign order movements, the following error occurs:
<DATE TIME> <VALUE> Error Exception deleteOrderMovements did not execute because of
order movementstatus conflict. See Log for details.
at sun.reflect.GeneratedConstructorAccessor45.newInstance(Unknown Source)
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Setup saved condition additives on Agent Gates for Assign OM and Unassign OM actions
2. Try and unassign an Order Movement
3. The action fails as the code checks the saved condition on agent gate for Assign OM and fails the status check
Due to this issue, users cannot unassign order movements using the custom saved condition check they have configured
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