Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version: 5.0 to 5.5
This problem can occur on any platform.
If the action 'Move to Consol Shipment' is done for an order movement already on a vessel (the primary leg of the itinerary in the example), it is unassigned from this original primary leg shipment, no matter if the order movement fails to plan onto the new consol or not. However, in both cases, the shipment_links remain between the primary leg shipment and the first leg of the order movement - this causes problems when the order movement is planned onto a new shipment.
Steps To Reproduce:
1. Go to Order Management > Order Release > Order Movement - Search for a multi-leg order movement.
2. Select an order movement that is on a consol shipment> actions > 'Move to Consol Shipment'.
3. Select another consol shipment and assign the order movement. The result of the action is irrelevant.
Run the following command through the sql backdoor:
select * from shipment_link where prev_object_gid like '%NAME OF ORDER RELEASE%'
There are entries for two shipments in the shipment_link table, despite that the order release was moved from one shipment to the other (or attempted to be moved if the action fails). When the shipments are queried (through the shipment manager), the order release is no longer on the shipment in question. But according to the above, the links still exist in the shipment_link table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms