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
PR36 not pulling in 2nd position pay rate
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
TomV
Past 24 Hours:
1
Prev. 24 Hours:
2
Overall:
5186
People Online:
Visitors:
432
Members:
0
Total:
432
Online Now:
New Topics
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Infor ION
ION vs IPA
2/29/2024 1:24 AM
We had a person new to Lawson and Infor go to Info
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson S3 HR/Payroll/Benefits
PR36 not pulling in 2nd position pay rate
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
MatthewD
Veteran Member
Posts: 53
6/3/2013 12:37 PM
We have an employee who was setup with a 2nd position level for a different dept & job code than their primary and it was effective for 5/12/13. This employee worked in both their 1st & 2nd position levels this past pay period (5/12-25/13) however the payrate for the 2nd pos level is reflecting the 1st pos levels rate not the 2nd's.
If I go directly to pr36 and enter a paycode and assign the 2nd pos levels job code the primary pay rate is pulled in not the 2nd level.
It appears to be setup correctly, what else can I check?
stephanie
Veteran Member
Posts: 330
6/3/2013 12:46 PM
Check your PA06 set up - payroll tab. You'll want your pay rate to default from all positions. Depending on your set up, you may need to add items like process level etc. to the time record on PR36 for correct defaulting.
Dave Curtis
Veteran Member
Posts: 136
6/3/2013 12:53 PM
Do you have the second job set up on HR14.1 (Alternate Pay Rates)?
MatthewD
Veteran Member
Posts: 53
6/3/2013 12:56 PM
Everything on pa06's payroll tab is set to 3 except for location which is set to 1. We have other people who've been setup with a 2nd position who've been working. Not sure if it makes a difference but were on 9.0.1.
MatthewD
Veteran Member
Posts: 53
6/3/2013 12:57 PM
No this employee is only setup on PR13 with pos level 01 & 02, nothing for HR14.1.
stephanie
Veteran Member
Posts: 330
6/3/2013 1:16 PM
If others are working and are set up the same, the only other thought I have is to double check the time record date, AND the effective date of the level 2 position.
MatthewD
Veteran Member
Posts: 53
6/3/2013 1:45 PM
The effective date on the 2nd position is 5/12/13. I looked at the record in SQL and see it has a date stamp of 5/17/13. We bring in all of our time on one date from Kronos into Lawson using PR530 and the PR530 reports shows the date of 5/25/13 and all pay codes are using the primary pay rate.
I have to do a little more detail review of others setup the same way then probably open a Lawson ticket.
Thanks for your help.
Dave Curtis
Veteran Member
Posts: 136
6/3/2013 5:23 PM
I have always found that multiple positions works more effectively when you add the non primary (levels 2-99) positions onto HR14. We add the process level, department and job code with the rate of pay onto HR14. Since Lawson first looks at the pay code and then to Alternate Rates, having the records on HR14 stops the flow at that point for time records with a process level, department and job code that match the entry on HR14.
The other things that could be effecting the time records are history records and pending actions.
I have seen where the effective date is not used when time records look at the pay rate but the date stamp is instead used. You may want to check to see if the date stamp on the position is after 05/17. If it is, this may be the issue.
MatthewD
Veteran Member
Posts: 53
6/4/2013 1:38 PM
By entering in the record in to HR14 I was able to get the correct pay rate to show up in PR36.
Should P/R be looking at the mult position tab (PA13) for different rates of pay or does only HR14 give us that option?
Dave Curtis
Veteran Member
Posts: 136
6/4/2013 2:40 PM
It is my understanding that if the time record has the position defined that it should look at employee position/job records. Do your time records have the actual position? Or (like many others) do you feed in dept and job code but not the position number?
MatthewD
Veteran Member
Posts: 53
6/4/2013 5:38 PM
Our feed doesn't have the position number we send over the jc & dept from Kronos
You are not authorized to post a reply.