My Oracle Support Banner

ETL9.2 :Incorrect XREF_NUM When Employee’s Termination Is Entered After Pay Sheets Are Created (Doc ID 2527272.1)

Last updated on JULY 22, 2020

Applies to:

PeopleSoft Enterprise HCM Time and Labor - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

 XREF_NUM on PS_PAY_EARNINGS is not correct. The time and labor record (sick leave) has no XREF_NUM and the earnings for the FLSA week ending on 6/18 in which sick leave was reported has two different XREF_NUM instead of a unique one.


STEPS
-----------------------

1. Report time in Time and Labor for 6/16-6/30. Employee is salaried paid semimonthly in arrears.
2. Report 5 hours of REG and 3 hours of Sick leave on 6/16, report 8 hours of REG, every day on 6/19-6/23
3. Create paysheets in Payroll, load time and run a calc
4. Enter termination on Job Data page effective 6/24
5. Load time and run a calc
6. XREF_NUM on PS_PAY_EARNINGS is not correct. The time and labor record (sick leave) has no XREF_NUM and the earnings for the FLSA week ending on 6/18 in which sick leave was reported has two different XREF_NUM instead of a unique one.
This is creating two issues.
1. Since the XREF_NUM is blank on the sick leave record, the cost is getting distributed by PY_PULL_COST to the default combo code that’s setup on the department budget table instead of task profile/combo code employee charged time to in Time and Labor, undercharging Projects. We interface with Projects.
2. If we try to SQL update XREF_NUM for the sick leave record, the sql is erroring out because it’s finding two different XREF_NUM for the FLSA week in which sick leave was reported.

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.