Overview of Seniority Dates
All topics in this section pertain to version 3 (V3) of the seniority dates functionality. You can define and manage
the seniority of workers using version 3 of the seniority dates functionality.
You can configure seniority dates using the Configure Seniority Dates task and fast formula. You can manage them
using the Seniority Dates task under Quick Actions.
Seniority Date Versions
You can manage the seniority of workers using V1, V2, or V3 versions of the Seniority Dates functionality. This
table describes these versions:
V1
Seniority dates that are managed using the Work Relationship task are referred to as V1 seniority dates. You can only manage the Enterprise
Seniority Date and Legal Employer Seniority Date using V1 seniority dates. V1 seniority dates are stored in the PER_PERIODS_OF_SERVICE
table.
V2
Seniority dates that are configured using the Configure Seniority Dates task without using advanced configuration options are referred to as V2
seniority dates. You can configure multiple seniority dates as per your requirement. These seniority dates are managed using the Seniority Dates
task. V2 seniority dates are stored in the PER_SENIORITY_DATES table.
Note:
You run the Populate Seniority Dates ESS job to initially populate the seniority dates. After this job is run, you don't need to run any other
scheduled process.
V3
Seniority dates that are configured using the Configure Seniority Dates task and advanced configuration options are referred to as V3 seniority
dates. You can configure multiple seniority dates as per your requirement. These seniority dates are managed using the Seniority Dates task. V3
seniority dates are stored in the PER_SENIORITY_DATES_F table.
Note:
The seniority dates aren't calculated during run time. You must run the Calculate seniority Dates process to calculate seniority dates. You need to
schedule this process because V3 seniority dates are populated only after the process is completed.
Seniority Dates User Entities
You can use user entities to describe seniority date information for V3 seniority dates.
User Entity Name Description User Entity Context
PER_SENIORITY_DATES_V3_SD This user entity is used to describe the seniority The following contexts must be provided for
C_UE date information for V3 seniority dates. this user entity:
• PERSON_ID
• EFFDT
• SENIORITY_DATE_CODE
PER_SENIORITY_DATES_V3_UE This user entity is used to describe the seniority The following contexts must be provided for
date information for V3 seniority dates. this user entity:
• PERSON_ID
• EFFDT
PER_SENIORITY_HOURS_V3_UE This user entity is used to describe the seniority The following context must be provided for this
hours information for an hours-based worker in V3 user entity:
seniority dates. • PERSON_ID
FAQs for Seniority Dates
How can I find out which version of seniority dates I am using?
Run this query in your database instance: SELECT VERSION_CODE FROM
FUSION.PER_EMPL_CONFIGURATIONS
Why can't I see the seniority rule on the Employment Info page
when it's displayed on the Seniority Dates page?
To display the rule on the Employment Info page, set the Display in Guided Flows option to Yes on the Configure
Seniority Date Rules page.
How can I find the most recent hire date when using V3
seniority dates?
You can do so by configuring a non-cumulative rule at the person level for the enterprise attribute. For more
information, see the document (Doc ID 2476188.1) on My Oracle Support: https://support.oracle.com
How can I exclude pending workers from the seniority dates
calculation?
You must clear the Pending worker check box in the Worker Type seniority filter on the Configure Seniority Date
Rules page.
What's the source for the seniority hours used in calculating
hours-based seniority?
The source is the hours loaded in the PER_SENIORITY_HOURS table.
How can I load hours in the seniority hours table?
By using HCM Data Loader. For more information, see the Oracle Human Capital Management Cloud Integrating
with HCM guide on Help Center at https://docs.oracle.com/en/cloud/saas/index.html
Can I use assignment or standard working hours when
calculating hours-based seniority?
No. To calculate hours-based seniority, you must load hours in the PER_SENIORITY_HOURS table using HCM
Data
Loader.
Why can't I calculate V3 seniority dates by running the Populate
Seniority Dates process?
The Populate Seniority Dates process is used to calculate version 2 (V2) seniority dates after the initial conversion.
You must run the Calculate Seniority Dates process to calculate the V3 seniority dates.
