When trying to add employees through New Employment Assistant, upon clicking Finish button, an error message appears that states "The Employee Employed Period already exists."
 

We think this is related to challenges with the DMM Data Migration tool.  The issue has to do with the EMP_EMPLOYED_TIME table. That table has a SEQ_NO field in it that is the primary key and was loaded during data migration. The Aurena client has a reference somewhere to a SEQ_NO that increases by 1 each time we try and save a new employee record. Somehow (possibly through the data migration process), the value in the client came out of sync with the underlying database. If you click save enough times (several thousand based on our load), it will eventually work and go through as the console log shows that each time someone clicks save, the SEQ_NO value in Aurena increments by 1. We need to have a way to reset the SEQ_NO for the EMP_EMPLOYED_TIME table that is stored in the Aurena client and set it to the next value available according to the database.

Has anyone else had this issue?
How to resolve?