you are definitely NOT alone. We can’t make ANY Time Entry Edits without getting these errors, have people stuck in the MES where I have to complete an End Activity for them and I have an open ticket with Epicor. we have removed the Enabled flag from the BPM’s and they are STILL saying it is the BPM’s, but we are pushing back because how could it be the BPM if it is not enabled.
They will be completing a data model regen tonight as a test. CS0005560969
Yeah its been pretty rough getting 5+ requests from department supervisors daily that their team gets an error when ending activity in MES out on the shop floor. I’ve been ending activity on the LaborDtl table using that process but that means someone has to go back and correct their time via Time Entry.
The bad part is in some cases, we also get an error using Time Entry
Great! removing the enables flag is a lie right now? LOL…I had to provide log in critentials for them, send them a video showing them that it was disabled and they came back with disable your BPM’s!
Thanks! so helpful.
So far so good, I’ve not heard of any users having issues clocking out of MES since we’ve done the Data Model Regen.
And for the job that was giving us problems in Time Entry, here’s what support recommended.
-Go to job adjustment and change the status of the operation and remove the complete. Then update Time Entry as needed.
-Please verify if the job operation has an earlier start date than the labor detail. If it does not, in Pilot if you can, please reschedule the job. This error message appears to come up if labor records are entered prior to the start date of the operation.
-From conversion workbench run Rebuild Shop Load Process (conversions 590, 650, 710)
Issue does not appear to be patched in 2026.100.9 for us either. Continuing to get the error on multiple jobs when ending activity or trying to use job adjustment. Support’s response was to ask if we had regenerated the data model.
Yes we have the datafix. But we understood it was supposed to have been fixed in this release so it seems like the fix didn’t make it in, or something.
We are in the same boat, still running the data fix daily. They recommended that we remove affected jobs from the schedule and reschedule them, but they just re-appear on the list the next day.
I have keeping a day orver day record of the list of jobs in the data fix and it is new and old jobs.
Our global schedule processes are completing every night and we can not figure out what is causing this.
I never received a datafix but they gave me a workaround that seems to have fixed the issue at the job level for me.
1- Remove the Schedule.
2- Save.
3- Release the Job without scheduling it.
4- Remove the Complete status (Job Adjustment).
5- Reschedule the Job. (Forward)
Ahh that sucks, this issue was super frustrating because I had to use “End Activity on Active Labor Detail” and we had to go back and correct the time daily. Even then, still had some issues using Time Entry.