OBIEE 11g - Displays Level Members from Wrong Alternative Hierarchy in Addition to the Correct Hierarchy When Working with Essbase Dimensions Having Multiple Hierarchies Enabled (Doc ID 1968363.1)

Last updated on JANUARY 30, 2017

Applies to:

Business Intelligence Suite Enterprise Edition - Version 11.1.1.7.141014 and later
Information in this document applies to any platform.

Symptoms

In the outline of Essbase, there is a dimension D expressed using 2 hierarchies
The alternative one uses shared members to group the cost centres following a different logic
 
The hierarchies are mapped into the Repository (RPD) as separated logical dimensions
 
You are reporting against the Level 4 from the dimension dimHI (mapped to DimH1 in the physical layer of OBIEE Repository) and NOT from the dimension dimH2 (by the way, you cannot reference members from both dimensions, as per out of the box functionality)
So when running the report, the expectation is to see only members of level 4 from the dimH1 hierarchy, and nothing, of course, from dimH2.
Instead, what is displayed is also the level 4 under dimH2


The Issue is explained further using an example.

Essbase Dimension D ( multiple hierarchies enabled )
First hierarchy is
H1root
---H1Lev1
------H1Lev2
---------H1Lev3
------------H1Lev4

Second hierarchy is
H2root
---H2Lev1
------H2Lev2
---------H2Lev3
------------H2Lev4

Importing this hierarchy into the RPD creates 2 separated logical dimensions, dimH1 and dimH2 that should work independently.

Now creating a report using dimH1
and for example H1Lev3

All is ok, only members of H1Lev3 do show

But as soon as adding a measure to the report, then also H2Lev3 gets listed in the report - which is wrong

Cause

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