Has anyone had any issues where during an operation it is being marked complete and any future operation is being marked complete. The Prod QTY on the Job is going to 0 even though the demand QTY is still what it should be.
We cannot seem to figure out what is happening, from what we can tell no one is doing anything out of the ordinary. We cannot seem to re-create it and support has not been much help. This only happens in one of our sites.
Is the operation in question inadvertently flagged as the Final Op?
Wondering if it is being marked as complete based on qty/hrs (however its set up) and if it is the final op, it is auto-completing following ops?
Never seen this behavior. Theoretical?
Thank you for the Reply
It is not marked as the final op, I cannot seem to find any pattern where this is happening. Just happens
Any BPMs in play at that site that might impact completion of jobs?
There is also functionality “Job Complete/Close Parameters Maintenance” which I’ve never played with. But set-up here may be auto-completing the job.
Just lobbing out areas to explore in case you have anything set up in those areas.
I have checked all that and all our sites use the same customizations and bpms etc.
This is just a mind boggling event that keeps happening
Is this some kind of Production Yield Recalc thing?
To my knowledge we do not use the Production Yield
I don’t suppose you have change log turned on for jobs? Knowing the who/when of the prod qty changing to 0 might be helpful.
I did not,
I do know though lol.
Thank you
Ive already got a few and I can see when and who the change is coming from and these people at that time are only using the MES and nothing in the actual Job Head. I didn’t think it was possible to change prod qty at all. even from MES.
Check your System Agent and make sure you are not running the Production Yield Recalc process.
We are not running that process at all.
That is weird then, as that is the only thing I know of that would change the Prod Qty automatically.
Are the operators reporting scrap or NCR on the operations?
Nope we dont use the scrap or NCR process in Epicor.
Just to be clear your saying the JobHead.ProdQty gets set to zero. But the demand is still there so your in an out of balance situation between Demand and JobHead.ProdQty?
In part transaction history are there any transactions with this job or this job number as a lot number like someone doing a lot split?
We have run into this a handful of times. We have a location that likes to keep a few jobs open and are constantly changing the production qty, completing a partial quantity then changing the prod quantity again. Seemingly never ending job that drives finance crazy. We have yet to pinpoint the exact cause but support has provided a fix (CRUJobHeadProdQty_xx) to correct the discrepancy.
Correct, and this happens only when ending activity on one certain operation in only one site.
I will take a look, but this is happening to all different part#'s, not just anyone specific.
Interesting,
They provided me with the same fix, but they cannot seem to actually fix the problem.