BW Universe with multiple hierarchies issue

Hi,
We created an OLAP universe off a BW BEx query that has 2 hierarchies enabled. Hierarchy 1 is 12 levels deep while Hierarchy 2 is only 5 levels. Level 00 was also generated for better hierarchy reporting. In Web Intelligence reporting, Hierarchy 1 is required to report starting on Level 4 and then drill as needed so L00, L01, L02, L03, L04 was included in the report. Hierarchy 2 is for grouping and only L00, L01 was included in the report along with key figures. This Web Intelligence result set works fine [Hierarchy 1: L00, L01, L02, L03, L04] , [Hierarchy 2: L00, L01] , measures/key figures.
If additional levels of Hierarchy 1 is added, at L06 and beyond, the query suddenly returns message "No Data to Fetch". In BEx, it was confirmed the query does run with the exact same drilldowns as Web Intelligence and it works in BEx. If Hierarchy 2 is removed from Web Intelligence, the report also can successfully fetch up to the lower levels up to L09. If other flat objects are added, the Web Intelligence report still works fine, it seems to get "No Data to Fetch" when Hierarchy 2 is added. Any information would be appreciated, thank you.
Issue: Web Intelligence report with two BW hierarchies gets "No Data to fetch" if Hierarchy 1 goes lower than L06.
Observations:
1) There are some empty nodes starting in Hierarchy 1 L06, but the Hierarchy 1 works fine by itself
2) The BEx and Universe has a hierarchy node variable prompt. We filtered at lower hierarchy nodes, levels where there is data, but it still does not work with Hierarchy 2
Environment:
- BOE XI 3.1 SP2
- SAP BI 7
- BEx query (2 hierarchies), OLAP universe, Web Intelligence

Please refer to: the below document page# 43. Hope this helps!
http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_sap_olap_universes_en.pdf

Similar Messages

Using HLEVEL Property with Multiple Hierarchies

Hello,
I am trying to use the HLEVEL property on a dimension to indent the rows different amounts. Easy stuff, except I'm doing a row expansion on hierarchy 3 (H3). Using EVPRO(AppName, MemberID, "HLEVEL") always returns the HLEVEL from H1. If you select the same member ID in the member selector under different hierarchies and click the Properties button you can see a different value for HLEVEL, but I can't figure out how to get that in a report using EVPRO.
Is there a way to tell EVPRO specifically which hierarchy to use when returning the value for HLEVEL?
Thanks!
Paul Petersen
Akili

Mike,
please check the answer in this other post:
EVPRO with multiple hierarchies
It's for the MS platform, but it's the same for Netweaver.
EVPRO can only retrieve the HLEVEL for the first hierarchy. You need to maintain further custom properties if you want to get the level of a member within multiple hierarchies.
Regards,
Simmaco

Using HLEVEL with multiple hierarchies

Hi all,
Is there a way to pass a parameter to the HLEVEL keyword to specifiy which hierarchy (Parent H1,H2, H3, etc.) to use when pulling the HLEVEL?
We would like to use HLEVEL for report formatting however we need the ability to choose the hiearchy.
Thanks!
Mike

Mike,
please check the answer in this other post:
EVPRO with multiple hierarchies
It's for the MS platform, but it's the same for Netweaver.
EVPRO can only retrieve the HLEVEL for the first hierarchy. You need to maintain further custom properties if you want to get the level of a member within multiple hierarchies.
Regards,
Simmaco

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

ASO Time balancing with multiple hierarchies

Hello,
I have an Essbase 9.3 ASO cube with multiple hierarchies in the period dimension (set as type = Time), and I'm trying to set one of my Measures to Time Balance Last with SkipMissing.
When I validate the outline, I get:
"This prototype must have all its shared members as siblings of previous sibling."
on all the leaf level members in my period dimension.
any ideas?

We are on Essbase 9.3.0.1 and also tried to use ASO Time balance functions in conjunction with multiple hierarchies enabled.
I recommend you not to use the ASO time balance functions. We did and had to revert everything after complaints from our user base.
If you still use it, please test cases where you retrieve TB Last as well as flow values together with ytd and periodic values.

Drill with multiple Hierarchies

Hi,
I have defined multiple hierarchies in an OLAP universe (like state>region>customer>product or state>region>customer segmentation>Product or state>region>product ...) in order to use the drill functionnality in webi.
In our scenario, each webi report should use only one hierarchy and we don't want the user to have the choice between the different hierarchies when he drills down. So is there a way to define in a webi report what hierarchy should be used?
Thanks,
Gabriel

hi,
As 'State' object is the starting point for both the Hierarchies,
Please duplicate the state object and place it in other class. (as two objects with same name shouldn't exist in same class)
Now edit the second hierarchy such that new State Object will be the starting point.
Also , please ensure that 2nd WEBI report uses new State Object in Query Pane.
This will prevent 1st hierarchy in 2nd webi report.
I tried this out and it's working.
Regards,
Vamsee

Bug in Aggregate Persistence Wizard with multiple hierarchies

Hi,
Let's say you have a dimension with 2 hierarchies. In example:
product -> subcategory -> category -> all products
product -> subtype -> type -> all products
Then you run the "Aggregate Persistence Wizard" and generate the code for 2 aggregations, one for each hierarchy.
Then you execute the generated code wiithout errors.
But no aggregate fact table is created, not inside the rpd, neither in the database.
You only found the aggregated dimension tables (both in rpd and database), which btw generate consistency check errors due to the missing fact table.
Workaround:
The code generated by the Persistence Wizard contains a single "create aggregates" statement.
Multiple aggregation are separated by commas inside the same statement.
Instead create multiple "create aggregates" commands, one for each aggregation, each separated by a semicolon.
OBIEE 11.1.1.5
Hope it helps,
Corrado

Cosimo,
If you've built your business model correctly with the complex joins and the dimensions relating to your fact, then the wizard will pick them up normally and will allow you to generate a script like this:
prepare aggregates
"ag_Fact_Budget"
for "Core"."Fact - Budget"("Budget Amount")
at levels ("Core"."Conformed Date"."Fiscal Year")
using connection pool "Siebel Data Warehouse"."Data Warehouse Connection Pool"
in "Siebel Data Warehouse"."Catalog";
Check that your BM is consistent and sound (stars in physical and BM layer built right).
Documentation-wise, refer to the Oracle Business Intelligence Server Administration Guide Version 10.1.3.2, page 189 f. or the Server Architect course, module 9 "Using Aggregates".

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

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

Help with universe with multiple related tables/loops

Post Author: bradwist
CA Forum: Semantic Layer and Data Connectivity
Hi. I am relatively new to Business Objects and have been putting together some universes for our use. Most things I can accomplish well enough. However, I've run into an issue that I think fits within this topic. I've got several related tables and I'm looking for the best way to construct the universe to support our queries. The best way to describe them is to say that the database has a table of Person records, and a table of Relationships. One Person may be related to another Person in a number of ways (sibling, spouse, parent, etc). This can be pictured as Person Relationship ID -
< PersonID -
< RelatedPersonID or Person1 -< Relationship >- Person2 where Person1 and Person2 really both point to the same physical table. I believe these tend to lend themselves to Aliases. However, each Person table really has a number of subordinate records in tables (addresses, phone numbers, etc). Address1 >--- Person1 -< Relationship >- Person2 ---< Address2 While this can be done (and I've done so), it's difficult to explain to some analysts why this construct is needed in the universe in order to answer a question like: Give me all of Bob's Siblings, their ages, and their addresses. This is a simplification, as our structures actually include other types of Entities (Person, Business, Government, Organizations), all of which can be related to one another. Is there a way that BO Universes will support this structure? Thanks.

exp system/manager file=exp.dmp log=exp.log full=y at the source database.
imp system/manager file=exp.dmp log=imp_show.log full=y show=y - create the log file without importing the data
edit the imp_show.log and extract the statements that are needed to re-create users,roles,alter user and grants.
Pre-create the tablespaces using SQL*Plus in the target database.
execute the modified imp_show.log(All DDl's)
imp system/manager file=exp.dmp log=imp.log fromuser=A touser=B
Re-compile all the Invalid Objects.
HTH
-Anantha

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

Multiple hierarchies in one dimesion

Hi all,
I am new in using AWM. I have problem when using two hierarchies in one dimension. This is sample of dimension.
A
---+B
-----+B1
-------+B2
---------+B3
---+C
-----+C1
-------+C2
---------+C3
Dimension is A and it has two hierarchies B and C. Maintaining the cube is succesfull. But when "add" this cube in OBIEE and try to make request using B1 and C1 we are getting error. How we can have mulitple hierarchies in one dimension and combine columns from hierarchies? We are using database 11g, AWM 11.2.0.2 and OBIEE 10.1.3.4.
Thanks all

Maybe you need to join the generic dimension view A_VIEW with the fact-cube view in the physical layer of rpd on the basis of the key corresponding to the (common) lowest level of the dimension.
Regd your dimension hierarchy setup:
A
---+B
-----+B1
-------+B2
---------+B3
---+C
-----+C1
-------+C2
---------+C3It looks like you have column/level B3 as leaf level of hierarchy B and C3 as leaf level of hierarchy C.
Is this distinction piurely logical and the same physical column is used to represent both B3 and C3?
Then A_VIEW and Fact view should be joined on basis of this single common level key column.
Generally a dimension A with multiple hierarchies B and C will work fine when you have a common lowest level D, say, which acts as the leaf level for both hierarchies of the dimension.
Can you model the hierarchy as
A
---+B
-----+B1
-------+B2
---------+B3
-----------+D
---+C
-----+C1
-------+C2
---------+C3
-----------+D NOTE1: Same level/column D acts as leaf level of Hierarchy B as well as Hierarchy C. We should not use 2 different columns D1 and D2 even if they contain the same data
NOTE2: Dimension A is joined to Fact F1 via level/column D.
In that case, you can issue a query against Fact F1 which uses both level columns B and C from different hierarchies of A against a measure defined in Fact table F1.
You can even add a filter (where clause) on columns B/C/both B and C as required.
Result will be at the granularity of level D (not summarized to either level B along HI_B hierarchy or level C along HI_C hierarchy) -- 1 record per distinct member at Level D of default hierarchy with the corresponding values for columns B and C available as part of the output since they are ancestor fields and availble at level D. A smart reporting tool like OBIEE or BO can even exclude the column corresponding to D locally within a pivot and create ad-hoc, report level, pivot table based local summaries (aggregated results for each combination of values in columns B and C).
HTH

Multiple Hierarchies in Dimension

Hi All,
I have a scenario, where I need to design a dimension with multiple hierarchies, is there a best practice on this ? I have about 6 hierarchy in one dimension. Could any share some idea and thoughts.
Thasnks
Zan

Hi,
Technically, there is no restriction on the number of hierarchies in a dimension. However, SAP suggests to have 3 dimensions for the performance sake. So, you can have 6 hierarchies. But, you should check the performance of the data retrieval.
Hope this helps.

Multiple hierarchies

Could any one tell me how we deal with Multiple hierarchies of data in XI without BPM OR with BPM?
how we solve Multiple hierarchies of IDOC problems for that should we use AS2 or module?

Hi Abhi,
see this link
Business Intelligence How-to Guides for SAP NetWeaver 2004 [original link is broken] - 65k
http://209.85.175.104/search?q=cache:uN8YMaLgj-QJ:www.wca.org/event_archives/2007/Khaitan_RFID_13Feb07.pdfMultiplehierarchiesofdatainXI%2Bsap&hl=en&ct=clnk&cd=7
thanks
karthik

Analysis Authorization based on Hier node with multiple display hierarchies

Hi guys - I've got a problem where s.o. might have an idea of how to switch on the light at the end of the tunnel, I am currently standing in:
Requirement:
Cost Center Authorization should be given through RSECADMIN, reporting should be possible for any hierarchy that exists for the authorization relevant info object.
Preferred solution:
The Cost Center Analysis Authorization should be given through RSECADMIN - Hierarchy node assignment.
u2022     A dedicated Authorization Cost Center Hierarchy will be maintained in ECC6 as an alternative cost center hierarchy and extracted into BW.
u2022     The RSECADMIN Hierarchy node assignment should be based on a particular node (Type 2).
u2022     The display level will be specified as required (here: Level 7)
u2022     The Authorization granted should be independent of hierarchy name and version (validity 3).
Reporting Scenario and technical impact:
As mentioned above, when designing and running a query the user should be able to freely select other (i.e. than the authorization) display hierarchies for the authorization relevant reporting object 'Cost Center' as well. The technical names of the semantically relevant hierarchy nodes could therefore vary. E.g. cost centers 1, 2 and 3, being assigned under hierarchy node u2018Au2019 of the RSECADMIN relevant authorization hierarchy, could be subsumed by hierarchy node u2018Bu2019 in another display hierarchy, which the user may want to display in accordance to his reporting needs. Ideally, the alternative display hierarchy should therefore display node u2018Bu2019.
My findings so far (based on prototyping) turn out that this is not possible as long u2018Bu2019 (and its hierarchy) is not authorized in RSECADMIN. Can these findings be confirmed? And if not, would anyone have an idea of how to facilitate the reporting scenario?
Would there be any other way to grant access, possibly based on RSECADMIN single values, and also enable the user to flexibly display hierarchies with only those hierarchy nodes whose single cost center values the user has been given access to?
Thanks everyone for your input...
Claus
Edited by: Claus64 on Jul 13, 2009 4:10 AM

HI CLause,
On Jul 14 2009, you wrote in SDN and said:
FYI: Found a solution...
The hierarchy analysis authorization will be based on a navigational attribute of cost center.
With analysis authorizations it is possible to declare the Auth object (e.g. 0COSTCENTER__RACCAUT0) as authorization relevant and leave the superior object 0COSTCENTER auth irrelevant.
The auth will be given for 0COSTCENTER__RACCAUT0. This object will be placed as a filter of the query, being restricted by an Authorization variable for hierarchy nodes.
Due to the concept of Analysis Authorizations, this variable will automatically pick up the nodes granted as part of RSECADMIN Hierarchy based Authorization.
As mentioned above, 0COSTCENTER as the regular reporting characteristic remains auth irrelevant and can therefore take any hierarchy thatu2019s available. Reporting on single values will be possible, too. Only those nodes show up that hold the authorized cost centers in accordance to the authorization.
If the auth relevant 0COSTCENTER__RACCAUT0 is not used in the query definition by either not taking it in as a filter or skipping the Auth variable, the query will launch the message that the authorization is missing. No data show up at all.
Claus
See this thread:
Analysis Authorization based on Hier node with multiple display hierarchies
I am also in the same situation as you and need to understadn your solution. I understand that you created a Nav Attr on 0COSTCENTER and made this auth relevant whilst ensuring that 0COSTCENTER is NOT auth relevant. This is all fine. The issue was you have multiple hierachies for 0COSTCENTER, how did the new Nav Attr help you solve your issue. When loading 0COSTCENTER what values did you load ino the new Nav Attribute and how did that link to the hierachies? Also, in RSECADMIN you created hiearchy nodes based on the Nav Attribute but I am confused as to what values you have in the Nav Attr.
I appreciate if you can share your solution from the past in more details.
many thanks

BW Universe with multiple hierarchies issue

Similar Messages

Maybe you are looking for