| | Order Processing Shipment planning and order processing - including data requirements, line items, ship units, order bases and order releases. |  | | 
July 24th, 2007, 21:24
| | Senior Member and Blogger | | Join Date: May 2007
Posts: 170
Thanks: 4
Thanked 31 Times in 31 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 2 | | | Re: OTM 5.5: Unable to Move Order Movements to Shipments Ian - from reading the GC3 help, it looks like the action to move an order movement to a shipment should work fine. If you have a shipment from A-B and a corresponding order movement from A-B that you want to add to that shipment, this order movement action should allow that to take place without any issues.
If that is failing, what exactly are Oracle support saying that an enhancement request should do that the current code does not support ? Would be interested in hearing that. | 
August 3rd, 2007, 03:07
| | Senior Member and Blogger | | Join Date: Dec 2006 Location: Singapore
Posts: 149
Thanks: 5
Thanked 11 Times in 10 Posts
Groans: 0
Groaned at 1 Time in 1 Post
Rep Power: 2 | | | Re: OTM 5.5: Unable to Move Order Movements to Shipments Quote:
Originally Posted by bmj_23 Ian - from reading the GC3 help, it looks like the action to move an order movement to a shipment should work fine. If you have a shipment from A-B and a corresponding order movement from A-B that you want to add to that shipment, this order movement action should allow that to take place without any issues.
If that is failing, what exactly are Oracle support saying that an enhancement request should do that the current code does not support ? Would be interested in hearing that. | Hi bmj_23,
Yeah that was what I told Oracle support as well. I have asked them for a detailed description of what the code was supposed to do - but they have not responded to me.
In addition, I just found out that Delete Order Movements only work when there are "orphaned" OMs as a result of Actual Shipments via Integration. - interesting isn't it? Likewise, they did not mention this in the help.
I am beginning to think that OMs were speced out for a very narrow purpose which was not documented properly in help - hence the confusion.
Will let you know once I get anything back from Oracle
Cheers!
Ian | 
September 5th, 2007, 10:07
| | Senior Member and Blogger | | Join Date: Dec 2006 Location: Singapore
Posts: 149
Thanks: 5
Thanked 11 Times in 10 Posts
Groans: 0
Groaned at 1 Time in 1 Post
Rep Power: 2 | | | Re: OTM 5.5: Unable to Move Order Movements to Shipments Hi,
Just a quick update, word from Oracle is that this does not work for shipments with interim stops  ...
But in our tests, even with a shipment with a simple 2 stops, point-to-point still does not work ...
Anyone has gotten moving Order Movements to shipments working?
Ian | 
July 20th, 2008, 17:45
| | Member | | Join Date: Dec 2007 Location: Mumbai
Posts: 95
Thanks: 11
Thanked 2 Times in 2 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 1 | | | Re: OTM 5.5: Unable to Move Order Movements to Shipments Ian,
Did you receive any solution for this from Oracle? Or what was the work around you have done.
regards
Vipin | 
July 21st, 2008, 03:37
| | Senior Member and Blogger | | Join Date: Dec 2006 Location: Singapore
Posts: 149
Thanks: 5
Thanked 11 Times in 10 Posts
Groans: 0
Groaned at 1 Time in 1 Post
Rep Power: 2 | | | Re: OTM 5.5: Unable to Move Order Movements to Shipments Hi Vipin,
To be specific, we heard from Oracle that move order movements to shipments does not work with Single Shipment - Multiple Equipment model (which we are using for some cases). We submitted an Enhancement Request and Oracle maintained that they will not support move order movements to shipments when the shipment has multiple equipments As of CU3 RU6, we are able to move order movements to shipments provided the following are met:
(1) There's only one equipment in the shipment.
(2)There is an equipment defined in the itinerary/carrier rates that is able to accommodate the whole ship units being merged together (original ship units in shipment plus those belonging from the OM being moved).
For the time being, we are using a manual workaround in our ops to circumvent this issue. However, we are moving our model to the Single Shipment - Single Equipment model and once that is completed, we should be ok.
There was a null pointer exception bug raised my my team - this is supposedly fixed in CU4 RU2.
However, due to go-live contraints, I am not able to test this on CU4 RU2.
Hope this helps!
Ian | | The Following User Says Thank You to ianlo For This Useful Post: | |  | | | Thread Tools | | | | Display Modes | Linear Mode |
Posting Rules
| You may not post new threads You may not post replies You may not post attachments You may not edit your posts HTML code is Off | | | |