My Oracle Support Banner

EPY: Payroll error 000002 - Earnings Type not found on FLSA calculations (Doc ID 623551.1)

Last updated on NOVEMBER 23, 2019

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 8 and later
Information in this document applies to any platform.

This document was previously published as Customer Connection Solution 200773536




Symptoms



Payroll error message 000002 - Earnings Type not found is generated on occasion the client is able to get around this error by a SQL update to the PAY_EARNINGS record.  The reason this is occuring is because an employee who has prior period adjustments in the current pay period had their paygroup switched at some point in the past.  PS has specific code that looks at the ORIG_PAYGROUP field when trying to determine the new calculated FLSA (the FLSA rate that should have been paid in the previous pay period if the prior period adjustment was included in that payroll).  However, it doesn't appear that ORIG_PAYGROUP is ever populated.

The suggested workaround is to put the earnings on a off-cycle check. This is not working.  The reason why is that would mean that we could just uncheck ok to pay on any earnings that generate this error and then just pay those earnings separately in an off-cycle check, which would work fine in theory. Unfortunately, the way the earnings are loaded into pay_oth_earns and pay_earnings in some instances prevents them from being corrected online. That means we still need to make updates to the database to get rid of the error. Please see attached documents for the example. Basically, some FLSA earnings (erncd OFO)were loaded with no deptid, state, position information along with job_pay=Y on pay_oth_earns and ok_to_pay=Y on pay_earnings. Since Job pay is set to Yes on pay_oth_earns and ok to pay is checked on pay_earnings there's no way to delete it online without updating job_pay to no on pay_oth_earns. Then we can get rid of the earnings online and generate an off cycle for the prior period earnings. So basically, we are still  stuck making database updates in order to get rid of this payroll error  message.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.