Unable To Create FLSA Time Period Definition. Period Type Is Not Available In The LOV.
(Doc ID 1903752.1)
Last updated on MARCH 25, 2019
Applies to:Oracle HRMS (US) - Version 12.1 HRMS RUP5 and later
Information in this document applies to any platform.
On : 12.1 HRMS RUP5 version, FLSA Overtime
Unable to create FLSA Time Period Definition. Period Type is not available in the LOV.
While attempting to create a Time Period Definition, the Period Type LOV was not available.
Expect to be able to enter the weekly Period Type while creating a Time Period Definition
The issue can be reproduced at will with the following steps:
Define Time Definition Period
The navigation for this window is Other Definitions > Dynamic Time Periods. (Note: you must be logged into the E-Business Suite Personal Home Page to view this form.)
For FLSA Periods (or Overtime Periods) that are: weekly, bi-weekly, semi-monthly, monthly or lunar month (28 days), follow this setup:
Set effective date to a date early enough to handle any historical information you want to enter.
Select Create Time Definition.
Enter the name of the time definition.
Enter the short name of the time definition.
Select a definition type of Static Period from the list.
Enter a start date for the overtime period in the Start Date field.
Enter the number of years for the overtime period in the Years field. The application generates overtime periods for the numbers of years as of the start date.
Select the appropriate value in the Period Type field (This is where there are no values in the LOV)
Select 'Element Allocation' in the Time Definition Usages region.
Click on Apply to save your work.
The record will not save without a Period Type.
The issue has the following business impact:
Due to this issue, users cannot calculate the Blended Rate for the FLSA Overtime Premium element
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document