[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
Re: Payroll Question
Hi david,
we had a similar situation at Education Department Of WA.
We found instances were the PayCalc would flag the pay earnings as 'E'
but not write to the pay message table.
We traced the COBOL and customised to ensure a record was written to the
pay message table.
Regards
Arthur C.
-----Original Message-----
From: Mark Boyd [mailto:mark@CG4.COM]
Sent: Wednesday, June 16, 1999 9:39 PM
To: Multiple recipients of list SQR-USERS
Subject: Re: Payroll Question
I don't know if you want to look directly at the database, but maybe the
panel limits the amount of messages which can be viewed.
This SQL statement will display all messages from your payroll.
SELECT
T1.COMPANY,
T1.PAYGROUP,
T1.PAY_END_DT,
T1.OFF_CYCLE,
T1.PAGE#,
T1.LINE#,
T1.SEPCHK,
T1.MSGID,
T1.MSGDATA1,
T1.MSGDATA2,
T1.MSGDATA3,
T1.RUN_ID,
T1.PRCSINSTANCE,
T2.DESCR,
T2.DESCRLONG
FROM PS_PAY_MESSAGE T1,
PS_PAY_MESSAGE_TBL T2
WHERE T1.MSGID = T2.MSGID
Good luck.... I hope this helps.
-Mark
David Anderson wrote:
> After the successful completion of PayCalc I perform a query
> to find all employees with Pay_Line_Status = 'E'. This
> returns about 300. Of these 300, only a portion are
> represented in the Pay_Messages records. What else
> should I check to identify the error and possible resolution.
>
> According to PeopleSoft, through searching their site, I
> should check the LOG. This, of course, tells me nothing.
> Only information in the LOG is the number of checks already
> calc'd, number of checks to calc, and if there are any
> messages to check. Of the 300 errors, 280 are in one
> paygroup. The LOG indicates to check messages!! - but
> there aren't enough messages for this paygroup.
>
> Further, PS identifies a potential source of the E code for
> employees (PS_PAY_EARNINGS) if someone is in the
> HRMS system and is updating a row in the tables used by
> calc. No one was in the system at the time of calc, so this
> isn't the cause, however, they suggest to do a RECALC ALL.
> Again, no help.
>
> Any guidance would be GREATLY appreciated.