Here's how I resolved this - though I'm not 100% sure whether it is all due to a data error or if there could be a programming issue at play as well.
The customer had one entry in their Time Track file which was from a prior month and which the program seemed to error on.
To figure out which key the process was stopping on - use the debug screen on the error
- Info
- Debug
Type in:
- Exit
- Escape
? timetrackkey$
This should return the key field which is the employee GUID plus other items from the time entry - look in PR_TimeTrack.M4T for it
** MAKE A BACKUP OF MAS_XXX JUST IN CASE **
1. Use DFDM to delete the record from PR_TimeTrack.M4T ( look for key found in above procedure )
Pull in all JC data from Time Track and update
Payroll - Setup - Payroll Options - remove check - accept
Error ( but still does remove records)
File - Run - *UTL - Purge Time Track to History
Payroll - Setup - Payroll Options - remove check - accept
No Error
0 Records in PR_TimeTrack.M4T
I haven't traced through to see if all the PR_TimeTrack.M4T records were moved appropriately to history. I have instructed the customer to review. If there seems to be any type of problem I'll update this post.
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------