[ianlo]

Hi everyone,

Has anyone been able to move unplanned order movements to existing Shipments using the action > Move To Shipment? I did not check the Consolidate Equipment checkbox.

I keep getting the error:
Failed to move order movements to shipment, see log for details Can not consolidate shipment without consolidate equipments, because can not assign best cost equipment for new shipment. (shipmentPK=DEV/CHN/CENTRAL.01117)

Any ideas anyone?

[bmj_23]

Ian - there are probably a few things you could check:

1. Is the source and destination locations on the order movement the same as the source and destination of the shipment you are trying to add it to ?

2. Also, when you create an order movement, it is based on an itinerary and the order movement contains a reference to the itinerary leg on which it was created. Is the shipment you are trying to add this to based on the same leg gid ?

3. I dont know the exact rules on what that action does, but I do know that using that action for an order release works very well. Therefore, it may be some restriction based around the fact you are using OM's. If you wanted to test that, you could try the same scenario using an OR instead of an OM.

If you post the bottom of the log file which contains some SQL and more detailed debug someone may be able to identify the exact problem. Definitely log an SR if you have not already done so.

[ianlo]

Originally Posted by bmj_23

Ian - there are probably a few things you could check:

1. Is the source and destination locations on the order movement the same as the source and destination of the shipment you are trying to add it to ?

2. Also, when you create an order movement, it is based on an itinerary and the order movement contains a reference to the itinerary leg on which it was created. Is the shipment you are trying to add this to based on the same leg gid ?

3. I dont know the exact rules on what that action does, but I do know that using that action for an order release works very well. Therefore, it may be some restriction based around the fact you are using OM's. If you wanted to test that, you could try the same scenario using an OR instead of an OM.

If you post the bottom of the log file which contains some SQL and more detailed debug someone may be able to identify the exact problem. Definitely log an SR if you have not already done so.

hi bmj_23

thx for the reply!

1. Yep same source and destination
2. Are you refering to the Original Leg ID or just the Leg ID? For each of my order movements, the Leg ID is not the same but the Original Leg ID is.
3. Yeah will try OR's but that would totally break my modelling as we have made the decision to go with Order Movements. Still will try to see if we can find a workaround if OM's fail.

Thx!

[bmj_23]

Ian, post the final 20 lines from the Planning log file when you are running this action and lets see if we can see what is happening there...

[ianlo]

Hi bmj_23,

Sorry I did not see your reply. Please find the logs as attched.

Thanks!

[bmj_23]

Hi, its not clear from that log file exactly what the issue is but it looks like OTM is failing to find a valid rate for the shipment that you are trying to create by adding the OM to the existing shipment.

This may be a problem with the rate that OTM is trying to use to rate the shipment, indicated by the text "rate engine result 1 was filtered out due to rate service constraint" in the log file.

I would think the best way to resolve this is to log an SR. There is nothing I am aware of in the set up you have explained which should prevent this action from working.

[ianlo]

Hi bmj_23

Thanks! I have logged an SR and will be having a OWC. Will update with any findings!

Ian

[samuellevin_mavenwire]

Ian
There is a option on the leg of the itinerary for equipment consolidation type. Can you tell me what it is set to?

[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.

[ianlo]

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