BSP Calculation Business Rule Pass the Wrong Member Name
(Doc ID 2593486.1)
Last updated on OCTOBER 07, 2020
Applies to:Oracle Financial Services Balance Sheet Planning - Version 8.0.5 to 8.0.5 [Release 8]
Information in this document applies to any platform.
Oracle Financial Services Enterprise Performance Management (EPM)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Balance Sheet Planning (BSP)
In BSP 8.0.5, BSP Calculation business rule appears to pass the wrong member name.
While running cash flows for a product and receiving error messages in the Config_FileCall.log that appear to show that the business rule is passing or somehow using the ORG_UNIT_CODE from the DIM_ORG_UNIT_B table instead of the member in the Planning and Essbase hierarchies. For example, the error says there is a unknown member 9999-9999999 being passed to a fix statement, when the member on the form is 9999-9999999_ORGN, which is the member name that is created after the metadata sync adds the dimension specific suffix to the ORG_UNIT_CODE.
2019-04-13 18:47:12,284 INFO com.oracle.bsp.configuration.ClsConfigurationFactory :: ERROR: Cannot calculate file. Essbase Error(1200497): Error parsing formula for [FIX STATEMENT] (line 2): unknown member name ["9999-9999999"] in function [@RELATIVE]
Steps to reproduce
1. Running cash flows
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document