In OBIEE using Essbase dimension display format issue.

Fat Goblin

Hi guys,

We are using Essbase as a data source in our OBIEE reporting.

We have changed  the hierarchy type of Essbase dimension from Unbalanced to Value-Based.

Because of which, for some dimension the hierarchy column value is coming as [Parent Name].[Child Name] for zero level data. But not for all dimension levels.

But when I am using as Unbalanced hierarchy, its coming normally.

Do you know why is this discrepancy?

[Deleted User]

Value-based (aka parent-child) hierarchies are two totally different things in terms of interpretation. So when you use the one or the other it's imperative that you update your RPD to reflect those changes since otherwise things won't work.

Fat Goblin

Thanks Christian Berg,

But I think my post is a little ambiguous, when I say [Parent Name].[Child Name], I meant the [Its parent level].[Bottom level].

So for Example, for Account Dimension, I have 2 sub-levels, Suppose Account A and Account B. And I have changed it to value-based hierarchy.

So when I am using hierarchy column in report, Account A column values are coming up as the original values, but for Account B when I go to the bottom most level, the values are coming as for example, [Account B].[Expense].

Also even when I re-imported the cube in RPD and  created from the scratch, value-based hierarchy column values are still coming as [Level 1].[Level 0].

But When changed it to unbalanced hierarchy Type, it coming as just Level 0.

I just want to the values as their original values

Fat Goblin

Hi Guys,

My question is becoming more and more ambiguous,

I just want to know why values of dimension are showing such way, when changed from Unbalanced to Value-based.

[Deleted User]

Your question isn't becoming more ambiguous it's actually becoming clearer thanks to your explanations and research! Thumbs-up on that!

I find it peculiar that your Account hierarchy is a value-based hierarchy.

Let me name-call @Gianni Ceresa (which is sth we're not supposed to do but is ok in this case) since he's also an Essbase junky.