Workforce Profile Does Not Pick Up Changes To Date Of Birth On The Employee Record In All Cases.

(Doc ID 1903096.1)

Last updated on SEPTEMBER 27, 2016

Applies to:

Business Intelligence Applications Consumer - Version 7.9.6.4 and later
Information in this document applies to any platform.

Symptoms

Workforce Profile subject area:
an employee record had the "DATE_OF_BIRTH" field changed, however this was not reflected in the warehouse after running a full ETL.

scenario
--------------
Workforce Profile subject area:
an employee record had the "DATE_OF_BIRTH" field changed, however this was not reflected in the warehouse after running a full ETL.
...
However clearly an employee with a DOB of 13/06/1993 cannot be in the 45-54 years age band!
The DOB is derived from the SDE_ORA_PersistedStage_WorkforceEvent_Assignment* mappings into the Persisted Staging Tables.
...
All records in the PS have the old DOB. Taking the source code from the mplt_BC_ORA_PersistedStage_WorkforceEvent_Assignment, there is a predicate:
...AND asg.effective_start_date BETWEEN peo.effective_start_date AND peo.effective_end_date
This means that any changes on the person record (per_all_people_f) will only be picked up if there is a change on the assignment record (per_all_assignments_f) with a start date between the effectivity dates of the person record.
It is quite plausible (and common) for a change to occur on the person record without a corresponding change on the assignment record, however the workforce profile doesn't deal with this.

Changes

 none

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms