V2 Version of

Seniority Dates
Oracle Fusion Human Capital Management

ORACLE W HITE PAPER AUGUST 23, 2018

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.

2 W HITE PAPER / V2 Version of Seniority Dates

INTRODUCTION

Using version 2 (V2) of the Seniority Dates feature, you can define seniority dates and configure the
rules for their creation and defaulting. Seniority dates can be configured at the person, work
relationship, and assignment level. When the employment objects are created, deleted, or updated
from the user interface (UI), the seniority dates rule engine is triggered and it populates the seniority
dates accordingly.

Using the Manage Seniority Dates feature, you can view the seniority dates for person, work
relationships, and assignments. You can view the length of service for each seniority date and
override the seniority date if the configuration allows it.

In the version 1 (V1) seniority dates release, only the following seniority dates were available in the
Manage Work Relationship UI:

 Legal Employer Seniority Date

 Enterprise Seniority Date

In the V2 seniority dates release, you can define multiple seniority dates at different levels (person,
work relationship, assignment) and leverage them for reporting and downstream processes.

The V2 seniority dates once configured, will be available from the Manage Seniority Dates task. If
you have not set up at least one seniority date rule using the Configure Seniority Dates task, the
Manage Seniority Dates task will not start the new UI. Instead, the Manage Seniority Dates task will
redirect you to the Manage Work Relationship UI.

3 W HITE PAPER / V2 Version of Seniority Dates

TOPICS FOR V2 SENIORITY DATES

Configuring Seniority Dates: Explained

You can configure the rules for creating and defaulting seniority dates using the Configure Seniority Dates task in the Setup and
Maintenance work area.

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 and defaulted when the employment data is changed, according to the rule definition. If the rule is not active, seniority dates
are not generated and defaulted.

Note: You cannot edit or delete a seniority date rule if the corresponding seniority date configuration has been used to populate
seniority dates for a person in the system. However, you can disable the seniority date rule in the Active field.

Seniority Date: You must select from one of the predefined code 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.

Seniority 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 logically created or modified, the corresponding seniority date will be populated in the system 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 will be considered while deriving the seniority date.
At the work relationship level, all the assignments for the given work relationship will be considered while deriving the seniority date. At
the assignment level, all the date effective records for the given assignment will be considered while deriving the seniority date.

4 W HITE PAPER / V2 Version of Seniority Dates

Object: Identifies the business object associated with the seniority attribute. When you select the seniority attribute and level, the object
field is automatically populated, and you cannot edit this value. For example, if you select bargaining unit and assignment, the object
field is populated with the assignment value.

Source: Rule that defines how the seniority date is populated. When you select the seniority attribute and level, the source field is
automatically populated, and you cannot edit this value. For example, if you select legal employer and work relationship, the source
field is populated with the first matching work relationship start date rule. This rule indicates that the first work relationship to match the
seniority rule is used to populate the seniority date. The start date of this work relationship will populate the seniority date.

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.

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.

5 W HITE PAPER / V2 Version of Seniority Dates

Populate Seniority Dates Process: Explained
Use the Populate 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 run the process.

This process is required to be run in the following scenarios:

 When the data is loaded through HDL.

 When a new seniority rule is configured in the application, and the customer wants to populate this seniority date for existing
workers.

Note: Once the seniority rules are configured, the application automatically populates the seniority dates based on UI transactions.

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 you pass a null
value for this parameter, the ESS Process will run for all the active rules in the system.

Exclude Terminated Work Relationships: This parameter checks the status of the work relationship. If you pass the value “Yes” for
this parameter, it detects all work relationships that are currently active. However, if you pass the value “Yes” after modifying the data
in an inactive work relationship, the application will not process the assignments in the work relationship.

Operation: If you pass the value “Clean and RePopulate” for this parameter, the process repopulates the seniority dates for the
seniority rules for which the process is run.

6 W HITE PAPER / V2 Version of Seniority Dates

Managing Seniority Dates: Explained
You can view and manage the seniority dates of persons using the Manage Seniority Dates task in the Person Management work area.

In the Manage Seniority Dates page, the seniority dates are organized in a hierarchy that shows all the work relationships and
assignments for a person. You can view the length of service for each seniority date and override the seniority date if the seniority date
rule is configured to allow edits.

You can view the seniority dates at the person, work relationship, and assignment levels.

Seniority Dates - Person Level

All the work relationships and assignments for the person are considered while deriving the seniority date at the person level.

Seniority Dates - Work Relationship Level

All the assignments under the work relationship are considered while deriving the seniority date at the work relationship level.

Seniority Dates - Assignment Level

Only the individual assignment is considered while deriving the seniority date at the assignment level.

7 W HITE PAPER / V2 Version of Seniority Dates

FAQS FOR V2 SENIORITY DATES
Can I load seniority data in V2 seniority dates?
No. You can’t load seniority data (using HCM data loader) in V2.

What is the OTBI subject area for V2 seniority dates?

OTBI doesn’t support V2 seniority dates.

What are the user entities supporting V2 seniority dates?

UE Name Base Name

Extract Person Seniority Dates PER_PER_SENIORITY_DATES_UE

What are the security privileges associated with V2 seniority dates?

The following security privileges are associated:

 Configure Seniority Dates (PER_CONFIGURE_SENIORITY_DATES_PRIV): For configuration access.

 Manage Seniority Dates (ORA_PER_SENIORITY_DATES_MANAGEMENT_DUTY): For “Manage seniority Dates” task
access. This is an aggregate privilege.

How can I provide view-only access for V2 seniority dates using application security?
You can’t provide view-only access using application security roles. Use page level personalization to provide view-only access for V2
seniority dates.

How can I configure a noncumulative seniority rule for V2 seniority dates?

You can’t configure a noncumulative seniority rule in V2 seniority dates.

Are there any enhancements planned for V2 seniority dates?

No. Any future enhancements will be available for version V3 of seniority dates only.

8 W HITE PAPER / V2 Version of Seniority Dates

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 © 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 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. 0818
V2 Version of Seniority Dates
August 2018
Author: Aliasgar Khambhaty and Girish Singh