Seniority Changes in V3 Seniority Dates: Oracle Fusion Human Capital Management

Seniority
Changes in V3
Seniority Dates
Oracle Fusion Human Capital Management
ORACLE W HITE PAPER JANUARY 2, 2020

DISCLAIMER
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions. The
development, release, and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
Note: In the images or examples included in this document regarding: user details, company
names, addresses, emails, and/or telephone numbers represent a fictitious sample of data
(based upon made up data used in a demo environment). Any similarity to actual persons,
living or dead, is purely coincidental and not intended in any manner.
2 W HITE PAPER / Seniority Changes in V3 Seniority Dates

Table of Contents
Introduction .................................................................................................. 4
Using Seniority Dates .................................................................................. 4
Implementing Seniority Dates .................................................................... 11

INTRODUCTION
This paper outlines the help topics for changes in version 3 (V3) of the Seniority Dates functionality.
USING SENIORITY DATES
Seniority Dates: Explained

A seniority date is a date on which the calculation of a person's seniority with the enterprise, department, grade, or other entity is based.
In most cases, seniority dates are the same as start dates; however, using separate seniority dates you can manage them independent
of start dates.
Managing Seniority Dates: Explained

You manage seniority dates using the Manage Seniority Dates task.
In the Manage Seniority Dates page, you can view the length of service, history, and other details for each seniority date. Additionally, if
the seniority date rule is configured to allow edits, you can adjust the seniority by updating or correcting the manual adjustment units.
You can enter the manual adjustment using integers or fractions. For example, you can enter the adjusted seniority hours as 20 hours
or 18.5 hours.
After you adjust the seniority for a person, you can recalculate the seniority by using the Recalculate Seniority feature. If you want to
populate the seniority dates for all workers, run the Calculate Seniority Dates batch process.
Calculating Seniority Dates: Examples

The following examples illustrate the calculation of seniority dates based on assignment and work relationship changes.
In this example, the job seniority date is configured at the following seniority date levels:
 Person
 Work Relationship
 Assignment
Based on Assignment Changes

Vijay Singh is hired in Vision IND legal employer on 1-Jan-2005. He has multiple assignments and work relationships in the enterprise.
The following table shows a summary of his default seniority dates.
Date Action Legal Employer Assignment Job Department
1-Jan-2005 Hire Vision IND Assignment 1 Sales Consultant ERP
Seniority calculation as of 1-Jan-2006:
Seniority Date Level Job Seniority Seniority Date Exit Date
Job – Person Level Sales Consultant 1 Year 1-Jan-2005 N/A
Job – Work Sales Consultant 1 Year 1-Jan-2005 N/A

Relationship Level
Job – Assignment Level Sales Consultant 1 Year 1-Jan-2005 N/A

Starting 1-Jan-2007, Vijay has a new assignment in the HCM department, but continues to perform the same job. His current
assignment is end dated.
1-Jan-2007 End Assignment Vision IND Assignment 1 Sales Consultant ERP
1-Jan-2007 Add Assignment Vision IND Assignment 2 Sales Consultant HCM
Job – Person Level Sales Consultant 3 Years 1-Jan-2005 N/A
Job – Work Sales Consultant 3 Years 1-Jan-2005 N/A

Relationship Level
Job – Assignment Level Sales Consultant 2 Years 1-Jan-2005 31-Dec-2006

(Assignment 1)

(Assignment 2)
Based on Work Relationship Changes

On 1-Jan-2010, Vijay's assignment undergoes a global transfer to a new legal employer. However, he continues in the same HCM
department.
1-Jan-2007 End Assignment Vision IND Assignment 1 Sales Consultant ERP
1-Jan-2010 Global Transfer InFusion US Assignment 3 Sales Consultant HCM

Job – Work Sales Consultant 5 Years 1-Jan-2005 31-Dec-2009

Relationship Level (Vision IND)

Relationship Level (InFusion US)

(Assignment 1)

(Assignment 2)

(Assignment 3)
Calculating Cumulative Seniority Dates: Examples

You can configure the seniority dates rules to calculate seniority on a cumulative basis. The following examples illustrate the calculation
of seniority dates based on cumulative and noncumulative seniority.
In this example, the job seniority date is configured at the following seniority date levels:
 Person
 Work Relationship
 Assignment
Based on Cumulative Seniority

This example illustrates the calculation of seniority dates for Priya Krishnan. She has multiple assignments and work relationships in the
enterprise, and the cumulative option has been turned on for all the 3 job seniority dates.
Priya Krishnan is hired in Vision IND legal employer on 1-Jan-2005. The following table shows a summary of her default seniority dates.

Relationship Level

On 1-Jan-2007, Priya Krishnan has a job transfer in the current assignment.
1-Jan-2007 Job Change Vision IND Assignment 1 Business Analyst ERP
Job – Person Level Sales Consultant 2 Years 1-Jan-2005 31-Dec-2006

Relationship Level
Job – Person Level Business Analyst 1 Year 1-Jan-2007 N/A
Job – Work Business Analyst 1 Year 1-Jan-2007 N/A

Relationship Level
Job – Assignment Level Business Analyst 1 Year 1-Jan-2007 N/A
Note
Two seniority date records are generated at each seniority date level because there is a change in the job attribute which is used for
calculating the seniority dates.
On 1-Jan-2008, Priya Krishnan has a new assignment in a different department. However, her job changes back to her earlier job of
Sales Consultant. Her current assignment is end dated.
1-Jan-2008 End Assignment Vision IND Assignment 1 Business Analyst ERP


Relationship Level

(Assignment 1)
Job – Person Level Business Analyst 1 Year 1-Jan-2007 31-Dec-2007
Job – Work Business Analyst 1 Year 1-Jan-2007 31-Dec-2007

Relationship Level
Job – Assignment Level Business Analyst 1 Year 1-Jan-2007 31-Dec-2007

(Assignment 1)
Job – Work Sales Consultant 3 Years 1-Jan-2008 N/A

Relationship Level

(Assignment 2)
Note
Job seniority dates are configured to be cumulative, therefore, the job seniority equals 1 year in the current assignment plus 2 years in
the previous assignment.
Based on Noncumulative Seniority

This example illustrates the calculation of seniority dates for Priya Krishnan. She has multiple assignments and work relationships in the
enterprise, and the cumulative option has been turned off for all the 3 job seniority dates.
Priya Krishnan is hired in Vision IND legal employer on 1-Jan-2005. The following table shows a summary of her default seniority dates.


Relationship Level
On 1-Jan-2007, Priya Krishnan has a job transfer in the current assignment.

Relationship Level
Job – Person Level Business Analyst 1 Year 1-Jan-2007 N/A
Job – Work Business Analyst 1 Year 1-Jan-2007 N/A

Relationship Level
Job – Assignment Level Business Analyst 1 Year 1-Jan-2007 N/A
Note
Two seniority date records are generated at each seniority date level because there is a change in the job attribute which is used for
calculating the seniority dates.
On 1-Jan-2008, Priya Krishnan has a new assignment in a different department. However, her job changes back to her earlier job of
Sales Consultant. Her current assignment is end dated.
1-Jan-2008 End Assignment Vision IND Assignment 1 Business Analyst ERP


Relationship Level

(Assignment 1)
Job – Person Level Business Analyst 1 Year 1-Jan-2007 31-Dec-2007
Job – Work Business Analyst 1 Year 1-Jan-2007 31-Dec-2007

Relationship Level
Job – Assignment Level Business Analyst 1 Year 1-Jan-2007 31-Dec-2007

(Assignment 1)

Relationship Level

(Assignment 2)
Note
Job seniority dates are configured to be noncumulative, therefore, the job seniority considers the length of service in the current
assignment only.
Calculate Seniority Dates Process: Explained

Use the Calculate Seniority Dates process to calculate the seniority dates for workers based on the seniority rules configured in the
application. Use the Scheduled Processes work area to schedule and run the process.
Process Parameters
Person Number: This parameter filters the person numbers which are to be included in the ESS process for processing. You can run
this process for more than one person by entering the person numbers separated by commas. For example, use the following format:
Person Number 1,Person Number 2,Person Number 3. Do not enter leading or trailing space, or special characters. If you want to run
this process for all persons, do not enter any value.
Seniority Date Code list: This parameter filters the seniority dates rules for which the ESS process needs to be run. If we pass the
parameter as null, the ESS process will run for all the active rules in the system.

Past N Days: This parameter indicates the last number of days in which the data is changed for the person. The parameter scans the
following tables to find any data changes:
 PER_ALL_ASSIGNMENTS_M
 PER_ASSIGN_GRADE_STEPS_F
 PER_SENIORITY_HOURS
The parameter analyzes the LAST_UPDATE_DATE column of these tables and compares it with the days passed in the parameter for
processing.
Legal Employer: This parameter filters the person records based on the legal employer specified.
Union: This parameter filters the person records based on the union specified.
Include Terminated Work Relationships: This parameter checks the status of the work relationship. If you pass the value Y as the
parameter, it will detect the work relationships that are currently active. When you modify the data in an inactive work relationship and
pass the value N, the application will not process the assignments in this work relationship. You notice this behavior even though the
assignment records are modified in the past N days.
Related Topics
Scheduled Processes: Explained
Submitting Scheduled Processes and Process Sets: Procedure
Why is the seniority rule not displayed for a person on the Manage Seniority Dates page?
It's because the seniority rule is not applicable for the person or the seniority rule calculated a null length of service for the person.
IMPLEMENTING SENIORITY DATES
Topic: Configuring Seniority Dates: Explained

You can configure the rules for creating seniority dates using the Configure Seniority Dates task.
The seniority date rule defines the name and behavior of the seniority date. For example, you can define an enterprise seniority date at
person level. When the first work relationship is created for a person, the enterprise seniority date is calculated from the start date of the
work relationship.
Configuration Options
You can use the following options in the Configure Seniority Date Rules page:
Active: You can enable or disable the seniority date rule using this option. If the rule is active, seniority dates are automatically
generated when the employment data is changed, according to the rule definition. If the rule is not active, seniority dates are not
generated.
Note
You cannot edit or delete a seniority date rule if the corresponding seniority date rule has been used to populate seniority dates for a
person in the application. However, you can disable the seniority date rule in the Active field.
Seniority Rule Name: You must select from one of the predefined values, such as the bargaining unit seniority date - assignment level,
enterprise seniority date - person level, and legal employer seniority date - work relationship level. These values are defined in the
ORA_PER_SENIORITY_ITEMS lookup type.

Attribute: You can define the seniority date configuration based on this attribute. For example, legal employer is the seniority attribute in
case of a legal employer seniority date and enterprise is the seniority attribute in case of an enterprise seniority date. When the
seniority attribute is created or modified, the corresponding seniority date will be populated in the application according to the rules in
the setup.
Level: You can configure seniority dates at the person, work relationship, and assignment levels.
At the person level, all the work relationships and assignments for the given person are considered while deriving the seniority date. At
the work relationship level, all the assignments for the given work relationship are considered while deriving the seniority date. At the
assignment level, all the date effective records for the given assignment are considered while deriving the seniority date.
Adjustment Formula: You can configure an adjustment formula to calculate the seniority date adjustments using the Employment
Seniority Date Adjustment formula type.
Cumulative: Identifies the calculation logic of seniority when there is a gap in service. When this option is set to yes, the application also
considers the previous seniority calculations for the calculation of seniority. For example, consider a worker who was associated with an
organization from 1-Jan-2001 to 31-Dec-2009 and the Cumulative option is set to yes for both the seniority dates. The details of his
association and the seniority calculation is shown in the following table.
Action Start Date End Date Legal Legal Enterprise Comments

Employer Employer Seniority
Seniority
Hire 1-Jan-2001 31-Dec-2001 Vision US 1 Year 1 Year
Global Transfer 1-Jan-2002 31-Dec-2002 Vision CA 1 Year 2 Years The enterprise

seniority is the
sum of 1 year in
the current work
relationship and
1 year in the
previous work
relationship.
Termination 31-Dec-2002
Rehire 1-Jan-2007 31-Dec-2007 Vision UK 1 year 3 years The enterprise

seniority date is
configured to be
cumulative.
Therefore, the
enterprise
seniority is the
sum of 1 year in
the current work
relationship and
2 years in the
previous work
relationship.

Action Start Date End Date Legal Legal Enterprise Comments
Employer Employer Seniority
Seniority
Global Transfer 1-Jan-2008 31-Dec-2009 Vision US 3 years 6 years The legal

employer
seniority date is
configured to be
cumulative.
Therefore, the
seniority for the
Vision US legal
employer is the
sum of 2 years
in the current
work
relationship and
1 year in the
previous work
relationship.
The enterprise
seniority date is
configured to be
cumulative.
Therefore, the
enterprise
seniority is the
sum of 2 years
in the current
work
relationship and
4 years in the
previous work
relationship.
Termination 31-Dec-2009
Allow Edit: Specify whether users can override the seniority date using the Manage Seniority Dates task. If you set the value in this field
to No, you cannot edit the corresponding seniority date on the Manage Seniority Dates page.
Display in Guided Flows: Specify whether the seniority date can be displayed in the guided processes. If this option is set to yes for a
seniority date, the seniority date is displayed in the guided processes in view-only mode.
Override Seniority Basis: Seniority is calculated in days or hours based on the seniority basis value in the worker's assignment. You can
define an override for the seniority basis at the individual seniority rule level. For example, you can specify that a seniority rule must
always be calculated in hours even though the worker's assignment basis is days.

Conversion of Hours: When you cannot use a single set of conversion rules, you can convert hours to days using the Employment
Seniority Hours to Days Conversion formula type. You can define the hours for:
 Hours to day conversion

 Hours to month conversion
 Hours to year conversion
Seniority Filters: You can optionally display seniority filters in the configuration options and restrict the population of seniority dates by
using different filter conditions. For example, if you use a filter condition worker type equal to employee, the seniority dates are
populated for employees only.
Note
There are additional seniority filter options hidden out of the box in the Seniority Date Rule List table. You can display these filter
options using the View menu from the table.
Seniority Date Configuration Levels: Explained

You can configure seniority dates at the person, work relationship, and assignment levels using the Configure Seniority Dates task in
the Setup and Maintenance work area.
Seniority Date Level
You can use the following levels in the Configure Seniority Date Rules page:
Person: All the work relationships and assignments for the person are considered while deriving the seniority date at the person level.
Work Relationship: All the assignments under the work relationship are considered while deriving the seniority date at the work
relationship level.
Assignment: Only the individual assignment is considered while deriving the seniority date at the assignment level.
Migrate Seniority Dates Process: Explained

Use the Migrate to Version 3 of Seniority Dates process to migrate the seniority dates data to the new version (V3) from earlier versions
(V1 or V2). Use the Scheduled Processes work area to schedule and run the process.
You can manage the seniority of workers using V1, V2, or V3 versions of the Seniority Dates functionality.
V1 seniority dates: Seniority dates that are managed using the Manage 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.
V2 seniority dates: Seniority dates that are configured using the Configure Seniority Dates task and without using any fast formula are
referred to as V2 seniority dates. You can configure multiple seniority dates according to your requirement. These seniority dates are
managed using the Manage Seniority Dates task.
V3 seniority dates: Seniority dates that are configured using the Configure Seniority Dates task and by using a fast formula are referred
to as V3 seniority dates. You can configure multiple seniority dates according to your requirement. These seniority dates are managed
using the Manage Seniority Dates task.
Note
After you migrate to V3, you cannot migrate back to V1 or V2 because only one version of seniority date can be active at a time.
For more information, see Comparison Between Different Seniority Dates Versions (2414630.1) on My Oracle Support at
https://support.oracle.com

Process Parameters
The Migrate to Version 3 of Seniority Dates process uses the following parameter:
 Migrate Seniority Data From: Indicates whether you want to migrate seniority dates data to V3 from V1 or V2 based on your
current application setup.
Points to Consider for Migration
 Migrate from V1 to V3 while V2 exists

o Select the Migrate Seniority Data from V1 version of Seniority process parameter.
o After the migration, you cannot view or modify V1 seniority dates.
o You can no longer view or modify V2 seniority dates.
o Create new rules for V3 seniority dates because all the V2 seniority date rules are inactivated.
 Migrate from V1 to V3 while V2 does not exist
 Migrate from V2 to V3 while V1 exists
o Create new rules for V3 seniority dates because all the V1 seniority date rules are inactivated.
 Migrate from V2 to V3 while V1 does not exist
 No previous versions installed
o New setup for V3 with no data migration.
Seniority Dates User Entities

The following table describes the user entities that are available for seniority dates:
User Entity Name Description User Entity Context
PER_SENIORITY_DATES_V3_SDC_UE This user entity is used to describe the The following contexts must be provided
seniority date information for version 3 for this user entity:
(V3) seniority dates.
 PERSON_ID
 EFFDT
 SENIORITY_DATE_CODE
PER_SENIORITY_DATES_V3_UE This user entity is used to describe the The following contexts must be provided
seniority date information for V3 seniority for this user entity:
dates.
 PERSON_ID
 EFFDT
PER_SENIORITY_HOURS_V3_UE This user entity is used to describe the The following context must be provided
seniority hours information for an hours- for this user entity:
based worker in V3 seniority dates.
 PERSON_ID

Related Topics
Scheduled Processes: Explained
Submitting Scheduled Processes and Process Sets: Procedure

ORACLE CORPORATION
Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA
Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com
CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.
blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed
orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0120
Seniority Changes in V3 Seniority Dates
September 2018
Author: Aliasgar Khambhaty and Girish Singh

Seniority Changes in V3 Seniority Dates: Oracle Fusion Human Capital Management

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Seniority Changes in V3 Seniority Dates: Oracle Fusion Human Capital Management

Загружено:

Авторское право:

Доступные форматы

Seniority

ORACLE W HITE PAPER JANUARY 2, 2020

2 W HITE PAPER / Seniority Changes in V3 Seniority Dates

Using Seniority Dates .................................................................................. 4

Implementing Seniority Dates .................................................................... 11

3 W HITE PAPER / Seniority Changes in V3 Seniority Dates

USING SENIORITY DATES

Seniority Dates: Explained

Managing Seniority Dates: Explained

Calculating Seniority Dates: Examples

Based on Assignment Changes

Date Action Legal Employer Assignment Job Department

1-Jan-2005 Hire Vision IND Assignment 1 Sales Consultant ERP

Seniority calculation as of 1-Jan-2006:

Seniority Date Level Job Seniority Seniority Date Exit Date

Job – Person Level Sales Consultant 1 Year 1-Jan-2005 N/A

Job – Work Sales Consultant 1 Year 1-Jan-2005 N/A

Job – Assignment Level Sales Consultant 1 Year 1-Jan-2005 N/A

4 W HITE PAPER / Seniority Changes in V3 Seniority Dates

Date Action Legal Employer Assignment Job Department

1-Jan-2005 Hire Vision IND Assignment 1 Sales Consultant ERP

1-Jan-2007 End Assignment Vision IND Assignment 1 Sales Consultant ERP

1-Jan-2007 Add Assignment Vision IND Assignment 2 Sales Consultant HCM

Seniority calculation as of 1-Jan-2008:

Seniority Date Level Job Seniority Seniority Date Exit Date

Job – Person Level Sales Consultant 3 Years 1-Jan-2005 N/A

Job – Work Sales Consultant 3 Years 1-Jan-2005 N/A

Job – Assignment Level Sales Consultant 2 Years 1-Jan-2005 31-Dec-2006

Job – Assignment Level Sales Consultant 1 Year 1-Jan-2007 N/A

Based on Work Relationship Changes

Date Action Legal Employer Assignment Job Department

1-Jan-2005 Hire Vision IND Assignment 1 Sales Consultant ERP

1-Jan-2007 End Assignment Vision IND Assignment 1 Sales Consultant ERP

1-Jan-2007 Add Assignment Vision IND Assignment 2 Sales Consultant HCM

1-Jan-2010 Global Transfer InFusion US Assignment 3 Sales Consultant HCM

5 W HITE PAPER / Seniority Changes in V3 Seniority Dates

Seniority Date Level Job Seniority Seniority Date Exit Date

Job – Person Level Sales Consultant 6 Years 1-Jan-2005 N/A

Job – Work Sales Consultant 5 Years 1-Jan-2005 31-Dec-2009

Job – Work Sales Consultant 1 Year 1-Jan-2010 N/A

Job – Assignment Level Sales Consultant 2 Years 1-Jan-2005 31-Dec-2006

Job – Assignment Level Sales Consultant 3 Years 1-Jan-2007 31-Dec-2009

Job – Assignment Level Sales Consultant 1 Year 1-Jan-2010 N/A

Calculating Cumulative Seniority Dates: Examples

Based on Cumulative Seniority

Date Action Legal Employer Assignment Job Department

1-Jan-2005 Hire Vision IND Assignment 1 Sales Consultant ERP

Seniority calculation as of 1-Jan-2006:

Seniority Date Level Job Seniority Seniority Date Exit Date

Job – Person Level Sales Consultant 1 Year 1-Jan-2005 N/A

Job – Work Sales Consultant 1 Year 1-Jan-2005 N/A

Job – Assignment Level Sales Consultant 1 Year 1-Jan-2005 N/A

6 W HITE PAPER / Seniority Changes in V3 Seniority Dates

Date Action Legal Employer Assignment Job Department

1-Jan-2005 Hire Vision IND Assignment 1 Sales Consultant ERP

1-Jan-2007 Job Change Vision IND Assignment 1 Business Analyst ERP

Seniority calculation as of 1-Jan-2008:

Seniority Date Level Job Seniority Seniority Date Exit Date

Job – Person Level Sales Consultant 2 Years 1-Jan-2005 31-Dec-2006

Job – Work Sales Consultant 2 Years 1-Jan-2005 31-Dec-2006

Job – Assignment Level Sales Consultant 2 Years 1-Jan-2005 31-Dec-2006

Job – Person Level Business Analyst 1 Year 1-Jan-2007 N/A

Job – Work Business Analyst 1 Year 1-Jan-2007 N/A