We use PMTOUT to create pay stubs for our employees and we're finding that, sporadically, the OF-YTD-GROSS-PAY is correct, but the OF-EARN-PSG-YTD-AMT is not matching - the psg ytd field seems to be doubling the employee's current gross pay. Its very insistent when it happens so I can't duplicate it on request, and we originally thought it related to employees receiving PR82 adjustments during the month (we close them separately before running the payroll cycle), but even that is not consistent - many people have the same type of adjustments, but their records are fine. I'm stymied, and I've opened a call with Lawson, but I'm already frustrated with their initial responses.

Thanks in advance

It's very INCONSISTENT - would help if I could type. Its the employees here who are insistent..... :beat:

Stephanie,

I'm guessing that when ya'll run system payroll there are no open Manual Payments or Reversals -- true?

Your problem description gives me a major deja vu...is this one of those annoying, recurring issues? :bonk:

I have time to look thru CTPs, if that'll help you at all. If so, let me know:
If you are UNIX or iSeries.
Your application version.

hth

Kate

Hi Kate - Happy Friday!!

No outstanding adjustments, voids or manuals. It is an annoying issue, and it IS recurring - but it's sporadic which makes it a nightmare. I looked for any CTPs, and even the GSC is telling me they've never heard of it. I'm trying to get them to tell me where the data in the PSG YTD field is derived, but have not had a response as of yet. I was first told the field doesn't exist - so I pointed out the file layout on the support site which has the data :banghead:

I was then told I needed to duplicate the issue, and when I said I couldn't, I was told they couldn't help. If I could duplicate it, I'd know what's causing it and wouldn't have a call open....

Can you feel my frustration level?

Many thanks for any enlightenment!!

Hi Stephanie!

Happy Weekend to you! Hmmm...Are you using LIS for this GSC ticket? I haven't opened a phone ticket in years because Omar said to use LIS and when I did I got FAST resolution from a veteran like Kathy McG, Kristen G., Diane E -- The A Team. You got a newbie (bless their heart).

To jog GSC memory banks, here's info re KB Article with unlike scenario but similar outcome:
Release: 8.0.x, 8.1.x Platform: unix ntwindows
Product: PR Article ID: 996120

PR160 YTD Amounts Doubling in PMTOUT for Gross Up Payroll Run

Description: When running Payment Print (PR160) for a Gross Up Calculation (PR189) payroll, the YTD amounts in the PMTOUT file are doubled.

Resolution: Priority 2 PT #131663 addressed this issue. 8.0.3 Critical Transfer Pack (CTP) #25870 was created as the fix for this issue. It is also included in Maintenance Service Pack (MSP) #9 for 8.0.3. For 8.1.0 applications the original CTP was #31340. It is also included in 8.1.0 MSP #3.

Additional Information:

Keywords: CT: 1700118 PT: 131663 PR160 PR189 gross up calculation PMTOUT YTD payment print double doubling twice the amount two times


On my perfect planet, this would happen:
1. Client creates a little math report to find this; inserts Pause Step in PR processing while rpt runs (as soon as PR160 is done).
2. AHA! New report helps client finds the condition again, while PR still open.
3. Client takes backup of data area, invites GSC over for a Web-Ex.
4. Call turns tech, goes to Sandy J. at GSC, who finds the problem, writes PT.

errr, welcome to earth. ;-D hth. hang in there! ~k~

Thanks Kate!! It is an LIS session, and it does appear to be a newbie, who I think may becoming frustrated with me because I'm sure someone else is telling her what to respond, and I keep shooting it down each time. Today, after contacting one of the managers there, someone is reviewing our pr160.cbl, and I'm supposed to hear back Monday. They did ask me if I was performing gross-ups, so the ctps may have been in the back of their minds. At this point, I'm sure they'll tell us the 160 is an old version and they'll send us a new one to test, but with it being a sporadic issue, I'm not sure what the outcome will be. Oh well - software gremlins strike again!! :rofl: