Empty parent-child hierarchy if a date attribute is "1800-01-01 00:00:00.000"!

I have an Employees dimension that contains a parent-child hierarchy as the supervisor->employees (Org. chart. starts from the CEO to the lowest level of employees). The hierarchy is built on a relation between the employee_id (as the primary and
surrogate key) and supervisor_id (as a foreign key). There are many other attributes in this dimension one of them is the Termination_Date. The value for Termination_Date for the current employees in the source
system is "1800-01-01 00:00:00.000" (which is also the default value). The weird thing is that keeping this value in the employee dimension will cause the previously mentioned parent-child hierarchy to show nothing! if I change it to any other
value or NULL, the hierarchy works fine and shows the expected tree of employees!
I can change "1800-01-01 00:00:00.000" to Null in the ETL stage and solve the problem, but I want really to know what causes this ? why ?!

Similar Messages

Parent-Child Hierarchy Show No Data

Hi:
OBIEE 11.1.1.6.5
I created a parent-child hierarchy following multiple examples in books and on the web. I can pull the presentation hierarchy--by itself--into a view and drill up and down. But when I add a measurement from the fact table, I receive a no data found error. I copied the SQL into SQL*Developer and ran it, and it too returned no data. I've tried to read and debug the query in SQL*Developer, but I don't understand what it is doing.
The dimension table I am using for the parent-child hierarchy has a cost_Center_id and parent_cost_center_id. I used the Parent-Child dimension wizard to create and populate the new hierarchy table.
I can create a view by using the cost_center item and a fact table measurement without the presentation hierarchy, so it has something to do with the presentation hierarchy.
I've been at this for a few days now, and I've run out of ideas. Can anyone suggest what I may have done wrong?
Thanks.

check if there is data in the fact table.. Next check also if the join condition between the dimension and fact is valid.

Essbase Studio (parent-child hierarchy + attributes)

There is a problem with the parent-child hierarchy and attributes (for example, structural units of the enterprise).
Composition data (source - table in Oracle):
id (ID of the structural unit - a surrogate key, it is PK)
idParent (ID of the parent structural unit)
code (code of the structural unit - the natural key)
name (the name of the structural unit)
type (type of structural unit)
address (address structural unit)
In this case, parent-child relationship is defined fields idParent -> id, all the rest - should serve as attributes for the various disclosures in the reports.
In all the examples that are found in the network, parent-child built without creating attributes, and it really works. But how "to enrich" the attributes of a hierarchy - and sample solutions are not found.
Most requested help: link, advice, examples from life, either by pointing out that "so definitely not!".

Dear guru of essbase,
I am quite sure that this problem can still be solved by Essbase Studio.
I can not believe that the Studio developers could not include this feature. It is very important to resolve this issue it is through this component, help please both. Thanks

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.

Sub Total value is empty in parent child hierarchy pivot table

Hi All,
I am using obiee 11.1.1.6.2 in Test environment. Is it a known issue/bug for 11.1.1.6.2 to show empty/blank values for sub total when using parent child hierarchy pivot table. The sub total for parent value is showing but sub total for child value is coming blank. However, in 11.1.1.5.0, we do not have any issue with this.
Is it a known bug in obiee 11.1.1.6.2?
Thanks,
Sushil

Yes it is a known bug...
Thanks.

Hide parents in a parent-child hierarchy with dynamic rights

Hi all,
I'm facing the following issue with dynamic rights on a parent-child hierarchy:
scenario:
- a cube with a company parent-child hierarcy
- dynamic security on through a role on dimension data based on a list with user (login names) and their
departments, with Enable
Visual Total is switched ON
- Multiple facts connected to this hierarchy.
When a user connects to the cube (in this case with Excel or through a dashboard in Performance Point services) he/she is allowed to see the facts belonging to theirs departments and all child departments, so far so good. But the totals of the facts are
repeated for all higher parents. Now i know thats nog 'wrong' but our users think thats very confusing in some cases, so is there a way
- to hide the parents in the hierarhcy
- or to set all the parent measures to null/empty?
I prefer to make a solution in the cube so that all client programs can benefit from this solution.
thanx in advance for all input!

so that User A have scope: [Dimension_Name].[Attribute XYZ] and User B: [Dimension_Name].[Attribute ABC] ?
Hi Wilfred,
If I understanding correctly, you want different user can see different dimension attributes based on the different right on role, right?
Based on my research, it seems that there is no a directly way to achieve this requirement. What we can do is that "Deselect all members" for each attribute of the dimension in Dimension Data tab, which will hide all members of the dimension for the role.
Even the dimension metadata is visible in the cube in clients, its members can't be seen. Here are some useful links for your reference.
http://saysmymind.wordpress.com/2013/01/15/hide-a-specific-attribute-hierarchy-in-role-playing-dimension-ssas-multidimensional/
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/e2596eec-7c2d-48c0-8e81-538a8c632360/hide-dimension-based-on-roles
Hope this helps.
Regards,
Charlie Liao
TechNet Community Support

Problem creating standard ECC Parent-Child Hierarchy in HANA

Hi all -
I've been trying to get a hierarchy to work on the front end of a stand alone HANA system using profit center hierarchy data from SETLEAF / SETNODE tables from ECC. Here is how my test hierarchy looks:
Following another post I found around here, I created an attribute view and filtered SETNAME to 'TST_HANA'.
The resulting data when connected to my attribute view caused an error that there was no root node, so I manually inserted the last row shown here (where PCA_PARENT = SETNAME and PCA_CHILD = SUBSETNAME):
Finally, I created my parent-child hierarchy in the attribute view and connected that view to my data foundation in the analytic view via left-outer join between Profit Center and VALFROM. However, when I go to connect to my view via MDX in excel, I get the following message:
"Hierarchy create error: Multiple parents not allowed for hierarchy node TST_ND1" Clearly from the data, there aren't multiple parents for TST_ND1. It's already a pain that to use a standard hierarchy I have to manually insert a root node, but that doesn't even seem to fix the problem.
Can anyone suggest how to fix this to get a standard profit center hierarchy working?
Thank you!
AZ

Hi,
According to me, Hierarchy level will work fine in ms excel for all analytical, calculation view using MDX Provider..
Do you have any composite primary key or composite foreign key in the tables....
r u getting correct level hierarchy output in Hana studio... plz check with all types of permutation possible.if u r getting correct output in analytical view w.r.t hana but fails to get in Ms excel..
please create Calculation view of that.. & then check the output in ms-excel..
Thanks,

Security on Parent-Child Hierarchy

Problem Statement: In Parent Child Hierarchy say with Manager - Employee relationship, if we apply security using Siblings function in the Dimension Data Security (Allowed Member Set) then it displays children of peers at
same level as current employee.
Scenario:
Create Employee Dimension with Parent-Child hierarchy with steps below -
1) add data
===============================
(EmpKey|Name|Position| loginId| level| MgrKey)
1|Scott King|CEO|sking|level1|null
2|Rick Peters|VP|rpeters|level2|1
3|Steve Parker|VP|sparker|level2|1
4|Matt Jones|Dir|mjones|level3|2
5|Doug Blanc|Dir|dblanc|level3|2
6|Jay Lawson|Dir|jlawson|level3|3
7|Lance Roberts|Dir|lroberts|level3|3
============================
2) Create Parent-Child hierarchy on MgrKey with its Usage = Parent
2a)set ValueColumn of Login_ID attribute to EmpKey.
2b) Also set ValueColumn of MgrKey attribute to Login_ID. Rename Parent-child hierarchy to Employees
3) Create Security Role and configure Dimension data security.
In the allowed member set write the below MDX statement.
{ StrToMember( "[Employee].[Employees].&[" + CStr(StrToMember("[Employee].[Login ID].&[" + UserName( ) + "]").MEMBERVALUE) + "]"), StrToMember( "[Employee].[Employees].&["
+ CStr(StrToMember("[Employee].[Login ID].&[" + UserName( ) + "]").MEMBERVALUE) + "]").SIBLINGS }
Expected Result:
Using Siblings function - Ideally if Steve Parker connects to SSAS Cube then he should see his totals, only his subordinate totals, only his Peer's totals(not their subordinates) and his manager's totals.
Actual Result:
Due to above Dimension Security configuration, if Steve Parker connects to SSAS Cube then he will see his totals, his subordinate totals and his manager's totals. However due to Siblings function "Steve Parker" is also able to see
Rick Peters's subordinate details.
Query: Is there a way to achieve the Expected Result by restricting the children of Siblings?

Hi Ketan,
Thank you for your question. I am currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.
Regards,
Elvis Long
TechNet Community Support

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 ?

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,

Dynamic hierarchy in parent child hierarchy table??

Do you have any experience to handle the requirement of dynamic hierarchy in universe/webi?
We have some data in parent child hierarchy as below u201CCustomeru201D table.
Customer
Parent          Child
Z                  A
Z                  B
A                  AA
B                  BB
AA               AAA
For example, Company Z is the parent company of Company A.
Another table, Amount is the amount value of different Customers.
Amount
ID               Amt
AA               10
AAA            1
BB                2
Is there any functionality in Universe designer to build related Classes and objects, So that the web intelligence documents represent the following report with the drilling results?
When we want to see the ID and Amt, the expected result should be:
Z                13
when we drill down Z
the result should be:
A                11
B                2
when we drill down A:
the result should be:
AA              11
notes **
the level of hierarchy is dynamic
Any suggestion is appreciated. Thanks.

Hi,
The only way to do it is to create recursive derived table that flatten you parent child hierarchy with a given maximum depth.
Here is a sample I built a long time ago to flatten a parent-child hierarchy on Employees table in Foodmart database (SQL Server).
Didier
SELECT DISTINCT
     Z.employee_id,
     A.supervisor_id_1,
     A.employee_id_1,
     A.full_name_1,
     A.supervisor_id_2,
     A.employee_id_2,
     A.full_name_2,
     A.supervisor_id_3,
     A.employee_id_3,
     A.full_name_3,
     A.supervisor_id_4,
     A.employee_id_4,
     A.full_name_4,
     A.supervisor_id_5,
     A.employee_id_5,
     A.full_name_5,
     A.supervisor_id_6,
     A.employee_id_6,
     A.full_name_6,
     Z.supervisor_id AS supervisor_id_7,
     Z.employee_id AS employee_id_7,
     Z.full_name AS full_name_7
FROM employee Z,
     SELECT DISTINCT
          A.supervisor_id_1,
          A.employee_id_1,
          A.full_name_1,
          A.supervisor_id_2,
          A.employee_id_2,
          A.full_name_2,
          A.supervisor_id_3,
          A.employee_id_3,
          A.full_name_3,
          A.supervisor_id_4,
          A.employee_id_4,
          A.full_name_4,
          A.supervisor_id_5,
          A.employee_id_5,
          A.full_name_5,
          Z.supervisor_id AS supervisor_id_6,
          Z.employee_id AS employee_id_6,
          Z.full_name AS full_name_6
     FROM employee Z,
          SELECT DISTINCT
               A.supervisor_id_1,
               A.employee_id_1,
               A.full_name_1,
               A.supervisor_id_2,
               A.employee_id_2,
               A.full_name_2,
               A.supervisor_id_3,
               A.employee_id_3,
               A.full_name_3,
               A.supervisor_id_4,
               A.employee_id_4,
               A.full_name_4,
               Z.supervisor_id AS supervisor_id_5,
               Z.employee_id AS employee_id_5,
               Z.full_name AS full_name_5
          FROM employee Z,
               SELECT DISTINCT
                    A.supervisor_id_1,
                    A.employee_id_1,
                    A.full_name_1,
                    A.supervisor_id_2,
                    A.employee_id_2,
                    A.full_name_2,
                    A.supervisor_id_3,
                    A.employee_id_3,
                    A.full_name_3,
                    Z.supervisor_id AS supervisor_id_4,
                    Z.employee_id AS employee_id_4,
                    Z.full_name AS full_name_4
               FROM employee Z,
                    SELECT DISTINCT
                         A.supervisor_id_1,
                         A.employee_id_1,
                         A.full_name_1,
                         A.supervisor_id_2,
                         A.employee_id_2,
                         A.full_name_2,
                         Z.supervisor_id AS supervisor_id_3,
                         Z.employee_id AS employee_id_3,
                         Z.full_name AS full_name_3
                    FROM employee Z,
                         SELECT DISTINCT
                              A.supervisor_id_1,
                              A.employee_id_1,
                              A.full_name_1,
                              Z.supervisor_id AS supervisor_id_2,
                              Z.employee_id AS employee_id_2,
                              Z.full_name AS full_name_2
                         FROM employee Z,
                              SELECT DISTINCT
                                   supervisor_id AS supervisor_id_1,
                                   employee_id AS employee_id_1,
                                   full_name AS full_name_1
                               FROM employee
                               WHERE supervisor_id = 0 OR supervisor_id IS NULL
                         ) A
                         WHERE A.employee_id_1 = Z.supervisor_id
                    ) A
                    WHERE A.employee_id_2 = Z.supervisor_id
               ) A
               WHERE A.employee_id_3 = Z.supervisor_id
          ) A
          WHERE A.employee_id_4 = Z.supervisor_id
     ) A
     WHERE A.employee_id_5 = Z.supervisor_id
) A
WHERE A.employee_id_6 = Z.supervisor_id
UNION
SELECT DISTINCT
     A.employee_id_6 AS employee_id,
     A.supervisor_id_1,
     A.employee_id_1,
     A.full_name_1,
     A.supervisor_id_2,
     A.employee_id_2,
     A.full_name_2,
     A.supervisor_id_3,
     A.employee_id_3,
     A.full_name_3,
     A.supervisor_id_4,
     A.employee_id_4,
     A.full_name_4,
     A.supervisor_id_5,
     A.employee_id_5,
     A.full_name_5,
     A.supervisor_id_6,
     A.employee_id_6,
     A.full_name_6,
     NULL AS supervisor_id_7,
     NULL AS employee_id_7,
     NULL AS full_name_7
FROM employee Z,
     SELECT DISTINCT
          A.supervisor_id_1,
          A.employee_id_1,
          A.full_name_1,
          A.supervisor_id_2,
          A.employee_id_2,
          A.full_name_2,
          A.supervisor_id_3,
          A.employee_id_3,
          A.full_name_3,
          A.supervisor_id_4,
          A.employee_id_4,
          A.full_name_4,
          A.supervisor_id_5,
          A.employee_id_5,
          A.full_name_5,
          Z.supervisor_id AS supervisor_id_6,
          Z.employee_id AS employee_id_6,
          Z.full_name AS full_name_6
     FROM employee Z,
          SELECT DISTINCT
               A.supervisor_id_1,
               A.employee_id_1,
               A.full_name_1,
               A.supervisor_id_2,
               A.employee_id_2,
               A.full_name_2,
               A.supervisor_id_3,
               A.employee_id_3,
               A.full_name_3,
               A.supervisor_id_4,
               A.employee_id_4,
               A.full_name_4,
               Z.supervisor_id AS supervisor_id_5,
               Z.employee_id AS employee_id_5,
               Z.full_name AS full_name_5
          FROM employee Z,
               SELECT DISTINCT
                    A.supervisor_id_1,
                    A.employee_id_1,
                    A.full_name_1,
                    A.supervisor_id_2,
                    A.employee_id_2,
                    A.full_name_2,
                    A.supervisor_id_3,
                    A.employee_id_3,
                    A.full_name_3,
                    Z.supervisor_id AS supervisor_id_4,
                    Z.employee_id AS employee_id_4,
                    Z.full_name AS full_name_4
               FROM employee Z,
                    SELECT DISTINCT
                         A.supervisor_id_1,
                         A.employee_id_1,
                         A.full_name_1,
                         A.supervisor_id_2,
                         A.employee_id_2,
                         A.full_name_2,
                         Z.supervisor_id AS supervisor_id_3,
                         Z.employee_id AS employee_id_3,
                         Z.full_name AS full_name_3
                    FROM employee Z,
                         SELECT DISTINCT
                              A.supervisor_id_1,
                              A.employee_id_1,
                              A.full_name_1,
                              Z.supervisor_id AS supervisor_id_2,
                              Z.employee_id AS employee_id_2,
                              Z.full_name AS full_name_2
                         FROM employee Z,
                              SELECT DISTINCT
                                   supervisor_id AS supervisor_id_1,
                                   employee_id AS employee_id_1,
                                   full_name AS full_name_1
                               FROM employee
                               WHERE supervisor_id = 0 OR supervisor_id IS NULL
                         ) A
                         WHERE A.employee_id_1 = Z.supervisor_id
                    ) A
                    WHERE A.employee_id_2 = Z.supervisor_id
               ) A
               WHERE A.employee_id_3 = Z.supervisor_id
          ) A
          WHERE A.employee_id_4 = Z.supervisor_id
     ) A
     WHERE A.employee_id_5 = Z.supervisor_id
) A
UNION
SELECT DISTINCT
     A.employee_id_5 AS employee_id,
     A.supervisor_id_1,
     A.employee_id_1,
     A.full_name_1,
     A.supervisor_id_2,
     A.employee_id_2,
     A.full_name_2,
     A.supervisor_id_3,
     A.employee_id_3,
     A.full_name_3,
     A.supervisor_id_4,
     A.employee_id_4,
     A.full_name_4,
     A.supervisor_id_5,
     A.employee_id_5,
     A.full_name_5,
     NULL AS supervisor_id_6,
     NULL AS employee_id_6,
     NULL AS full_name_6,
     NULL AS supervisor_id_7,
     NULL AS employee_id_7,
     NULL AS full_name_7
FROM employee Z,
     SELECT DISTINCT
          A.supervisor_id_1,
          A.employee_id_1,
          A.full_name_1,
          A.supervisor_id_2,
          A.employee_id_2,
          A.full_name_2,
          A.supervisor_id_3,
          A.employee_id_3,
          A.full_name_3,
          A.supervisor_id_4,
          A.employee_id_4,
          A.full_name_4,
          Z.supervisor_id AS supervisor_id_5,
          Z.employee_id AS employee_id_5,
          Z.full_name AS full_name_5
     FROM employee Z,
          SELECT DISTINCT
               A.supervisor_id_1,
               A.employee_id_1,
               A.full_name_1,
               A.supervisor_id_2,
               A.employee_id_2,
               A.full_name_2,
               A.supervisor_id_3,
               A.employee_id_3,
               A.full_name_3,
               Z.supervisor_id AS supervisor_id_4,
               Z.employee_id AS employee_id_4,
               Z.full_name AS full_name_4
          FROM employee Z,
               SELECT DISTINCT
                    A.supervisor_id_1,
                    A.employee_id_1,
                    A.full_name_1,
                    A.supervisor_id_2,
                    A.employee_id_2,
                    A.full_name_2,
                    Z.supervisor_id AS supervisor_id_3,
                    Z.employee_id AS employee_id_3,
                    Z.full_name AS full_name_3
               FROM employee Z,
                    SELECT DISTINCT
                         A.supervisor_id_1,
                         A.employee_id_1,
                         A.full_name_1,
                         Z.supervisor_id AS supervisor_id_2,
                         Z.employee_id AS employee_id_2,
                         Z.full_name AS full_name_2
                    FROM employee Z,
                         SELECT DISTINCT
                              supervisor_id AS supervisor_id_1,
                              employee_id AS employee_id_1,
                              full_name AS full_name_1
                          FROM employee
                          WHERE supervisor_id = 0 OR supervisor_id IS NULL
                    ) A
                    WHERE A.employee_id_1 = Z.supervisor_id
               ) A
               WHERE A.employee_id_2 = Z.supervisor_id
          ) A
          WHERE A.employee_id_3 = Z.supervisor_id
     ) A
     WHERE A.employee_id_4 = Z.supervisor_id
) A
UNION
SELECT DISTINCT
     A.employee_id_4 AS employee_id,
     A.supervisor_id_1,
     A.employee_id_1,
     A.full_name_1,
     A.supervisor_id_2,
     A.employee_id_2,
     A.full_name_2,
     A.supervisor_id_3,
     A.employee_id_3,
     A.full_name_3,
     A.supervisor_id_4,
     A.employee_id_4,
     A.full_name_4,
     NULL AS supervisor_id_5,
     NULL AS employee_id_5,
     NULL AS full_name_5,
     NULL AS supervisor_id_6,
     NULL AS employee_id_6,
     NULL AS full_name_6,
     NULL AS supervisor_id_7,
     NULL AS employee_id_7,
     NULL AS full_name_7
FROM employee Z,
     SELECT DISTINCT
          A.supervisor_id_1,
          A.employee_id_1,
          A.full_name_1,
          A.supervisor_id_2,
          A.employee_id_2,
          A.full_name_2,
          A.supervisor_id_3,
          A.employee_id_3,
          A.full_name_3,
          Z.supervisor_id AS supervisor_id_4,
          Z.employee_id AS employee_id_4,
          Z.full_name AS full_name_4
     FROM employee Z,
          SELECT DISTINCT
               A.supervisor_id_1,
               A.employee_id_1,
               A.full_name_1,
               A.supervisor_id_2,
               A.employee_id_2,
               A.full_name_2,
               Z.supervisor_id AS supervisor_id_3,
               Z.employee_id AS employee_id_3,
               Z.full_name AS full_name_3
          FROM employee Z,
               SELECT DISTINCT
                    A.supervisor_id_1,
                    A.employee_id_1,
                    A.full_name_1,
                    Z.supervisor_id AS supervisor_id_2,
                    Z.employee_id AS employee_id_2,
                    Z.full_name AS full_name_2
               FROM employee Z,
                    SELECT DISTINCT
                         supervisor_id AS supervisor_id_1,
                         employee_id AS employee_id_1,
                         full_name AS full_name_1
                     FROM employee
                     WHERE supervisor_id = 0 OR supervisor_id IS NULL
               ) A
               WHERE A.employee_id_1 = Z.supervisor_id
          ) A
          WHERE A.employee_id_2 = Z.supervisor_id
     ) A
     WHERE A.employee_id_3 = Z.supervisor_id
) A
UNION
SELECT DISTINCT
     A.employee_id_3 AS employee_id,
     A.supervisor_id_1,
     A.employee_id_1,
     A.full_name_1,
     A.supervisor_id_2,
     A.employee_id_2,
     A.full_name_2,
     A.supervisor_id_3,
     A.employee_id_3,
     A.full_name_3,
     NULL AS supervisor_id_4,
     NULL AS employee_id_4,
     NULL AS full_name_4,
     NULL AS supervisor_id_5,
     NULL AS employee_id_5,
     NULL AS full_name_5,
     NULL AS supervisor_id_6,
     NULL AS employee_id_6,
     NULL AS full_name_6,
     NULL AS supervisor_id_7,
     NULL AS employee_id_7,
     NULL AS full_name_7
FROM employee Z,
     SELECT DISTINCT
          A.supervisor_id_1,
          A.employee_id_1,
          A.full_name_1,
          A.supervisor_id_2,
          A.employee_id_2,
          A.full_name_2,
          Z.supervisor_id AS supervisor_id_3,
          Z.employee_id AS employee_id_3,
          Z.full_name AS full_name_3
     FROM employee Z,
          SELECT DISTINCT
               A.supervisor_id_1,
               A.employee_id_1,
               A.full_name_1,
               Z.supervisor_id AS supervisor_id_2,
               Z.employee_id AS employee_id_2,
               Z.full_name AS full_name_2
          FROM employee Z,
               SELECT DISTINCT
                    supervisor_id AS supervisor_id_1,
                    employee_id AS employee_id_1,
                    full_name AS full_name_1
                FROM employee
                WHERE supervisor_id = 0 OR supervisor_id IS NULL
          ) A
          WHERE A.employee_id_1 = Z.supervisor_id
     ) A
     WHERE A.employee_id_2 = Z.supervisor_id
) A
UNION
SELECT DISTINCT
     A.employee_id_2 AS employee_id,
     A.supervisor_id_1,
     A.employee_id_1,
     A.full_name_1,
     A.supervisor_id_2,
     A.employee_id_2,
     A.full_name_2,
     NULL AS supervisor_id_3,
     NULL AS employee_id_3,
     NULL AS full_name_3,
     NULL AS supervisor_id_4,
     NULL AS employee_id_4,
     NULL AS full_name_4,
     NULL AS supervisor_id_5,
     NULL AS employee_id_5,
     NULL AS full_name_5,
     NULL AS supervisor_id_6,
     NULL AS employee_id_6,
     NULL AS full_name_6,
     NULL AS supervisor_id_7,
     NULL AS employee_id_7,
     NULL AS full_name_7
FROM employee Z,
     SELECT DISTINCT
          A.supervisor_id_1,
          A.employee_id_1,
          A.full_name_1,
          Z.supervisor_id AS supervisor_id_2,
          Z.employee_id AS employee_id_2,
          Z.full_name AS full_name_2
     FROM employee Z,
          SELECT DISTINCT
               supervisor_id AS supervisor_id_1,
               employee_id AS employee_id_1,
               full_name AS full_name_1
           FROM employee
           WHERE supervisor_id = 0 OR supervisor_id IS NULL
     ) A
     WHERE A.employee_id_1 = Z.supervisor_id
) A
UNION
SELECT DISTINCT
     A.employee_id_1 AS employee_id,
     A.supervisor_id_1,
     A.employee_id_1,
     A.full_name_1,
     NULL AS supervisor_id_2,
     NULL AS employee_id_2,
     NULL AS full_name_2,
     NULL AS supervisor_id_3,
     NULL AS employee_id_3,
     NULL AS full_name_3,
     NULL AS supervisor_id_4,
     NULL AS employee_id_4,
     NULL AS full_name_4,
     NULL AS supervisor_id_5,
     NULL AS employee_id_5,
     NULL AS full_name_5,
     NULL AS supervisor_id_6,
     NULL AS employee_id_6,
     NULL AS full_name_6,
     NULL AS supervisor_id_7,
     NULL AS employee_id_7,
     NULL AS full_name_7
FROM employee Z,
     SELECT DISTINCT
          supervisor_id AS supervisor_id_1,
          employee_id AS employee_id_1,
          full_name AS full_name_1
      FROM employee
      WHERE supervisor_id = 0 OR supervisor_id IS NULL
) A

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

Script populate parent-child hierarchy not running

Hallo guys
I have problem when running script populate Parent-Child Relationship Table.
Here is the script.I don't even change the script.just run it in PL/SQL
declare
v_max_depth integer;
v_stmt varchar2(32000);
i integer;
begin
select max(level) into v_max_depth
from V_D_BRANCH
connect by prior BRANCH_KEY=PARENT_BRANCH_KEY
start with PARENT_BRANCH_KEY is null;
v_stmt := 'insert into DM_ANALYTICS.BRANCH_HIERARCHY (MEMBER_KEY, ANCESTOR_KEY, DISTANCE, IS_LEAF)
            select BRANCH_KEY as member_key, null, null, 0 from V_D_BRANCH where PARENT_BRANCH_KEY is null
            union all
            select member_key,
            replace(replace(ancestor_key,''\p'', ''|''), ''\'', ''\'') as ancestor_key,
            case when depth is null then 0
            else max(depth) over (partition by member_key) - depth + 1
            end as distance, is_leaf
from
select member_key,depth,
case     when depth is null then '' || member_key
when instr(hier_path, ''|'', 1, depth + 1) = 0 then null
   else substr(hier_path, instr(hier_path, ''|'', 1, depth) + 1, instr(hier_path, ''|'', 1, depth + 1) - instr(hier_path, ''|'', 1, depth) - 1)
end ancestor_key,
is_leaf
from
    (    select BRANCH_KEY as member_key, PARENT_BRANCH_KEY as ancestor_key, sys_connect_by_path(replace(replace(BRANCH_KEY, ''\'', ''\''), ''|'', ''\p''), ''|'') as hier_path,
      case when BRANCH_KEY in (select PARENT_BRANCH_KEY from V_D_BRANCH ) then 0 else 1 end as IS_LEAF
from V_D_BRANCH
connect by prior BRANCH_KEY = PARENT_BRANCH_KEY
start with PARENT_BRANCH_KEY is null
( select null as depth from dual;
for i in 1..v_max_depth - 1 loop
v_stmt := v_stmt || union all select '' || i || '' from dual;
end loop;
v_stmt := v_stmt || ) )
where ancestor_key is not null;
execute immediate v_stmt;
end;
but I got errors like following:
Error report -
ORA-06550: line 19, column 12:
PLS-00103: Encountered the symbol "insert into DM_ANALYTICS.BRANCH_HIERARCHY (MEMBER_KEY, ANCESTOR_" when expecting one of the following:
   ( - + case mod new not null <an identifier>
   <a double-quoted delimited-identifier> <a bind variable>
   continue avg count current exists max min prior sql stddev
   sum variance execute forall merge time timestamp interval
   date <a string literal with character set specification>
   <a number> <a single-quoted SQL string> pipe
   <an alternatively-quoted string
06550. 00000 - "line %s, column %s:\n%s"
*Cause:    Usually a PL/SQL compilation error.
*Action:
what should I do guys?any idea,any solution would be appreciated.thanks alot guys

956850 wrote:
hi,
i tried making "Dimension with Parent-Child Hierarchy" as described in your tutorials.
i finished with the admin tool and database changes and with no errors.
when trying to create a new answer, by only puting the hierarchy column in the answer.
the result show "no result" exist.
i am not sure what i am doing wrong. maybe you can point me to the problem?
thanks
Mirit.Hi Mirit,
What is the table that you created hierarchy on?
Which column in the hierarchy you pulled into your reports to see the No Result message?
Please query the table and see if has data.
Thanks,
G. SK

No Results after build a Parent-Child Hierarchy in OBIEE11G

Hi All:
Here's an problem. I followed the "http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/" this article step by step to create a parent-child hierarchy in admin tool in OBIEE11G.
But after check in and try to retrieve the hierarchy data in Answer. There's always displays "No Results."
Is there any suggestions for this ? Really urgent and thanks for your help.
Best regards
Sunny

@Aketi
It is One way that We derive
"sys_connect_by_path(RowIDToChar(RowID),'.') as
RowIDList"
Then
We use Left Join Using
"instr(RowIDList,RowIDToChar(RowID))".sorry, didn't catch what you mean.
my site :-)
http://oraclesqlpuzzle.hp.infoseek.co.jp/4-13.html
pity, I don't know Japanese :(
@Rob
your query is good and simple :) probably it's the best alternative for the OP.
But it won't work with not a plain hierarchy, e.g.:
      1
    2   3
      4
    5   6
SQL> create table hierarchy (child,parent)
2     as
3     select 1, null from dual union all
4     select 2, 1 from dual union all
5     select 3, 1 from dual union all
6     select 4, 3 from dual union all
7     select 4, 2 from dual union all
8     select 5, 4 from dual union all
9     select 6, 4 from dual
10 /
Table created
SQL>
SQL> create table data (hierarchyid,value)
2    as
3    select 5, 10 from dual union all
4    select 6, 25 from dual
5 /
Table created
SQL>
SQL> select h.child
2           , sum(connect_by_root d.value)
3        from hierarchy h
4           , data d
5       where h.child = d.hierarchyid (+)
6     connect by prior h.parent = h.child
7       group by h.child
8       order by h.child
9 /
     CHILD SUM(CONNECT_BY_ROOTD.VALUE)
         1                          70
         2                          35
         3                          35
         4                          70
         5                          10
         6                          25
6 rows selected
SQL>

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 ?

Empty parent-child hierarchy if a date attribute is "1800-01-01 00:00:00.000"!

Similar Messages

Maybe you are looking for