ETL9.0: Concurrent TL Load Updates The Payable Status To RP But Loads Time To Payroll
Last updated on AUGUST 02, 2016
Applies to:PeopleSoft Enterprise HRMS Time and Labor - Version 9 to 9.1 [Release 9]
Information in this document applies to any platform.
Load Time & Labor updates the payable status to RP but loads time to Payroll.
Once the Payroll is confirmed and Pull Cost Process is ran, Payable status changes to PD and the Requisition number remains zero.
Also, the rejected time gets reloaded again in the following pay period and the employee gets over paid.
This happens for employees who switched Pay Groups in the middle of the Pay Period and during the Load Time and Labor parallel processing.
1. Employee switched Paygroups on May 19th 2013.
2. Paygroups pay calendars start / end dates are the same, 5/12 - 5/25/13, with different pay run ids.
3. Payable time created for period.
4. Paysheets created for both paygroups.
5. Load payable time to payroll with concurrent runs using different run controls.
As a result, Payable time after May 18th 2013 is Rejected by Payroll Status (in RP status) and payroll_req_num is zero but still the data is pulled into current Payroll.
After Extact Pull Cost, the payable_status is 'PD' and payroll_req_num = '0'.
Payable time after May 18th, can be reloading in the next pay period payroll and the employee can be over paid every pay period going forward.
When we process 2 paygroups concurrently by running Load Time and Labour process (PSPLDTL1) and both paygroups belonging to same pay period, some of the entries are set to Rejected by Payroll even though TL data is loaded into the pay sheet. This was caused due to inappropriate updating of payable status as data was not selected into PSPLDTL2_S_PAYWRK2.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms