• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Human Capital Management Lawson S3 HR/Payroll/Benefits

Upgrade - 8.1 to 9.0.1

 9 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Jodi Kruesel
Veteran Member Send Private Message
Posts: 75
Veteran Member
3/23/2010 6:44 PM
We are nearing the end of your testing for the upgrade from 8.1.0.5 to 9.0.1.3. We have encountered an issue with PR132. When and employee has received OT pay during a pay period and then receives a backdated pay change that includes a day the OT was previosly paid. Upon running PR132 after the backdated pay change, PR132 is overpaying OT by the amount he EE already received. In other words, it does ot recognize that the EE received OT pay at the previous rate of pay.

We have been working with GSC for quite some time and they are not able to recreate the issue. The are directing us to the PR20.2 OT Pay, OT Hours flags. I think it is an issue with the Premium Credit Flag on the OT pay code (ours is flagged to a Y). These setting worked correctly in 8.1 but not with 9.0.1.

Has anyone experienced this problem? How do you have your PR20.2 flags set for your regular earnings and OT pay summary groups>

mark.cook
Veteran Member Send Private Message
Posts: 444
Veteran Member
3/24/2010 11:32 AM
Jodi, We had a very similar issue during our upgrade. The issue ended up being more on PR140 than PR132. We worked the case with Lawson and ended with PT # 185585 that we put in to correct the issue. If you want you can contact me and I can provide the Lawson case number ect that might help out with this.
Carolyn Lee
Veteran Member Send Private Message
Posts: 53
Veteran Member
3/30/2010 2:44 PM
hi, we are having the same exact issue as you in 9.0.1. ctp 66391 was installed/compiled and issue still exists. i have a case open with lawson right now. i'll let you know what will come out of this.
Jodi Kruesel
Veteran Member Send Private Message
Posts: 75
Veteran Member
3/30/2010 6:42 PM
Carolyn,

We also have tried the recommended CTP with no luck. We've had a call open with GSC since the end of January and haven't had much luck. The case is still in progress and someone different is now looking at it. What is your CASE #? It is sometimes helpful to be able to point GSC to a related case.

Our CASE # is 3341195. You might want to reference it in your next communication with CASE on this. Maybe power in numbers will help in the resolution.

If we learn anything, I'll let you know. If you could do the same, I'd appreciate it.

Carolyn Lee
Veteran Member Send Private Message
Posts: 53
Veteran Member
4/1/2010 6:19 PM
Thanks, mine is 1586 or 2098599.
When they ran the PR132 to recalc the new regular rate of pay and adjust the overtimes, clearly the employee is double paid on the system generated overtime. the support person replicated it but cannot see the problem. the problem is that they assume their PR132 is correct, when it's not. i've tried to convey this in 10 different ways, the error is right in front of their eyes. wish me luck on the 11th try.
email me lee.carolyn@ghc.org if you want a copy of my case.
Jodi Kruesel
Veteran Member Send Private Message
Posts: 75
Veteran Member
4/2/2010 10:50 AM
Carolyn,

I am going to pass your information on to a co-worker who is working directly with GCS on this issue. I'll make sure and let you know if we get a resolution from them.
Janelle M
Basic Member Send Private Message
Posts: 4
Basic Member
4/19/2010 12:11 PM
Carolyn, I work with Jodi and I'm the one who has been working with gsc on our PR132 issue. We have determined that we need to change our flags on PR20.2. Our Pay Summary Group flags for overtime were set to N N N Y in app 8.1.0. In app 9.0.1 we must change them to Y Y N Y in order to get PR132 to adjust for credited overtime. How are your flags set on PR20.2 for overtime?
Carolyn Lee
Veteran Member Send Private Message
Posts: 53
Veteran Member
4/20/2010 7:12 PM
Hi, thanks. I received the same response for the FLSA setup in PR20.2 change from NNNY to YYNY. unit test looks good so far and will regression test next.
Except for that FLSA paycode, all other FLSA related overtime codes were coded as YYNY.
I'll let you know of my test results later this week.
Carolyn Lee
Veteran Member Send Private Message
Posts: 53
Veteran Member
4/27/2010 7:15 PM
regression passed with the new setup. how did yours go?
Janelle M
Basic Member Send Private Message
Posts: 4
Basic Member
5/3/2010 11:52 AM
The new setup worked for us, too. Thanks!