I am doing some testing with UOM conversions -
The current approach in E9 and E10 as many have found is limiting.
The other issue that you run into is that after you have entered in a conversion rate on a part and do a transaction, the conversion is locked.
I believe that you can get a fix from Epicor, but not sure about that.
When is the conversion of one UOM to another really used?
For most - it is when you are buying a material like steel by the pound but putting into inventory as feet, or hardware by the box and inventory it as each.
I created a PO Line for some hardware with a UOM of EA and checked the override conversion and entered LB in the UOM for the supplier.(note - LB was not a UOM in the UOMClass of Count)
I entered in my price per pound and was able to process the transaction. The parttran is recording the inventory unit of measure only. The purchase UOM is for information only.
What is another reason to approach it this way?
When you buy a box of screws from one supplier it will be 30 but another supplier is 50.
When buying steel the extrusion die changes over time and the conversion of pounds to feet changes
You can override the conversion at the time of receipt also, that may become your choice.
Now the next step in this journey is to review using the weight on the part which is the weight per inventory unit of measure.
I have found that the Part table still has the purchaseFactor, purchaseFactorDirection, SalesFactor, Salesfactor direction. Also available is the netweight, length, width, height, thickness and volume per inventory unit of measure along with the uom of each of those measurements.
Now the challenge is to create the BPM to populate the PO Line with these “adhoc” conversions by part.
Looking for thoughts on this from the group.