Is it possible to write more than one nonconformance on an operation?
The job is for quantity 1, so when creating an NC for quantity 1 and then trying to write another NC, I get error “The Non-Conformance quantity cannot be greater than the completed quantity of 0” I am assuming because there is already an NC for qty 1 and the op is for qty 1.
Any way around this?
From the system perspective it’s still one NC transaction. You’re moving that piece off the job and into the inspection-DMR pipeline. Which mirrors what you’re doing physically.
The issue (as you know) with that model is that often pieces are non-conforming for multiple reasons. So you want to catalog each failure, but the system only let’s you pick 1 reason per transaction. So you’re typically left with 3 out of the box options:
-
Put the additional issues in the comment fields, which is awful for data analysis, but requires zero implementation time.
-
Run the part through the whole NC-Insp-DMR pipeline multiple times. Captures the data in a way that’s easy to aggregate but is extremely tedious.
-
Build inspection plans for each part, which capture all significant features (conforming or otherwise) simultaneously. Ideal from an operational side, but can take years to set up fully.
All of these have significant drawbacks. Still, my org is working (eventually) towards the last one. In theory.
However, as an interim solution, I bootstrapped a UD table to the NonConf, RMA, Receipt, and DMR tables. This lets QA catalog multiple reason codes to each non-conforming transaction. It has been quite successful. It is also the most difficult customization I’ve ever added to Epicor. Inspection Processing is 4 entirely separate apps in a trench coat. So I’m not sure I’d recommend that route to anyone else. I’m not sure I’d recommend it to myself, but it was the best choice given the resources available.
3 Likes