I think I may be facing off with some ghosts from our Epicor past.
First off, we do not have the Quality module. We have a customization on the Receipt Entry screen that contains 5 UD fields for measurements but also uses the RcvDtl.InspectionDate field to hold the date the user enters the inspection values.
However, I realize that anytime that Inspection date field is used, we are getting a (UNINTENDED) line in the time phase for that part number that says inspection. This is happening for all receipts where a date is entered.
I have done a BAQ on the RcvDtl table and for all these lines, “Inspection pending” checkbox is set to true. I tried to use DMT to set it to false in TEST enviro but failed.
Oddly enough, we never noticed this since the received lines are hitting inventory and I see no PUR-INS lines in tran history (we only have one bin, one warehouse and one site):
I don’t know where to go from here. It looks like, from my testing, that the part gets an inspection line in time-phase the minute a value is entered in RcvDtl.InspectionDate field and once entered cannot be undone. This implies to me that a new record has been created somewhere but I donbt know what table to look in.
Can anyone guide me as to how to undo this mess? I only came across it when I tried to change costing method on MTL parts and the parts that are in “Inspection Purgatory” cannot be effectively zeroed prior to DMT.
Hmmm … I missed it if you already said it, but does this happen 100% of the time, or just on items that you use your home brewed QA customizations on?
The description for the InspectionReq field is:
Indicates if this receipt will be categorized as requiring inspection. It is set to Yes if any of the related Vendor, PartClass, PoDetail, JobMtl, JobOper have their RcvInspectionReq field = Yes.
If I had to guess, its happening because you used some of the built-in fields related to Inspection. And some BO is picking up on that and getting in the way.
It ONLY happens when we enter a date into the inspection date field. I agree that the misuse of these fields is causing us pain. Its confusing though, as the “Inspection Required” box is never checked on any of these records. Only “Inspection pending”. Hmmm.
I’d guess that something else normally clears that pending. Do you use the PassedQty and FailedQty fields?
Maybe do a trace to see what BO’s are being called. And find the one that is setting the pending flag. Just to prevent it from doing so. But you might need to do a little SQL magic to fix the existing RcvDtl records.
No, no QA components. Which I suppose is why we felt safe hijacking the inspection date field on RcvDtl, since we thought it unlikely to impact anything, given that we have no QA module.
Did you check to see if the module was just hidden in Menu Maintenance? I could have sworn that the base Quality module came with Core Epicor. I thought that anyone who had Production had Quality.
Also, are you on one of the versions that has your license info in Company Configuration? You could double check to see if you are licensed for Quality Assurance.
I am thinking maybe I need to DMT received qty to = passed qty. Does that seem reasonable that that might resolve? I am dabbling in TEST enviro so no damage done…
