Full-Impact Action on Order Release or Order Movement Errors
(Doc ID 731041.1)
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version: 5.5.04 to 5.5.04.04
This problem can occur on any platform.
On 5.5.04.02, When attempting to unassign order movements, the following error occurs:
2008-06-09 17:21:36.63 849470 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
-- Business Impact:
The issue has the following business impact:
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|