Data Corruption Is Happening in PER_PERSON_TYPE_USAGES_F Table When User Changing Latest Start Date For Contingent Worker
(Doc ID 2828696.1)
Last updated on DECEMBER 16, 2021
Applies to:
Oracle Human Resources - Version 12.2 HRMS RUP14 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-------------------
Observed that Person type usages "PER_PERSON_TYPE_USAGES_F" table start date is incorrect when changing latest start date for Contingent Worker
EXPECTED BEHAVIOR
-----------------------
Expected that Person type usages "PER_PERSON_TYPE_USAGES_F" table start date is correct when changing latest start date for Contingent Worker record
Steps to Reproduce
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to HRMS Manager Responsibility
2. Navigate to people --> Enter and maintain
3. Create placement with person type Outsourced with latest start date as 01-Mar-2021
4. Now navigate to People form -> Others button -> Person Type Usage -> Update person type to Contingent Worker with effective date 1-Apr-2021.
Query the PER_PERSON_TYPE_USAGES_F table from Data base:
effective start date effective end date person type
---------------- -------------------------- --------------
01-Apr-2021 31-Dec-4712 Contingent Worker
01-Mar-2021 31-Mar-2021 Outsourced
5. Now in People form -> update latest start date to 01-Apr-2021
Query the PER_PERSON_TYPE_USAGES_F table from Data base:
effective start date effective end date person type
-------------------- -------------------- -----------------
01-Apr-2021 31-Dec-4712 Contingent Worker
01-Apr-2021 31-Mar-2021 Outsourced --- This record is having the data corruption.
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 |