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

Similar Messages

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.

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)

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'))

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

Value-based hierarchy on ROLAP dimension. Is this possible and how?

Value-based hierarchy on ROLAP dimension. Is this possible and how?
If yes, what tool I have to use. Any simple examples?

Based on my experience of OWB10gR2 the option to create a "Value Based" hierarchy is only enabled if you create an AW based OLAP model. If you want to create a ROLAP model then I do not think this is possible.
Question is why create a ROLAP model when you could get better performance and more powerful analytical features by using a multidimensional model within an analytic workspace.
Keith

Value based Hierarchies

Hello,
Has anyone created a parent-child hierarchy using Oracle Warehouse Builder or Analytic Workspace Manager. I am using Oracle 10g Rel2 (and AWM) and OWB 10g Rel2.
The values in the dimension table defines the hierarchy.
I don't see an option of creating a value-based hierarchy in OWB though it is mentioned that it supports this particular hierarchy.
In AWM, I am able to create the hierarchy but when I try to view the data in the dimension it gives an error BIB-9531 Invalid hierarchy specified.
Can you please let me know if I am missing something.
Thanks a lot in advance!
Regards,
Maruthi

To create a value based hierarchy:
define the storage as MOLAP, as a minimum create 2 attributes one for the dimension member (define as business in Identifier column), one for the parent member referenece (define as parent in Identifier column), the hierarchy will have no levels. If you add this dimension into a map, you should have a mapping port for both the dimension member and the parent reference. The dimension will use 'Use natural keys from data source'.
There is an expert for simplifying some of this, not sure on when it will be made available on OTN, it drives the creation of the dimensional objects from tables/views etc..

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.

Multiple values based on LOV in report

Hi,
I have a checkbox on a form where I can select values like e-mail, fax, post.
And then I have report that has a column for confirmation type that is based on same LOV as the checkbox.
The problem is that wen there is one value selected it shows correctly in report that e-mail for example. But when I have multiple values there it shows P:E only not Post, E-mail as it should. So when there are multiple values it shows only LOV return values not display values.
How can I get it to show display values instead of return values when there are multiple values (Post, E-mail instead of P:E)?
Thank you a lot.

anyone?

How to Aggregate "Value Based Hierarchies"

I've a tipical parent-child dimension ( Company ).
I've created Company dimension using Analitic Workspace Manager defining the Hierarchy as "Value Based Hierarchy".
In the fact table there are some entries related to non leaf nodes of the Company dimension.
After the loading process I view the cube but I see the aggregation computed only on leaf nodes, intermediate node's amounts were not summed.
Example on Company table ( from "Kimball Design Tip #17: Populating Hierarchy Helper Tables" )
Microsoft
---Software
------Consulting
------Products=================AMOUNT==>100.0
---------Office
------------Visio
---------------Visio-Europe====AMOUNT==>100.0
---------Back-Office
------------SQL-Server
---------------OLAP-Services===AMOUNT==>100.0
---------------DTS
---------------Repository======AMOUNT==>100.0
---------Developer-Tools
---------Windows
---------Entertainment
------------Games
------------Multimedia
------Education
---Online-Services=============AMOUNT==>100.0
------WebTV
------MSN
---------MSN.co.uk
---------Hotmail.com
---------MSNBC
------------MSNBC-Online=======AMOUNT==>100.0
---------Expedia
------------Expedia.co.uk
Expected Aggregation: 100 + 100 + 100 + 100 + 100 + 100 = 600
But I see only 400. , it seems that Online-Services and Products Entries were not aggregated.
What's wrong?
Andrea

Aggregation aggregates from lower levels to higher levels overwriting whatever values might be in the upper level cells. Aggregation within the analytic workspace is not cummulative. The problem is that commulative aggregation is to compute the first time the data is aggregated, but it's very difficult to understand what do in later aggregations. E.g., in your example you would expect the following values from these nodes (I'm not including the whole example:
Microsoft 400.00
---Software 400.00
------Consulting 400.00
------Products=================AMOUNT==>100.0
---------Office 100.00
------------Visio 100.00
---------------Visio-Europe====AMOUNT==>100.0
---------Back-Office 200.00
------------SQL-Server 200.00
---------------OLAP-Services===AMOUNT==>100.0
---------------DTS
---------------Repository======AMOUNT==>100.0
If you aggregate again and aggregation is cummulative, you would get:
Microsoft 1900.00
---Software 1500.00
------Consulting 1100.00
------Products=================AMOUNT==>700.0
---------Office 300.00
------------Visio 300.00
---------------Visio-Europe====AMOUNT==>100.0
---------Back-Office 400.00
------------SQL-Server 400.00
---------------OLAP-Services===AMOUNT==>100.0
---------------DTS
---------------Repository======AMOUNT==>100.0
That is, there's no way to understand whether to accumulate or not.
You can model this by adding dummy detail members for all summary members and aggregating from those. E.g.,
Microsoft
---Software
------Consulting
------Products
------------------- Products Detail 100.00
---------Office
------------Visio
---------------Visio-Europe====AMOUNT==>100.0
---------Back-Office
------------SQL-Server
---------------OLAP-Services===AMOUNT==>100.0
---------------DTS
---------------Repository======AMOUNT==>100.0
---------Developer-Tools
---------Windows
---------Entertainment
------------Games
------------Multimedia
------Education
In this case, you can aggregate as often as you like.

How to generat multiple invoices based on per employee/contractor/services?

Hello Experts / Dina,
I am in situation where customer is in business of body shopping and charges to his final customer based on individual invoice / per employee /contracor & customer services. This was happening in legacy system but after the implementation of Oracle Project costing and Oracle Project billing, customer is not able to generate invoices per employee services. Rather consolidated invoices are getting generated.
How to achieve this functionality in oracle project billing?
Lets take example - On Project P1 for customer ABC, 3 below employees are working on different task for 3 months.
Now after one month employees have been billed as shown below.
Emp 1 - 1000 USD - for 100 Hrs
Emp 2 - 2000 USD - for 200 Hrs
Emp 3 - 1000 USD - for 50 hrs
Now @ end of the month when invoice is getting generated is 1 invoice including 3 lines of amount total 4000 USD. There is problem; customer wants that there should be 3 different invoices per employee shoud generated based on above mentiond 3 diff lines for customer ABC.
I guess with oracle projects billing - You can split the invoice based on Accrue through date ( which is not possible in this case ) and agreement ( which is also not possible in this case ) and different currency ( which is again not possible in this case) - I may be wrong when saying it is not possible. plz correct me if I am wrong.
even I guess billing extension wont work. So is there any way to achive this?
Right now only option i am thinking is let single invoice of 4000 USD with 3 different lines should pass to AR and while priniting the invoice customer can create 3 diff prints which includes individual lines. and while applying receipts on the single invoice in the system, customer can apply the receipts to indivual lines.
but I am not sure about AUDIT issues.. Can some one think about any AUDIT issues comes to this approch or issues with TAX rounding amount issues ?
Infact I would like to solve this issue with the help of Oracle Projects billing and not with custom invoice print program. I guess someone from you experts can figure it out to generate muiltple invoice based on employees / suppliers / contractors / materials etc.
A suggestion on Extension / customization / seeded functionality of Oracle Project billing on thi issue would be gr8 help.
Please help.
Thanks
Edited by: oracle_samba on Jan 7, 2013 1:06 AM
Edited by: oracle_samba on Jan 7, 2013 1:07 AM

Hi Dina,
First of all thanks for your update :-) Your solution looks much promising.
I thought of using billing extension but rejected on the ground that I would end up in generating events based on employee for their corsponding billig amounts so finally generating a consolidated invoice only in One GDI run. But what i was missing was pre-processing extension and running the extention in loop based on employee count.
I am fully sure business would not have any issues of auto approving and releasing invoice upon generation. But my question is "is it possible to just approve the invoice & not release it using auto approve and release extension?" The reason is I think when GDI runs it only deletes Unapproved invoice & spare Approve invoices. - So please suggest.
Also please validate my understanding about your solution with an existing example -
As with the current example, there are 3 EMP presents so need to run GDI 3 times and develop pre-processing ext in a such a way that at each time it will put on hold on all the billable items except EMP1, and EMP2 and EMP3 on each consecutive run respectivly. And ensure that Auto Approve and release extension should be used in order to avoid overriding previously generated invoice? Am I right ?
Many Many thanks for solution !!!
Regards,
:-)

Get Variant Attribute Should Search for and return multiple values based on RegEx

I am using Variants as lookup tables (see this article):
Using Variant Attributes to Build a Dictionary or Look-up Table
I would like to be able to use some sort of wildcard to return multiple results from the Get Variant Attribute VI (all results are of the same type, and I don't know the exact names of all the results - those two points make this idea distinct from this idea: Set/Get Variant Attribute for Multiple Attributes).
Ideally the wildcard would be RegEx. If it were, the means by which you specify what to return is standardized.
In the above example, there would be some ambiguity in terms of whether or not you would want to return a result or an array of results given an input, and I doubt you could detect and assume RegEx is what the programmer desires to use. So I think this means a new input would be required to specify whether or not the "name" input of the Get Variant Attribute VI should be interpreted as a RegEx query.

Why RegEx? Why not SQL query? Why not filename wildcard matching?
I don't see anything that makes RegEx special. For this kind of functionality, the code that you've written seems like exactly the right way to do it rather than bolting a RegEx parser or any other system into the primitives or clouding the palette with a bunch of primitives to support various search functions. I could see a primitive that takes a VI refnum that has a conpane of string in/boolean out that you would pass in to supply the filter functionality that you want for any given application, but even that I'd lean toward just letting that be a library that someone writes on top of the primitives. Yes, there is some memory reduction that can be done if it is internal to the primitives, no question about that. But there are so many variations in how to do that filtration/sorting/etc that I'm not confident that any prim would cover a sufficient use case to be worth it. I could be wrong here ... let's see what other comments come in.

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.

Issue drilling on Value Based Hierarchy

I just wanted to post this issue in the hopes that someone else may have run across the same behavior.
The issue I am having is that when I build Value Based (i.e. parent/child) hierarchies at some point I am losing the edibility to drill down on those hierarchies. For example I can create a cube that uses one or more value based hierarchies but when I try to build a Discoverer workbook based on that cube I am not able to drill down on any value based hierarchy. In other words the drill down icon (the little + sign or the little triangle) does not appear where they should. In fact they do not appear at all, thus making the "hierarchy" useless.
I am hoping someone else has run across the same or similar behavior and could maybe point me towards a solution. Any feedback would be greatly appreciated.

Thank you for your feedback. It seemed to have something to do with checking the 2 boxes to delete dimension members and delete dimension attributes in the Analytic Workspace Manager while maintaining a cube. When maintaining (i.e. reloading) a cube I had been habitually checking those two boxes. When I refrain from checking those boxes things seem to behave. Now I am ONLY checking those two boxes if and when I am maintaining a dimension. I leave them unchecked if I am maintaining a cube.

Level Based vs. Value Based hier: advantages, disadvantages and limitations

Could someone give an overview about the advantages, disadvantages and limitations when comparing OLAP Level to Value based hierarchies?
Thanks,
Marcio

OLAP can handle both types of hierarchies. No performance advantage using one over the other (while loading cube or querying).
If you are "pushing" dimensional-security inside OLAP, in that case also it does not matter.
Cube-based MVs (with query-rewrite) can only be created if the hierarchies are level-based. Are you going to need that?
Generally there are other "non-olap" factors:
(#1). Which reporting tool will be used. Does it provide better reporting capabilities if the source is parent-child or level-based?
(#2). Are there any reporting requirements that will need "level" information when selecting data.
(#3). Are there are any security requirements that will be handled in "reporting-layer" which will need level-based information.
Although in case of (#1) and (#2), you can "expose" an olap's parent-child hierarchy as "level-based" hierarchy to the reporting tool using internal GID (grouping-id) information.
OBIEE 11.1.1.5 (and future versions) works well with OLAP metadata, and with any type of hierarchy in olap.
For other reporting tools, you have to see what features are available.
In short, its the source system, the reporting tool and the reporting requirements that will dictate what type of hierarchy should be stored in OLAP.

Multiple Value Based hierarchies per MOLAP dimension

Similar Messages

Maybe you are looking for