OBIEE's Project Dimension's Delete_flg Is Not Getting Set To 'Y' When Projects Are Deleted In EBS
(Doc ID 1477508.1)
Last updated on NOVEMBER 12, 2019
Applies to:Business Intelligence Applications Consumer - Version 220.127.116.11 [AN 1900] and later
Information in this document applies to any platform.
A Project was created in EBS and placed in UNAPPROVED status, brought into the DW by the incremental loads and later deleted in EBS by business users.
Subsequent incremental loads left that project as not deleted (delete_flg='N'), its initial value.
Another project was then later created by EBS users in an Approved status, using the same project_number as the previously deleted one, then brought into the DW by incremental loads, resulting in 2 projects with the same project_number in w_Project_d.
Rare, but possible occurrence.
Also note that all of our projects have a delete_flg='N', none have a 'Y'; There appears to be no functionality that can detect the deletion of a project in EBS.
Revenue transactions followed for the Appproved project, causing DW incremental loads to fail while attempting to insert duplicate rows in fact tables W_GL_REVN_F and w_AP_XACT_F, whom found two (2) matching project dimension entries in their outer joins on Project_Number. Furthermore, it appears as if those workflows are not excluding projects with delete_flg='Y':
Subsequent failing Workflows - outer joins
Attempted duplicates fails in unique indexes
Please let us know if or why or OBIA's Project dimension's delete_flg is not getting set to 'Y' when projects get deleted in EBS?
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