Is there a way to break an NC or DMR connection to an active job while keeping the part in DMR?
My issue is that my production floor is unable to close jobs while I have active investigations going on with various parts. For instance, a PCBA subassembly may have been non-conformanced due to a test failure during production. I may move it to DMR and give it to an Engineer to do additional testing and root cause analysis, but the production floor may have completed and ship the product in that job before an answer is found.
Since the NC/DMR is still connected to that job, they are unable to close it out.
Thank you, Vinay. It seemed like that was the case.
Anyone have a workaround process that I can implement? Currently, I’m considering accepting to stock, then placing in a non-net inventory warehouse and bin. It’s messy, though, and I don’t like pulling items out of NC until they have been fully reviewed and dispositioned.
the close process is trying to protect you from yourself… it is saying “Hey, you have an open transaction that will happen at a future date. You are not allowed to Close this”.
I believe you SHOULD be able to COMPLETE it, which would take the job out of production.
The way I explain the difference is:
“Complete” says you are done in Production
“Close” says you are Financially closing the job.
There are other times that this may be the case… (but not always handled as friendly as this):
you have an uninvoiced AP Invoice on an Outside Processing operation
same for a purchase Direct Material
Anyway, the way around this is to not do the DMR against the job… but instead, receive the product to stock and then reject it from there. This way the job doesnt see the open transaction.
@Zodiac7
Epicor standard functionality is logical, jobs can not be closed until all NCR/DMR been dealt with, so in order to monitor this process i have created a dashboard to check Open WIP Jobs with received to stock qty, NCR qty, scrap qty, and DMR rejected qty, once the four numbers matched then raise a flag to close the relevant job, production planner to check this dashboard daily, however you can schedule a task to scan through this BAQ and alert whoever you want about an open Job need to be closed
Tim - Thank you for the info. I’ll check into the “Complete” status on the jobs and see if that will be the best path for Accounting and Production.
From a QA side, I recognize and agree with the many reasons to maintain the connection to the job; both financial and for tracking failures back to production lots. I’m stepping into this company with some imperfect uses of the software, though, so am trying to keep things functioning while we adjust the norms.
This would be a great tool to use. I’m afraid my Epicor skill will need some expansion to build something like this.
Currently, I am spending an unnecessarily long amount of time back-tracing from Job Tracker to identify which NC items are related to a job, then moving them through NC/DMR. Many of our items may sit for several months before they complete a recondition/quarantine period for final evaluation. The issue is that I have many part numbers, many of which have many lot numbers in a small period of time, and failures are created daily and/or by job completions. It is a lot of hands on management of individual line items.
Definitely some improvement needed on our end! I will look into creating a dashboard similar to yours. Thank you for the help!
I have multiple jobs that they are trying to close. Since the items are already in NC (or possibly DMR if being actively reviewed), I don’t know of a way to remove the material from the job(s) at this point. My workaround for the moment is to accept to stock and move items to the MRB warehouse to keep them non-nettable. It is messy, though.
We have a workaround for a commodity material that is used in our product. This item falls out regularly and generates multiple NC’s/day, which causes issues trying to close jobs. These cannot be released from DMR until testing determines if it can be recovered or salvaged, which can take months due to the quantity.
We created a non-nettable bin in the MRB warehouse that only stores these items for recovery. We “accept to stock” from DMR into this location, using a reason code “Issue for Reprocessing”. These items are then put through our test/recovery process when possible, with the rejects going back into NC.
This is messy and generates a considerable amount of extra work, particularly because these items are lot tracked. It works fine for this single item type, but there are quite a few other materials that generate similar situations. We do not roll these into this same process, because they each have different actions required to determine their usability.
