Parent-Child hierarchy based on two-column key

Hello
Is it possible to create a parent-child hierarchy, if the primary key of the table consists of two columns?
My table looks like:
TRACE_ID | DIAG_ID | SUPER_DIAG_ID
with TRACE_ID and DIAG_ID as PK.
If I define only DIAG_ID as PK, I can add a logical dimension (PC-hierarchy) without problems.
However when I also add TRACE_ID to my PK, I cannot select a member key in the new logical dimension window and therefore not create a logical dimension.
Is this a limitation of OBIEE and I have to merge the two colums (which would be rather bad, as there are FK relations to DIAG_ID) or is there a solution?
Regards
Matthias

Dear Gowtham ,
I am very well aware of the level based hierarchy available in BO .
The issue that i have raised is all about the Parent Child Hierarchy which creates the recursive query.
I.e Every Parent has a child and that child can be parent of some other . (See the original example for more illustration)

Similar Messages

Parent-child hierarchy and fragmentation content

Hello,
I've tried to build simple model with OBIEE 11 using Oracle 11r2 as a data source. BMM has fragmentation content for fact table and few dimensions with different hierarchy types. It works fine with all hierarchy types except for parent child.
When I build an answer with parent child hierarchy it terminates with error "Target data source does not support the operation".
Does OBIEE 11 not support parent child with fragmentation content? Or am I missing something?
Greetings
Marcin

I'm seeing the same issue. I've created a parent-child hierarchy along with two normal level-based hierarchies (one "normal", one skipped-level). The two level-based hierarchies work just fine in Answers. I can include them in the criteria, and data is displayed with the correct drilldowns.
If I include the parent-child hierarchy, I get the same results as noted in the original post: "The layout of this view combined with the data, selections, or drills, or prompt values chosen, resulted in no data." I'm trying to look at the table view, with no filters.
Interestingly, I can explicitly include that dimension's Parent column and Member column in the criteria, and data is displayed just fine.
Here is the XML for the set of criteria that includes the separate Parent and Member columns (the one that works):
SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10, s_11 FROM (
SELECT
0 s_0,
"Retro_Biz"."Channels"."MEMBER" s_1,
"Retro_Biz"."Channels"."PARENT" s_2,
"Retro_Biz"."Products"."TOTAL_PRODUCT" s_3,
"Retro_Biz"."Times"."YEAR" s_4,
SPACE(1) s_5,
SPACE(1) s_6,
SPACE(1) s_7,
IDOF("Retro_Biz"."Products"."Product"."Total Product") s_8,
IDOF("Retro_Biz"."Times"."Time"."Year") s_9,
"Retro_Biz"."Facts"."SALES" s_10,
CAST(NULL AS DOUBLE) s_11
FROM "Retro_Biz"
UNION ALL
SELECT
1 s_0,
"Retro_Biz"."Channels"."MEMBER" s_1,
"Retro_Biz"."Channels"."PARENT" s_2,
SPACE(1) s_3,
SPACE(1) s_4,
SPACE(1) s_5,
SPACE(1) s_6,
SPACE(1) s_7,
SPACE(1) s_8,
SPACE(1) s_9,
CAST(NULL AS DOUBLE) s_10,
REPORT_SUM("Retro_Biz"."Facts"."SALES" BY ) s_11
FROM "Retro_Biz"
) djm ORDER BY 1, 5 ASC NULLS FIRST, 4 ASC NULLS FIRST
Here is the XML that includes the Parent-Child hierarchy (the one that fails):
SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10, s_11, s_12 FROM (
SELECT
0 s_0,
"Retro_Biz"."Channels"."MEMBER" s_1,
"Retro_Biz"."Products"."TOTAL_PRODUCT" s_2,
"Retro_Biz"."Times"."YEAR" s_3,
CASE WHEN ISLEAF("Retro_Biz"."Channels"."Channel") THEN 1 ELSE 0 END s_4,
IDOF("Retro_Biz"."Channels"."Channel") s_5,
SPACE(1) s_6,
SPACE(1) s_7,
SPACE(1) s_8,
IDOF("Retro_Biz"."Products"."Product"."Total Product") s_9,
IDOF("Retro_Biz"."Times"."Time"."Year") s_10,
PARENT("Retro_Biz"."Channels"."Channel") s_11,
"Retro_Biz"."Facts"."SALES" s_12
FROM "Retro_Biz"
WHERE
ISROOT("Retro_Biz"."Channels"."Channel")
UNION ALL
SELECT
1 s_0,
SPACE(1) s_1,
SPACE(1) s_2,
SPACE(1) s_3,
CAST(NULL AS INTEGER) s_4,
SPACE(1) s_5,
SPACE(1) s_6,
SPACE(1) s_7,
SPACE(1) s_8,
SPACE(1) s_9,
SPACE(1) s_10,
SPACE(1) s_11,
"Retro_Biz"."Facts"."SALES" s_12
FROM "Retro_Biz"
WHERE
ISROOT("Retro_Biz"."Channels"."Channel")
) djm ORDER BY 1, 4 ASC NULLS FIRST, 3 ASC NULLS FIRST

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.

No data for Parent-child hierarchy column in Pivot table view

Hi all,
I used OBIEE 11.1.1.6.2 Version.
I drag one Parent-child hierarchy column and one measure and show result with a pivot table view.
But when I click "+" icon to show detail level data,
It messaged that: "*the layout of this view combined with the data,selections,drills,or prompt values chosen resulted in no data*."
But it can show every-level data when I used table view.
It was so strange..
Did anybody meet this before?
Thanks in advance.
regards,
Anne

Hi,
Yes, I have the same problem with pivot table for hierarchy dimension.
If you use a normal table (not pivot) it seem to work. Unfortunatley with restrictions as normal table view have.
Same problem still exist in 11.1.1.6.5
I have logged a SR to Oracle about this.

Want to flatten my parent-child hierarchy into an level-based hierarchy.

Hi Expert,
Can anyone let me know how I can convert my parent-child hierarchy into an LEVEL-based hierarchy.
Thanks in Advance
S

If you have an Oracle DB have a look on the CONNECT BY PRIOR functionality.
regards
John
http://obiee101.blogspot.com

OBIEE 11g Parent Child hierarchy

Hi,
I'm trying to setup a parent-child hierarchy dimension. I have setup a new hierarchy dimension using numeric keys but want to display another field in the hierarchical column on a report e.g. employee fullname & not the member_key based on a numeric value. Can this be done & how do you do it? All the examples I have seen use varchar2 type columns as the keys to do this.
Thanks in advance, Phil
My Setup
=============
Dimension - logical level
===============
member key = employee_id
parent-child table source
===============
member key = employee_id
parent key = supervisor_id
relationship distance = levels_removed
leaf node identifier = isleaf
Employee logical folder
==============
employee_id ( number)- primary key
full_name (varchar2) - unique key
supervisor_id ( number)
Closure table
=========
employee_id ( number)
supervisor_id ( number)
level ( number)
isleaf ( number)

Thanks for the link Suresh but the aggregations are working correctly.
My problem is only at the display level. I need to create a dashboard that displays the complete hierarchy.
So for example if I have this hierarchy:
- Steven King
- Adam Frip
Alexis Bull
Anthony Cabrio
Alberto Erraruriz
Den Raphaely
I want the dashboard to display immediately that complete hierarchy. If someone adds a member to the hierarchy in the database, the dashboard should display this new member without having to manually modify the dashboard.
- Steven King
- Adam Frip
Alexis Bull
Anthony Cabrio
- Alberto Erraruriz
Mozhe Atkinson
Den Raphaely
Also, if I just manually open the hierarchy and save the dashboard, if "Steven King" is replaced by "Shanta Vollman", the dashboard doesn't like it and returns a result looking like:
- Adam Frip
Alexis Bull
Anthony Cabrio
- Alberto Erraruriz
Mozhe Atkinson
Den Raphaely
+ Shanta Vollman
So I'm looking for some option that will tell OBIEE to open the hierarchy without having to specify "Drill down on member "Steven King"", "Drill down on member "Adam Frip"...
I hope I'm explaining correctly...

Parent Child Hierarchy causes numbers to be different

Hello,
We have a parent child hierarchy in our chart of account dimensions. When the hierarchy is included in an analysis, the numbers are correct. If the hierarchy is not included in the analysis and a column from the dimension with the hierarchy is included, the numbers are very different. They are overstated by a large amount.
For Example, I have two analysis:
-In the first analysis the hierarchy is included and the grand total is 2,383,080,784.
-The second analysis has simply excluded the hierarchy from the analysis and the total shoots all the way up to 6,901,729,527.
I have screen shots but don't know how to include them in this kind of a post.
Has anybody else seen such behavior? This seems like it would be a big deal so either we are doing something wrong or this is a bug that needs fixed.
We are on 11.1.1.6
Thanks in advance,
Brian

Hi,
Thanks for the reply, I'm actually using snapshots. But even with the Type 2 Dim I don't think it will work.
When OBIEE generates the very first sql against the Parent-Child table the fact table is not included in the query. It seems to create 2 queries - one to find the top level parent (ancestor key is null) and then one to find all the leaf nodes.
It does not have any join to the fact table when it does this. So if you have multiple rows in the table (with date stamps) for a single row (person in this case) - it picks up both rows. Therefore, when you have a person who was, say, promoted to manager, and WAS a leaf node, and is now a manager, they show up in the leaf query and don't display in the hierarchy as a manager.
Once it has the leaf nodes and it joins to the fact table everything works (ie the surrogate key join).
I'm trying to figure out if there is any way to influence those initial queries against the parent-child table.
Hopefully that made sense.
Thanks,
Tori

Parent Child Hierarchy Issue in OBIEE 11g

Hi All,
I am in OBIEE 11G v6. I have a sales fact table where the grain is one sale. So I have one row for every sale done.
Now I have a ragged employee hierarchy like this with David at the root node.
David >>Richard>>Sean
David >>James
Also, I have a role dimension which gives me what role each employee has performed on a sale. Only one employee can be associated with one sale. This is the way Roles have been asssigned
David = Manager
Richard = Off1
Sean = Off2
James = Off2
Both Sean and James can have same Roles. Now I have created a parent child hierarchy for my employee dimension and the closure table. Defined the member key, ancestor key relationship in the parent child setting etc.
Now in the report when I pull the parent child hierarchy and the sales_amount in the report, it comes out perfect with all the ragged hierarchy resolved. But the issue comes when I try to limit the report on Role = Off2. It gives me an error saying " The layout of this view combined with the data, selection , drills resulted in no data. Undo drill and view prompt values". Basically what i want is to be able to select any role type and then my hierarchy should be adjusted to show me that data. Like when I select Off2, I want to see David at the Top level and Sean and James under him because they are both Off 2 and David is their manager.
Is that possbile? Also, am I getting this error because when I select Off2 though it gets Sean and James but since David is not Off2, I don't get the data?
I hope I was able to explain the issue, any help on this would be greatly appreciated.
Thanks
Ronny

So basically this means that if I build a parent child hierarchy on table A having the stucture like
--David (Manager)
-----James (Off1)
--------Bill (Off2)
and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

Parent Child Hierarchy for Type 2

I have read the articles on Parent Child hierarchy setup in OBIEE 11g, however, most are based on what seems to be a current snapshot of the Employee-Manager relationship. Has anyone tried to build out a Parent-Child hierarchy/table off a Type 2 dimension. Being able to navigate what the hierarchy may have been on a specific date.
I would welcome any feedback, thanks.

Hi,
Thanks for the reply, I'm actually using snapshots. But even with the Type 2 Dim I don't think it will work.
When OBIEE generates the very first sql against the Parent-Child table the fact table is not included in the query. It seems to create 2 queries - one to find the top level parent (ancestor key is null) and then one to find all the leaf nodes.
It does not have any join to the fact table when it does this. So if you have multiple rows in the table (with date stamps) for a single row (person in this case) - it picks up both rows. Therefore, when you have a person who was, say, promoted to manager, and WAS a leaf node, and is now a manager, they show up in the leaf query and don't display in the hierarchy as a manager.
Once it has the leaf nodes and it joins to the fact table everything works (ie the surrogate key join).
I'm trying to figure out if there is any way to influence those initial queries against the parent-child table.
Hopefully that made sense.
Thanks,
Tori

Parent Child Hierarchy in OBIEE 11G

Hi All,
I am working on the parent child hierarchy in OBIEE 11g Source ESSBASE ..followed some of the blogs.
http://www.rittmanmead.com/2010/07/obiee-11gr1-enhancements-to-essbase-support/
I followed the following steps.
1.Imported the Cubes from ESSBASE.
2.Selected Accounts Hirearchy and changed the Hierarchy type to Value.
3.Dragged the subject area to BMM and to Presentation.
4.Now when i checked the Account Hierarchy from in the dashboard its not drilling down.
If i change the Hierarchy type to Unbalanced ...then the Account hiearchy is working fine.
Is there is any settings or process i have to follow..inorder to implement the Value based Hierarchy in OBIEE 11G source ESSBASE.
Thanks

So basically this means that if I build a parent child hierarchy on table A having the stucture like
--David (Manager)
-----James (Off1)
--------Bill (Off2)
and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

Parent Child Hierarchy Issue

Guys,
I have a parent-child hierarchy and users would select a randomn level from the prompt (Hierarchical column used in the prompt). So for the level selected I need to capture all the leaves and put a top n function on them.. Any ideas??
Things that i have tried are using Selection steps with hierarchical columns.
Step 1: Start with all Memebers
New step: Step 2 is Selected Members based on hierarchy relation Ship (Keep only members of leaves of hierarchy)
But the problem is I am not able to override the Step -2 with dashboard prompt. I was able to do only fior STEP -1
So any ideas??
If i can atleast capture all the leaves of selecte level from the prompt that would solve my problem to a large extent?/ Thought abt Hierarchical Navigation Functions but didnt succeed?? Any suggestions really appreciated
Thanks..
Prash
Edited by: Prash11 on Aug 6, 2012 11:14 AM

I have got lot of hierarchies which are atleast 20 levels deep. So its not really feasible for me to create multiple views for multiple levels.
I tried to use hierarchical column functions and it works but not able to override the values from prompts in the selection steps. So still trying few things
Step 1: Start with All members (over ride with prompt checked)
Step 2: Select a level with in the hierarchy and Keep only leaves of the selected level
Step 3: Apply Condition do a TOP 10 and keep only that result set.
This works fine with out any issues from an ad-hoc stand point. Only problem there is no way for me to over ride the dashboard prompt value in Step - 2 as it expects me to select a value from the hierarchy. Any alternativeS?

Parent Child Hierarchy (N Level Hierarchy ) in BI 4.0

Hi ,
We have following table structure . We are trying to create parent-child hierarchy and implement drill on the same .
We are using Oracle database as RDBMS.
e.g.
Child Key    Parent Key
1
2                 1
3                 1
4                 2
5                 2
6                 3
7                 1
8                 5
Now based on this table structure , if we create hierarchy using parent key and child key , we should be able to drill from 1 to {2,3,7} directly.
further when i click on 2 , we should get {4,5 } as resulting rows.
At the same time drill-down should not work on the values which are not parent of anyone (i.e. Leaf Node). e.g. 4, 8, 7, 6.
Can anyone please let me know how can i achieve the same result by building hierarchy or any work around ?
Regards ,
Jeevan Chaudhari

Dear Gowtham ,
I am very well aware of the level based hierarchy available in BO .
The issue that i have raised is all about the Parent Child Hierarchy which creates the recursive query.
I.e Every Parent has a child and that child can be parent of some other . (See the original example for more illustration)

Parent Child hierarchy Scenario

Hi friends,
Im just working on the parent child hierarchy using the following link with the sample data.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/biadmin11g_02/biadmin11g.htm_
I tried to implement the same hierarchy using my local data instead of referring to the sample data.
I have a below query which returns the employee with manager along with the employee position
select distinct papf.person_id, papf.full_name "Employee Name", supf.person_id "Manager Id", supf.full_name "Manager Name", pj.name "Position Name"
from per_all_people_f papf, per_all_assignments_f paaf, per_all_people_f supf, per_jobs pj
where papf.person_id = paaf.person_id and supf.person_id = paaf.supervisor_id and paaf.job_id = pj.job_id
and trunc(sysdate) between paaf.effective_start_date and paaf.effective_end_date and
trunc(sysdate) between papf.effective_start_date and papf.effective_end_date
Im looking forward to implement the same result in my BI with a parent-child hierarchy.
Since i have imported three tables to my physical layer
per_all_people_f------------Dimension
per_all_assignments_f-----Fact
per_jobs---------------------DimensionFor creating parent-child in BI, we need to have a separate Parent child table which consist of four columns like ancestorkey, memberkey, distance, leaf.
From the above column i can understand the meaning like
For Ancestorkey-->Managerid
Memberkey------->Employeeid
But i couldnt get with the meaning for distance column as the meaning suggest like a distance b/w the two and leaf column as the meaning suggest like a leaf member. which leaf member does it refer.
I also referred the below link then too couldnt get the meaning for it
http://www.rittmanmead.com/2010/08/oracle-bi-ee-11g-parent-child-hierarchies-differing-aggregations/+
How i can form the parent child table for the BI from my above three tables of HRMS.
Thanks
Regards,
Saro

Hi friends,
I think i found a link of doing it
http://prasadmadhasi.com/2011/11/15/hierarchies-parent-child-hierarchy-in-obiee-11g/
Let me try this and will update accordingly.
Thanks for your views.
Regards,
Saro

HELP: how to build a parent-child hierarchy

Hy everyone,
my question is very basic: i need to know what is the structure of the relational tables that OBIEE accepts upon which i can build a parent-child hierarchy. I have data that OBIEE does not accept, do you know where i can find a clear description of the structure of the tables that has to be builded for creating correctly a parent-child hierarchy?
Thanks anyone a lot,
Regards

I've found what i needed, for everyone else:
http://docs.oracle.com/cd/E21043_01/bi.1111/e10540/dimensions.htm#BGBGACFJ
The parent-child relationship table must include four columns, as follows:
•A column that identifies the member
•A column that identifies an ancestor of the member. Note: The ancestor may be the parent of the member, or a higher-level ancestor.
•A "distance" column that specifies the number of parent-child hierarchical levels from the member to the ancestor
•A "leaf" column that indicates if the member is a leaf member (1=Yes, 0=No)
The column names can be user defined. The data types of the columns must satisfy the following conditions:
•The member and ancestor identifier columns have the same data type as the associated columns in the logical table that contains the hierarchy members. Note that the example shown in Table 9-1 uses text strings for readability, but you normally use integer surrogate keys for member_key and ancestor_key, if they exist in the source dimension table.
•The "distance" and "leaf" columns are INTEGER columns.
Note the following about the rows in a parent-child relationship table:
•Each member must have a row pointing at itself, with distance zero.
•Each member must have a row pointing at each of its ancestors. For a root member, this is a termination row with null for the parent and distance values.

How to update a parent child hierarchy in OBIEE

Hello All
Quick question about updating parent child hierarchy in OBIEE.
As we know, OBIEE 11G allows us to create value based hierarchy by generating table creation script and insert script. In the typical example of employee dimension, the parent child relationship table will be created with the following 4 attributes:
MEMBER_KEY, ANCESTOR_KEY, DISTANCE, IS_LEAF
So, what if later in the years some of the employees got promoted, retired or transferred? The value based hierarchy is going to change because person 1 reports to manager 2 now instead of 1. Obviously, the records in employee dimension is going to be updated. When that happens, how to update the parent child relation table with the same information? Do we have to rerun the insert script? How do we keep the history of employee changes and hierarchy changes?
Please advice
Thank you

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

Parent-Child hierarchy based on two-column key

Similar Messages

Maybe you are looking for