Alias Value Incorrectly Inserted into Code Columns for Version / Scenario After Metadata Synch
Last updated on OCTOBER 21, 2016
Applies to:Oracle Financial Services Balance Sheet Planning - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Balance Sheet Planning (BSP) 8.02.0.x, when you edit a member of the Scenario or Version dimensions and give it an Alias value, the subsequent Metadata Synchronization process updates columns in FSI_SCENARIO_MLS and FSI_VERSION_MLS with the Alias value. The <dimension>_DISPLAY_CD and <dimension>_DESCRIPTION columns are incorrectly updated with the alias.
For example, you update a Version dimension member to have an Alias of "Working 01 Test".
After the Metadata Sync, FSI_VERSION_MLS contains the following:
VERSION_DISPLAY_CD: Working 01 Test
VERSION_DESCRIPTION: Working 01 Test
You expect these columns to be populated with the Name displayed in the Dimension screen (ex. First Pass) and not the Alias.
This can create a problem when running a Calculate. The process will not be able to join to members in the FSI_SCENARIO_MLS and FSI_VERSION_MLS correctly and the Calculate will find no data to process.
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