Hierarchical Dimension with a leaf node w/o any parent

Hi
We have a Product Dimension with five levels L0, L1, L2, L3 and L4 (L0-lowestlevel, L4-HighestLevel).
With one Hierarchy STANDARD as
L4, NULL (Parent)
L3, L4 (L4 is the parent of L3)
L2, L3
L1, L2
L0, L1 (L1 is the parent of L0)
The product dimension table has a record with values only for L0 and NULL values for other Levels..
(ie) We have a requirement to create a value in L0 which will have no parents.. The rest of the values in L0 will have parents.
Would like to know if this is possible in AW. This was possible in Express Server
regards
uma

HI
yes we have run into a big problem. We have created leaf nodes w/o parent in aw and created relational views of those. The measure views thus created has data for these dimension values but when accessed thru BI Beans (ie in the cross-tab if we have this measure) the data is not getting displayed for these dimension values (Which do not have parent)
Any immediate response will be of greate help to us.

Similar Messages

Hierarchical Query from a leaf node

I have thist table
create table employee(
emp_id number(7) not null
name varchar(30)
supervisor_id number(7)
Constraint PK_employee primary key(emp_id))
This is my data
Insert into employee(emp_id,name) values (1,Boss)
Insert into employee values(2,Subordinate1,1)
Insert into employee values(3,Subordinate2,1)
Insert into employee values(4,Subordinate3,1)
Insert into employee values(5,Subordinate4,2)
Insert into employee values(6,Subordinate5,5)
Insert into employee values(7,Subordinate6,3)
In my program, I'll be given the leaf node lets say, Subordinate5, I want to get the whole hierarchy for that subordinate like this:
Boss\Subordinate1\Subordinate4\Subordinate5
or Subordinate 6
Boss\Subordinate2\Subordinate6
Help will be greatly appreciated. Thanks.

Here is another - a little bit rewritten - version:
michaels> SELECT full_path
FROM (SELECT LTRIM (SYS_CONNECT_BY_PATH (NAME, '\'), '\') AS full_path
              FROM employee e
        CONNECT BY PRIOR emp_id = supervisor_id ORDER BY LEVEL DESC)
WHERE ROWNUM = 1 AND SUBSTR (full_path, INSTR (full_path, '\', -1) + 1) = 'Subordinate5'
FULL_PATH
Boss\Subordinate1\Subordinate4\Subordinate5
1 row selected.

Dimension with multiple leafs

Hello,
We want to set up the following hierarchy:
--- OXN
....|--- POT
....|....\--- RST
....|
....\--- OIN
.........\--- PJT
..............\--- RST
So this means OXN has 2 child levels (POT&OIN)
and RST has 2 parent levels (PJT&POT)
Now when we make this we get the following warning in the consistency checker:
Warning: [38073] Dimension "<dimension_name> has multiple leaf levels which are not identical
Does anybody know how we can solve this?
Thanx in advance,
Remc0

I'd really like to know what causes this error to occur in the first place.
For me I sat down to construct a time dimension.
Single source table. Single drill path...
Added year... Fine.
Added Month... Fine
Added Week... Fine.
Added Day... Failed???
Exactly the same process for Day as for week, month and year but for day I get the error.
If I knew what criteria was being used to identify the error then i could figure out how to get around it but at the moment it almost looks like a bug( in this circumstance).

Drill and Navifgate only from leaf node

Hi
I have implemented level based hierarchy for my dimension. I want to navigate to another report only from the leaf node of the hierarchy.
Can you please let me know how can this be achieved? How can i identify the leaf node in a level based hierarchy

This is not a duplicate of the item mentioned. With one I have a node anywhere in the tree and need to walk up to find the parent. In this one, I have the parent and need to delete leaf nodes up to this parent. I each one I have a different set of constraints and different ids to work with. Thanks for your help.

TechTool 4 Volume test and "invalid leaf node"

Just a "heads up". I just installed TechTool 4 and ran the usual diagnostics as a level-set. I was surprised to discover that I had two volumes with invalid leaf nodes. To make a long story short, the discussion with TT support revealed that there's apparently nothing wrong with my drives. They've both been re-formatted, surface scanned, repaired, etc. I've never had any errors from either of them. One is a Seagate 250GB and the other is a WD 160GB. TT support asked to borrow one of my drives for a couple weeks(!) because they think it's a bug and can't reproduce it. Disk Utility says there's nothing wrong. Take Volume Scan leaf node errors reported by TT4 with about a pound of salt, since the bug is still there (and will be, since I can't live without the drive for weeks and they won't buy it). I'm reporting it here, because they suppressed the majority of our discussion on their forum and I don't particularly approve of them hiding a known bug from customers. I have the TT logs and anyone who wants to see them can just ask, BTW. This isn't a vendetta against them so much as an attempt to spare others the 2 days of lost work I experienced while running various things for TT support, all to find out that I'm not the one with the problem.
Mac Pro Mac OS X (10.4.9) 3GHz, 4GB

Oh Yeah, that I know. I run two intermediate backups and a full clone daily. The awkward thing is that one of the drives is my "snapshot backup" drive, naturally. They swear that they've only had one other report of this and it went away with a reformat. Mine did not. You'd think that a reformat and surface scan would reveal a hard, repeatable, drive error - which TT4 implies I have. What are the odds that I have two drives with a totally unique problem (such as they described it), made by different manufacturers, with hard and repeatable errors that only their program can detect? SMART says they're OK, Disk Utility says they're OK, no errors are logged, their temperatures are the same. If this error is so rare, how is it that I just happen to have it on 50% of my drives? It's been a Royal Pain to re-jigger my drives so that the backups go to a drive that doesn't have the "error", just in case.

Hide leaf nodes from jtree.

Hi,
How can I hide all nodes that are leafs on a tree? Basically, I'm creating a splitpane where on the left side I have a jtree where when a user clicks on a node on that jtree the leaf nodes will appear on the right split pane as icons.
V

Thanks for the reply...
I wanted to include the leaf nodes in the tree model so that I won't need to work with two data structures--one with the leaf nodes, and another without the leaf nodes.
So far, I think I resolved the problem. I created my own treemodel class where I pass a defaulttreemodel into it and created a modified getChildCount which will go into the defaulttreemodel and filter out the leaf nodes.
It all seems to work pretty well.
My problem now... How do I remove the stupid node icons? :)
I just want the dashed lines to appear and nothing more....
Thanks again...
V

Copy Top node of a hierarchy to the leaf node of another - within dimension

Hi,
Scenario is, user uploads monthly data in the respective leaf nodes of Monthly Input hierarchy. But at a later stage user might want to adjust figures directly on the Annual level.
For that matter I've got 2 hierarchies in Time Dimension, which look like as below:
Monthly Input
2007.TOTAL
2007.Q4
2007.Dec
2007.Nov
2007.Oct
2007.Sep
2006.TOTAL
Annual Input
xxxx.ANL
2009.ANL
2008.ANL
2007.ANL
I could think of two solutions:
1- To upload monthly data directly into .ANL leaf nodes and add signed data values w.r.t. key dimensions and YEAR. Problem is Append functionality isn't available if you loading/importing data from flat file. Can guide me if, somehow, it is workable or not?
2- To copy the .TOTAL nodes to the respective member of .ANL nodes (e.g. 2007.TOTAL to 2007.ANL). I'm not sure if it is possible or not?
Many thanks in advance for more suggestions and earliest reply.
Regards,
Shabbar
Edited by: Ali Shabbar on Jun 30, 2009 1:00 PM

Hi Shabbar,
If I was faced with the requirement to provide a means for allowing both monthly inputs and annual adjustments, I would use one hierarchy, rather than trying to sync signdata values between two hierarchies. With the structure I've shown below, users could report on unadjusted values with 2007.YEAR, annual adjustments with 2007.ADJ or both with 2007.TOTAL.
2007.TOTAL
|
|--2007.ADJ
   |--2007.ANL
|
|--2007.YEAR
   |--Q4
       |--2007.DEC
       |--2007.NOV
       |--2007.OCT
Best regards,
[Jeffrey Holdeman|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/jeffrey+holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group

Hierarchical query - Stop at specific leaf nodes - How to in Oracle 9i ?

Table H -- Master table to build Hierarchical tree
C -- Child
P -- Parent
Table RN -- Table defining Root Nodes
N -- Node
Table LN -- Table defining Leaf Nodes
N -- Node
The following Query can generate trees starting with the nodes specified in the Table:RN
SELECT LEVEL L, C, P, SYS_CONNECT_BY_PATH(C,'/') SCBP
FROM H
START WITH C IN ( SELECT N FROM RN )
CONNECT BY PRIOR C = P
How do I limit the tree to the nodes specified in the LN table ?
"CONNECT BY" does not support "IN" clause
i.e
CONNECT BY PRIOR C = P AND P NOT IN (SELECT N FROM LN)
Say we have 2 trees
1-2-3-4-5
A-B-C-D-E
RN : 2,B
LN : 5,D
Result:
2,3,4 (5 is excluded)
B,C (D is excluded)
Any help is appreciated...

What about:
select level l, c, p, sys_connect_by_path(c,'/') scbp
from (select * from h
where c not in (select n from ln)) -- filter via an inline view
start with c in ( select n from rn )
connect by prior c = p;

Dimension Design - Single Dimension with Multiple Hierarchies

Morning,
the purpose of this discussion is to understand how we should design a specific dimension with 3 levels and multiple hierarchies for optimal performance.
We have an institution dimension with the following characteristics:
Characteristics
Dimension: Institution
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
Hierarchies:
1. Some of the hierarchies have 3 levels and others have only 2 levels (Skip Level)
2. ALL the hierarchies have a TB level and an Institution level
3. None of the hierarchies have the same leafs
4. Some of the hierarchies leafs can overlap
Design:
We are considering two approaches for the institution dimension levels:
a)
Levels:
Hierarchy 1 TB Level
Hierarchy 1 PG Level
Hierarchy 1 Inst Level
Hierarchy 2 TB Level
Hierarchy 2 Inst Level
Hierarchy 3 TB Level
Hierarchy 3 Inst Level
Note:
This approach is working and the resulting dimension and cubes are used by OBIEE, but some of the OBIEE analysis takes a long time (more than a minute) to return the results.
At this point, we are not sure whether this approach will result in an optimal design from a performance perspective and are looking at restructuring the dimension to represent only the three conceptual levels as indicated below.
b)
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
The rest of the dimension i.e. hierarchies, attributes and mappings are defined in the same way.
The cube associated with this dimension have approximately 80 million records.
Please advise on any best practices or design considerations that we need to take into account.
Thanks

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

ADF 10.1.3.0.4: tree leaf with no child nodes still displays folder icon?

I was reading through Frank Nimphius's Blog and found the entry entitled "ADF Faces: Building a hierarchical tree from recursive tables - October 05, 2006" and found a tree example in which a tree leaf with no child nodes do not display the folder icon.
I've followed the instructions listed with adf:tree, CoreTree and ChildPropertyTreeModel, but my tree leaves with no child nodes still displays the folder icon.
How do I remove this icon when the node is a leaf with no children?
Thanks,
--Todd

I figured it out.
I used the ChildPropertyTreeModel.isContainer() method.
--Todd

Dimension with 2 roles and 2 hierarchies used in 2 cubes

Hi,
I have a dimension in which there are two dimension roles (roleA, roleB) defined as well as two hierarchies (hierarchyA, hierarchyB). Currently hierarchyA is set as default. (Not because that is in fact the default one, only because OWB forces one to choose a default)
I need to define two cubes (cubeA, cubeB). CubeA will use the dimension with roleA and cubeB will use the dimension with roleB.
Is it possible to tell cubeA to use/see/make available only hierarchyA and cubeB only hierarchyB? HierarchyA makes no sense in cubeB so I want to "specify" hierarchyB for cubeB.
Thanks,
Juanita

A different issue but possibly related:
I have a ROLAP cube with one of the dimensions containing multiple hierarchies. If I deploy this with deployment option set to "Deploy data only", it works 100%. As soon as I change the deployment option to "Deploy All", I get a VLD-0398 error.
I need to choose "Deploy all" since the cube metadata must be deployed to the OLAP catalog in order for Disco OLAP and BI Spreadsheet Add-In to see the cube.
First question:
Is it possible to deploy to the OLAP catalog if the cube has a dimension with multiple hierarchies?
Second question:
If it is not possible, what is the workaround?
Thanks,
Juanita

Load hierarchical attribute dimensions with Integration Services?

Hi everybody,
I need to load product dimension which is organized in a relational table like this:
Product (parent_code, member_code, member_alias, brand, consolidation, formula)
Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
Brand (brand_parent_code, brand_child_code, brand_child_alias).
I have used in the past Integration Services but with flat attribute dimensions.
Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
Thank you,
Daniela

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

SSM7.5 - Dimension with Multiple Hierarchies

Hi all,
I'm facing here one problem in the SSM front-end when I'm trying to use one the possibilities that PAS database offers, in this case the use of a dimension with multiple hierarchies.
As you can see in this image, the dimension is created in PAS and works without problems in the dataview.
Hierarchy one:
[http://img121.imageshack.us/img121/334/pas1y.jpg]
Hierarchy two:
[http://img831.imageshack.us/img831/2586/pas2.jpg]
In the SSM front-end, when I try to use that dimension, by default appears the first hierarchy:
[http://img826.imageshack.us/img826/4043/hier3.jpg]
In the dimensional selector the dimension appears fine for the first hierarchy:
[http://img30.imageshack.us/img30/3103/hier1.jpg]
But when I select the second hierarchy...
[http://img34.imageshack.us/img34/1722/hier2.jpg]
The Internet Explorer crashes and close all the open windows. This happens in the scorecard and also in the reports.
Is not possible to use dimensions with multiple hierarchies in SSM? Did anyone had this problem before?
Thanks in advance
Pedro
Edited by: Pedro S. Costa on Sep 13, 2010 11:03 AM

Hi Shashi,
first of all, thanks for your answer.
But I don't understand when you say that "we cannot have two hierarchies on the same dimensions"?!?!?
I already have some years of experience with PAS database and it's not the first time I create a dimension with more than one hierarchy. I use also that in a productive system (before this SSM front-end) without problems. And in this latest version of PAS (version 7.5.6) it's still possible to use that feature. As you can see in my initial post, I put two screen shots of the dimension with two hierarchies in PAS dataview, and works fine, without problems in the drill-down/up.
From PAS online help:
HIERARCHY is a Dimension command that defines the members and levels that comprise a particular hierarchy level within a dimension. It also allows multiple consolidation structures that stem from a central root of inputs. Use hierarchies when the input members are consolidated into more than one output member. When a dimension has hierarchies, members can have more than one path for rolling up into output levels. If a dimension has only one hierarchy, no HIERARCHY statement is necessary.
Based on this, I create my example of a dimension (named MULTI) with two hierarchies (REGION and TYPE). Maybe the name I use for the second hierarchy create some confusion to you, because of the TYPE dimension that can exist in SSM. I just hope the problem I'm having in the SSM front-end is not related with the name I used for the second hierarchy!!!!
I will rename that and test again.
Regards
Pedro

Logic Doubling in v7 SQL - Dimension with 3 hierarchies

I'm having a problem with logic doubling at a client where I have a dimension with 3 hierarchies in v7 SQL 2008. When I try to run logic off a property in this dimension, base members in all 3 hierarchies are doubling, whereas base members in only two hierarchies are not. I've tried using *Membersets, *Select, and *XDIM_Memberset statements to stop the values from doubling, but I'm not having success.
Any ideas? Has anyone else seen this?
Thank you,
Grant

Yes, sorry, I've been busy.
Basically, I had two rollups of data in one dimension, and when I was trying to reconcile the logic push that consolidated all the data from this dimension into one member, I was only looking at one of the rollups, and not the other one. So, it was really just a matter of writing logic and running it without taking into account all the data I was manipulating.
Thanks,
Grant

OBIEE Parent-Child Dimension with multiple hierarchies

Is it possible to have in a parent-child dimension multiple hierarchies? I want to have the same botom childs to aggregate to different parrents. example.
Account Dimension
HR1-total
HR1-parrent1
CHILD1
HR1-parrent2
CHILD2
HR2-total
HR2-parrent1
CHILD1
CHILD2
Thanks in advance.

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

Hierarchical Dimension with a leaf node w/o any parent

Similar Messages

Maybe you are looking for