'Move Order to Shipment' Does Not Provide Expected Stop Sequencing
Last updated on APRIL 26, 2017
Applies to:Oracle Transportation Management Cloud Service - Version 6.4.1 and later
Oracle Transportation Management - Version 6.3.4 and later
Information in this document applies to any platform.
You are manually assigning return Orders to Shipments.
The orders are getting moved / added to the existing shipment but the incorrect route (i.e. stop sequencing) is given after planning those Orders on to the Shipment.
The stop sequencing result for the planned route is not optimized.
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