We ran into an issue today where we issued 5 of lot 1 and 5 of lot 2 for a total of 10. We then needed to return material to make some changes and it allowed us to return all 10 to a single lot number.
Does anyone know if there is a way to stop this from happening or if it was something that was fixed in a later version than 10.2.600? I would think we shouldn’t be able to return more than what was issued per lot number right?
What if you had one left over from another job, and found it on the floor?
Wouldn’t you like to return it?
Ridiculous maybe, but there could be reasons.
I understand what you are saying but wouldn’t it make more sense to then quantity adjust it versus returning the material to the job you are on? Or return the material to the job it started from if you knew? Since we are lot tracking it would be very bad for us to be mixing lots together and calling them the same.
Will I need to add something custom to stop us from being able to return more than was issued per lot?
Yes, you will need a BPM to do this if you want to prevent it from happening. This was always an issue at my previous job.
We have an internal ticket in our system to control that. It will be a BPM. This is how I rough speced it
Thanks! Now I just need to learn how to do the BPM.
Here is the one I just built. Go ahead and test it out if you like see if it does what you need it to. Might have to load it in an upgraded staging database then grab the code out of it.
WCI-6131.zip (26.8 KB)
We are in the process of moving to Kinetic 2023.1 so I may just throw it in there and do all the testing for it and tell users it will be available there if everything works.
I appreciate your help!
It has a bug lol. I forgot to handle null results if no transactions were made at all.
WCI-6131.zip (27.1 KB)
Final working version with error for a lot that was never transacted on the job (null)
Nice, I just had a user ask me if I could tweak a form customization to allow a field to be left blank… In the code I was always assuming they’d put somethign in the field… they also have been getting null reference pop ups because I never thought they’d leave it blank (or in your case, use a non-existing lot number).
