OBIA 11g: Incorrect Mapping In ODI Interface SDE_ORA_GLAccountDimension.W_GL_ACCOUNT_DS_SQ_BCI_GL_ACCOUNTS (Doc ID 1960487.1)

Last updated on JANUARY 30, 2017

Applies to:

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

Goal

Incorrect Mapping In ODI Interface SDE_ORA_GLAccountDimension.W_GL_ACCOUNT_DS_SQ_BCI_GL_ACCOUNTS

Filter condition does not have variable name start with # sign


RUN_FULL_INCREMENTAL("IS_INCREMENTAL",1=1,GL_CODE_COMBINATIONS.LAST_UPDATE_DATE > TO_DATE_VAR('#LAST_EXTRACT_DATE') or NATURAL_ACCOUNT.LAST_UPDATE_DATE > TO_DATE_VAR('#LAST_EXTRACT_DATE') or BALANCING_SEGMENT.LAST_UPDATE_DATE > TO_DATE_VAR('#LAST_EXTRACT_DATE') or COST_CENTER.LAST_UPDATE_DATE > TO_DATE_VAR('#LAST_EXTRACT_DATE'))

This condition may always fail and it will always run for full load only.

Even generated scenario has code without #. I checked in SNP_SCEN_TASK table using following query.

select TASK_NAME2,TASK_NAME3,COL_TXT,DEF_TXT from SNP_SCEN_TASK where SCEN_NO=6350131
and TASK_NAME3='Load data';

 

Solution

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