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
User Level EMP-USER-LEVEL
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:
36
Members:
0
Total:
36
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
User Level EMP-USER-LEVEL
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
Mary Porter
New Member
Posts: 0
12/27/2012 5:53 PM
We aren't using User Level for anything right now and we would like to use it to record the Division that the employee works in. We were told that this is a field that Payroll normally uses for check sorting purposes. We don't need to use it for check sorting purposes. Will populating this field have any impact on payroll jobs if they aren't using it? i.e. for PR160 the report sequence is PL/Dept, so I just want to make sure there isn't any "hidden" sorting that would bring in User Level and impact payroll reports.
SherryW
Basic Member
Posts: 12
1/18/2013 2:14 PM
Split
We were using this field for something non-payroll related. We have had no issues with our PR160 with this field and we process payroll in -house.
Please
login
to post a reply.