Assignment Effective Dates Corrupted When Changing Hire Date On Employee With 3 Or More Periods Of Service
(Doc ID 2952757.1)
Last updated on JANUARY 25, 2024
Applies to:
Oracle Human Resources - Version 12.2 HRMS RUP16 and laterInformation in this document applies to any platform.
Symptoms
Problem Statement:
Assignment Data corruption occurs (in per_all_assignments_f table) when a person is on their third(or more) period of service and the hire date is changed on the third period of service.
The system takes the final process date from the first period of service and it updates every assignment record on the second period of service with final process date (from first period of service).
Expecting effective_end_date for the assignment should not change (with same effective_end as final process date) after rehire and changing hire date.
Steps to Reproduce:
The issue can be reproduced at will with the following steps:
- Responsibility: US Super HRMS Manger
- Navigate: People > Enter and Maintain > Query the ex-employee with 3 or more period of service
- Re-hire the person.
- Change the Hire Date on the third period of service, Save
- Assignment Data corruption occurs in per_all_assignments_f table. If there are 20 date tracked records on the second period of service, All 20 records will have the same effective_end_Date. (with first process date of 1st period of service date)
Changes
Applied 12.2 HR RUP16 -> <Patch: R12.HR_PF.C.delta.16> 33527653
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 |
Changes |
Cause |
Solution |
References |