ETL9.x: Time and Labor Load Ignores Users Manually Turning Off OK to Pay on Paysheet (Doc ID 1964107.1)

Last updated on JULY 01, 2016

Applies to:

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

Symptoms

On : 9.1 version, TL Integrations

For an employee that transfers from one paygroup to another within the same company they only want one check issued. They manually turn off ok to pay on the old paygroups paysheet and then manually move the hours from Time and Labor to the new Paygroups paysheet. When they run pay calc they are experiencing issues of employee's getting their time loaded again and ok to pay turned back on in the old paygroups paysheet.

They do not want Time and Labor load process to turn back on the OK to pay flags that were manually turned off or to reload additional time to that paysheet.

The issue can be reproduced at will with the following steps:
1. two pay calendars for two paygroups within the same company, with the same pay period end date and using the same payrun id
2. transfer an employee from one paygroup to the other within the same company mid period (example: bi weekly, employee transfers to new paygroup second week of period)
3. run tl load to load time to paysheets (time loaded to both, one for the first week and the new one for the second week)
4. manually turn ok to pay off on the old paygroups paysheet and move the hours to the new paygroups paysheet
4. create offsets or make job changes of some kind for the first week
5. run preliminary calc (this calls tl load to load the additional time or refresh the paysheets and brings the hours back into the old paygroup paysheet and turns ok to pay back on, the manually entered hours remain on the new paygroup paysheet...thus if not caught employee overpaid

The issue has the following business impact:
Due to this issue, the manual changes being made are undone by the TL Load/Payclc process and can cause overpayments if not caught. They only want one paycheck not two to be issued to the employee.

Cause

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