HR Analytics Change capture logic

Question

Hi All
My customer currently has a custom built warehouse and is using obiee as the reporting tool.
I am busy implementing 7.9.6.2 apps for them from their EBS 12.1.1 instance.
They have a burning issue which is that in their source system, the users do not always capture the fields required for their compliance reports, so their headcounts are not correct, then the users correct the data and the BI headcounts historically are not correct.
I have suggested that this problem must be dealt with in the source system, but they want to find out if the pre built apps will offer any relief.
The question is how does the BAW change capture work surrounding this scenario?
I have said that from what I have experienced the change capture works with the refresh dates in the DAC and that any changes will be picked up by the last updated date and an update will be effected to change the data.
This is unless there is SCD type logic built in where the snapshots will reflect the history as it was and perhaps only the aggregates will be effected.
I have been checking the employee headcount in the rpd and following the process back to the SDE_ORA_PersistedStage_WorkforceEvent_HeadCount_Full where the data is extracted from the source and there is a lot of headcount logic built in but I cannot work out for sure how the net changes will be handled.
Is there anyone who has had experience with HR Head count snapshots and aggregations being affected by back dated source system changes?
Regards
Nick

Answer 1

Hi Tarik
Thanks for the info, I have generated the flex field and configured the csv's, I am stuck at this stage with the similar issue to the 'Error in SDE_ORA_AbsenceEvent_Full workflow' post in this forum and have an sr logged on metalink so I cannot actually test the behaviour.
The customer wants to know what will the result be if they backdate a change specifically around headcount and compliance fields in the source system when the pre built hr etl's run. They want to know if it will update the warehouse and how will the snapshot tables be effected.
I followed from source to target on headcount as a metric;
on a high level this is what I understand about the process:(corrections welcome)
SDE_ORA_PersistedStage_WorkforceEvent_HeadCount_Full loads W_ORA_WEVT_HDC_PS (stores a history of headcount)
Then SDE_ORA_WorkforceEventFact_Hdcnt loads W_WRKFC_EVT_FS
then
SIL_WorkforceEventFact loads W_WRKFC_EVT_F with the update strategy in Upd W Wrkfc evt f ins upd identifies from comparing the etl proc wid & data source num whether there will be an insert update or delete.
If there is a change it inserts a new record and marks the old one as delete with the soft delete logic.
The the rpd looks at alias's of w_wrkfc_evt_f with joins to ago keys for history and to current for up to date records.
So assuming the changes do not fall out side of the dac's prune days, and the 'back dated' change is picked up in the etl by the OLTP ' last updated time stamp' being later then the etl refresh date, will the behaviour be that the records are updated but the snapshots remain unchanged and therefore reflect the incorrect data?
For example. A person joins the organization in Jan, but there current system report does not reflect him because the record does not have the mandatory fields correctly filled out and he falls into an exeception report. In Feb the data is not corrected but in March the HR team correct the data and back date the change in their system to January.
How will this affect the headcount in the BAW? How would the BAW handle this scenario? Is the question from the client ( assuming the ootb values are correct and in use.)
I have said I think the dac will pick up the last upd, load the tables above and update the total so it is showing correctly, looking back at the snapshot should refelct the correct data because the BAW will have picked up the join 'Event' off PER_ALL_ASSIGNMENTS_F unlike their bespoke system which uses per all people f.
If there are any HR gurus out there who can confirm my expectations or offer any comments I would appreciate it.
Many thanks
Nick