My Oracle Support Banner

Fusion Global HR: Employees Are Not Fetching by Extract Because of Using Wrong User Entity for Extracting Effective Start Date (Doc ID 2540327.1)

Last updated on AUGUST 13, 2020

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.13.19.01.0 and later
Information in this document applies to any platform.
This note was created for Release 11.13.19.01.0. The note has been reviewed and is current for release11.13.20.07.0.

Symptoms

ACTUAL BEHAVIOR
---------------
The EFFECTIVE_START_DATE of PER_ALL_PEOPLE_F table of some employees is not coming in between the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE of per_person_type_usages_m.


EXPECTED BEHAVIOR
-----------------------
The EFFECTIVE_START_DATE of PER_ALL_PEOPLE_F table should come in between the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE of per_person_type_usages_m.

STEPS
-----------------------
The issue can be reproduced with the following steps:

My Client Groups > Data Exchange > View User Entity Details: PER_EXT_SEC_HISTORY_PERSON_UE.

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.