Errors Running fn_drmdataloader Due to CODE Column In STG_<DIMENSION_B_INTF Table Defined As NOT NULL in Seeded EPM 6.0 Data Models and 5.6 FSDW Data Model (Doc ID 1506919.1)

Last updated on FEBRUARY 14, 2013

Applies to:

Oracle Financial Services Funds Transfer Pricing - Version 6.0 and later
Oracle Financial Services Analytical Applications Infrastructure - Version 7.2 and later
Oracle Financial Services Profitability Management - Version 6.0 and later
Oracle Financial Services Asset Liability Management - Version 6.0 and later
Oracle Financial Services Data Foundation - Version 5.2 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI) - Version 7.x
Oracle Financial Services Analytical Applications (OFSAA) - Version 5.x/6.x
FSDW

Symptoms

On Oracle Financial Services Data Warehouse (FSDW) 5.6, the V__CODE columns are NOT NULL in STG_<DIM>_B_INTF tables in the 5.6 FSDW Data Model.   It is also defined with NOT NULL in the 6.0 Enterprise Performance Management (EPM) OFSAA applications:

Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)

ACTUAL BEHAVIOR
The p13368852_56_Generic Erwin file name :- FSDW_Integrated_Reporting_Staging_Datamodel.erwin contains additional NOT NULL V__CODE columns in the STG__B_INTF tables.  This incorrect data model change causes issue with the dimension member loader for 5.6 and 6.0.  As per dimension loading process, code column of DIM__B is updated from DIM__ATTR by function fn_updateDimensionCode. Refer section "Updating DIM__B _Code column with values from DIM__ATTR table" of Data Model Utilities user guide.  Using a single default value causes additional errors during the DRM Dimension Member loader:

Error.Duplicate code values for column v_prod_code in base table v_prod_code. Use Query to find out duplicates :select distinct v_prod_code from stg_products_b_intf group by v_prod_code having count(1) >1.

EXPECTED BEHAVIOR
These columns should not be NOT NULL and there should be a solution to use the DRM dimension loader.

STEPS
The issue can be reproduced at will with the following steps:
1. Open the FSDW_Integrated_Reporting_Staging_Datamodel.erwin from p13368852_56_Generic.zip
2. Find the V__CODE columns are NOT NULL in STG__B_INTF tables

Cause

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