Parent-child hierarchy (Value based hierarchy)

As 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

I've done some work with this, and it hasn't been easy going. There is no built-in ability to form a hierarchy of measure columns, at least nothing that can be predefined as the drill for a fact column. For example: I have 220 details of expense that have an exact arrangement with 5 levels and subtotals. Besides the expense detail there are say 4 dimensions, so the expense detail would be the 5th dimension. I have both arrangements in my rpd: 4D and 5D. They can be used together or separately. The 4D basically has 1000's of measures and there is no relationship between them besides the display arrangement in Answers. The 5D has a 5 column dimension that can drill the expense column from Total_Expense down to the 220 rows of detail expense.

Similar Messages

API for parent-child flex value norm hierarchy

Hi,
We are looking for an API to create or delete parent - child flex value hierarchy.
Could someone please advice?
Thanks

Yes, I did check here but did not find any information.
http://irep11i10.oracle.com/OA_HTML/OA.jsp?page=%2Foracle%2Fapps%2Ffnd%2Frep%2Fwebui%2FInterfacesBrowsePG&_ti=2085868704&oapc=3&oas=ioOnKXcQLw-VgcHrVUTNXQ..

Value based hierarchy (parent-child)

Does anybody have any experience in modeling a parent-child dimension ( value based hierarchy instead of level based ) in OBIEE?
Swapan.

I've done some work with this, and it hasn't been easy going. There is no built-in ability to form a hierarchy of measure columns, at least nothing that can be predefined as the drill for a fact column. For example: I have 220 details of expense that have an exact arrangement with 5 levels and subtotals. Besides the expense detail there are say 4 dimensions, so the expense detail would be the 5th dimension. I have both arrangements in my rpd: 4D and 5D. They can be used together or separately. The 4D basically has 1000's of measures and there is no relationship between them besides the display arrangement in Answers. The 5D has a 5 column dimension that can drill the expense column from Total_Expense down to the 220 rows of detail expense.

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.

Aggregation On Value Based Hierarchy

Hi
I am having a problem with aggregation on value based hierarchy
Well I have a table which will serve as my fact and dimension table
It is as follows
ID     Name     MID     Salary
0     All
1     A     0     10000
2     B     1     9000
3     C     1     9000
4     D     1     9000
5     E     2     8000
6     F     2     8000
I created a value based dimension named EMPLOYEE , with child as ID and parent as MID
I created a cube EMP_SALARY with a measure salary mapped to the Salary column in Employee
My expectation here is to see the total salary at every level including the salary at that level
So let us take employee B as an example. He is the manager for employees E and F
So what I would like to see at level B is sal of B + sal of E + Sal of F = 9000 + 8000 + 8000 = 25000
But what I get from the cube is 9000. Now is the above possible ? If so please so provide me suggestions
I can achieve the same by using the following sql query
select e1.id,rpad('*',2*level,'*') || e1.name,e1.sal,
select sum(e2.sal)
from test_emp e2
start WITH e2.id = e1.id
CONNECT by PRIOR e2.id = e2.mid
) sum_sal
from test_emp e1
start with e1.mid is null
CONNECT by prior e1.id = e1.mid;

The same basic problem, along with a solution, was discussed in the following thread.
Re: Value Based Dimension causing Aggrega                         tion problems

Security for value based hierarchy + OLAP

Hi,
I am using row-level security mechanism described here: http://www.rittmanmead.com/2012/03/obiee-11g-security-week-row-level-security/
It works well for level based hierarchies... but is there a way to apply it to value based OLAP hierarchy in OBIEE 11.1.1.6?
My case is:
- I have parent-child value based hierarchy representing management structure with various depth.
- of course facts are always linked to leaf members of hierarchy
- I need to apply security at different levels. E.g. Office manager should have access to one/multiple offices information (basically all employees he manage currently + his previous office before he was moved)
- In report I display presentation hierarchy that starts at country level and then manager drill to his offices
- At country level, manager should see a measure aggregate only for his offices (not whole country)
In relational database there is no problem:
- I follow rittman blog
- create session variable that store list of all leaf members of hierarchy (employees) managed by manager
- with OBIEE "Manage"->"Identity" I apply filter on fact table and get right measure aggregates at all levels of hierarchy
Issue for OLAP:
- with OBIEE "Manage"->"Identity" I apply filter on OLAP value based hierarchy
- in case of filter "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST") -> when manager include hierarchy column to report there are no results because hierarchy starts at country level and he have no access to country data
- to workaround it I tried: "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST_AND_ALL_ANCESTORS") -> manager can see all aggregates at country level because he have access to country, and OLAP just use country level aggregate
- IsDescendant("MY_BMM"."Org Str" , VALUEOF(NQ_SESSION."OFFICE_ID")) will work only for single office as we can not use row wise variables here
One solution I can imagine is to create additional level based dimension that have only 2 levels: "All"->"Org Str Leaf". Then apply filter on this "artifitial" dimension. It is not perfect solution to duplicate dimensions only for security purposes... that's why I ask you for advice if you know better way?
Regards,
mudi

Here is an example, how to set security in OBIEE 11.1.1.5 (or future versions) against Oracle OLAP dimensions.
*(1). Create the Oracle OLAP Hierarchy Descendant View against Value-based hierarchy*
These views return a row for each ancestor-descendent relationship in the hierarchy. As you can see how easy it is.
CREATE OR REPLACE VIEW DEPT_DESCENDANTS
AS
SELECT 'DEPT' "DIMENSION", 'DEPTHIER' "HIER", ancestor, descendant
FROM TABLE(OLAP_TABLE('BAWOLAP.BNSOLAP DURATION QUERY', null, 'LIMIT DEPT_HIERLIST TO 'DEPTHIER''',
'DMNS DESCENDANT AS VARCHAR2(60) FROM DEPT
DMNS GID_VAL AS NUMBER FROM ___AW_GID_DIMENSION
MSR ANCESTOR AS VARCHAR2(60) FROM DEPT_FAMILYRELVAL'
where ancestor is not null
*(2). Create the User ACL Tables and Populate with Data*
Create an Access Control list test table by user and Dept. Later this will be populated with production data.
create table user_dept_acls
username varchar2(30),
dept varchar2(60)
insert into user_dept_acls(username, dept) values ('user1', 'GWM');
insert into user_dept_acls(username, dept) values ('user1', 'GT');
insert into user_dept_acls(username, dept) values ('user1', 'SC');
insert into user_dept_acls(username, dept) values ('user2', 'GWM');
insert into user_dept_acls(username, dept) values ('user2', 'GT');
insert into user_dept_acls(username, dept) values ('user3', 'SC');
commit;
*(3). Create an Init Block Connection Pool*
Oracle BI EE requires a separate Connect Pool for Init blocks. It does not allow the default query connection pool to be reused for init blocks. So, we need to create a new init block.
*(4). Create the ACL Session Variables*
These session variables hold the list of all members that the user may access.
Example Session Variable: DEPT_ACL
Init Block: "Init DEPT_ACL"
SQL:
select 'DEPT_ACL', account from user_DEPT_acls where username = ':USER'
union all
select 'DEPT_ACL', descendant
from DEPT_descendants
where ancestor in (select account from user_DEPT_acls where username = ':USER')
union all
select 'DEPT_ACL', ancestor
from DEPT_descendants
where descendant in (select account from user_DEPT_acls where username = ':USER')
The first query block of the init block SQL just selects the members explicitly entered into the ACL table. The second block selects all the descendants of those members from the descendants view. The third block selects all the ancestors to ensure that the user has access to all the members in the drill path starting from the root member.
Make sure that row-wise initialization is checked in the Variable Target section of the init block.
*(5). Add the Data Filters*
In our test case we assigned the data filters to the BIAuthor role, but the filters should be added to whatever role makes the most sense.
Data filter on "BNSGL"."Department":
"BNSGL"."Department"."Dept" = VALUEOF(NQ_SESSION."DEPT_ACL")
*(6). Log in as a Normal User and Query the Hierarchy*
The user can only see to the members to which they are granted access in the ACL table plus all ancestors and descendants of those members.
Drill down to the bottom of the hierarchy.
*(7). Look at the Query Log*
In the nqquery.log we see that the session variable is expanded into an IN list in the physical SQL query. The BI Server breaks the IN list into two IN lists to avoid the Oracle SQL limit of 1,000 items per IN list.
Edited by: Nasar Ali-Khan on Jul 2, 2012 8:14 AM

Security for value based hierarchy OBIEE11G

Hello All
I have a value based hierarchy where the structure is
EMP 1 -> EMP 2
                EMP 3
EMP 2 -> EMP 4
               EMP 5
               EMP 6
I have implemented a parent child hierachy and it works fine and i am trying to implement a row level security. Can you please advice.
1) When emp1 logs in, he/she can able to see all employees
2) When emp2 logs in, he/she can able to see emp2 and the reportees 4,5,and 6
3) When emp3 logs in he can able to only his information.

Hello All
I have a value based hierarchy where the structure is
EMP 1 -> EMP 2
                EMP 3
EMP 2 -> EMP 4
               EMP 5
               EMP 6
I have implemented a parent child hierachy and it works fine and i am trying to implement a row level security. Can you please advice.
1) When emp1 logs in, he/she can able to see all employees
2) When emp2 logs in, he/she can able to see emp2 and the reportees 4,5,and 6
3) When emp3 logs in he can able to only his information.

Value Based Hierarchy in OBI EE

Hello,
In OBI SE we use both value-based and level-based hierarchies. But in EE I can't find an opportunity to use value based hierarchy.
How to use value based hierarchy (parent-child) in OBI EE?

I've done some work with this, and it hasn't been easy going. There is no built-in ability to form a hierarchy of measure columns, at least nothing that can be predefined as the drill for a fact column. For example: I have 220 details of expense that have an exact arrangement with 5 levels and subtotals. Besides the expense detail there are say 4 dimensions, so the expense detail would be the 5th dimension. I have both arrangements in my rpd: 4D and 5D. They can be used together or separately. The 4D basically has 1000's of measures and there is no relationship between them besides the display arrangement in Answers. The 5D has a 5 column dimension that can drill the expense column from Total_Expense down to the 220 rows of detail expense.

Value based hierarchy

Hello forum,
I'm using a value based hierarchy with managers and their employees.
Employees sell products, those sales are a measure in my cube.
Problem is that not only employees sell products but managers as well.
Products sold by managers are not loaded in my sales cube.
Is there a way to get products sold by managers in the cube?
Thank you.

One way to do it is that you can add a virtual node (dummy node) as a child of every manager record in the value based hierarchy and then just hook the facts to this dummy node for getting products sold by managers in the cube. The reason being that the data can be associated with only a leaf node (a node with no children) and i am assuming that all managers have atleast one employee as a child which makes them non-leaf nodes.
Hope this helps,
Swapan.

Preaggregation across value based hierarchy dimension in 11g

Hi All,
I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
Olap Version: 11.2.0.1
AWM version: 11.2.0.1
Thanks

Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
</PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
SELECT PRECOMPUTE_CONDITION
FROM USER_CUBES
WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
</PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1.   This gives you complete control over what is precomputed.   Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server. The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
begin
dbms_cube.import_xml(q'!
<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<Cube Name="MY_CUBE">
    <Organization>
      <AWCubeOrganization>
        <PrecomputeCondition>
          <![CDATA[
           "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
           CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
           CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
           PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
        </PrecomputeCondition>
      </AWCubeOrganization>
    </Organization>
</Cube>
</Metadata>
end;
/

Value based hierarchy 11g question

Hi,
in my BMM i've created a level based hierarchy composed of two levels: TOTAL and Audiologist
Total level is setted as Grand Total level and doesn't have logical columns.
At audiologist level insted i drag and drop two logical columns: Audiologist Code and Audiologist Name
Then i created two keys.
First Key: Audiologist Code - Use to display: None
Second Key: Audiologist Code and Audiologist Name - Use to display : YES
Graphically my hierarchy is as follow:
Total-----
Audiologist
Audiologist Code
Audiologist Name
Now i would like that if i drill down Total appear simultaneously two columns: Audiologist Code and Audiologist Name.
Is it possible? I remember that in 10 it was.
It's quite urgent.
Thanks

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

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

AWM 10.2.0.1 - I can not choosing Value Based hierarchy

I have Oracle client 10.2.0.1 software with AWM 10.2.0.1 . I want to build a dimension with value-based hierarchy . In AWM I have hierarchy editor with the two radio buttons for choosing type of hierachy : Level Based hierarchy and Value Based hierarchy . But the secod one (Value Based hierarchy) is disabled - I can not choosing this type of hierarchy . Why this?
Thanks in advance,
Aurel

Hi there,
I really would not recommend that you work with the 10.2.0.1 version of AWM. This version is fairly old now and there have been a number of important bug fixes added to more recent releases.
What version of the Oracle database are you running? And on what operating system?
I suggest that you consult the following link and ensure that you are working with the versions of BOTH database and AWM that are recommended by Oracle:
http://www.oracle.com/technology/products/bi/olap/collateral/olap_certification.html
Thanks
Stuart

Owb dimenion value based hierarchy

Hi,
I am looking for some documention or an example to create value based hierarchy in owb 11g r2. Under what condition value based hierarchy should be created and under what condition level based hierarchy should be created

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

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.

Parent-child hierarchy (Value based hierarchy)

Similar Messages

Maybe you are looking for