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
mid pay period changes
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Elia Kfouri
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5214
People Online:
Visitors:
56
Members:
0
Total:
56
Online Now:
New Topics
IPA/ProcessFlow
IPA Question - Filtering Employees by XRef Cost Center Across Person and HR Modules
3/2/2026 4:29 PM
Hello Everyone, I am building an IPA process in
Lawson S3 Financials
Lawson S3 to SAP S/4 Hana Migration
2/12/2026 8:54 PM
Can anyone recommend a consulting company who has
Lawson Add-Ins for Microsoft Office
Deleting an Orphan Time Record with MS Add-ins
12/13/2025 7:26 PM
I have discovered an Orphan Time Record when dumpi
Lawson S3 HR/Payroll/Benefits
Secure 2.0
12/8/2025 9:06 PM
Has anyone using S3 V10 for Benefits been able to
Lawson Add-Ins for Microsoft Office
More.... ic81.2
12/5/2025 10:51 PM
We build our PAR's with MS Addins using IC81 a
Lawson Add-Ins for Microsoft Office
Uploads
11/20/2025 3:32 AM
The Next button has stopped functioning on the upl
S3 Systems Administration
Lawson Security Admin (LSA) - Securing Print Manager to self only
10/24/2025 6:27 PM
Looking for someone who would be willing to share
Lawson Add-Ins for Microsoft Office
Lawson Add-in
9/30/2025 6:51 PM
I am looking for a Lawson Add-ins query to add new
Lawson S3 Procurement
Anyone getting PO 0000 not found for company error in PO23?
9/30/2025 2:45 AM
Anyone getting PO 0000 not found for company error
Lawson Add-Ins for Microsoft Office
PO20 - Cancel PO via Add-in
9/25/2025 8:03 PM
Is it possible to cancel PO's using add-ins? I
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
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
mid pay period changes
Please
login
to post a reply.
6 Replies
0
Subscribed to this topic
69 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Mary Porter
Veteran Member
Posts: 337
2/12/2013 5:21 PM
we are step and grade and allow employees to change positions in between pay periods, and we have a two week pay cycle. So let's say the employee worked for the first week in old position 1 at old position 1's pay rate, and worked the second week in new position 1 with new position 1's pay rate. When we change the employee's position record effective the second week, any time records that come in regardless of position code default to the new position 1 pay rate. So we have been creating a second position with old position 1's payrate so that the first week's time records will come in at the right pay rate. Then we end that second position when the payroll is over.
Is there a better way to handle this?
Margie Gyurisin
Veteran Member
Posts: 538
2/12/2013 6:52 PM
Split
You may try to make adjustments to the schedule rule on the PA06. We are looking at adjusting ours to be a "2" instead of a "1" for that reason. We have decided that a "3" will not work for us.
Mary Porter
Veteran Member
Posts: 337
2/12/2013 8:46 PM
Split
our schedule rule is already at a 2. I don't think 3 worked for us either. I can play around with this though and see what happens.
We are also testing changing the Process Level, Department rule to a 2 (currently it's 3) with hopes that it will fix our issue with deductions splitting
between process levels.
Karen Ploof
Veteran Member
Posts: 118
New Poster
Congrats on posting!
2/13/2013 4:38 AM
Split
Hi Mary,
When the two time records are created, are all the other fields from the prior position (accounting unit/account, location, etc) correct - it's just the rate of pay that's wrong?
The situation you're describing doesn't seem to be related to the PA06 rules - I believe they only come into play when an employee has more than 1 concurrent position. In your case, the employee really only has one position, you are "faking" a second to get the rate correct.
Would you please check the job code form (HR05? I think that's the form) for a field that's something like "allow pay at lower rate"? If it's not set correctly, the time record will always use the current (usually higher) rate.
Karen
Deleted User
New Member
Posts: 0
2/13/2013 1:34 PM
Split
A little late to the party - what dates are you using on your time records? Step and grades can some times work unexpectedly, but we have a population here that is on that type schedule, and our position rules have rates default from all positions. As long as you have time record dates that refelct the appropriate work period, the rate should default without having to add or re-open positions. We're monthly, and generally have 1 time record for the full month - I just ran a quick test to make sure I'm not a liar, and I entered 2 time records - each for a half month and time record dates based on my position history - and the rates default correctly. So, if you're bi-weekly, you'd need two 40 hour/regular work week time records with period end dates and it should work as you expect.
Mary Porter
Veteran Member
Posts: 337
2/13/2013 3:18 PM
Split
we couldn't set the rate to default from all positions because we had problems with alternate positions - and the fact that we have employees that float to other departments in their alternate positions. I'll test that though when we are testing another change to position defaulting. thanks for the help!
I saw in another post that you might have made a custom calculation for a 457f/403b match issue - was that what you were talking about?
Mary Porter
Veteran Member
Posts: 337
2/13/2013 3:22 PM
Split
Karen - our hr06 is currently set to Allow Pay Below Normal Rate on all of our positions
Please
login
to post a reply.