OTL Authorized Delegate - Default Timecard Period Not Taken Into Account (Doc ID 1598741.1)

Last updated on JULY 15, 2016

Applies to:

Oracle Time and Labor - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

In OTL, changed the preference in "Default Timecard Period" from null to "Closest period prior to system date" and the server has been bounced.
In the Self Service timecard page, the setting is correctly taken into account (= the last not entered period is displayed for time entry),
but in the "OTL Authorized Delegate Time entry" responsibility, the system displays very old periods.
It seems that the system shows the "Earliest period prior system date", instead of the "closest" one, as expected.
Additionally, when selecting the Upload Timecard option, the period displayed is null, and no timecard periods are displayed in the drop down list.

Why is the behaviour not the same in both OTL and Self Service responsibilities ?
 

Solution

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