My Oracle Support Banner

Seniority Dates for Employees who are converted from Pending Workers Are Not Calculated Appropriately (Doc ID 2644722.1)

Last updated on MARCH 02, 2020

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.13.19.10.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.19.10.0 version, Global Human Resources

ACTUAL BEHAVIOR
---------------
Incorrect Seniority Date calculation for employees who are converted from Pending Workers.
Rule is not calculating The Seniority Dates set at Person Level for Enterprise, having Cumulative set as No.
Is creating only one row for the Pending Worker Relationship


EXPECTED BEHAVIOR
-----------------------
Customer is expecting to have separate rows and separate seniority dates for 1. Pending worker work Relationship and 2. Employee Work Relationship.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Pending Worker Relationship created as of 1/1/2020
2. Converted to Employee having Hire Date : 02/02/2020
3. Navigate to Manage Seniority Dates -> Only one row is displayed for Pending Worker type and having Seniority Date as 1/1/2020


Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.