Good Morning All,
We have a list of jobs that have been growing over time that have labour transactions that keep getting stuck with a timestatus of “E”. The employee has successfully completed the operations and the job should be completed and closed but looking through I can see that the approval has not automatically completed to an “A”.
I have seen some topics about UBAQ’s back in the early versions of 10 and I was wondering if anyone had a converted version for Kinetic?
Kind Regards,
Adam
Any patterns to related to those time entries? Like similar employee?
If it is then perhaps there is some issue as to their set-up.
We had some mysterious labor records stuck in an “E” status that at first we could not track down. Turned out that some of the employees were using multiple MES stations, leaving one open and logged in at their desk and then going out onto the shop floor and using another.
We have this issue on 3-4 jobs at the moment. Yet to trace the cause, but received a data fix this afternoon that we need to test in our third environment after the flex update this weekend. I tried the Updatable BAQ, but the record did not take.
Unfortunately not. we have about 550 jobs built up over the last 10 years from 10.1.400 into kinetic upgrade.
I have been able to track them all down and looking to get a datafix from Epicor to correct them all at once.
Some had entries in Time Entry that could be approved, some could be closed manually through the new “End Activity on active labour detail” menu item.
There are a load that have come off the back of split jobs and don’t have a TimeStatus at all.
Hopefully the datafixes will successfully close them all in one sitting
Does anyone in your company use Time and Expense to recall and edit labor entries when an operator makes a mistake?
Usually when this happens here it is because someone forgot to re-submit the entry after editing it.
They do but quite a few of the jobs that have issues don’t have an entry against the employee in Time Entry. I can see the row when looking at the LaborDtl table but it doesn’t have a record in Time Entry. Hopefully the datafix clears them all out. was just looking for a UBAQ than pulls all entries from the LaborDtl table that are not “A” in timestatus and then we could go through and approve anything outstanding.