Quote:
Originally Posted by Shells  You've probably already resolved this by now - but just fyi - I have found that building a direct shipment then doing a force merge on the 2 together works much better than moving an order to an existing shipment - esp where the stop does not exist or the weight/volume causes the logic to go a different route. The merge usually works pretty well as long as the dates are aligned in previous versions. |
Hi everyone,
Thanks for your replies - sorry I have not been keeping tabs on this thread as I have been working to resolve a TON of issues on 5.5 with Oracle Support.
Sam: The Itinerary Equipment Consolidation type is NO CONSOLIDATION but with the Build Single Shipment checkbox checked
Shells: Thanks for the tip! I will consider using it as well. Currently I am at my wits end and am thinking of going the Order Release way - moving the Order Release to the Shipment
Everyone: The reply from Oracle is that the code is behaving as it is. For me to do otherwise is an Enhancement Request. I am still in the process of getting Oracle to give me the intended business functionality of this.
Does anyone know what Order Movement > Move To Shipment is for? I am very interested to find out!
Thanks!
Ian