You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Clarification Required on Seniority Dates Data Fetching in Oracle HCM BI Report.

in Human Capital Management 1 comment

Summary:

A person having 2 Seniority entries- one for worker type as "Pending worker" and other for "Employee" is existing  for below Seniority codes-
"Legal Employer Seniority Date-Work Relationship Level-Migrate",
"Professional Experience Date" &
"Enterprise Seniority Date - Person Level - Migrate"

For Seniority code- "Legal Employer Seniority Date-Work Relationship Level-Migrate", it is possible to filter only record with Worker type as "Employee" using LEVEL_OBJECT_ID (since it is configured at Work Relationship level and thus the LEVEL_OBJECT_ID stores the periods_of_service_id) but same is not possible for Seniority code- "Professional Experience Date" & "Enterprise Seniority Date - Person Level - Migrate" since both are configured at Person level (the LEVEL_OBJECT_ID stores the person_id).

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!