We deal with this all the time.  It's a duplicate record in your ESS Requests for Time Off for employee 3080 that was submitted more than once and all submitted transactions have been approved.... I have written a SQL Script to delete the duplicate transactions using SQL Management Studio... there is no other way to remove the duplicated transactions once they have become a past dated transaction.  We spent many countless hours working with Sage and our own troubleshooting in order to rectify this issue. When we sent our data to Sage, they could not duplicate the problem, however, it is still an issue in HRMS/ESS 2017 system and we manage it through manual deletions.

The duplicated transaction is not in the hattran table, hence why you can't find duplicates.   When ESS is processing time off and trying to commit the time taken from ESS to hattran is when the error occurs.  It encounters the duplicate transaction in the tTIME_OFF_REQUESTS table in ESS.

Thanks Terry,

We are having a heck of a time trying to figure this out.  First client we have had issues with on this version.  So we need to review the ESS table and remove the records there?  Once you do this, does it continue to occur?  Do you know why it is happening?

Thanks again

Hi Terry,

Would you be willing to share the SQL script?

Thanks

This error did not start until we went to 2017 as well. Prior to that, no issues.  Sage has always remained committed that there is no issue with 2017 in this regard.

In our environment, it happens when an employee submits a transaction for approval.  Periodically, ESS generates an error sending the Notification through to the Manager.  When the employee receives the error they assume the submission did not go through, so they do it again.  To help reduce the duplicates from occurring, we have tried to educate staff to check their Message Center before they submit any subsequent transactions for time off to make sure they did not previously submit for the same period.  The secondary catch for the duplicate is for the Manager to make sure they are only approving one transaction submitted and rejecting all subsequent transactions, however, because this process relies on human interaction, it does not always happen.   

We continue to encounter this issue, but my IT Department now manages the SQL and the removal of the duplicates in this manner.  The one issue with using SQL to remove the transactions is the Notification record sent to the Employee becomes an orphaned record and cannot be removed.

Yes, you'll have to review the ESS time off request table for the specific employee.

Another curve ball to this duplicate issue is if an employee submits a transaction for a period of time, the manager approves it and ESS sends it over to hattran.  The employee, days later, does not remember submitting the transaction, submits it again, the manager approves it again, and ess sends a second transaction over to hattran you end up with duplicates in hattran that ESS processed.   We use ABRA Alerts to catch these duplicates and HR manually deletes them from HRMS Attendance.

The ESS error only occurs when Process Time Off is trying to send two identical transactions over for a  the same employee, at the same time.

Hope this helps you.

Terry

Thanks Terry,

This helps a lot.  We didn't know if the upgrade had gone bad, if the database was corrupted... and to be honest were not getting any feedback from Sage.  

Regards,

Howard

We worked with Sage on and off for nearly six months.

do you have an email address Howard?  I can send you my SQL

Thank you!  [email protected]  

Hi Terry,

I am experiencing the same issue.  Would it be possible to send me the information on how you fixed it?  My email address is [email protected].  I appreciate any help you can give me. :-)

Thanks,
Arlena