• Search Forums
    Advanced Search
Prev
Next
Forums Human Capital Management Lawson S3 HR/Payroll/Benefits

PA100 error

 7 Replies
 0 Subscribed to this topic
 69 Subscribed to this forum
Sort:
Author
Messages
Chesca
Veteran Member
Posts: 490
Veteran Member
New Poster
New Poster
Congrats on posting!
4/4/2013 3:48 PM
Hello everybody, hope someone can help me figure out this issue.  Benefits isn’t able to change EE to termed. The PA100 is saying “Time recs or one time deductions exist”. Employee till has time records in PR30, which is preventing Benefits from changing her status to termed. It looks like her accruals have been paid out, but the REG hours are still in Lawson (PR30.1)

I opened a ticket with Lawson and I was told to manually delete the timerecord for the employee from PR30. PA100 rerun and still got the same error.
Margie Gyurisin
Veteran Member
Posts: 538
Veteran Member
4/4/2013 3:53 PM
Are there any orphan manual time records that exist?

Go to PR 80, enter co and ee number and inquire. They will show up.
Margie Gyurisin
Veteran Member
Posts: 538
Veteran Member
4/4/2013 3:55 PM
While you are on the PR80, you should go to the one time deduction button and see if there are any manual one time deductions as well and delete if need be.
pookey
New Member
Posts: 0
New Member
4/4/2013 3:57 PM
I am assuming you've also checked PR39 for one time deductions? Another place to look is PR80 - check the one time ded button. We've had deductions stuck here in the past. Finally, check your time record table - again, here we have occaisonally found "ghost" time records on the TIMERECORD table - no idea how they got stuck there, and they can't be seen on any of the time entry forms. They need to be deleted using sql - good luck!!
Deleted User
New Member
Posts: 0
New Member
4/4/2013 4:00 PM
KB 83746 will help, and here are notes from my own Problems/Solutions database.

Problem:
HR cannot terminate an employee due to the error message “Time Recs or One Time Deds Exist; Cannot Terminate”.
Employees cannot be terminated until time records and one-time deductions are deleted from the system.

Solution 1:
Lawson KB 83746 identifies all of the places that time records or one-time deductions might exist:
PR36.1 Time Record Entry
PR39.1 One Time Deduction
PR80.1 Manual Payment
PR35.1 Time Entry (Batch)
PR29.1 Pension
PR82.1 Adjustment
PR80.3 Manual Payment One Time Deductions (from PR80, Payment Tab, One Time Deduction button)

Solution 2:
If you find that there aren’t any time records on the above forms, there may be orphaned records on either the ONETMDED or TIMERECORD tables that need to be deleted behind the scene. This requires painting a screen and removing the records that erroneously exist.
Deleted User
New Member
Posts: 0
New Member
4/4/2013 4:03 PM
I should have also said that I usually have to use Solution 2, Paint them out, because they are orphaned.
Chesca
Veteran Member
Posts: 490
Veteran Member
New Poster
New Poster
Congrats on posting!
4/4/2013 5:44 PM
Oh wow, thank you all for the quick responses. Yes, there were 2 ghost records out there from 6/12. My users removed them and re-run PA100 and the issue has been fixed. Thank you, ladies! 
Mary Porter
Veteran Member
Posts: 337
Veteran Member
3/3/2014 10:35 PM
Does anyone know what causes the orphaned records? It happens to us fairly frequently, mostly with one time deductions staying
after a manual check has been processed and closed.