[jeff.depaul]

Thanks Chris,

Some additional context on the above issue which might be helpful to others facing similar challenges and as to why this approach was taken (it is implemented & works beautifully by the way) for removing the order from the shipment.

I am the tech lead for the project Krishna is working on and we are in the final stages of integrating EBS & OTM using Fusion 10.1.3.3. The approach of having to update all 400 ship units actually stems from the fact that our company has multiple packaging or UOMs for the same item shipping from different DC's. In EBS, this requirement is handled using multi-org functionality. The seeded integration shipped with the EBS/OTM product however, completely ignores multi-org setups for items. In fact, EBS items are "duplicated" in OTM since the item IDs are truely unique (by Org) although the item name is not.

So, our design on Item synch in Order Release needed to accomodate via the ship unit level. We concatenate the Org and UOM to the item iteself to overcome this limitation and keep items "Org specific".

The real issue is that true multi-org functionality (as designed in EBS) does not exist within OTM v.5.5 CU2. Would be very interested if there is any buzz of future releases supporting this requirement - does anyone know?
-Jeff