Removing UOM from Class after UOM Conversion

Epicor ERP 10
14

This all comes down to a bug in Epicor that they would never admit to in the course of a ticket that I had open for three weeks.

I have A LOT of info on this, but I’ll try to be brief.

When you try to inactivate the conversion, it’s supposed to be checking the “HasBeenUsed” field in UOMConv. But it’s coded wrong. It checks the equivalent field in the UOM itself.

The result of this is that I could do conversions with an obscure UOM but not EA, for example.

Part of the dialog in my support ticket:

Support:
Expected Behavior:
“You should be able to delete the UOM Conversion record (UOMConv) from the UOMClass as long as it has never been used in any conversion.”
Check the UOMConv table and look for the has been used flag

Me:

  • In the CONV2 class, the 100-PK UOM “Has Been Used” and yet I am able to inactivate
  • Also in CONV2, the 10PACK UOM “Has Been Used” and I cannot inactivate
  • And then just now I converted my part from FT in CONV2 into FT in CONV3 and I was just able to delete all of the CONV2 class, despite it having so many “Has Been Used” UOMs in it.
  • How am I allowed to delete the whole class but not even able to inactivate a UOM inside of it?
3 Likes