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
LP64 Absence Balance - Extra Accrual
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:
116
Members:
0
Total:
116
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
LP64 Absence Balance - Extra Accrual
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Kelci
Basic Member
Posts: 11
8/12/2014 7:45 PM
Hi everyone,
I'm stumped with this one, so I'm hoping someone out there can point me in the right direction! Our employees are on accrual vacation and PTO plans that reset each January 1st and carryover balances are created. For one of our smaller employee groups, the LP64 balance isn't lining up with the balance when we manually calculate it via the LP264 - the LP64 is exactly one accrual higher than we would expect.
I'm running the LP264 from 1/1 to present for all transactions. I sorted the output by plan name and transaction date so that I could compare it exactly with the LP64, and everything lines up: Carryover balances are the same in both places, and the usage and weekly accruals all match up; but when I total the LP264 spreadsheet transactions, we see the one accrual difference. Has anyone encountered this issue before? We recompiled our LP31 and LP64, but that didn't solve the discrepancy, and other other employee absence plans aren't affected - their LP64 and LP264 balances match up just fine.
Any suggestions or troubleshooting tips so that I can understand what's happening would be appreciated!
Kelci
M.J.
Veteran Member
Posts: 38
8/13/2014 11:52 AM
Hi Kelsi,
One thing you might check is on LP31 for the 'Accrual Last' and 'Hours last period end' - does it match your last pay period?
Kelci
Basic Member
Posts: 11
8/13/2014 4:50 PM
Hi M.J.,
Thanks for your comment! The LP31 screen appears correct with the correct Accrual Last date, so I started looking at prior years in the LP264 and found the issue. We posted the last 2013 accrual for this group on 1/6/2014; unbeknownst to me Lawson treated it as an "Available" accrual instead of rolling it into the "Carryover" balance (I think this may have been due to the order our year-end LP140 transactions.)
Based on the instructions of my predecessor - who knew a great deal more about the absence plans than I - our payroll team ran the LP140 using Option 3 - Events/Usage Only to pick up hours used, then ran LP197 to close it out. We then ran a second LP140 using option 6 (Carryover Only), and LP197. Finally, a 3rd LP140 was processed using Option 1 (All processing), with LP197.
If I understand the process correctly, that meant that the Carryover balance was calculated before the last 2013 accrual was processed. Could we prevent that by modifying the process to:
1. LP140 Option 3 (Events/Usage); LP197
2. LP140 Option 7 (Retroactive Accruals); LP197
3. LP140 Option 6 (Carryover); LP197
4. LP140 Option 1 (All); LP197
Or are we over-complicating the process entirely? Any (and all) feedback is appreciated!
-K.
You are not authorized to post a reply.