Good morning,
We have QC operations in between a lot of our steps. These were not setup as backflush, but our QC staff never completes these ops in Epicor. I believe by setting these ops to backflush, then the value will be filled in automatically (and checked complete if applicable).
What is the best or proper way to correct these operations now that lots of part masters and jobs are created? Has anyone ever had to do this for existing jobs/parts? We have DMT and I am considering testing that to update the ops. I just want to make sure I take the best approach.
We do have one QC op at the end of the op sequence. This is the only QC op that they fill out with time and qty. I think I need to set the labor entry type for the other QC ops to backflush only. They are all set to time and qty, and they have never reported either for these internal ops.
I see that you canāt set an op to backflush qty, if the next op is a subcontract op. We always have a QC op right before shipping to a subcontractor. Can the receipt of the subcontract op quantity trigger the backflush to the qc op? Why not? This seems like it should be an āIdeaā, unless someone can say why this is a bad idea.
The current backflush service mechanism I believe is looking at labor detail records. Subcon ops donāt have those. So a secondary mechanism to make it work would have to be created and put into that scheduled service.
Not to mention the āundoā part of that, which is a tricky, as Iām finding out with auto receipt with subcon operations.
What happens when the operation after the subcontract is reported? Does it backflush the inspection op that came before the subcon? Theoretically, you are able to stack the operations and only have the last operation where you report and backflush everything prior.
I just simulated this in Pilot. After running the backflush server process, I see the other backflush ops filled in, but the backflush of before the subcontract op did not fill in quantity or get marked complete.
This seems like a big oversight. How are others handling backflush ops before subcontract ops?
Youāre probably right there. I skipped the subcontract op in my pilot test. Iāll try to fake some PO receipts for that subcon. and see if that makes any difference.
Unfortunately, that didnāt help with the backflush op before the subcontract op. I created the PO, and received it in, then completed the rest of the ops. I ran the backflush process, and every other backflush op gets completed, but that one backflush op before the subcontract op stays incomplete.
I am considering trying to setup a directive of some sort to get this working, but I am not sure if that is even a good idea.
Donāt other folks have backflush ops before subcontract ops?
Do I have to invoice the subcontract PO maybe? I didnāt go that far yet.
I think Epicor is assuming that the act of shipping stuff out for subcontracting will need more hand holding and tracking, so they donāt tie in subcontract ops into the backflush ops process.
On 100% quantity completed on the final operation of the job post processing on Labor.Update I check all JobOper records for any unclaimed quantities and create BackFlush LaborDtl records for them.
I want to experiment with this process. If I understand this correctly, once the user enters a labor entry for the final op, that quantity is pushed back though the other ops to show they are all completed. Is that correct? How is the quantity updated though the other ops? Thanks again!
You need to set the labor type to backflush, and you need to schedule this process to run, it doesnāt work 100% automatically like backflushing material does.
