Hierarchies within a Dimension

Hello,
The BW Multidimensial modeling states there are 3 types of Hierarchies that BW employs.
Can anyone shed light on what " Hierarchies within a Dimension" does?
Thanks in advance.

Hi
Any dimension's members may be organized based on parent-child relationships, typically where a parent member represents the consolidation of the members which are its children.
The result is a hierarchy, and the parent/child relationships are hierarchical relationships. For example, the Time dimension would contain the following hierarchy
Day Week Month Quarter Year.
Based on the business queries, such hierarchies would be formed in all dimensions.
Regards
Sai

Similar Messages

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

How to create Hierarchies for a Dimension?

Hi,
How to create Hierarchies for a Dimension in Multidimensional Models? Could you please suggest some document provides step by step instructions to create Multidimensional Model?
Thanks
M Thiyagarajan

Hi M Thiyagarajan,
connect dimension to first level and after that connect that level to another one and so on. For level - each additional outgoing connection means additional hierarchy.
Philip

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

BAPI to get all levels of all hierarchies of all dimensions of a cube

Hi Experts,
Is there are way to get all properties of all levels of all hierarchies of all dimensions of a cube (InfoCube, ODSObject, QueryCube, InfoSet) in one BAPI call?
Any useful answer will be rewarded with suitable points.
Thanks,
Rohan

Hi
Check the following Cube related BAPIS
BAPI_CUBE_ACTIVATE
BAPI_CUBE_CHANGE
BAPI_CUBE_CREATE
BAPI_CUBE_GETDETAIL
BAPI_CUBE_GETLIST
BAPI_INFOCUBE_READ_REMOTE_DATA
BAPI_MDPROVIDER_GET_CUBES
BAPI_MDPROVIDER_GET_STREAMCUBE
UMK_BW_BAPI_CUBE_GETDETAIL
Reward points for useful Answers
Regards
Anji

Multiple Hierarchies from Single Dimension Table in OBIEE-11g?

Is it possible to have Multiple Hierarchies from Single Dimension Table in OBIEE-11g?
Like 1)Year-Qtr-Month-Weeks 2)Year-Month-Days

Hi,
or if your lowest level is the same like
Day->month->year->Total
Day->businessMonth->businessyear->Total
Then yes, it is.
Create the first, then you start to create the second by adding your top(business year) level on the same level as the one you have (year) both under your total.
Then when you would add your second base level, there is a special option for it, something like use other hierarchy level/shared level (sorry can't recall and does not have a connection right now) then you select your existing day level under your businessmonth level.
Hope this helps,
Regards,
D

1:N relationships within a dimension

We are using OBIEE 10.1.3.3
I have a request from users where they want attributes within a dimension where those attributes have a 1:N relationship.
Example, Sales is dimensioned by Customer and Time.
The granularity of the Sales Fact is Day and Customer.
Now each customer can be know by different names and that attribute is known as Customer Synonym. There is a 1:N relationship between Customer and Customer Synonym. The users want to see both Customer and Customer Synonym and also query sales. When I add the Customer Synonym table within the same logical table source and run a query,the Sales numbers are doubled counted where there are more than one Synonyms. To avoid confusion we have trained users about this issue. However, I would like to figure out a better way to avoid the double counting. I cannot create a dimension out of Customer Synonym because the grain of the sales data is customer.
Is there a better design pattern within OBIEE to address this issue ?
Any suggestions would be appreciated.

Ya got your requirement,I got an idea or think its a suggestion lets give a try
If you know SQL coding and as you said they are alternative names,you can do 1 thing instead of displaying both names as different columns.You combine them in SQL it is concatenated like this
customer_name||' '||customer_synonym so result=AB Corporation Alpha Beta Corporation Barclay Corporation
so end result AB Corporation Alpha Beta Corporation Barclay Corporation 100
but this can be written in the query itself or may be as a condition you should give a try and play around.
Hope it helps you.
Cheers,
Kranthi

How to build 2 hierarchies in time dimension

Hi All
I want to know how to build 2 hierarchies in time dimension in SAPBPC 7.5 NW.
thanks

Hi nilanjan chatterjee
thanks for your feedback. please check my time dim below.
we got two financial years.
1. jan to dec ( thats my parenth1)
2. apr to mar ( thats my parenth2)
In usertime id i copied 2008 time ids for fy2009 jan sep and from oct to dec copied 2009 jan to mar time ids.
ID                         Desc            parenth1        parenth2                               Timeid         usertimeid
2009.Q1          2009.Q1          2009.TOTAL                                   20090001
2009.Q2          2009.Q2          2009.TOTAL                                   20090002
2009.Q3          2009.Q3          2009.TOTAL                                   20090003
2009.Q4          2009.Q4          2009.TOTAL                                   20090004
FY2009.Q1     FY2009.Q1                           FY2009.TOTAL                 20090001
FY2009.Q2     FY2009.Q2                            FY2009.TOTAL          20090002
FY2009.Q3     FY2009.Q3                          FY2009.TOTAL               20090003
FY2009.Q4     FY2009.Q4                           FY2009.TOTAL               20090004
2009.TOTAL     2009.TOTAL                                                      20090005
FY2009.TOTAL     FY2009.TOTAL                                        20090005
2009.JAN     2009.JAN     2009.Q1                                        20090100     20090100
2009.FEB     2009.FEB     2009.Q1                                        20090200     20090200
2009.MAR     2009.MAR     2009.Q1                                        20090300     20090300
2009.APR     2009.APR     2009.Q2                                        20090400     20090400
2009.MAY     2009.MAY     2009.Q2                                        20090500     20090500
2009.JUN     2009.JUN     2009.Q2                                        20090600     20090600
2009.JUL     2009.JUL     2009.Q3                                        20090700     20090700
2009.AUG     2009.AUG     2009.Q3                                        20090800     20090800
2009.SEP     2009.SEP     2009.Q3                                        20090900     20090900
2009.OCT     2009.OCT     2009.Q4                                        20091000     20091000
2009.NOV     2009.NOV     2009.Q4                                        20091100     20091100
2009.DEC     2009.DEC     2009.Q4                                        20091200     20091200
FY2009.JAN     FY2009.JAN                    FY2009.Q1                    20090100     20080400
FY2009.FEB     FY2009.FEB                    FY2009.Q1                    20090200     20080500
FY2009.MAR     FY2009.MAR                     FY2009.Q1                    20090300     20080600
FY2009.APR     FY2009.APR                     FY2009.Q2                    20090400     20080700
FY2009.MAY     FY2009.MAY                     FY2009.Q2                    20090500     20080800
FY2009.JUN     FY2009.JUN                      FY2009.Q2                    20090600     20080900
FY2009.JUL     FY2009.JUL                     FY2009.Q3                    20090700     20081000
FY2009.AUG     FY2009.AUG                     FY2009.Q3                    20090800     20081100
FY2009.SEP     FY2009.SEP                     FY2009.Q3                    20090900     20081200
FY2009.OCT     FY2009.OCT                      FY2009.Q4                    20091000     20090100
FY2009.NOV     FY2009.NOV                      FY2009.Q4                    20091100     20090200
FY2009.DEC     FY2009.DEC                        FY2009.Q4                    20091200     20090300
thanks

Automatic handling of BW hierarchies within infopackages

Within BW there are infosources and
within infosources there are infopackages. You can create time
versioned hierarchies within a infopackage. We create the hierarchies
for each month. When you do this, in order to load the data into the
correct hierarchy, there is radio button that you have to select. I
would like to know if there is a automatic way, weather with ABAP
calling BAPI's or some other program(s) to first create the hierarchy
for the month and then select the radio button so that the data is
loaded to the correct hierarchy.
thanks in advance.

hi pavan,
No automatic handling of BW heirarchies , i guess.
Just go thru it , it may helpful to you.
Activities for generating a DataSource for a set hierarchy:
1. Enter the table that the set uses (for example, an FI-SL totals table GLFUNCT) and then select the table field (for example, RBUSA Business Area) for the set.
2. If the characteristic is compounded in the BW, which the hierarchy is based on, and if you want to transfer its compounding information on the source system to BW, select BW Characteristic is compounded. Enter the data element to which the hierarchy is compounded. When the hierarchy is loaded, the compounding information is taken into account in BW. If you want to extract the FI-SL set of a characteristic compounded in BW, you have to run the compounding process in a customer exit. In transaction CMOD, create a project for SAP enhancement RSAP0001 and program EXIT_SAPLRSAP_004 (ZXRSAU04).
3. Run the program to generate the DataSource for the set hierarchy.
4. The new DataSource is called 4R_GSBER_0000_HIER. GSBER is the data element of the field GLFUNCT-RBUSA and 0000 specifies the set class.
hope IT Helps.. !!
Regards
Varun CN

M:N relationships within a dimension: Standard process vs. BI Data model

Hi,
I just completed a review of the u201CMulti-Dimensional Modeling with BIu201D from this link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84 and I have a quick question here:
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
i.e. my understanding is that, based on Standard Process it is NOT possible to place two characteristics in M:N relationships in the SAME dimension but with BI Data Model, this, the author points out is possible
u201Cdue to the usage of surrogate keys (DIM-IDs) in the dimension tables allowing the same material several times in the dimension tableu201D i.e. although material is the unique key of the dimension.
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
Thanks

Hi Amanda.......
In a dimension table, any number of semantically related dimension attributes are stored in a hierarchy (parent-child relationship as a 1:N relationship). If an M:N relationship exists between dimension attributes, they are normally stored in different dimension tables.
I checked the document.........
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
Here the first thing that I want to tell u is that............the diagram shown here is Classic Start Schema............since Extended Star Schema will never store Master data in Dimension tables.........it stores Masterdata in seperate Master data tables..........and nowadays..............Classic Star schema is obsolet.......Dimension table will only store Dimension id and SID......
Now the Standard process is that..........anything which is Describing a master data..........can be added as an Attribute of that master data.......
Suppose........Employee is the Masterdata.then Ph no can be one of the Attribute of this master data......
So this the Standard Process.........but this cannot be followed every time.........why........already explained.....
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
Bcoz ..........we use compounding Characteris tic to define the Master data uniquely.........and we load compounding Characteristic seoerately...which is independent of the Master data........ie......compounding Characteristic there is a seperate master data tables...........so ..........problem resolved......
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
For Compounding Characteristic............u hav to laod the Coumpoundede master data seperately..which is a overhead...........moreover while query execution......two tables will be accessd..which may result a performance issue.......Performance can be affected when compounded characteristics are used extensively, particularly when a large number of characteristics are included in a compounding. In most cases, the need to compound is discovered during data modeling.
Regards,
Debjani.........

Hyperion Planning : multiple hierarchies for a dimension ?

Hi,
Is it possible into planning 9.2 to manage multiple hierarchies for a dimension ?
I didn't found that in the documentation but I had already listened that there is a workaround to do that.
Regards

Hi,
I would like for the entity dimension used two differents hierarchies (two differents relation Parent/child), one for example used by the accounting service and an other used by the sale service.
The level0 member are the same but parents are differents in these two hierarchies.
It's something possible to do into OFA or EPB and I would like to do the same into Hyperion. planning.
Regards

Defining multiple hierarchies for single dimension in Administrator?

Hello,
We are attempting to define multiple hierarchies in a single dimension in Administrator. The following two examples are representative use cases for what we're trying to do:
DateDim
----By Calendar Quarter
--------By Calendar Month
------------By Week
----------------By Day
----By Fiscal Quarter
--------By Fiscal Month
----By Calendar Month
--------By Week
Note that "By Calendar Month" can't really be a shared level because we do not want to include "By Day" in the third hierarchy.
ServiceLocationDim
----By Sales Region
--------By State
------------By City
----By State
--------By City
------------By Zip
----------------By Store
Note again that "By State" can't be a shared level because its children differ in the two hierarchies.
The goal is to have multiple drilldown paths supported. If there is a different way to do this in Administrator that does not use hierarchies, that would be acceptable.
Can anyone point me in the right direction?
Thanks,
Matt Warden
Balanced Insight, Inc.
http://www.balancedinsight.com

Hi,
when defining multiple hierarchies in a dimension, the lowest level needs to be the same for each hierarchy...that's a prerequisite.
But I think you can define them this way...and restrict your 'drill' level on your fact table...as I think you will have a different aggregation level overthere.
So for your dimension you'll set the logical level on the lowest level and in your fact you can play with the logical level depending on to the drill level?
Can that help you?
A.

The Cube should refers to all leaf levels of hierarchies of the Dimension

Dear All,
I'm trying to link a fact table to the month level of a time dimension and i got the following error
VLD-0398: The Cube TIME_TEST_CUBE does not refer to leaf/lowest level DAY of the dimension SINGLE_HIR_TIME.
The Cube should refers to all leaf levels of hierarchies of the Dimension.
would you please help me to solve this problem
Regards,
Shaimaa

I realized that this feature is allowed only for MOLAP dimensions but not for ROLAP
which exactly the opposite of what is mensioned in
Oracle® Warehouse Builder
User's Guide
10g Release 2 (10.2.0.2)
B28223-03
in page 116
" For a cube that uses a relational implementation, you can refer to intermediate
levels in a dimension. However, for cubes that use a multidimensional
implementation, you can only reference the lowest level in the dimension. "

BAPI for properties of all levels of all hierarchies of all dimensions cube

Hi Experts,
Is there are way to get all properties of all levels of all hierarchies of all dimensions of a cube (InfoCube, ODSObject, QueryCube, InfoSet) in one BAPI call?
Any useful answer will be awarded with suitable points.
Thanks,
Rohan

I have one material BOM like PA0100P3DR000 --- finish material
                                            PA0100P3GR000 --- Go blank
                                            BA0100P3GR000 -- Hard blank
                                            AA0100P3GR000 --- Soft blank
                                            RSTR0010000000 -- Raw material
This is for one material display level i.e. for PA0100P3DR000 finish code.
How i will get for all materials in a single display .
Pl' tell the step by step procedure.........
I have little knowledge of BAPI.
Thanks.

BAPI for all levels of all hierarchies of all dimensions of a cube

Hi Experts,
Is there are way to get all properties of all levels of all hierarchies of all dimensions of a cube (InfoCube, ODSObject, QueryCube, InfoSet) in one BAPI call?
Any useful answer will be rewarded with suitable points.
Thanks,
Rohan

Hi
Check the following Cube related BAPIS
BAPI_CUBE_ACTIVATE
BAPI_CUBE_CHANGE
BAPI_CUBE_CREATE
BAPI_CUBE_GETDETAIL
BAPI_CUBE_GETLIST
BAPI_INFOCUBE_READ_REMOTE_DATA
BAPI_MDPROVIDER_GET_CUBES
BAPI_MDPROVIDER_GET_STREAMCUBE
UMK_BW_BAPI_CUBE_GETDETAIL
Reward points for useful Answers
Regards
Anji

Hierarchies within a Dimension

Similar Messages

Maybe you are looking for