Last updated on JUNE 19, 2016
Applies to:Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Analytical Applications (OFSAA), after you add custom dimensions to the Erwin Data Model and register the new dimensions using the batch_leaf_registration program, the user defined dimensions are not getting assigned the "Processing Key" property for the LEDGER_STAT table. In REV_COLUMN_PROPERTIES, there are no rows with table_name = 'LEDGER_STAT' and COLUMN_PROPERTY_CD = 15 for the custom dimensions:
select * from rev_column_properties where table_name = 'LEDGER_STAT'
and column_property_cd = 15;
Additionally, the SMSService.logs in $FIC_APP_HOME/common/FICServer/logs do not contain an insert into REV_PROPERTY_COLUMNS for these custom columns. There are only inserts for the standard columns:
[UMMLOG] Jan 22,14 07:43:46 : [DACDATABASEGATEWAY]Adding Query : INSERT INTO REV_COLUMN_PROPERTIES (TABLE_NAME,COLUMN_NAME,OWNER,COLUMN_PROPERTY_CD,PROPERTY_COLUMN,PROTECTED_FLG) VALUES ('LEDGER_STAT','GL_ACCOUNT_ID','ATOMIC',((SELECT COLUMN_PROPERTY_CD FROM REV_COLUMN_PROPERTY_MLS WHERE COLUMN_PROPERTY = 'Processing Key')),'',0)
Checking LEDGER_LEAF_COLUMNS in the Erwin Data Model, the custom dimensions all have the correct setting in the UDP tab with "Processing Key" = YES. Additionally, the correct data exists for the dimensions in OFSA_CATALOG_OF_LEAVES and REV_DIMENSIONS_B. You do not understand why the new dimensions are not getting the Processing Key assignment in REV_COLUMN_PROPERTIES.
Note: Rows are inserted into tables like REV_COLUMN_PROPERTIES during the Object Registration stage of the Model Upload.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms