Hyperion Financial Management (HFM) Custom Dimension Mix Up Exists When More Than 9 Custom Dimensions Are Used And Short Names Are Used To Refer Custom Dimensions In Cx Format
(Doc ID 2013202.1)
Last updated on FEBRUARY 03, 2019
Applies to:Hyperion Financial Management - Version 184.108.40.206.500 and later
Information in this document applies to any platform.
When more than 9 custom dimensions are used in a EPMA based HFM application and if short names are used in the Cx format (C1,C2 etc..) then there is a mix up of custom dimensions. The 10th Custom dimension (C10) is not recognized properly. The following behaviors are observed
1. There is a mix up of custom dimensions. For example, when a data grid is set up with Custom 9 and Custom 10 in the columns, if the data grid is extracted in xml format the column definitions shows that column contains "Custom 8" and "Custom 9" which is wrong.
2. With respect to rules, if custom dimensions are referred as C10 then it results in error stating "Invalid Custom Member". For example, consider the rules
HS.Exp "A#anyaccount.C10#[None] = A#anotheraccount.C10#mymember"
The member defined in the rules like ".C10#mymember" results in error loading the rule file "Invalid custom member" though the member definitely exists in the custom10 dimension.
3. With respect to the HFM database tables, it has been observed that a custom dimension mix up exists in the CUSTOM_DESC, CUSTOM_LAYOUT, CUSTOM_ITEM tables in the database.
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