Considerations for Hierarchy Member Names in Financial Reporting and Allocations
You must publish hierarchies for financial reporting and allocations to Oracle Essbase cubes. When a hierarchy is published to an Essbase cube, a fully qualified member name is generated for each node in the hierarchy.
This fully qualified member name is used to refer to the node in the hierarchy in financial reports and allocation rules.
Each combination of tree plus tree version is published as a different account hierarchy to Essbase cubes.
When a chart of accounts child or parent value is assigned to multiple hierarchy versions, the fully qualified member name includes the hierarchy version name.
Member Names and Financial Reporting and Allocations Hierarchies
You must consider the implications to your financial reports, allocation rules, and Smart View templates if the member name changes due to hierarchy changes. The points to considered are:
-
The member name for a member can change if you originally published a single hierarchy to a cube and later published another hierarchy. The change happens if the member includes the same chart of accounts value.
-
If the fully qualified member name changes, you must update existing financial reports, allocation rules, and Smart View templates that refer to that member. Otherwise, such processes have errors.
For example, only a single hierarchy version, V1, existed when you defined a financial report. The hierarchy version includes the chart of accounts value of 500 for a cost center. The path does not include a hierarchy version name, since there is only one hierarchy version in the cube. The fully qualified name path is 500.
Later, you publish a new hierarchy version, V2. The fully qualified member name changes since there are now two versions and cost center 500 is associated with two hierarchy versions, V1 and V2. When selecting the value 500, the cube has logic to uniquely identify the member. The fully qualified member name for the two hierarchy versions is now:
-
[All VF Cost Centers-V1].[999].[500]
-
[All VF Cost Centers-V2].[999].[500]
Update configurations, such as financial reports, allocation rules, or Smart View queries that referenced the original name path of 500 with the correct name.