OBIA 11g Incorrect Date in Absence End Date, it Defaults Null End Date To SYSDATE
Last updated on JULY 18, 2017
Applies to:Business Intelligence Applications Consumer - Version 188.8.131.52.1 and later
Information in this document applies to any platform.
On : OBIA 184.108.40.206.1 DataWarehouse,SDE_ORA_AbsenceEventDimension the default null end dates are changed to sysdate.
You have noticed a that a number of absences with end-dates equal to the ETL run date are inconsistent with the source system where they were NULL.
Further investigation has shown that the issue appears to be in the interface as follows:
- "SDE_ORA_AbsenceEventDimension.W_ABSENCE_EVENT_DS_SQ_PER_ABSENCE_ATTENDANCES.TAB" of the "SDE_ORA_AbsenceEventDimension" mapping, where the date_end column is derived by the expression "NVL(PAA.DATE_END,SYSDATE)".
- This gives a completely wrong view of the data because it looks like absences that are still open have ended on the date that the ETL has run.
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