Hello,
We have run into a bit of a dillema today whilst working through importing Landed Cost Containers from our old system to E10.
We have discovered that the volume calculation on the LC container lines actually takes the Net Volume value from the part and multiplies it by the XRelQty field on the PORelase. So for scenarios where we have complex UOM conversions (for example Qty5 of a 2.4M length) the volume is calculated incorrectly.
I am trying to devise a way that will enable us to substitute the correctly calculated volume into the Volume Field on the ContainerDetail.
It appears we may need two BPMs to cope with the two methods of putting a PO release line on the Container, one for the Add MultiShip lines as it fires the CreateMultiDetails method and the PreUpdateContainer method when you add an individual line.
I am hoping that If I grab the ContainerDetail.IUM and then lookup the PartUOM.UOMCode and muliply the ContainerDetail.PORelXRelQty with the factors working through the UOM conversions to get the correct calculation out the other end to M3, and then substitute the ContainerDetail.Volume value with the newly calculated one, it will work. I clearly want to avoid any situation where calculating the volume goes through all detail records when we save/update is fired as there is the potential for hundreds of POreleases per container.
So at this point I’m going to ask two questions.
-
Has anyone seen or had to do this before with regards to calculation of the Volume on Landed Costs
and -
Does this sound like a sound approach or can someone provide a better suggestion.