Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
PR197 question
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
61
Members:
0
Total:
61
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
PR197 question
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
69 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Linda Ogle
New Member
Posts: 3
New Poster
Congrats on posting!
12/4/2007 3:40 PM
We are trying to close a payroll in a test environment but PR197 gives us the message "run pr160 for bank code WACH", but the PR00 screen says that PR160 has been run It has an "*". When I look at the paymaster and the prcheck files the check-id do not match.
Any ideas how we can get out of this ?
Jodi Kruesel
Veteran Member
Posts: 75
12/4/2007 3:47 PM
Split
We have had this situation as well. It may be that someone changed process levels between PR140 and PR160. KB Article #524859 mentions this. You can either re-run PR160 for that process level or correct the EE and then re-run the payroll jobs.
Please
login
to post a reply.