Question on DataStage J_Dim_PS_D_PERSON vs J_Dim_PS_D_PERSON_CRM
(Doc ID 1528376.1)
Last updated on DECEMBER 16, 2019
Applies to:
PeopleSoft Enterprise EPM Campus Solutions Warehouse - Version 9 and laterInformation in this document applies to any platform.
Goal
Running the D_PERSON dimension is yielding duplicate rows in Fact tables(one in particular i discovered was F_CLASS_ENRLMT).for CS and HCM both read from the same OWS table and they DO NOT filter on "CS" specifically or HCM etc... they both read 2 + 2 rows into the hashfile with different SIDs that are ending up in duplicates in the dimension. Hence, duplicates in the hashfiles and then duplicates into the fact tables.
Is this a bug?
Is it ok to replace the J_Dim_PS_D_PERSON job in the HCM MSEQ
with the J_Dim_PS_D_PERSON_CRM job then, just so we get the D_PERSON table
updated daily?
Solution
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
| Goal |
| Solution |
| References |