I’m looking for help to create a BPM to block users from doing an inventory transfer on a lot tracked part if they forget to pick the lot number on the From warehouse. This is a glitch that Epicor has not fixed since 10.1 and every time it happens I have to get them to make a fix to correct the part that now has a blank negative lot transaction. It gets annoying because it takes at least a day for them to figure out what I need and then it still never works out right in the end.
Any help on how to write that would be great. I can’t make it just a required field since that prevents inventory transfers of SN tracked parts since that LOT field is left blank and inactive.
I had something like this very similar setup to prevent some other issues, they worked great in 9, but going to 10 they stopped working. I’ll have to check them and see if it’s the same logic as you described to see if it may present the same problem of being ineffective.
Here is an example of one I had for making Part Class mandatory but I had to do that via extended properties. This BPM didn’t work after going to 10.1.
That’s what I would expect to see, but amazingly it does not come up when you forget a from lot number on my system. I can reproduce it at any time too.
No, it was done on a part that has always been lot controlled, has no QOH without a lot number, and when the process happens we end up with a negative blank lot number on the from warehouse. Of course you can’t fix that either because every other function prompts you with the “lot required” error. Every part in our DB is either LOT or SN controlled and I can take any part and mess it up this way. I’m up to case number 7 with support on getting fixes to remove the negatives from the mistake.
That is a good question and why I posted this, I hoped someone would know the proper context. Also in response to your other questions, we have no other BPM’s on that method directive at all. We have maybe 6 in total on other directives, and I think 4 are circumvented by required field check box in extended properties now. I need to verify that and remove them if they are.
Seeing as how we don’t have much custom programming I’m unfamiliar with how to run a trace, so I’m glad you did to see what is used. I will try it against the PreCommitTransfer as Ron noted, as well as check it against the Part.Tracklots value. It sounds like it works for him, so hopefully it does for me to.
Thanks Calvin.
Ron, when I setup the BPM on PreCommitTransfer I do not have the option to check against the field Part.TrackLots, the only option available for a field is the ttInvTrans.TrackLots field. Can you link the BPM to check other tables not present in the current method?