When you create a Nonconformance with DMT, it does not seem to reliably honor the “STOP” option on a part class (to prohibit negatives). Out of 3 or 4 tests where a bin would go negative (or was already), only once did the DMT not allow it to go through.
The UI did block me as expected.
Reason for this discovery is that I was working on an Epicor Function to create a Nonconformance. (It’s done and working now.)
I traced the UI and the DMT. I started with DMT, since I thought that would be nice and streamlined.
Well apparently DMT and the UI use different BO methods for checking for negative inventory.
DMT uses NonConf.NegativeInventoryTest
UI uses NonConf.ValidateQtyInventoryTest
So I made my EFx with ValidateQtyInventoryTest and that has worked well in testing, even when I tried to confuse it with odd UOMs.
I mean, just imagine how long it would take to explain this.
Yes, you all understand it in a couple minutes. But the burden of proof required for me to convince EpicCare is monumental. How many times are they going to tell me to consult Professional Services?
No thanks; I’m good.
Nonconformance via DMT is pretty rare (on this site, it sure is anyway).
Blocking negatives is also not terribly common.
Combined, it’s like Halley’s Comet. The odds of this are miniscule.
The only person I would ever expect to need to know this is the one who is trying to make an Epicor Function like I am doing.
Sure the fix is simple - the DMT should use the same method as the UI. But I’m not fighting that fight.
