Hierarchy based on one dimension.

Hi,
How to create a hierarchy based on one dimension. For example: we have table:
Category
Category_ID
Parent_Category_ID
I want to create hierarchy, which like as:
Category_Level_1
Category_Level_2
Is it possible without create new alias of table for each level?
Thanks

Which version of BO are you using?
Assuming that you are using BO XI R2 or above version.
And Is your question - how to create custom hierarchies in Universe Designer..... for two different fields (columns) taken from a single database table?
If so, yes you can create custom hierachy for above scenario. In Custom Hierarcies option: Add the Parent_Category_ID first and below that add Category_ID.
If you want to rename your hierarchy levels as Category_Level_1 & Category_Level_2, then rename their corresponding objects names in Clasess & Objects pane.
- Anil

Similar Messages

Can we create a hierarchy based on two logical table in 10g RPD

Hi,
I have a question, please give me some clarity, about creating hierarchy,
I know we can create a hierarchy based on one logical table which is form by two physical table...
Can we create a hierarchy based on two logical table? If yes, and how?
Thanks in advance!
anne

Use preffered drill paths...
-suman

Problem creating hierarchy based on 2 physical dimension tables

I'm having a problem creating 1 logical dimension with a drill-down hierarchy, based on two separate physical dimension tables. The errors I receive when navigating the drill-down hierarchy is:
"Cannot find logical table source coverage for logical columns" &
"Missing join between logical tables".
I'm using OBIEE 10.1.3.4
Here are the details of what I have setup sofar:
Physical layer:
Dimension table DIM_ORG with columns:
-dimension_key
-org_total_code
-org_total_description
-org_detail_code
-org_detail_description
Dimension table DIM_DEPT with columns:
-dimension_key
-dept_total_code
-dept_total_description
-dept_detail_code
-dept_detail_description
Fact table FACT_SALES with columns:
-fk_org
-fk_dept
-sum_sales
Physical Joins:
FACT_SALES.fk_org = DIM_ORG_dimension_key
FACT_SALES.fl_dept = DIM_DEPT.dimension_key
Business Model & Mapping layer:
I created a logical dimension ORG_DEPT. It contains two logical table sources (DIM_ORG & DIM_DEPT) and the following logical columns:
- All Departments (mapped to dept_total_code)
- Organisation (mapped to org_detail_description)
- Organisation Number (mapped to org_detail_code)
- Department (mapped to dept_detail_description)
- Department Code (mapped to dept_detail_code)
The business logical key is based on the combination of Organisation Number & Department Code
The hierarchy I need is: All Departments -> Organisation -> Department so I created the following hierarchy for ORG_DEPT:
- Total Level containing: All Departments
- Organisation Level containing: Organisation Number (defined as the Logical level key) & Organisation (defined als the Drill level key)
- Detail Department Level containing: Department Code (defined as Logical level key) and Department (defined as Drill level key).
In the LTS of the dimension ORG_DEPT I've set the Content levels for the sources:
DIM_ORG : Organisation Level
DIM_DEPT: Detail Department Level
In the LTS no -inner- joins have been added against related physical tables.
I created a logical fact table SALES (based on the physical fact table) and joined it against the logical dimension table ORG_DEPT.
In the LTS the Content level for ORG_DEPT is set against the Detail Department Level. No - inner- joins have been aded against related physical tables.
When I create a report in Answers to test the hierachy and select only 'All Departments' I get the correct dimension value returned. When I try to drill to the next level I get the following ODBC error:
"Cannot find logical table source coverage for logical columns: [All Departments]. Please check more detailed level keys are mapped correctly".
When I create a report in Answers and select both 'All Departments' and 'Sales' I get the correct result. When I try to drill to the next level I get a different ODBC error:
"Missing join between logical tables DIM_DEPT and DIM_DEPT: There must be at least one physical join link between the underlying physical tables".
Any suggestions are welcome!
Thanks!

Hello Robert,
Your suggestions were known to me but I still wanted to combine the two physical dimension tables in one logical dimension. So I've played around a bit more and found the solution: In my original setup I had two seperate logical table sources (one for each physical dimension table). The solution was to combine the two logical table sources in one logical table source. I achieved that by logical joining the DIM_DEPT table to the FACT_SALES table and subsequently to the DIM_ORG within the 1 LTS and using inner joins.
Then I created the logical table key (a combination of org_detail_code & dept_detail_code). After that I could create the hierarchy with no problem.
Edited by: The_Dutchman on Nov 4, 2011 9:43 PM

Variable for one Dimension based on another Dimension's Property

Hi all,
This is a Acript Logic question.
I have a dimension called P_BUDGET_MODEL. It has a property called PROFIT_CTR.
I also have a dimension called P_PCA.
I would like to have a variable that defines the values of P_PCA based on the values of PROFIT_CTR once the user selected the P_BUDGET_MODEL.
Please note:
1. One value of PROFIT_CTR might yield fiew values of P_PCA based on a well defined logic that I can code in the script using some sort of Concatenation.
2. I want to use the variable in *XDIM_MEMBERSET P_PCA to improve performance.
3. I have authorizations defined both for P_PCA and P_BUDGET_MODEL.
4. I would like to use similar logic to define the time dimension based on the category dimension.
Any ideas?
Kind regards,
Avihay

Hello Nilanjan,
First of all thanks for your response.
I am not sure I understood. Allow me to elaborate the business scenario.
I have a distributed planning process. Various planners are responsible for various P_BUDGET_MODEL values, which are organized in a hierarchy based on these responsibilities.
When the user selects in a planning package the P_BUDGET_MODEL values, I want to run a logic that will perform calculations. In the logic I need to create data with various values of P_PCA. The values of P_PCA can be derived from the property P_BUDGET_MODEL.PROFIT_CTR.
I also have authorizations on P_PCA and they are synchronized with the authorizations on P_BUDGET_MODEL. The reason I have authorizations on P_PCA is that in various reports I have P_PCA as the display criteria and I do not want users to see all of the values. I also plan to base planning approval processes on this dimension in the future.
Since I have few users basically I needed a simple IF inside my logic, but there is no such statement.
I am a veteran BPS and IP consultant. Such a request was very easy to implement in those tools (using characteristic relations for example and also in FOX). It surprises me that it is so hard to implement in BPC.
Any new ideas?

Two Dimension Hierarchys based on one Logical Table

Is it possible to have two dimesion hierarchys based on one logical table? Suppose we have the following case:
Accounts Table
Code
Name
Category
Subcategory
Level 1
Level 2
Level 3
I would like to have one dimension Total > Category >Subcategory > Code and one Total > Level 1 > Level 2 > Level 3 > Code, so I can drill down on both paths. Is this possible?
Thanx

Yes, the trick is to have the same key on the lowest level in your hierarchy.
regards
John
http://obiee101.blogspot.com/

2 date columns and one dimension hierarchy

Hi,
I have one question in OBIEE 10g.
I have one dimension table with 2 date columns (insertedOn, updatedOn)
I created insertedOnYear, insertedOnMonth and updatedOnYear, updatedOnMonth columns from my date columns.
I have hierarchy
Year -> Month -> Day for that dimension table
and I would like to dril down both columns insertedOnYear and updatedOnYear
insertedOnYear -> insertedOnMonth -> insertedOn
updatedOnYear-> updatedOnMonth -> updatedOn
I am able to do it only for one of these columns and not for both.
I can place both columns to appropriate levels, but drilling doesn´t work as I want
Can you tell me how to solve my problem?

Oops, I was talking about 11G. Ok no problem. Do this. In the physical layer, cretea 2 alias tables. Both pointing to the table where you have these 2 fields. The put everything in your BMM. There create the 2 hierarchies using the 2 different tables (that will point to the 2 alias tables create in the physical layer). This will make them unique.

Multiple hierarchy in one dimension

hi ,
i have a dimension with 4 levels and 2 hierarchy . one hierarchy uses all 4 levels (default hierarchy) and one uses 3 levels .
i have 2 cubes , one cube needs to use hierarchy 1 from that dimension and there is no problem on validation time .
one cube needs to use hierarchy 2 of that dimension when i uses 'deploy all ' as deployment option , OWB says to me that i have to use last level of that dimension . I use relational implementation .
can i use diffrent hierarchy of 1 dimension in diffrent cubs ?
thank u in advance for your advise
Padideh

Hi Sankar,
You can define Employee, Organization, Physical, Customer & Product as navigational attributes of Role and in the query enable the hierarchy for Role. Then pull Employee, Organization, Physical, Customer & Product under Role this way you will be able to display, the hierarchies of Employee, Organization, Physical, Customer & Product under the nodes of Role hierarchy in the order in which you place them in the report.
Hope this helps.
Regards
Kumar

Multiple Hierarchies in one dimension - comments?

multiple hierarchies
Hi Experts,
I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
a) still enables users to choose the hierarchy in a dashboard prompt
b) reduces maintenance to a minimum
The dimension groups ages into several different groups like the example below:
Hierarchy1 Hierarchy2
Age......Groups........Groups.....
0........0-2...........0-5
1........0-2...........0-5
2........0-2...........0-5
3........3-5...........0-5
4........3-5...........0-5
75.......70-75.........70-80
76.......76-80.........70-80
Right now I've implemented this by defining one dimension having one hierarchy:
Total
....Hierarchy
.......Group
.........Age
The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
Columns in the logical table (and of course in the underlying LTS) are:
Column               mapped to hierarchy-level
- Hierarchy          Hierarchy
- Hierarchy_id          Hierarchy
- Group          Group
- Group-id          Group
- Age               Age
Advantages:
A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
Disadvantages:
A new grouping needs manual steps to implement
- a new physical table
- a new LTS attached to the logical table (including the fragmentation content)
Thanks for your time and comments
Regards
Andy

multiple hierarchies
Hi Experts,
I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
a) still enables users to choose the hierarchy in a dashboard prompt
b) reduces maintenance to a minimum
The dimension groups ages into several different groups like the example below:
Hierarchy1 Hierarchy2
Age......Groups........Groups.....
0........0-2...........0-5
1........0-2...........0-5
2........0-2...........0-5
3........3-5...........0-5
4........3-5...........0-5
75.......70-75.........70-80
76.......76-80.........70-80
Right now I've implemented this by defining one dimension having one hierarchy:
Total
....Hierarchy
.......Group
.........Age
The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
Columns in the logical table (and of course in the underlying LTS) are:
Column               mapped to hierarchy-level
- Hierarchy          Hierarchy
- Hierarchy_id          Hierarchy
- Group          Group
- Group-id          Group
- Age               Age
Advantages:
A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
Disadvantages:
A new grouping needs manual steps to implement
- a new physical table
- a new LTS attached to the logical table (including the fragmentation content)
Thanks for your time and comments
Regards
Andy

OBIEE mixed hierarchy based on Essbase

Hi all,
I wonder if anyone of you came accross the following requirement: There is an essbase cube with 2 for this post relevant dimensions - location and rates.
Location is a geographical dimension structured as follows
Global -> Region -> Country -> State -> City
Rate is a flat attribute dimension that stores scoring of a given city (high, medium, low).
Customer would like to see a following mixed hierarchy
Global-> Region -> Rate -> City
One thing is that 2 levels should be omitted (country, state), that is no problem. You can model an additional logical table that consists only of above attributes and build logical hierarchy based on it. However, there is a problem when you want to display data using hierarchy column in answers. Specifically when you drill down from Rate node to City. What happens is that when you try to expand for example "medium" node under "EMEA" Region, all "medium" nodes get expanded, also under ASIA end America nodes. It happens probably because values of Rates do not uniquely identify levels (there should be difference between EMEA->Medium and ASIA->Medium). My first idea would be to concatenate Region and Rate and display for example "EMEA high", "EMEA medium" and so on, that would certainly work with Oracle database as a source, with Essbase there is a problem, when you try concatenate anything and then filter on it.
What would be the way to go? I guess it might be a common requirement when there are attribute dimensions in essbase...

Hello Robert,
Your suggestions were known to me but I still wanted to combine the two physical dimension tables in one logical dimension. So I've played around a bit more and found the solution: In my original setup I had two seperate logical table sources (one for each physical dimension table). The solution was to combine the two logical table sources in one logical table source. I achieved that by logical joining the DIM_DEPT table to the FACT_SALES table and subsequently to the DIM_ORG within the 1 LTS and using inner joins.
Then I created the logical table key (a combination of org_detail_code & dept_detail_code). After that I could create the hierarchy with no problem.
Edited by: The_Dutchman on Nov 4, 2011 9:43 PM

Dynamic non-hierarchy based Member Access Profile

Hello all,
I have few (semi related) questions:
Qouestion 1:
I would like to perform the following configuration:
1. We have a dimension called "Budgeting Model".
2. We have a property called "Division" to this dimension.
3. I would like to create a Member Access Profile based on the value of the property.
4. I do not want to use hierarchy.
Question 2:
1. We have a dimension called "Budgeting Model"
2. We have a dimension called "Profit Center"
3. I would like to create a property for the Budgeting Model called Profit Center that will be checked against the Profit Center dimension valued. I saw something in the documentation but I wonder if anyone can provide me with a step-by-step guidance.
Generally speaking - I am trying to create the BPC/IP "Characteristics relationships" functionality in BPC and using the Profit Center as a secured dimension bypass the limitation of question 1 above.
Thanks in advance for you help,
Avihay

Hi Avihay,
1. Yes, you are absolutely right. You cannot set it dynamically. This maintenance has to be done manually.
2. If you look at the entity dimension, this dimension refers to currency type dimension. Similarly, an account dimension refers to the rate type dimension. You can see these information when you modify these dimensions. These relationships are pre-delivered. And you cannot create any new relationships.
So, lets say if you want to create a relationship, then you can have one dimension as entity and another as currency. Then you can establish the relationship between them. This is just an example. You can explore more on these types of pre-existing relations.
Hope this helps.

Inclue children and exclue children in a single hierarchy in parent child dimension in mdx

hi,
include children and exclude children in a single hierarchy in parent child dimension in mdx
*12-parent
**20-parent
- 9-parent
--250-child1
--210-child2
--240-child3
aggregation of 12-parent only
aggregation of 20-parent only
aggregation of 9 with children
regards,
Manish

Hi manishcal16PPS,
According to your description, you have a parent child dimension in your cube. Now you want to use one measure use show aggregation value including/excluding child member based on different parent level member. Right?
In this scenario, we could use IIF() in the calculated measure to apply different calculation depends on the current dimension member. Please refer to query below:
with member [x] as
IIF([Dim].[Hierarchy].CurrentMember is [Dim].[Hierarchy].[Parent].&[9]
sum(Descendants([Dim].[Hierarchy].CurrentMember,
[Date].[Calendar].[Parent]),
[Measures].[Amount])
sum([Dim].[Hierarchy].CurrentMember,[Measures].[Amount])
select [x] on 0,
[Date].[Calendar].[Parent].members on 1
from
[Cube]
Best Regards,
Simon Hou
TechNet Community Support

How to sort two different hierarchies in one dimension

Does anyone know of a way to sort two different hierarchies in one dimension and still make drilling work correctly? We have two hierarchies in our item dimension; one called category and the other origin. Simplified, it looks like this:
CATEGORY
Hardware (100)
..PCs (100.100)
....PC 1
....PC 2
....PC 3
..Monitors (100.200)
....Monitor 1
....Monitor 2
....Monitor 3
Software (200)
..Big (200.100)
....ERP package
....CRM package
..Small (200.200)
....Solitaire
....Mine Sweeper
ORIGIN
Vendor A (10)
..Site A1 (10.10)
....ERP package
..Site A2 (10.20)
....PC 1
....Monitor 3
Vendor B (20)
..Site B1 (20.10)
....PC 2
....PC 3
....Monitor 1
....Monitor 2
....Solitaire
....Mine Sweeper
..Site B2 (20.20)
....CRM package
We have numeric codes at each level above item which I represents the sort order (the number in parentheses at each level), and the items themselves should be sorted according to item number. I have implemented this (level code/item number) as an attribute in AWM making this the default sort order. However, as item is the lowest level in each hierarchy, I have only been able to list the items under the correct level in one hierarchy. As soon as I drill using the other hierarchy, the levels above item are sorted correctly, but the items appear at very odd places...
The AWM documentation states that if default order is not selected on any attribute, hierarchies are sorted in the order they are created. Is there a way to control this order?
Any input will be greatly appreciated!

Hi,
thank you for your answer. Yes, now I also find the class CL_SALV_WD_MULTI_CELL_EDITOR which could be used to set different UIE in one cell. But it is quite limited, just the following UIE could be used
- LinkToAction
- LinkToURL
- FileDownload
- Button
- ToggleButton
best regards,
Wenwen

One dimension used twice in a cube

I have one dimension, but it has two meanings. How can i use the same dimension twice in the same cube as it was two separate dimension?
Example:
There is dimension "Region". The fact table has two keys. First key means - "region of birth", and second "region of living". So one dimension has two meanings.
I tried put the same dimension twice with two different aliases in one cube. OEM shows such cube as valid, but querrying it through OLAP API, or building analytic workspace based on this cube is impossible (error ORA-1007).
The only workaround i see is to build two separate but identical dimensions.The bad side of this is that i have to create two separate but identical tables of data for those dimensions (i can't create two levels from the same column).
Raf
i work with Oracle9iR2

i did the same on Oracle9iR2 with OEM 9.2.0.1.0.
Creating the cube with two aliases for one dimension was ok.
But creating MOLAP cube from that source cube using AWM was impossible .
Also querrying that cube (the one created in OEM) for example through Discoverer or Excel is imposible.
I searched forums on that question, and some people had the same problem, but no answer.
Raf

Can We generate Check report based on Custom Dimension in FDM

Hi All,
We got a requirement in our project to generate the check report based on custom dimension. As far as i know the check reports that got generated in FDM are based on Entity Dimension.
So, will you please let me know whether it is possible to generate report based on any one of the custom dimension.
Thanks.

I guess I am not understanding the question here?
The check report is based on the location/entity that you are running the report for. You can pull values for a specific intersection in the target application with the check report, so you could specify the custom dim in the intersection.

'Hierarchy Based Login' and 'Direct Reports' field in Dim - Position table

Hello -
I am trying to build a "My Team's" report, which basically shows the logged in Managers ( and his subordinates) revenues rolled up by default. Then the manager needs to drilldown on his name and see revenues grouped by his direct reports. I am using OBIEE 10G. In the out of the box RPD, there are two fields in the BMM layer called 'Hierarchy Based Login' and 'Direct Reports'.
1. The 'Hierarchy based Login' field uses the INDEXCOL method to get relevant column from the W_POSITION_DH table based on the the Logged in users hierarchy level (the hierarchy level is stored in a session variable (HIER_LEVEL). This session variable works fine and i have tested the SQL)
2. The 'Direct Reports' is using the same INDEXCOL method, just that it uses the formula HIER_LEVEL - 1. This works fine as well.
The issue i am facing is neither of these out-of-the-box fields are assigned to the Position dimension (the position dimension also exists OOTB).
So basically, i am able to create a manager and his direct subordinate report, but without any drill functionality.
I am trying to get the report to drill all the way down to the bottom most level of the heirarchy.
Any help to get this working is much appreciated

What i meant was neither of these out-of-the box fields are assigned to a Dimension Hierarchy ( there is a hierarchy called 'Position' that already exists out-of-the box). Other fields in the 'Dim-Position' table are assigned to a level in this position hierarchy, except these two. I guess what i am trying to achieve is to dynamically assign the hierarchy level based on the users Hierachy level in W_POSITION_DH table.
Thanks for spending time to look into my issue

Hierarchy based on one dimension.

Similar Messages

Maybe you are looking for