Comparison between Different Seniority Dates

Versions
Oracle Fusion Human Capital Management
ORACLE WHITE PAPER | JUNE 2018
Introduction
Seniority is the length of time that an individual has served in a job or worked for an organization. Seniority can bring
higher status, rank, or precedence to an employee who has served an organization for a longer period of time. In
HCM Cloud, customers can manage seniority using different approaches. This white paper aims to outline the
differences between these various seniority solutions in HCM Cloud.

Comparison
The following table describes the differences based on the decision points:

Decision V1 Version of Seniority V2 Version of Seniority V3 Version of Seniority

Available from
What's New release
documentation
Steps required to enable
seniority dates
Coexistence with other
versions of seniority
dates
Which seniority dates
can be managed?
Dates Dates Dates
Release 1 Release 10 Release 13.17.11 (17D)
N/A Ability to Define Seniority Dates Seniority Dates Enhancements
None None Run the Enterprise Scheduler
Service (ESS) job: Migrate to
Version 3 of Seniority Dates
Can coexist with V2 Can coexist with V1 After the customer has migrated to
V3, they cannot use V1 or V2.
Only the following seniority Customers can configure the Customers can configure the
dates: seniority dates at different levels, seniority dates at different levels,
such as Person, Work such as Person, Work
 Enterprise Seniority
Relationship, and Assignment for Relationship, and Assignment for
Date
the following attributes: the following attributes:
 Legal Employer
 Bargaining Unit  Business Unit (18B)
Seniority Date
 Collective Agreement  Bargaining Unit
 Enterprise  Collective Agreement
 Grade  Country
 Grade Step  Department
 Job  Enterprise
 Legal Employer  Grade
 Legislation  Grade Step
 Position  Job
 Union Member  Legal Employer
 Location
 Position
 Union

From where are the
seniority dates
managed?
Can the seniority dates
be entered during Hire
flows?
How are seniority dates
calculated?
Is the seniority calculated
Manage Work Relationship UI Manage Seniority Dates UI Manage Seniority Dates UI
Yes No No
Manually entered or Manually Automatically calculated Automatically calculated when the
updated following ESS job is run: Calculate
Seniority Dates
N/A Yes No, the following ESS job must be

1 | COMPARISON BETWEEN DIFFERENT SENIORITY DATES VERSIONS

Decision V1 Version of Seniority V2 Version of Seniority V3 Version of Seniority
Dates Dates Dates
in real time? run regularly to recalculate the
seniority dates: Calculate Seniority
Dates
How are the seniority Manually on the Manage Work Automatically based on Automatically based on
dates updated or Relationship UI Employment actions. Employment actions.
adjusted? Additionally, the seniority dates can Additionally, manual adjustments
be manually updated on the can be entered for the seniority
Manage Seniority Dates UI dates on the Manage Seniority
Dates UI.
The Legal Employer The seniority date is corrected The seniority date is corrected to 1- Provide an adjustment of 30 days
Seniority Date is 1-May- to 1-Apr-2018. Apr-2018. for the seniority date. This will
2018 and needs to be update the seniority date to 1-Apr-
updated to 1-Apr-2018. 2018 when the ESS job is run.
How is the seniority date
updated in this case?
Do you need to configure No configuration is required. Seniority rules configuration is Seniority rules configuration is
seniority dates? required. Use the Configure required. Use the Configure
Seniority Dates task. Seniority Dates task.
Is Fast Formula Not Supported. Not Supported. Supported, and uses the following
supported? formula type: Employment Seniority
Date Adjustment
Do you need to run any No Run the following ESS job to Run the following ESS job to
process post data populate the seniority dates for calculate the seniority dates for
migration? workers: Populate Seniority Dates workers: Calculate Seniority Dates
This ESS job needs to be run
regularly to recalculate the seniority
dates for workers.
What are the None None You must provide a value of
considerations when ORA_PER_SNDT_DAYS for the
uploading worker Seniority Basis attribute.
assignments? File Name: worker.dat
File Discriminator: Assignment
Attribute: SeniorityBasis
How can I update The Enterprise and Legal Not Supported Not Supported
seniority dates using Employer seniority dates can
HCM Data Loader? be updated using the following
parameters:
File Name: worker.dat
File Discriminator:
WorkRelationship
Attributes:
EnterpriseSeniorityDate,
LegalEmployerSeniorityDate
How can I load seniority N/A N/A Adjustment for each configured
date adjustments using seniority rule can be uploaded
HCM Data Loader? using the following parameters:
File Name: worker.dat
File Discriminator: SeniorityDate
Attributes: ManualAdjustmentDays,
ManualAdjustmentComments
Is Database Item (DBI) Supported Supported Supported
supported?
Which is the table storing N/A PER_SENIORITY_DATES_SETUP PER_SENIORITY_DATES_SETUP
the seniority dates

2 | COMPARISON BETWEEN DIFFERENT SENIORITY DATES VERSIONS

Decision V1 Version of Seniority V2 Version of Seniority V3 Version of Seniority
Dates Dates Dates
configuration?
Which is the table storing PER_PERIODS_OF_SERVICE PER_SENIORITY_DATES PER_SENIORITY_DATES_F
the seniority dates of
workers?
Is Oracle Transactional Supported N/A Planned for a future release.
Business Intelligence
(OTBI) supported?
Is Eligibility Profile Supported N/A Planned for a future release.
supported?
Supporting N/A N/A Configuring Seniority Dates:
documentation Explained
Seniority Date Configuration
Levels: Explained
Migrate Seniority Dates Process:
Explained
Loading Seniority Dates: Examples

FAQs
How can I find out the version of seniority dates that is configured in my environment?

Run the following query in Business Intelligence Publisher (BIP): Select * from
FUSION.PER_EMPL_CONFIGURATIONS;

How can I revert from V3 version of seniority dates to V2 or V1?

In the short term, you can revert to V2 or V1 by raising a service request (SR). We will be releasing a self-service
option shortly to enable this switch.

The self-service option will leverage the Diagnostics Report feature. The diagnostic report checks if the customer
has willingly run the following ESS job: Migrate to Version 3 of Seniority Dates. If yes, then the V3 version is not
reverted.

If no, the diagnostic report further checks if the users have entered any manual adjustments. If the users have
entered manual adjustments, the V3 version is not reverted.

If there are no manual adjustments and the customer is using V3 because of an upgrade, the diagnostic job updates
the seniority version to V2. The seniority version is updated in the PER_EMPL_CONFIGURATIONS and
PER_SENIORITY_DATES_SETUP tables and the records are cleared from the PER_SENIORITY_DATES_F table.

3 | COMPARISON BETWEEN DIFFERENT SENIORITY DATES VERSIONS

 Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

CONNECT W ITH US

blogs.oracle.com/oracle
Copyright © 2018, 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
facebook.com/oracle 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
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.

oracle.com 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. 0618

White Paper Title

June 2018
Author: [OPTIONAL]
Contributing Authors: [OPTIONAL]