This goes out to any Epicor 10 users that use EasyClocking (aka EasyWorkforce) for Time and Attendance, and integrate it to Epicor using GingerHelp Integration.
When using EasyClocking/GingerHelpIntegration (EC/GH), an Epicor Time And Expense(ET&E) record is created when the employee clocks in for Time and Attendance (T&A) using EC/HG.
At that point, the employee is “On shift” in Epicor, so we disable clocking in and out using MES. This, however, does not start the Idle Time “Clock” (for lack of a better term). Likewise, when the employee clocks out in T&A at the end if his work day, his ET&E record for that day logs the Clock-out time, and the ActiveTrans flag on LaborHed is set to zero (0). This does not trigger the the Idle Time calculation.
If there are any EasyClocking/GingerHelpIntegration users that have successfully addressed this issue, I would like to hear from you and get some direction with this issue.
Hi Tom,
I don’t have specific knowledge of this GingerHelp tool/integration, but I believe the way Epicor does it is to calculate the number of payroll hours (Clock Out - Clock In), and subtract the number of labor hours (Sum of Labor Hours on each Labor Detail within that Labor Header). An ‘Idle Time’ indirect labor detail record is created and added to the labor header upon clock out.
If you could hook in to the ‘Clock Out’ feature of this GingerHelp tool (which is probably calling Labor.Update) with a BPM, you could try to replicate this behavior.
Thanks for the ping Kevin. Myself and Tom connected directly but just in case anybody else comes across this for whatever reason - the MES methods for clock in and clock out are EmpBasic.ClockIn and EmpBasic.ClockOut. When these methods are used, the idle logic works just fine but unfortunately these methods are always as of “now”. We use the LaborSvc object for our time clock solution to allow us to explicitly set the times (as opposed to “now”) to deal with situation like when the Internet is down, time clock records punches, and then syncs up to Kinetic when it finally comes back up. The LaborSvc does not automatically add the idle time (understandably) so our solution for Tom is just going to be a BPM that tallies up the idle time and slaps a LaborDtl at the end of the day with the total. I’ll post some code out here when I’ve got it built in case any of you others ever run across this in your own solutions.