ETL9.1: TL LOAD is Ignoring the Filters on Run Controls and Calls the Paysheet Creation Process

(Doc ID 1492220.1)

Last updated on JULY 13, 2016

Applies to:

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


On : 9.1 version, NA Payroll Integration/TL Load

TL Load for on cycle payroll is ignoring the filters specified on the run control. It is also rejecting payable time previously loaded if there is some kind of job change, even when employee isn't specified on the run control. A new hire also had a paysheet created which wasn't expected as they were hired after the cut off date.

When only one or two employees are specified on the filter for an on cycle load the TL Load process should only be processing those employees and should not be looking at any other employees.

The issue can be reproduced at will with the following steps:
1. Set paygroup automatic paysheet update flag off on the paygroups
2. Load in preliminary calc is turned on on the main installation page
3. Create payable time ready to load for several employees
4. make a job change to one of the employees you don't want time loaded for
5. hire a new employee after the cut off date but within the pay period date range
6. run tl load to oncycle calendar using the filters and specifying just one employee
7. TL Load process caused a new paysheet to be created for the new hire, the employee with the job change had previously loaded payable time rejected and no error messages were given.

There are two issues reported because of the behavior:
1) Why did the filtered TL Load cause the new hire paysheet to be created even though we honored the automatic paysheet update flag and didn’t load the time?   No messages provided informing users.
2. Why was the employee’s time with the job change rejected without messages and the employee wasn’t even on the run control? The job change calling refresh isn’t surprising, what was surprising was that it rejected the payable time but no messages as to why the time was rejected.

The issue has the following business impacts:

1. An employee who was newly hired but not expected to be paid (based on policy) is paid based on job hours in error.  The employee should have been paid only in the next period due to cut off date and the 'Automatic Paysheet Update' setting on the Paygroup being off.  The preliminary calculation process in payroll does honor this flag setting and does not create a paysheet for new hires after they were originally created.

2. An employee has their previously loaded payable time rejected without any error messages warning the end users. In this case because they do load time in preliminary calc process this time will get picked up again. However, for a customer that has the load in preliminary calc turned off the employee will not get time reloaded and would be underpaid.


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