OBIEE 10g - Ragged & Skip Level Hierarchy

Hi Frnds,
I'm aware of the fact that OBIEE 11g supports Ragged & Skip Level Hierarchy. But I'm looking for some heads up while implementing the same on OBIEE 10g using Oracle DB as source. I have done this before for Essbase Data Source but now waiting for my Oracle dataset for design.
Has anyone actually implemented in Real Time Project? Pls share your challenges like:
- Dimensional Hierarchies Challenges
- Drill Down Challenges
- Report Challenges
Thanks,
Deepak
Edited by: Deepak Gupta on Aug 11, 2011 5:18 AM

Deepak,
10g does not handle the idea of Skip hierarchies and the ragged hierarchies definitely has its limitations.
We've implemented several projects using Essbase and SAP BW for Oracle BI 10g. The biggest issue is that in Answers creates a new column for each drill down selection when attempting to navigate down a hierarchy. Though this is klugy it does work and provides the data the user is looking for. It is however, not aesthetically please when compared to other tools or now Oracle BI 11g which satisfies this issue with a native drill-down tree folder structure.
My opinion and advice would be to upgrade to 11g as soon as possible to enjoy these new features.

Similar Messages

Issue with Skip Level Hierarchy in OBIEE 11g

Hi,
I have implemented Ragged and Skip Level Hierarchy as explained in the links below in OBIEE 11g RPD.
(checked the 'Ragged' and 'Skipped Levels' check boxes)
http://www.rittmanmead.com/2010/07/obiee-11gr1-support-for-ragged-skip-level-value-based-hierarchies/
http://docs.oracle.com/cd/E17904_01/bi.1111/e10540/dimensions.htm#BABFBBFG
When the Presentation Hierarchy is dragged in the OBI Answers, the leaf level beyond the skip (null) levels is not shown in the report.
When any level finds intermediate null values, OBIEE is failing to show the existing value of the leaf level (Most Granular Level) or any values after Skipped Levels.
For example, following is the values in database for different levels of department hierarchy.
A -> B -> C -> Null -> Null -> F
The OBIEE Presentation Hierarchy can only drill down till C, not beyond that. (does not show the leaf level value 'F').
Could you please suggest whether I am missing any step?
Thanks.

Hi, My problem is that in my report it is showing me that levels as -- A -> B -> C -> Null -> Null -> F, however I want to show data as A -> B -> C -> F, i.e the null valus(columns) should be skipped. Please help.
Thanks and Regards,
Deepak

Ragged Hierarchy and Skip Level Hierarchy

Hi all,
I am confused with ragged and skip level hierarchy, as i read some documents related to obiee 11g.
Will you please explain with an example the difference between ragged hierarchy and skip level hierarchy and also when to use these hierarchies?
regards
chandra kanth.

Chandra Kanth,
Hope this helps you
http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
Thanks,
Saichand.v

OBIEE Essbase skip-level hierarchy

Is it possible to setup OBIEE and Essbase to be able to model skip-level hierarchy? It is obvious with connection to the relational database. How the essbase should designed and populated with data to faciliate this type of hierarchy?

Refer this http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/overview/obiee-essbase-modeling-guide-130897.pdf for Modeling. And for any Essbase releated question post it in Essbase forum Essbase

Design a dimension with skip-level hierarchy and its ETL

Hi gurus,
I'm trying to understand how to set up and use a skip level dimension and its corresponding mapping in OWB 11.2.
A simplified version of my hierarchy would be like Total-Brand-LOB-Product where Some Products connect directly to Brand and others connect to LOB.
My first question is about designing this kind of dimension in OWB. Is it better to create a single hierarchy with the Product level skipped to Brand level or 2 hierarchies - one Total-Brand-LOB-Product and the other Total-Brand-Product?
My second question is about creating its corresponding ETL mapping. Selecting each option above result in 2 FKs for Brand and LOB in Product level. What is the correct design to fill these 2 FKs?
Any help/guidance would be truly appreciated!
Thanks,
Iman

Hi, My problem is that in my report it is showing me that levels as -- A -> B -> C -> Null -> Null -> F, however I want to show data as A -> B -> C -> F, i.e the null valus(columns) should be skipped. Please help.
Thanks and Regards,
Deepak

Skipped and ragged level hierarchy in OBIEE11g

Hi
I tried creating aboth skipped and ragged hierarchy in OBIEE 10g
It works fine without error
SO I have doubt why they have introduced this concept in OBIEE 11g, Is there any more feture about this
Please help me

@Abdul : can you please let us know how you have implemented skip level hierarchy in 10g..
actually we need to implement it ,didn't find anything in google search ...
thanks In advance

Skip Level Dimensions

Dear all
We have a client with an interesting problem. I was wondering if the group could offer any feedback on this design question, where we think it involves a concept called 'skip levels'. The client is using Oracle 9.0.2 with their data mart cube held as ROLAP. Our first thoughts are that what they want to do is better served by using a true OLAP tool such as Oracle Express, or Oracle 9i OLAP, which deals with skip level dimensions easier. Anyway, here's the problem :
"For our warehouse project, we need some dimensions (initially: account, company) that use a skip level hierarchy. This means that the lowest level dimensions are of the same level (G/L account or company) and they need to roll up in a structure of varying levels, before they come together again in a highest level.
Ideally, we would like to use a data structure that can be used transparently by the user and allows for rollups of amounts through the dimension. We would like to be able to populate the dimension through OWB and to query the data using both Crystal reports v9 and BI beans and possibly other tools that recognize the Oracle data warehouse concept.
The two solutions we are aware of are:
1. Insert Dummy levels:
This is not a nice solution but is will work and it is simple.
2. Insert a helper table that contains the higher level account with all the children (as per Ralph Kimball)
This seems a cumbersome solution but I am sure it would work also. The question is how the Oracle's BI beans and the CWM2 metadata would recognize this and how we can make this transparent to the user.
I am sure there are other solutions to the problem. It seems like the problem would be solved by the next release of Oracle (9.0.3?), which allows us to deal with skip level hierarchies through CWM2 (which I believe this is). The solution we choose should also allow us to easily upgrade to the new skip level hierarchy, which I would expect to be easier to use then the above."
The main thing to bear in mind here is that they want to implement a ROLAP solution, using Oracle 9i tables, dimensions and heirarchies. It also has to work with Oracle Warehouse Builder, take advantage of the CWM2 metadata (if possible) and work with the BI Beans.
Any thoughts on this? Does anyone know how Oracle are going to cater for skip-level dimensions with the next release? Is this through the improved support for the CWM2 metadata standard for ROLAP cubes, or is the customer best of going to the true OLAP 'Analytic Workspace'? If we ignore a MOLAP solution, what's the best way of dealing with this, in such a manner that it's transparent to query tools, and isn't too much of a 'hack'?
Many thanks in advance,
Mark Rittman
Mark Rittman
Consulting Manager, Plus Consultancy
[email protected]
[email protected]--------------

As part of my search i've uncovered an article by Ralph Kimball on using 'helper tables' to deal with ragged hierarchies.
http://www.dbmsmag.com/9809d05.html
This advocates using a table between the fact table and the dimension. Quoting from Mr. Kimball;
"You can solve this modeling problem by inserting a helper table between the dimension table and the fact table, as shown in Figure 3 (http://www.dbmsmag.com/9809d05.html#fig3). Amazingly enough, you don't have to make any changes to either the dimension table or the fact table; you just rip the join apart and insert the helper table.
The helper table contains one record for each separate path from each node in the organization tree to itself and to every node below it. There are, then, more records in the helper table than there are nodes in the tree. In Figure 3 we need a total of 43 records in the helper table. See if you can work this out.
Each record in the helper table contains the fields:
- Parent Customer Key
- Subsidiary Customer Key
- Depth From Parent
- Lowest Flag
- Topmost Flag.
If you are descending the tree from certain selected parents to various subsidiaries, you join the dimension table to the helper table and the helper table to the fact table with the joins as shown in Figure 3. The Depth From Parent field counts how many levels the subsidiary is below the parent. The Lowest Flag field is True only if the subsidiary has no further nodes beneath it. The Topmost Flag field is True only if the parent has no further nodes above it.
The beauty of this design is that you can place any normal dimensional constraint against the Customer dimension table and the helper table will cause all the fact table records for the directly constrained customers plus all their subsidiaries to be correctly summarized. In other words, you can use your standard relational databases and your standard query tools to analyze the hierarchical structure."
My question is - has anyone tried to implement this with OWB, or with the Oracle ROLAP data warehouse in general, reporting through Discoverer or BI Beans? Any opinions?
thanks
Mark

Poor performance when using skip-level hierarchies

Hi there,
currently we have big performance issues when drilling in a skip-level hierarchy (each drill takes around 10 seconds).
OBIEE is producing 4 physical SQL statements when drilling f.e. into the 4th level (for each level one SQL statement). The statements runs in parallel and are pretty fast (the database doesn't need more than 0,5 seconds to produce the result), but ... and here we have probably somewhere a problem ... putting all the 4 results together in OBIEE takes another 8 seconds.
This are not big datasets the database is returning - around 5-20 records for each select statement.
The question is: why does it take so long to put the data together on the server? Do we have to reconfigure some parameters to make it faster?
Please guide.
Regards,
Rafael

If you really and exclusively want to have "OBIEE can handle such queries" - i.e. not touch the database, then you had best put a clever caching strategy in place.
First angle of attack should be the database itself though. Best sit down with a data architect and/or your DBA to find the best setup possible physically and then when you've optimized that (with regard to the kind of queries emitted against it) you can move up to the OBIS. Always try t fix the issue as close to the source as possible.

ROLAP skip level dimension support - CWM2?

Dear all
We have a client with an interesting problem. I was wondering if the group could offer any feedback on this design question, where we think it involves a concept called 'skip levels'. The client is using Oracle 9.0.2 with their data mart cube held as ROLAP. Our first thoughts are that what they want to do is better served by using a true OLAP tool such as Oracle Express, or Oracle 9i OLAP, which deals with skip level dimensions easier. Anyway, here's the problem :
"For our warehouse project, we need some dimensions (initially: account, company) that use a skip level hierarchy. This means that the lowest level dimensions are of the same level (G/L account or company) and they need to roll up in a structure of varying levels, before they come together again in a highest level.
Ideally, we would like to use a data structure that can be used transparently by the user and allows for rollups of amounts through the dimension. We would like to be able to populate the dimension through OWB and to query the data using both Crystal reports v9 and BI beans and possibly other tools that recognize the Oracle data warehouse concept.
The two solutions we are aware of are:
1.     Insert Dummy levels:
This is not a nice solution but is will work and it is simple.
2.     Insert a helper table that contains the higher level account with all the children (as per Ralph Kimball)
This seems a cumbersome solution but I am sure it would work also. The question is how the Oracle's BI beans and the CWM2 metadata would recognize this and how we can make this transparent to the user.
I am sure there are other solutions to the problem. It seems like the problem would be solved by the next release of Oracle (9.0.3?), which allows us to deal with skip level hierarchies through CWM2 (which I believe this is). The solution we choose should also allow us to easily upgrade to the new skip level hierarchy, which I would expect to be easier to use then the above."
The main thing to bear in mind here is that they want to implement a ROLAP solution, using Oracle 9i tables, dimensions and heirarchies. It also has to work with Oracle Warehouse Builder, take advantage of the CWM2 metadata (if possible) and work with the BI Beans.
Any thoughts on this? Does anyone know how Oracle are going to cater for skip-level dimensions with the next release? Is this through the improved support for the CWM2 metadata standard for ROLAP cubes, or is the customer best of going to the true OLAP 'Analytic Workspace'? If we ignore a MOLAP solution, what's the best way of dealing with this, in such a manner that it's transparent to query tools, and isn't too much of a 'hack'?
Many thanks in advance,
Mark Rittman
Mark Rittman
Consulting Manager, Plus Consultancy
[email protected]
[email protected]--------------

Dear all
We have a client with an interesting problem. I was wondering if the group could offer any feedback on this design question, where we think it involves a concept called 'skip levels'. The client is using Oracle 9.0.2 with their data mart cube held as ROLAP. Our first thoughts are that what they want to do is better served by using a true OLAP tool such as Oracle Express, or Oracle 9i OLAP, which deals with skip level dimensions easier. Anyway, here's the problem :
"For our warehouse project, we need some dimensions (initially: account, company) that use a skip level hierarchy. This means that the lowest level dimensions are of the same level (G/L account or company) and they need to roll up in a structure of varying levels, before they come together again in a highest level.
Ideally, we would like to use a data structure that can be used transparently by the user and allows for rollups of amounts through the dimension. We would like to be able to populate the dimension through OWB and to query the data using both Crystal reports v9 and BI beans and possibly other tools that recognize the Oracle data warehouse concept.
The two solutions we are aware of are:
1.     Insert Dummy levels:
This is not a nice solution but is will work and it is simple.
2.     Insert a helper table that contains the higher level account with all the children (as per Ralph Kimball)
This seems a cumbersome solution but I am sure it would work also. The question is how the Oracle's BI beans and the CWM2 metadata would recognize this and how we can make this transparent to the user.
I am sure there are other solutions to the problem. It seems like the problem would be solved by the next release of Oracle (9.0.3?), which allows us to deal with skip level hierarchies through CWM2 (which I believe this is). The solution we choose should also allow us to easily upgrade to the new skip level hierarchy, which I would expect to be easier to use then the above."
The main thing to bear in mind here is that they want to implement a ROLAP solution, using Oracle 9i tables, dimensions and heirarchies. It also has to work with Oracle Warehouse Builder, take advantage of the CWM2 metadata (if possible) and work with the BI Beans.
Any thoughts on this? Does anyone know how Oracle are going to cater for skip-level dimensions with the next release? Is this through the improved support for the CWM2 metadata standard for ROLAP cubes, or is the customer best of going to the true OLAP 'Analytic Workspace'? If we ignore a MOLAP solution, what's the best way of dealing with this, in such a manner that it's transparent to query tools, and isn't too much of a 'hack'?
Many thanks in advance,
Mark Rittman
Mark Rittman
Consulting Manager, Plus Consultancy
[email protected]
[email protected]--------------

Parent child Hierarchy in OBIEE 10G

Hi,
I want to implement the parent child hierarchy in OBIEE 10g where I need to show people working under manager directly and indirectly.
Please let me know as users doesn't want to drill the report but by selecting the option from the drop down Direct/Indirect they should see the results.
Thanks

I guess it will update when the structure changes,Let see the response from other gurus.
Thanks,

Object Level security by creating catalog groups in OBIEE-10G

Hi All,
I have a requirement to display the dashboard based on the user login. Ex. Mike belongs to HR, Smith belongs to Accounts
When Mike logs in he should see only these three dashboards. HR View, Common data1, common data2. When Smith logs in he should see only these three dashboards. Accounts view, Common data1, commondata2.
The commondata1 and commondata2 dashboards has common reports for all the departments. The other dashboards are department specific with all different reports. How can I implement this?
From one of my earlier posts I was advised to do it using Object Level security by creating catalog groups. Can you please provide me end to end instructions on how to create Object level security based on catalog groups.
Thanks for your time and help.

Hi,
Mike to HR
Smit - Account
Yes, You achive by Object Level security by creating catalog groups
1) Create Catalog group and users in RPD part(Ex: Account_grp,HR_grp)
2)assign user to that particular group(let say Ex: Account_grp= Smith and HR_grp=Mike )
3) login (Admin user id ) into dashboard page and --->mange dashboard page -->add users to that particular
dashboard to relevent users and save it then
try to login that mike and smith user it will work
kindly refer below link
http://www.rittmanmead.com/2010/01/obiee-10g-web-catalog-best-practices/
http://www.rittmanmead.com/2007/05/obiee-and-row-level-security/
thanks
Deva

Do BI Beans support ragged or skip-level hierarchies

Do BI Beans support ragged or skip-level hierarchies ?

Hi Alexander.
Well I am also a positive person ;)
Here it goes....
In the guide page 93/412
Oracle® OLAP
Application Developers Guide
Release 9.2.0.4.1
Part No. B10333-01
"Dimension Tables with Complex Hierarchies
If your source data is a star or snowflake schema, but the dimension tables include
any of the following variations, then use the CWM2 APIs:
-> Level columns containing NULLs, such as skip-level hierarchies
-> Multiple hierarchies with different base levels (sometimes called ragged
hierarchies)
-> Multiple hierarchies with values mapped to different levels
-> Parent-child dimensions
Choosing a Tool for Creating OLAP Catalog Metadata
If your schema contains parent-child dimension tables, then you must convert them
to level-based dimension tables. The CWM2 write APIs include a package for this
transformation."
You can use the next three steps to add different levels and do the mappings you want!
CWM2:
execute cwm2_olap_level.add_level_to_hierarchy
execute cwm2_olap_table_map.Map_DimTbl_HierLevel
execute cwm2_olap_table_map.Map_DimTbl_HierLevelAttr
Best regards.
Odds

Help with Skip Level dimensions in OWB 10.2 (Paris)

Hi all,
I'm trying to understand how to set up and use a skip level dimension in OWB 10.2. A simplified version of my hierarchy would be:
Plant - Equipment - Assembly - Item
Where Some Items connect directly to equipment and others connect to assemblies. How sould I define this in the Dimension wizard or editor in OWB?
Can I create a single dimension hierarchy and in the Item level put Skip Level as "Equipment"?
OR
Do I need 2 hierarchies - one Plant-Equipment-Assembly-Item and the other Plant-Equipment-Item?
There is an example in the Users guide that created 2 hierarchies -
TOTAL-GROUP-PRODUCT and TOTAL-PRODUCT
In the example, they show the PRODUCT in TOTAL-PRODUCT setting the skip level field. I don't understand why that is necessary if it is 2 seperate hierarchies.
Any help/guidance would be appreciated!
Thanks,
Mike

Hi Donna,
Perhaps JP can expand on his answer. In my case, I did go the route of seperate hierarchies. It is a bit of work defining multiple hierarchies and my example was much simplified. We actually have about 8 levels in the primary hierarchy and 6 levels in the second. It does work well with the cubes by using 2 roles for the dimension - one for each hierarchy.
I saw that truly "ragged hierarchies" or "level hierarchies" can be defined in OWB and deployed as MOLAP but MOLAP has quite a few drawbacks - no SCDs and requires analytic workspaces etc. I haven't done anything with these yet.
Our data is a classic manufacturing Bill of Material so the level hierarchy would be the easiest to manage, though I'm not sure how easy it would be to report on! I do want to shield my end-users from CONNECT-BY madness.

Value based hierarchies, Skip Level Hierarchies

Hello,
I need to create hierarchy based on column value , Please give me some details on implementing value based hierarchies and skip level hierarchies in obiee 10.1.3.
Thank you

With 10.3 i do not think we have a inbuilt solution to build value based hierarchies, you have to flatten the hierarchy and build a level based hierarchy.
OBIEE 11g has value based hierarchies feature.
refer this one for 11g.
http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/
- Madan
Edited by: Madan Thota on Sep 14, 2010 11:15 AM

Error in reports after upgrade from OBIEE 10g to 11g : [nQSError: 14025]

Hi All, We upgraded RPD and web catalog from OBIEE 10g to 11.1.1.5. I see the following error while running few reports.
Error: State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A
general error has occurred. [nQSError: 43113] Message returned from OBIS.
[nQSError: 14025] No fact table exists at the requested level of detail:
When I add an user under BIAdministrator Application role and login, all the reports work correctly.
I verified Oracle BUG fix (11850704) document and tried to make changes as suggested.
Please suggest me if this issue is related to 10g to 11g RPD upgrade or are we missing any privileges?
Also should I add every user to BIAdministrator role to avoid this issue?
Thanks in Advance

Hi,
First of all i am not familiar on linux box.
I tried in windows environment the rpd is deployed with out any errors.
But i ran the ua.bat file in the following path
\MWHOME\Oracle_BI1\bin\ua.bat.
while i am running in oracle_common\bin\ua.bat is not responding in my local system.
Please Mark if it helpful.
Thanks

OBIEE 10g - Ragged & Skip Level Hierarchy

Similar Messages

Maybe you are looking for