ETL8.x/9.x: Deleting Time on The Timesheet Should Keep The Reported Time as Zero '0'.
Last updated on MAY 20, 2016
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 8.9 to 9.2 [Release 8.9 to 9]
Information in this document applies to any platform.
This document was previously published as Customer Connection Solution 201017609
Customer has elected to use the delivered Time Period view for Timesheet entry. The majority of employees have a biweekly time period. Using this view will enable users to enter the entire pay period on one page and will help to increase productivity. We have discovered some issues with using the view. There is no problem with positive time reporters however; we have found major issues with exception time reporters that affect the employee's pay.
In the following scenario, time is entered in the current pay period. The first week has no exceptions whereas the second week should not have any paid time. The user deletes all of the time in the second week and saves the time sheet. The user sees scheduled time in the first week and no time in the second week which is correct.
The problem is that the users are under the assumption that no time will be created for the second week because it was deleted. In fact, what happens is that scheduled time still exists and will be sent to Payroll resulting in the employee being overpaid. (Screen shots follow)
PeopleSoft has suggested a workaround whereby the time in the second week would be saved with zero hours rather than just deleting it.
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