ETL9.1: Employee Overpaid Even If High Priority Exception Was Generated, Exception Didn't Stop New Payable Time (Doc ID 1908415.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.

Symptoms

On : 9.1 version, Time Administration

Employee paid more than 40 hours in a week even if a high exception is generated for the day. The negative offset is created but instead of not creating the new payable time due to the high exception the new positive row of payable time was generated in error.

The high priority exception should have stopped the time admin process from creating the new payable time.

The issue can be reproduced at will with the following steps:
1. create template 150 rule to generate high exception if more than 40 hours in the week
2. report 8 hours a day mon thru fri = 40 hours
3. time admin is run and it generates payable time
4. time is loaded to paysheet resulting in the payable time now being in a status of TP (frozen)
5. employee changes one of the days to 10 hours (let's say it's on Thursday)
6. time admin runs and generates an exception that the employee worked more than 40 hours
7. check payable time and see that there is now a negative 8 hours on the day that was changed but it still generated the new positive row of payable time with the new amount on the day, resulting in employee being paid for more than 40 hours.

The issue has the following business impact:
Employees are overpaid if the exception isn't seen by the end users.

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