Dimension with multiple leafs

Hello,
We want to set up the following hierarchy:
--- OXN
....|--- POT
....|....\--- RST
....|
....\--- OIN
.........\--- PJT
..............\--- RST
So this means OXN has 2 child levels (POT&OIN)
and RST has 2 parent levels (PJT&POT)
Now when we make this we get the following warning in the consistency checker:
Warning: [38073] Dimension "<dimension_name> has multiple leaf levels which are not identical
Does anybody know how we can solve this?
Thanx in advance,
Remc0

I'd really like to know what causes this error to occur in the first place.
For me I sat down to construct a time dimension.
Single source table. Single drill path...
Added year... Fine.
Added Month... Fine
Added Week... Fine.
Added Day... Failed???
Exactly the same process for Day as for week, month and year but for day I get the error.
If I knew what criteria was being used to identify the error then i could figure out how to get around it but at the moment it almost looks like a bug( in this circumstance).

Similar Messages

Getting Error - Dimension has multiple leaf levels which are not identical

Hi All,
While creating two hierarchies with in same dimension , i am getting error like - Dimension has multiple leaf levels which are not identical.
Does this error mean , the number of levels in both hierarchies should be same or it has some thing else meaning.
I was creating hierarchies like below -
LE details
- LRU Details
- LRU's Registration Details
- LE's Registration Details
How should i create the hierarchy?
Thanks ,Ashish

Hi... Ashish
Look at this... http://oraclebizint.wordpress.com/2007/11/30/oracle-bi-ee-101332-one-dimension-multiple-hierarchies/
Thanks & Regards
Kishore Guggilla

[38073] dimension has multiple leaf levels which are not identical

Hi,
I am trying to implement a time dimension with 2 source tables.
The time dimension is from minute to year where logical table includes 2 source tables :
Source table#1 : Year,month,week,day
Source table#2: hour,minute (minute is a leaf level and chronological key)
When i try to check-in i got the following error: [38073] dimension has multiple leaf levels with are not identical.
Thank you.
Michael

Hi RM
i am able to create multiple hirerachy in time dimension and assigned time_id as chronological key which is at the dimension detail level and acting as shared child level for both of them......
I have created AGO function for calendar year as
AGO(Test."Fact".amount_sold, Test."Time Dim"."Calendar Year", 1)
but when i have used AGO column in answers i am getting below mentioned error:-
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22046] To use AGO function, the query level ('Calendar Year, Fiscal Year') must be a static level. (HY000)
any suggestion would be appreciated to solve this.
thanks & regards

SSM7.5 - Dimension with Multiple Hierarchies

Hi all,
I'm facing here one problem in the SSM front-end when I'm trying to use one the possibilities that PAS database offers, in this case the use of a dimension with multiple hierarchies.
As you can see in this image, the dimension is created in PAS and works without problems in the dataview.
Hierarchy one:
[http://img121.imageshack.us/img121/334/pas1y.jpg]
Hierarchy two:
[http://img831.imageshack.us/img831/2586/pas2.jpg]
In the SSM front-end, when I try to use that dimension, by default appears the first hierarchy:
[http://img826.imageshack.us/img826/4043/hier3.jpg]
In the dimensional selector the dimension appears fine for the first hierarchy:
[http://img30.imageshack.us/img30/3103/hier1.jpg]
But when I select the second hierarchy...
[http://img34.imageshack.us/img34/1722/hier2.jpg]
The Internet Explorer crashes and close all the open windows. This happens in the scorecard and also in the reports.
Is not possible to use dimensions with multiple hierarchies in SSM? Did anyone had this problem before?
Thanks in advance
Pedro
Edited by: Pedro S. Costa on Sep 13, 2010 11:03 AM

Hi Shashi,
first of all, thanks for your answer.
But I don't understand when you say that "we cannot have two hierarchies on the same dimensions"?!?!?
I already have some years of experience with PAS database and it's not the first time I create a dimension with more than one hierarchy. I use also that in a productive system (before this SSM front-end) without problems. And in this latest version of PAS (version 7.5.6) it's still possible to use that feature. As you can see in my initial post, I put two screen shots of the dimension with two hierarchies in PAS dataview, and works fine, without problems in the drill-down/up.
From PAS online help:
HIERARCHY is a Dimension command that defines the members and levels that comprise a particular hierarchy level within a dimension. It also allows multiple consolidation structures that stem from a central root of inputs. Use hierarchies when the input members are consolidated into more than one output member. When a dimension has hierarchies, members can have more than one path for rolling up into output levels. If a dimension has only one hierarchy, no HIERARCHY statement is necessary.
Based on this, I create my example of a dimension (named MULTI) with two hierarchies (REGION and TYPE). Maybe the name I use for the second hierarchy create some confusion to you, because of the TYPE dimension that can exist in SSM. I just hope the problem I'm having in the SSM front-end is not related with the name I used for the second hierarchy!!!!
I will rename that and test again.
Regards
Pedro

Dimension Design - Single Dimension with Multiple Hierarchies

Morning,
the purpose of this discussion is to understand how we should design a specific dimension with 3 levels and multiple hierarchies for optimal performance.
We have an institution dimension with the following characteristics:
Characteristics
Dimension: Institution
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
Hierarchies:
1. Some of the hierarchies have 3 levels and others have only 2 levels (Skip Level)
2. ALL the hierarchies have a TB level and an Institution level
3. None of the hierarchies have the same leafs
4. Some of the hierarchies leafs can overlap
Design:
We are considering two approaches for the institution dimension levels:
a)
Levels:
Hierarchy 1 TB Level
Hierarchy 1 PG Level
Hierarchy 1 Inst Level
Hierarchy 2 TB Level
Hierarchy 2 Inst Level
Hierarchy 3 TB Level
Hierarchy 3 Inst Level
Note:
This approach is working and the resulting dimension and cubes are used by OBIEE, but some of the OBIEE analysis takes a long time (more than a minute) to return the results.
At this point, we are not sure whether this approach will result in an optimal design from a performance perspective and are looking at restructuring the dimension to represent only the three conceptual levels as indicated below.
b)
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
The rest of the dimension i.e. hierarchies, attributes and mappings are defined in the same way.
The cube associated with this dimension have approximately 80 million records.
Please advise on any best practices or design considerations that we need to take into account.
Thanks

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

Dimensions with multiple joins

Hi,
Discoverer Desktop 9.0.2
Discoverer Administrator 9.0.2
OWB 9.2
I have imported the dimensions and facts from OWB EEX file.
While I trying to create a report based on the dimensions, I found the problem in Dimensions used multiple times against the fact table.
For example,
I use the Time Dimension (TIME_DIM) for assigned date, open Date and Close dt. My fact table will have the foreign keys for these 3 columns.
TIME_DIM
DAY_ID
DAY_DAY
DAY_MONTH
DAY_YEAR
data
DAY_ID DAY_DAY DAY_MONTH DAY_YEAR
1 01-JAN-04 JANUARY 2004
2 01-FEB-04 FEBRUARY 2004
3 01-MAR-04 MARCH 2004
FACT_TABLE
DAY_ID
DAY_ID2
DAY_ID3
Data
DAY_ID DAY_ID2 DAY_ID3
1 2 3
1 1 2
While I am creating the report, in 'work book wizard: step 2' shows the TIME_DIM only one time, also it allows to select only one time with any one of these keys. Whereas I need to select the time dimension for each of the time keys in fact table.
Is their any work around to get these values in my reports?
I mean
My report will look like,
ASSIGNED DT OPEN DT CLOSE DT
01-JAN-04 01-FEB-04 01-MAR-04
01-JAN-04 01-JAN-04 01-FEB-04
I tried with creating hierarchies, modifying the SQL to add these keys manually and then import SQL, doesnt work at all.
Please help me !!
Thanks,
Shree

You have to load the table up several times into the EUL and create links to the different column in your fact table.

Hierarchical Dimension with a leaf node w/o any parent

Hi
We have a Product Dimension with five levels L0, L1, L2, L3 and L4 (L0-lowestlevel, L4-HighestLevel).
With one Hierarchy STANDARD as
L4, NULL (Parent)
L3, L4 (L4 is the parent of L3)
L2, L3
L1, L2
L0, L1 (L1 is the parent of L0)
The product dimension table has a record with values only for L0 and NULL values for other Levels..
(ie) We have a requirement to create a value in L0 which will have no parents.. The rest of the values in L0 will have parents.
Would like to know if this is possible in AW. This was possible in Express Server
regards
uma

HI
yes we have run into a big problem. We have created leaf nodes w/o parent in aw and created relational views of those. The measure views thus created has data for these dimension values but when accessed thru BI Beans (ie in the cross-tab if we have this measure) the data is not getting displayed for these dimension values (Which do not have parent)
Any immediate response will be of greate help to us.

OBIEE Parent-Child Dimension with multiple hierarchies

Is it possible to have in a parent-child dimension multiple hierarchies? I want to have the same botom childs to aggregate to different parrents. example.
Account Dimension
HR1-total
HR1-parrent1
CHILD1
HR1-parrent2
CHILD2
HR2-total
HR2-parrent1
CHILD1
CHILD2
Thanks in advance.

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

Custom Dimension with multiple children defined as "Never Share"

Hyperion Planning - 11.1.1.3
There is Custom dimension "Appliance" with root defined as a "Never Share". It has multiple level 0 (SubAppl1, SubAppl2, SubAppl3 etc) members with "Store". Data is some times loaded at root level and some times at the lower levels and at times both. What is the expected result?
When POV is Appliance and when it is drilled down?
For Ex:
For Jan -
Appliance is 100, No other members loaded with data.
For Feb -
Appliance is 30
SubAppl1 is 10
SubAppl2 is 10
SubAppl3 is 5
POV
Appliance Jan - 100
Appliance Feb - 30 or 25? and why?
Trying to understand the behavior or "Never share" in this scenario.
Appreciate your feedback.
Edited by: 847514 on Mar 28, 2011 11:17 AM

Never Share has no bearing on your sample. The Never Share flag is to prevent a implicit sharing which will happen when you have one parent with a single child under it. Your structure is not setup such that an implicit share would occur based on your example.
I really do not recommend loading data at upper level members as this means you can never run a normal aggregation on your data. If you were to aggregate your data and you happened to have the AGGMISSG set to true you would see the data in your january example of 100 was removed due to the level 0 members not having any values.
So the question of your February being 30 or 25 is did you load 30 to February Appliance or did you load to the level 0 and then aggregate?
Regards,
John A. Booth
http://www.metavero.com

Formulas in account dimension with multiple hierarchies

Hello all,
I am having troubles with finding the exact syntax for a formula in an account dimension that has two hierarchies:
- I have two parent accounts in H1 (accountA and accountB)
- I have one account in H2 that has to add up accountA and accountB
It was easy in V4, the formula would just say: accountA+accountB
Does anyone have the exact syntax for me in V5?
Some extra info:
- SAP BPC version: 5.1sp2
- SQL 2005
- I know that dimension formulas have a problem with performance, but believe me, in this case this, it is the only way
Hope someone can help me,
Alwin

Alwin,
There should be formulas in the MDXlib.lgl that look like the following examples:
*Function Hir1_P(%Arg%)
     iif(AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, rollupchildren(AccountL.H1.currentMember,"+"))
*endfunction
*Function Hir2_P(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, rollupchildren(AccountL.H2.currentMember,"+"))
*endfunction
*Function Hir3_P(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2],%Arg%, rollupchildren(AccountL.H3.currentMember,"+"))
*endfunction
*Function Hir1(%Arg%)
     iif(AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%,Null)
*endfunction
*Function Hir2(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, Null)
*endfunction
*Function Hir3(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2],%Arg%, Null)
*endfunction
These are functions that may be used to aggregate the values in version 5 across hierarchies. I don't think you need them all, but I included the set I have in a current application.
I hope this helps.
Petar

Dimension with 2 roles and 2 hierarchies used in 2 cubes

Hi,
I have a dimension in which there are two dimension roles (roleA, roleB) defined as well as two hierarchies (hierarchyA, hierarchyB). Currently hierarchyA is set as default. (Not because that is in fact the default one, only because OWB forces one to choose a default)
I need to define two cubes (cubeA, cubeB). CubeA will use the dimension with roleA and cubeB will use the dimension with roleB.
Is it possible to tell cubeA to use/see/make available only hierarchyA and cubeB only hierarchyB? HierarchyA makes no sense in cubeB so I want to "specify" hierarchyB for cubeB.
Thanks,
Juanita

A different issue but possibly related:
I have a ROLAP cube with one of the dimensions containing multiple hierarchies. If I deploy this with deployment option set to "Deploy data only", it works 100%. As soon as I change the deployment option to "Deploy All", I get a VLD-0398 error.
I need to choose "Deploy all" since the cube metadata must be deployed to the OLAP catalog in order for Disco OLAP and BI Spreadsheet Add-In to see the cube.
First question:
Is it possible to deploy to the OLAP catalog if the cube has a dimension with multiple hierarchies?
Second question:
If it is not possible, what is the workaround?
Thanks,
Juanita

Dimension usage multiple columns

In the Data source view, it is possible to create a relationship between a fact and dimension with multiple columns. How is this handled in the dimension usage pane? Can I create a dimensions that relates to a fact on multiple columns?
John Schroeder

Yes it is possible to have multi column relationships in SSAS multidimensional.
If you create the relationship in the DSV then when you create the cube the dimensions usage will pick up the columns in the relationship. If the cube already exists - when you add a dimension that has multiple columns in it's key attribute you can pick
which two columns in the fact should be used to link to the dimension.
http://darren.gosbell.com - please mark correct answers

How to tune performance of a cube with multiple date dimension?

Hi,
I have a cube where I have a measure. Now for a turn time report I am taking the date difference of two dates and taking the average, max and min of the date difference. The graph is taking long time to load. I am using Telerik report controls.
Is there any way to tune up the cube performance with multiple date dimension to it? What are the key rules and beset practices for a cube to perform well?
Thanks,
Amit

Hi amit2015,
According to your description, you want to improve the performance of a SSAS cube with multiple date dimension. Right?
In Analysis Services, there are many tips to improve the performance of a cube. In this scenario, I suggest you only keep one dimension, and only include the column which are required for your calculation. Please refer to "dimension design" in
the link below:
http://www.mssqltips.com/sqlservertip/2567/ssas--best-practices-and-performance-optimization--part-3-of-4/
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Report with multiple dimensions in Row and Column with EvEXP

Hi
We are currently running BPC 7.0 SP3 and try to create the report(or schedule) with more 2 x 2 dimensions in the row and column.
e.g.
row dimension : Outer row is Entity, Inner row is Account
column dimension : Outer column is Time, Inner row is Category
We created the report with 2 x 2 dimensions like above e.g. with EvEXP and EvNXP, NOT EvDRE
based on default dynamic template:Template13.xlt(Nested Row, 2 x 1 dimensions defined by EvEXP and EvNXP formula).
However, when expanding the dimension with double click these dimensions or change CV of the report with 2 x 2 dimensions defined by EvEXP and EvNXP formula,
error occurs on EvEXP and EvNXP formula and can't retrieve the result correctly.
[Question]
Can't we create the report with more 2 x 2 dimensions in the row and column using EvEXP and EvNXP function ?
We understand that we can make the report with more 2 x 2 dimensions in the row and column if using EvDRE.
Thank You in advance
Kenya

Thank you for your advice.
I understand that we should use EvDRE when creating the report with multiple dimension in the row/column　because EvEXP have some erros, poor performance, etc.
Then, we have two questions.
1)
>plus they had some errors in the designs.
what kind of errors they have as an example?
2)
>If you must build the EVEXP and EVNXP, I would suggest building the template from scratch
We built the simple template with just 2 x 2 dimension from scratch.
But this report doesn't work well when double-click the dimension or changing CV...
Would you please check the following template?
<https://sapmats-de.sap-ag.de/download/download.cgi?id=RCZE1ME4YSORY3DCDO4NNMANZLBL1L5ZBUOB2F71YVNVS8XDJW>
It would be greatly appreciated if you could give me your advice for the template.
Thank you again
And my best regards,
Kenya

OWB10gR2 - Cube with relations to a dimension with more than one hierarchy

Hi,
I have defined a time dimension with two hierarchies. The standard hierarchy with the levels year-> month-> day,
and a week hierarchy with the levels year-> week-> day.
When I define the cube i choose dim_time on the dimension tab of the cube and select the level day for that dimension since this is the lowest level of both hierarchies.
When I validate the cube I get the following error Message: VLD-0398: In the Cube test_cube, the dimension DIM_TIME has 2 hierarchies but Cube does not have reference to all lowest levels of these hierarchies.
Validation details: The Cube should refer to a leaf levels of all multiple hierarchies of the Dimension.
Do I have to add the dimension to the cube several times? or is it maybe another way to fix this? To me it seems a bit messy to add a dimension for each hierarchy.
And just as a comment, Yes i know OWB now has a time dimension wizard but I have chosen not to use this at the moment.. ;)
Regards Ragnar

Hi, i assume this logic is for Dimension formula?
If you have multiple hierarchy like ParentH1 and ParentH2 you should use FormulaH1 and FormulaH2 and not FORMULA column.
in FORMULAH1
[Account.H1].[Account_A] / [Account.H1].[Account_B]

Dimension with multiple leafs

Similar Messages

Maybe you are looking for