Multiple hierarchies in same dimension

[Ammus1234]

Hello All,

I get this error when I try to create a report in report studio using SSAS cube. Cognos version is 10.2.1 FP1.

XQE-PLN-0022 Values cannot be computed correctly in the presence of multiple hierarchies ([Product].[Group], [Product].[Product]) due to their relationship with the attribute 'Group'.

The problem happens when I give the hierarchies from the same dimension in the report and slicer.
Is there a solution? I can't differentiate the hierarchies into multiple dimensions as this doesn't make any sense.

I tried this but it is not working. I get the same error.  :(
http://www-01.ibm.com/support/docview.wss?uid=swg21611427

[Ammus1234]

It is strange that nobody has faced this issue before. It must be a very common requirement to use the same item in report and filters.

[blom0344]

Multiple hierarchies within a dimension reflect different ALTERNATIVE paths to choose from.  Why does it make sense to select from BOTH hierarchies within 1 analysis?

[Ammus1234]

Thanks blom for the reply.
I do not have alternate hierarchies. I have only a single hierarchy under the dimension. But each level of the hierarchy is displayed again as a hierarchy. I'm not sure if SSAS displays in this way or it is a design problem.

In the list report I added the lowest level(product) and in the slicer I added the product group(level above product). When I run the report I get this error.

I will try with the sample adventure works cube and try to  build a sample report to replicate this issue.

Do you think this can happen due to overlapping sets?

[blom0344]

1. Each product has one parent in the productgroup level?
2. All keys are unique within the hierarchy?

Did you try to check the SSAS design within BIDS?  SSAS is a powerful product, but it has its quirks (for as far as I know, I'm no microsoft expert   ;) )

[br54016]

Did you ever get this issue resolved, I am running into the same issue.  Each level is displayed as a separate hierarchy.  I can't drilldown from level to level.

Thanks,
Brad

[Ammus1234]

Try to use the levels from same hierarchy instead of using attribute hierarchies.

[Ahuevonao]

So I just registered because I wanted to say that I found a solution that works fine to prevent this error. We had this error for a long time.
I am a Microsoft gyuy so my knowledge of Cognos is very limited.

The solution in brief of how to build SSAS-cubes so that this error ("XQE-PLN-0022) does not occur in Cognos:
You may use attribute hierarchies but never use them on the same Attribute that you are using as a level in a hierarchy in the dimension.
To be able to have the same level as a hierarchy just drag it in again from the Data Source View and give it another name (and it gets another ID which probably is what solves it)
So by doing this (to all attributes that has hierarchies enabled and are used as a level in a hierarchy within the same dimension) you still can have the underlying dsv column as an attribute hierarchy and as a level in a hierarchy in the same dimension.

If the problem still occurs when using hierarchies (not attrubute hierarchies) from the same dimension then you have to act similair and copy each level from the datasource to the attributes with a new name and then add it to each hierarchy. As a hierarchy level there is no problem to change the level name to the same name as the attribute hierarchy if you prefer that. That means that every level of any hierarchy should be based on attributes with different ids after this.

After having done that to all hierarchies in the dimension we never saw this error again after.

Hope this helps anyone running into this error.
If you have further questions then feel free to send me a message and I will explain further.

BR
Christian

[Ammus1234]

Hi Ahuevonao,

Thank you so much for your solution. I will try this and let you know if this solves our issue.