When Unassign Order Movement Fails for any Reason its SHIPMENT_GID is Removed but SHIP_UNIT Data Remains - Leaving Order Movement with Corrupted Data
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Operational Planning - Version 6.2.0 to 6.2.7 [Release 6.2]
Information in this document applies to any platform.
If there is a failure (for any reason) during the Order Movement Unassign, the Shipment GID is removed from the Order Movement, whereas the rest of the data (e.g. reference to ship_unit) remains. This leaves the Order Movement in a corrupted state.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms