Last updated on JULY 13, 2016
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
After applying individual fix for bug TL20958553_CODECHANGES employees can no longer see the initial in punches for cross over shifts at the beginning of the week. This was not an issue prior to applying bundle #17 and then the individual fix. After applying the bug fix, we have the display issue, which directly affects the Employee and Manager Timesheet view, and will cause serious issues for us from the client side, as they may not be able to view their timesheet and the workaround provided is unacceptable. The issues are becoming more and more unmanageable.
When opening timesheet for the week the punches that correspond to the first out punch should be displayed and are not. Employees cannot see the initial punches even if they refresh the timesheet to the prior day, have to refresh it 2 days or more back to see the entire punch sequence.
The issue can be reproduced at will with the following steps:
1. Base Time Zone is CST
2. Overnight punch reporters and managers in PST timezone
3. Punch time is entered via TCD interface or rapid time
4. Work week runs from Monday thru Sunday
5. Employee's in PST Timezone do not see the in punches from Sunday on the timesheet, even if the timesheet is refreshed to start on Sunday
6. This is only specific to employees not in base timezone and in a later timezone than base.
Due to this issue, users cannot edit the punches for the first part of their shift without refreshing the timesheet for a few days prior to shift. This did not work like this before Bundle #17 and the individual fix. Refreshing the timesheet to prior days is causing confusion and this workaround is unacceptable.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms