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

Similar Messages

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

Problem with skip-level hierarchies

Hi,
I have created metadata using CWM2 procedures. These procedures allow define skip-level or ragged hierarchies.
I created skip-level hierarchies by setting null values to several keys in dimension table.
The result is... OLAP did not created cursor error, when I try to drill that hiuerarchy?
Why?
How to build BIBeans compatible skip-level hierarchies and?
My next question: Is it possible to use BIBeans with fact tables which contain embedded totals?
Slawek.

Hello Vicky,
Products created in R/3 can always be downloaded to CRM using the download object MATERIAL.
But products created in CRM could not be recovered back unless you archive them in CRM.
In order to delete the materials in CRM , you can use report COM_PRODUCT_DELETE_SINGLE or COM_PRODUCT_DELETE_ALL.
You can then download these materials from R/3.
Or you can have your own Z-report using the above standard report, where you can pass on the material id or range.
Also,please note that before executing these reports, you need to make an entry in table COMC_PR_TOOL_REG.
Hope this helps!
Best Regards,
Shanthala Kudva.

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.

Is there any process to convert an value-based hierarchy to level-based one

Hi Experts,
Is there any automated or manual process to convert the value-based hierarchy to the level-based hierarchy.
Thanks
VR

Using SQL's "CONNECT BY" clause and PL/SQL programming we can convert a value-based hierarchy to a level based. I have not done this myself but I am positive we can get it to work.

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.

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

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]--------------

Problem when querying OLAP for Value based hierarchy

Hi I have problem when querying OLAP for value based hierarchy , for level based dimension it work fine
the strange part is if I only put one value, it will work perfectly
for example if I put only 1 value for that value base hierarchy like CF_HIER::426362, then it will get the correct value for that id 426362
but if I put multiple value to the list
CF_HIER::426362
CF_HIER::424470
CF_HIER::429073
CF_HIER::424230
then only some value will come out correctly, some of them will be 0, I wonder why because if I query using each value, then it show correct value
for multiple value usually only the top in hirarchy give correct value, but the leaf will give 0, but if I query only the leaf, the leaf will give correct value
this problem only happen for my value based hierarchy, for the level based hierarchy it work fine both for each value or multiple value in the list
this is the code how I guery
////the "elementIdList" is where the value is (CF_HIER::426362,CF_HIER::424470,CF_HIER::429073,CF_HIER::424230), if I only put single value in this list the query work fine, but if I put multiple value then some value give correct result, some will give 0
String[] elementIdArr = new String[elementIdList.size()];
          int i = 0;
          for (Long elementId: elementIdList) {
               String elementIdStr ="";
               if (hierarchy instanceof MdmLevelHierarchy)
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        level.getName()+dimension.getValueSeparationString()+
                                        level.getName()+"_"+elementId;
               else
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        elementId;
               elementIdArr[i++] = elementIdStr;
          Source myList = dp.createListSource(elementIdArr);
          result = hierarchy.getSource().selectValues(myList);
     Source joinedSource = measure.getSource();
          joinedSource = joinedSource.join(result );
is there any suggestion where I'm doing wrong?or is it different between querying value based hier with level based hier?
thanks

Hi I have problem when querying OLAP for value based hierarchy , for level based dimension it work fine
the strange part is if I only put one value, it will work perfectly
for example if I put only 1 value for that value base hierarchy like CF_HIER::426362, then it will get the correct value for that id 426362
but if I put multiple value to the list
CF_HIER::426362
CF_HIER::424470
CF_HIER::429073
CF_HIER::424230
then only some value will come out correctly, some of them will be 0, I wonder why because if I query using each value, then it show correct value
for multiple value usually only the top in hirarchy give correct value, but the leaf will give 0, but if I query only the leaf, the leaf will give correct value
this problem only happen for my value based hierarchy, for the level based hierarchy it work fine both for each value or multiple value in the list
this is the code how I guery
////the "elementIdList" is where the value is (CF_HIER::426362,CF_HIER::424470,CF_HIER::429073,CF_HIER::424230), if I only put single value in this list the query work fine, but if I put multiple value then some value give correct result, some will give 0
String[] elementIdArr = new String[elementIdList.size()];
          int i = 0;
          for (Long elementId: elementIdList) {
               String elementIdStr ="";
               if (hierarchy instanceof MdmLevelHierarchy)
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        level.getName()+dimension.getValueSeparationString()+
                                        level.getName()+"_"+elementId;
               else
                    elementIdStr = hierarchy.getName()+dimension.getValueSeparationString()+
                                        elementId;
               elementIdArr[i++] = elementIdStr;
          Source myList = dp.createListSource(elementIdArr);
          result = hierarchy.getSource().selectValues(myList);
     Source joinedSource = measure.getSource();
          joinedSource = joinedSource.join(result );
is there any suggestion where I'm doing wrong?or is it different between querying value based hier with level based hier?
thanks

Problems with value-based hierarchies in Oracle 11gR2

Hello,
I have the following problem:
I want to cereate a dimension with 2 hierarchies.
These hierarchies have to be value-based.
It's no problem to fill and display one of them, but when I fill both and try to display them, at the lowest level, the parent-child relevancy is now incorrect.
Let's display this in OLAP Worksheet for Cube Type OLAP 11g :
lcolwidth=20
rpr down nim_2 w 25 NIM_2_PARENTREL
                          ------------------NIM_2_PARENTREL------------------
                          ------------------NIM_2_HIERLIST-------------------
NIM_2                                KON                       AGT
L1_Total_AGT_A            NA                        NA
L1_Total_KONZ_K           NA                        NA
L2_AGT_A_A                NA                        L1_Total_AGT_A
L2_AGT_B_A                NA                        L1_Total_AGT_A
L2_AGT_C_A                NA                        L1_Total_AGT_A
L2_KONZ_1_K               L1_Total_KONZ_K           NA
L2_KONZ_2_K               L1_Total_KONZ_K           NA
L3_100_A                  NA                        L2_AGT_A_A
L3_100_K                  L2_KONZ_1_K               NA
L3_200_A                  NA                        L2_AGT_B_A
L3_200_K                  L2_KONZ_1_K               NA
L3_300_A                  NA                        L2_AGT_C_A
L3_300_K                  L2_KONZ_2_K               NA
L4_101_A                  NA                        L3_100_A
L4_101_K                  L3_100_K                  NA
L4_301_A                  NA                        L3_300_A
L4_301_K                  L3_300_K                  NA
L5_302_A                  NA                        L4_301_A
L5_302_K                  L4_301_K                  NA
100                       NA                        L3_100_A
101                       L4_101_K                  NA
102                       NA                        L4_101_A
200                       NA                        L3_200_A
201                       L3_200_K                  NA
300                       L3_300_K                  NA
301                       NA                        L4_301_A
302                       NA                        L5_302_A
303                       NA                        L5_302_A
304                       NA                        L5_302_AAs you see, the lowest level items are only connectet with one of the hierachies, instead connected with both. (100, 101, e.g)
If I build the same dimension in a 10g Cube, the result is now correct.
Let's display this in OLAP Worksheet for Cube Type OLAP 10g :
lcolwidth=20
rpr down nim w 25 NIM_PARENTREL
                     -------------------NIM_PARENTREL-------------------
                     -------------------NIM_HIERLIST--------------------
NIM                             AGT                       KON
L1_Total_AGT_A       NA                        NA
L1_Total_KONZ_K      NA                        NA
L2_AGT_A_A           L1_Total_AGT_A            NA
L2_AGT_B_A           L1_Total_AGT_A            NA
L2_AGT_C_A           L1_Total_AGT_A            NA
L2_KONZ_1_K          NA                        L1_Total_KONZ_K
L2_KONZ_2_K          NA                        L1_Total_KONZ_K
L3_100_A             L2_AGT_A_A                NA
L3_100_K             NA                        L2_KONZ_1_K
L3_200_A             L2_AGT_B_A                NA
L3_200_K             NA                        L2_KONZ_1_K
L3_300_A             L2_AGT_C_A                NA
L3_300_K             NA                        L2_KONZ_2_K
L4_101_A             L3_100_A                  NA
L4_101_K             NA                        L3_100_K
L4_301_A             L3_300_A                  NA
L4_301_K             NA                        L3_300_K
L5_302_A             L4_301_A                  NA
L5_302_K             NA                        L4_301_K
100                  L3_100_A                  L3_100_K
101                  L4_101_A                  L4_101_K
102                  L4_101_A                  L4_101_K
200                  L3_200_A                  L3_200_K
201                  L3_200_A                  L3_200_K
300                  L3_300_A                  L3_300_K
301                  L4_301_A                  L4_301_K
303                  L5_302_A                  L5_302_K
304                  L5_302_A                  L5_302_K
302                  L5_302_A                  L5_302_K-----
We are using the latest Version of AWM: Version 11.2.0.1.0A
Database:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
"CORE     11.2.0.1.0     Production"
TNS for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
Thank you verry much for any help.

11.2.0.2 for AIX was announced in October 2010. See DOC ID 1249584.1
What is being announced?
We are pleased announce the October 19, 2010 release of Oracle Database 11g Release 2 Patchset 1 (11.2.0.2) on HP-UX > Itanium and IBM AIX on POWER Systems.Patchset 10098816
Description 11.2.0.2.0 PATCH SET FOR ORACLE DATABASE SERVER
Product Oracle Database Family
I have looked, but I cannot find a formal bug for this problem. My hunch is that it was fixed as a side effect of other changes, and I know there were several in this area. My simple test case did work in 11.2.0.2, so I hope it is all fixed. But feel free to enter an SR if you want. (If you mention my name in the SR then support should contact me.) You should certainly do this if moving on to 11.2.0.2 does not resolve the issue.

OBIEE and Oracle OLAP Value Based Hierarchies

Hi there...
I have a value based dimension built on Oracle OLAP and want to map it on OBIEE Administration tool.
I've been using the above link as reference:
http://www.oracle.com/technology/obe/olap_biee/CreateBIEEMetadata.htm
There's no option to import from Oracle Multi-dimensional Database. Either to import/configure the view created by OLAP as an Unballanced or Ragged Dimension.
I also checked this example, but it uses ESSBASE as the multi-dimensional source....
http://www.rittmanmead.com/2008/08/27/ragged-hierarchy-handling-in-obiee/
How to map this Ragged Dimension created in OLAP workspace in OBIEE? Any suggestions or directions will be highly appreciated...
Thanks in advance
Marcos

Mark and others,
You can create OLAP_TABLE views with level columns on top of value-based hierarchies. BI Beans used to do that too behind the scenes in Discoverer Plus OLAP. If you trace the Discoverer session, where you are querying data from Value-based hierarchies, you will see that it also generates OLAP_TABLE views with level columns in it.
So the question is how to do it. Internally, even for Value-based hierarchies Oracle OLAP keeps track of the "depth" of each value by using a structure called GID_DIMENSION (i.e., Grouping Dimension). Here is an example of a view on top of a value-based hierarchy (CFC_ACCT_GAPP) for RPT_ACCOUNT dimension. You have to know how "deep" your value-based hierarchy is.
Similar kind of a thing is done by OLAP View Generator application, which I never use - since I always prefer to define my own OLAP_TABLE views.
This kind of a view can then be used in the RPD of OBIEE.
select *
FROM table(OLAP_TABLE ('AW duration session',
*'DIMENSION RPT_ACCT_ID FROM RPT_ACCOUNT WITH*
HIERARCHY RPT_ACCOUNT_GAAP_PARENT   FROM RPT_ACCOUNT_PARENTREL(RPT_ACCOUNT_HIERLIST ''CFC_ACCT_GAAP'') INHIERARCHY RPT_ACCOUNT_INHIER
HATTRIBUTE RPT_ACCOUNT_GAAP_LVL_NUM FROM RPT_ACCOUNT_DEPTHVAL
FAMILYREL RPT_ACCOUNT_GAAP_LVL1,
RPT_ACCOUNT_GAAP_LVL2,
RPT_ACCOUNT_GAAP_LVL3,
RPT_ACCOUNT_GAAP_LVL4,
RPT_ACCOUNT_GAAP_LVL5,
RPT_ACCOUNT_GAAP_LVL6,
RPT_ACCOUNT_GAAP_LVL7,
RPT_ACCOUNT_GAAP_LVL8
FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
FAMILYREL RPT_ACCOUNT_GAAP_LVL1_DSC,
RPT_ACCOUNT_GAAP_LVL2_DSC,
RPT_ACCOUNT_GAAP_LVL3_DSC,
RPT_ACCOUNT_GAAP_LVL4_DSC,
RPT_ACCOUNT_GAAP_LVL5_DSC,
RPT_ACCOUNT_GAAP_LVL6_DSC,
RPT_ACCOUNT_GAAP_LVL7_DSC,
RPT_ACCOUNT_GAAP_LVL8_DSC
FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
LABEL RPT_ACCOUNT_LONG_DESCRIPTION
ATTRIBUTE ACCOUNT_LDSC    FROM RPT_ACCOUNT_LONG_DESCRIPTION
ATTRIBUTE ACCOUNT_SDSC    FROM RPT_ACCOUNT_SHORT_DESCRIPTION
ATTRIBUTE ACCOUNT_TYPE    FROM RPT_ACCOUNT_TYPE
ATTRIBUTE SOURCE_LEVEL    FROM RPT_ACCOUNT_LEVEL
ATTRIBUTE CALCULATION     FROM RPT_ACCOUNT_CALCULATION
ATTRIBUTE CALC_DATA       FROM RPT_ACCOUNT_CALC_DATA
ATTRIBUTE GAAP_SORT_ORDER FROM RPT_ACCOUNT_GAAP_SORT_ORDER
ATTRIBUTE RATIO           FROM RPT_ACCOUNT_RATIO
ATTRIBUTE ACCOUNT_LEVEL   FROM RPT_ACCOUNT_LEVELREL'))

Multiple Value Based hierarchies per MOLAP dimension

Hi,
a) Is it possible to have multiple value based heirarchies in a single MOLAP dimension in OWB and deployed to analytical workspace ?
Are there any pitfalls, that we need to be aware of...
b) Can we have a mix of Value and level based heirarchies per dimension ?
Thanks in advance,
Chakri

Hi Chakri
Yes, you can have multiple value based hierarchies and also a mix of value/level based.
Cheers
David

Value based hierarchies and Period dimension should only contain 2 monthl

Hi,
Can anyone tell me what is value based hierarchies. And also can anyone let me know to filter the records in AWm because in Period dimension should only contain 2 monthly values (Oct. 2008 ( 200810) and Sep. 2008 ( 200809)) it is urgent.
Thanks
vel

The following definition of a value hierarchy comes from the OLAP Developers guide
"A hierarchy defined only by the parent-child relationships among dimension members. The dimension members at a particular distance from the base level do not form a meaningful group for analysis, so the levels are not named. For example, an employee dimension might have a parent-child relation that identifies each employee's supervisor. However, levels that group together first-, second-, and third-level supervisors and so forth may not be meaningful for analysis."
Typically this means that the source table has two columns, VALUE and PARENT, where PARENT has a (logical) foreign key relationship to VALUE. An example may be EMPLOYEE, MANAGER, where MANAGERs are also EMPLOYEEs.
The simplest way to restrict the values loaded into the AW is to define a SQL view over the source table with an appropriate WHERE condition. You then use AWM to map the dimension to your new view. E.g.
CREATE OR REPLACE VIEW RESTRICTED_TIME AS
SELECT *
FROM TIME
WHERE MONTH IN (200810, 200809)

OLAP on 11g and Materialised Views with Multiple Value-Based Hierarchies

Hello OLAPians
I am trying to setup Orable BIEE to report on an OLAP cube with pre-aggregated data. As OBIEE is not able to hook into the OLAP directly i have to create an SQL cubeview.
Currently i am on a 10g OLAP environment and am using the oracle sample SQL cubeview generator to create an SQLview of my cube.
The cube itself has multiple dimensions and these dimensions have multiple VALUE-based (ragged) hierarchies and dimension members can be shared across hierarchies also.
Initially i had a problem running the view generator plugin because there is a bug within it that does not finish if there are multiple value-based hierarchies present. I was able to get around this by manually editing the limitmap for the cubeview and manually creating the SQL view.
The question that i want to ask is how robust is the 11g materialised views with multiple value-based hierarchies and the sharing of dimension members across different hierarchies?
Has anyone successfully been able to create a cubeview and import it into OBIEE without the hassle of manually editing the limitmap?
A problem arises with the value-based setup whereby if the client creates a newer depth in the ragged hierarchy, i need to manually create the limitmap and the cube-view over again, and then re-map the BI Administration mappings.

The simple answer to your question,
how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

Has anyone setup BIEE with OLAP 10g using value-based dimension hierarchies

I just wanted to know if it is possible to setup BIEE with 10g using multple dimensions containing multiple value-based hierarchies?
I know this involves using the OLAP Cube View Generator to create an sql view of the cube data.
I have been able to get this to work with nine dimensions all containing a single value-based hierarchy bar one which had four value-based hierarchies. But as soon as i have multiple hierarchies in multiple dimensions it seems to go haywire and i cannot get the sql view to return correct data.
I thought i would post on the BI side to see if anyone has been successful in creating a BIEE setup like this?

The simple answer to your question,
how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

Value based hierarchies, Skip Level Hierarchies

Similar Messages

Maybe you are looking for