3rd Shift not Calculating Correctly when Clocking Out for Lunch

Hi @Elizabeth Williford ,

We have noticed the same issue in IFS Application 10 Update 15 during our testing of the update.   In IFS Application 10 Update 8 everything works as we expect the time stays on the day the same work day.   Anytime they clock out after midnight the time goes to the next work day.   We also use Incremental and we noticed when an employee clocks out after midnight the differential calculation isn’t running so the employee does not receive the 3rd shift differential for the hours after midnight.  If they do not clock out for lunch they receive the proper Increment and all time is on same work day.

We have not reported the issue to IFS as we decided instead of upgrading to IFS Application 10 Update 15 we’d upgrade to IFS Cloud 22R2 which we have just began but it sounds like we will encounter the same issue.  😣

Regards,

William Klotz

Hi @Elizabeth Williford ,

Have you found a solution to this issue?  We are beginning our IFS Cloud 22R2 with a go live version of IFS Cloud 23R1 and we run 3 shifts with a 2nd and 3rd shift differential calculated using an increment.

Regards,

William Klotz

Hi guys,

Having the same problem here. Do you have any news? IFS Cloud 22R2.

Thanks,

@Elizabeth Williford ,

Have you been able to resolve this issue?

If so is the resolution in 22R2 or 23R1?

Regards,

William Klotz

No, and unfortunately, we have been told by IFS that it is a setup issue not an R&D issue. We are 23R1 and the issue has not been resolved yet. 

HI @Elizabeth Williford , @gianni.neves  and @BHern12 ,

I was reviewing the bug fixes in IFS Cloud 23R2 today and I noticed this item.  I’ve attached the 23R2 Fixes spreadsheet.  Its line 606 in the spreadsheet.  Hopefully it really does the trick and resolves the issue.

Case: G2377365 - Third shift clocking appearing on the wrong day.

Description: Clocking appear on the wrong day when the employee clocks in after midnight from lunch.

Resolution: IFS Cloud 23R2

Regards,

William Klotz

Thanks @william.klotz.

@william.klotz fingers crossed!!!

Thank you!!!

Hi @BHern12 @gianni.neves @william.klotz - Did this issue resolve?