Defining hierarchy level keys

Hi,
What is the best practice regarding the level keys (used in the hierarchy level for dimensions)?
I had a problem with the numbers shown because the level key contained values with a mix of letters and numbers. If the level key only contains letters or numbers it worked as it should, but once there was a mix like this
0101
X010
the numbers for the balance sheet came out wrong (combined with a level based measure though).
To me it seems like the level keys ALLWAYS should be in Numbers but this is not stated anywhere. Only by experience. I have searched the forum for this but could not find any exact hit.

Hi,
I am not sure why the existing reports throw an error when I change the RPD dimension hierarchy level keys. Does anyone know how I resolve this issue.
This is urgent. Any help will be most appreciated.
Thanks in advance.

Similar Messages

URGENT: Issue with hierarchy level keys and report drill down

Hi,
BASIC STRUCTURE:
I have created a subject area with 3 facts (FACT_A, FACT_B, FACT_C) and 4 dimesnions (TIME_DIM,DIM_2,DIM_3,DIM_4). Each fact table also has additional aggregate tables aggregated along levels of the time dimension. Also our timw dimension has aggregated dimension tables like TIME_DIM_WEEK, TIME_DIM_MONTH, TIME_DIM_QUARTER and TIME_DIm_YEAR.
GOAL:
All 3 facts have the same measures M_1 and M_2 in them but may not have data for the same dimension values selected.
For example
For month JAN 2000 FACT_A.M1=100$ and no data exists for JAN 2000 in FACT_B and FACT_C. Then in the report
for JAN2000 it should show FACT_A.M1= $100, FACT_B.M1 = 0 and FACT_C.M1 =0. In this case I should be able to drill down to the lowest level.
ISSUE:
The time dimension TIME_DIM has the following levels - Total -> Year -> Quarter -> Month -> Week -> Day
However I am having an issue with drill down in the reports whenever I pull metrics from more than 1 fact at a time. I have defined the level keys but not sure if I need to do anything in addition since I am using aggregates.
I have to fix this issue quickly. Please help me.

Alastair,
All the fact tables have aggregated facts as sources.
I have checked the levels set for each of the sources to the time dimesnion table in BMM and they look okay. So the Time dim table in BMM has 4 source tables
Time_Day (level set to day, table key is "day"),
Time_month (level set to month, table key is "Fiscal_Month_Code"),
Time_Quarter(level set to quarter, table key is "Fiscal_Quarter_Code") and
Time_Year(level set to year, table key is :Fiscal_Year_Code").
Note: No time week aggregate added as logical source.
Again the time dim hierarchy based off of this table has levels: Total -> Year ->quarter -> Month -> week -> day
The levels keys set for each level are
Year -> Primary key is Year_Name (YYYY)(Checked as chronological key) and another key is Year_Num (YYYY)(Checked as chronological key)
Quarter->Primary Key is Quarter_Name (YYYY Qn), another key is Quarter_Number (Format n where n can assum values 1,2,3,4). Both keys are set as chronological keys
Month -> Primary key is Month_Name (MON YYYY), another key is Month_Num (Format n where n can assume values from 1 to 12) Both keys are set as chronological keys
Week -> Primary Key is week name (YYYY Wk nn, where nn can have values from 1 to 53), another key is week num (nn, where nn can have values from 1 to 53)
Day -> primary key set to day (date format)
Issue1: When I try to drill to lower levels it throws out an error saying report cannot find any data because filters may be too restrictive even though I see data at higher level
For ex: If I drill down to Year: 2010 and Qtr: 2010 Q2 and M1:$100 when I click on Qtr to drll to month level it throws me the error
Issue2: when I add year and qtr colums to the report I see data as below which is incorrect
Year_Name Qtr_Name data:FACTA_M1 Data: FactB_M1
2009 2009 Q1 $10 $5
2009 2009 Q2 $20 $80
2009 2009 Q3 $20
2009 2009 Q4 $30
2010 2010 Q1 $100
2010 Q2 $101
2010 Q3 $102 $230
2010 Q4 $103
2011 Q1 $10
In the above example year_name is not showing up for 2010 Q2 and after. However if I change the primary key for level 'Quarter' by having key consist of year name and quarter name instead of just quarter name the issue doesnt occur and drill down works great. The only issue is when I drill from qtr it first shows year name and quarter name instead of showing the next level which would be month name.
Sorry about the long message but I thought you might notice something in how I have set up the keys.
Thanks

Changing the dimension hierarchy level keys in RPD online mode caused issue

Hi,
We tried to correct the dimension hierarchy level keys and remove prefered drill path settings in the business model layer in RPD in online mode. However this caused all the reports and dashboards based off of this subject area to show incorrect, and/or restricted data. The physical query generated by the answers requests were also incorrect.
Even restarting the server and presentation services could not resolve the issue. Can someone please help us to understand what could have caused this issue?
Thanks in advance

Hi,
I am not sure why the existing reports throw an error when I change the RPD dimension hierarchy level keys. Does anyone know how I resolve this issue.
This is urgent. Any help will be most appreciated.
Thanks in advance.

Logical Difference of defining Multiple Logical level keys

Hi All,
We add logical level keys in BMM layer by right cliking the logical level column of a dimesional hierarchy, doing so defines a new logical key, i already have another logical level column defined as logical level key.
When i double click on logical level hierarchy, it has keys tab where i have two keys now.
say the two keys are: "channel desc key" and "channel id key"
My question is in one key say "channel id key" if we click edit, i am getting all the columns including channel desc column, so if i click it as key, it forms a composite key of (channel id) + (channel desc) inside "channel id key". Then what is the use of maintaining another key = "channel desc key"
Is there any logical difference of ("maintaining two keys having single column defined as key in either of them") and ("maintaining one key having two logical columns defined as keys in a single logical level key")?
Thanks in Advance.
Regards,
Sreekanth.

Hey got the answer, there is a difference, if i add multiple columns as keys under a single logical level key, they both come under one key and its drill down on both the columns, i cannot select selectively out of which column of the two drill down is applicatble.
If i create two different logical keys for two columns i can selectively choose which column drill down is applicable to.
Drill Down is based on "Logical Level Key" not on Logical Level Column selected as key.
Thanks,
Sreekanth.

Defining a level without a natural key

Hi All,
How can i define a level that only has a description ... I only need to have a surrogate key and the description of the level ... there's no natural key
is it possible?

I tried to make this trick and mark the description as the business natural key ... but then when I tried to use this dimension in a mapping i got an error stating that the dimension doesn't have an updatable field which is a must

Regarding Logical level key and row wise initialization

Hi Gurus,
What is the purpose of row wise initialization in external table authentication and when we have to go for row wise initialization.
Why we have to enable logical level key in hierarchy is this only for getting drill down to the next level if we make two columns as logical level key what will happens. If we want to enable a column as a logical level key what are the character sticks that column should satisfy.
Thanks,

1) Row Wise Initialization used to hold multiple values in a variable. Let says SQL gives 4 rows (A,B,C,D) as output. Now I want to hold 4 value in a variable to get this happen we need to go for RowwiseIniziation. If you do not do this at any point in time Variable holds only value A not others. Simply it works as Array.
2) Level keys define the unique elements in each level and provide the context for drill down. You can make two logical columns as logical key but you need to make sure what to be displayed in your hierarchy by selecting DISPLAY. If you make to as separate logical keys and set Display for both you get two columns in the hierarchy
http://gerardnico.com/wiki/dat/obiee/hierarchy_level_based

Use of New logical Level Key in OBIEE

Hi all,
can anybody tell me what is the use of newlogicallevel key in hierarchies(OBIEE).
why we need to set a newlogical level key for each level in hierarchies.
pls explain in detail....
regards
bharath

You may get info as below if you use Admin tool help file
Level keys. Each logical level (except the topmost level defined as a Grand Total level) needs to have one or more attributes that compose a level key. The level key defines the unique elements in each logical level. The dimension table logical key has to be associated with the lowest level of a dimension and has to be the level key for that level.
A logical level may have more than one level key. When that is the case, specify the key that is the primary key of that level. All dimension sources which have an aggregate content at a specified level need to contain the column that is the primary key of that level. Each logical level should have one level key that will be displayed when an Answers or Intelligence Dashboard user clicks to drill down. This may or may not be the primary key of the level. To set the level key to display, select the Use for drill down check box on the Level Key dialog box.
Be careful using level keys such as Month whose domain includes values January, February, and so on—values that are not unique to a particular month, repeating every year. To define Month as a level key, you also need to include an attribute from a higher level, for example, Year. To add Year, click the Add button in this dialog and select the logical column from the dialog that is presented.

Main item and Hierarchy level items in SAP EWM

We use ERP SAP AFS and EWM 9.1
ERP sales order 20000 - 5PCS ( Different grid values chosen and delivery is distrubuted to EWM)
Outbound delivery order contains main item and corresponding SKU displayed with Grid values like Color, Cup and Size. (Hierarchy Level)
20000
20000-0001A30
20000-0001A32
20000-0001C34
20000-0001B36
20000-0001D38
We create Warehouse tasks for SKU items ( Items 60,70,80,90,100) for picking.
I need to process VAS activites for this.
Price labeling and putting on plastic bag for all SKU's ( 2 VAS activity).
I have maintained packaging specification and tried to process it.
But here I get an error in VAS order. Because WR Qty from ODO to VAS order is not copied. It is getting deleted at the time of VAS order creation.
Then I tried to maintain the packaging specification for item 20000 (main item) and process the VAS order. Here VAS order got created and WR Qty also displayed.
But Picking Warehouse tasks are created for SKU items not for main items. In this case I am not able to process it also.
Packaging specification for main item or SKU item I should consider? If it is for SKU , need to have lot of master data. Is there any link i can make maintaining packspec for main item and process the warehouse tasks for SKU.
Which way i have to go now?
Any suggestion please
Please ask me if you need more inputs

Hi Jobi,
I agree to Juergen, you'll need individual pack specs per subitem in order to process VAS on this level. Did you think of using batches and depending characteristics for the grid values? This is how EWM for Fashion works. Then you could define only VAS pack spec for multiple grid values.
Best regards,
Christian
Remark: did you consider EWM for Fashion for your implementation?

Hierarchy Level Values Field SAP Retail

Hello Everyone,
I´m looking for the table and the fields specifically that contains the values of the hierarchy levels. I was looking in the table KLAH but only brings me the CLASS number (Material Group) and I need the values of the levels.
Hope you can help me
Regards,

Hi Jobi,
I agree to Juergen, you'll need individual pack specs per subitem in order to process VAS on this level. Did you think of using batches and depending characteristics for the grid values? This is how EWM for Fashion works. Then you could define only VAS pack spec for multiple grid values.
Best regards,
Christian
Remark: did you consider EWM for Fashion for your implementation?

Hierarchy Level value displayed in BEx Query

Is there a way to display the Hierarchy Level value (0, 1, 2, etc...) associated with each hierarchy level in BEx Query as a characteristic?
we are currently using the Crystal Reports function HierarchyLevel(GroupingLevel(GL Account Node id)) to display the level of the node (0, 1, 2, etc...). Is there something similar to this in BEx Query.
We would like to use this Level value to do groupings in Crystal Reports. When we try to create a Group, we can only create the groups on fields that are brought over in the BEx Query results.
Thanks --

Hi ,
Hierarchy level can be defined in Bex query as well.
In the query property there is option where you can say hierarchy active for that particular object.
Also you can define level upto which it can be active in initial display say 3 level
Also when you want to drill down further level 4,5 you can right click and select that particular level say 4 or 5 or 6.
If you want to display hierarchy flat there is no option in BW then to right code,but I heard in crystal report it will automatically display in fl;at version as well means
Level 0 level 1 ......KF1 KF2 etc.
Thanks and regards

Loading Hierarchy levels as Navigational Attributes of 0MATERIAL.

Hello Guys, 
bit of background about the issue: 
I am loading 0MATERIAL hierarchy from ECC using 0MATERAIL_LKLS_HIER Data source.(IS Retail). this job runs very fast.
We have a 8 level hierarchy in ECC/BI and the lowest level of hierarchy is 0MATERAIL. I am also loading 0MATERIAL_ATTR from ECC. While loding 0MATERAIL_ATTR into BI, i need to populate each hierarchy level of an artcile as navigation attributes of 0MATERIAL. 
For this requiremetn i wrote a start routine in the update rules and reading hierarchy levels and node names from /BI0/HMATERIAL table. the problem is the performance of the extractor is very very poor. It runs for more than 10 hours every day and it is causing many problems for our transactional data loads. 
Here is the code i am using in my start routine. 
I need suggestions on improving the performance of this extractor asap. are there any other best practices to load Article hierarchy levels as attributes apart from using ABAP lookups?? any help will be appreciated. 
TYPES: BEGIN OF TY_HIER, 
 MATERIAL TYPE /BI0/OIMATERIAL, 
 HIER_LEVEL1 TYPE RSSHNODENAME, 
 HIER_LEVEL2 TYPE RSSHNODENAME, 
 HIER_LEVEL3 TYPE RSSHNODENAME, 
 HIER_LEVEL4 TYPE RSSHNODENAME, 
 HIER_LEVEL5 TYPE RSSHNODENAME, 
 END OF TY_HIER. 
DATA: GT_HIER TYPE STANDARD TABLE OF TY_HIER, 
 WA_HIER TYPE TY_HIER. 
DATA: LT_MAT_HIER TYPE STANDARD TABLE OF /BI0/HMATERIAL, 
 WA_MAT_HIER TYPE /BI0/HMATERIAL, 
 wa_hier TYPE ty_hier. 
DATA: l_nodename TYPE rsshnodename. 
* Retrieving the whole hierarchy table into an internal table 
SELECT * FROM /BI0/HMATERIAL INTO TABLE LT_MAT_HIER. 
* Looping at the data package 
LOOP AT DATA_PACKAGE. 
 WA_HIER-MATERIAL = DATA_PACKAGE-MATERIAL. 
* Sort internal table for binary search 
 Sort LT_MAT_HIER by iobjnm nodename. 
 READ TABLE LT_MAT_HIER 
 INTO WA_MAT_HIER WITH KEY IOBJNM = '0MATERIAL' 
 NODENAME = DATA_PACKAGE-MATERIAL 
 binary search. 
 Sort LT_MAT_HIER by nodeid. 
 WHILE WA_MAT_HIER-TLEVEL > 1. 
 READ TABLE LT_MAT_HIER 
 INTO WA_MAT_HIER WITH KEY NODEID = WA_MAT_HIER-PARENTID 
 binary search. 
* IF SY-SUBRC = 0. 
 SHIFT WA_MAT_HIER-NODENAME BY 3 PLACES LEFT. 
 CASE WA_MAT_HIER-TLEVEL. 
 WHEN '07'. 
 CONTINUE. 
 WHEN '06'. 
 WA_HIER-HIER_LEVEL5 = WA_MAT_HIER-NODENAME. 
 WHEN '05'. 
 WA_HIER-HIER_LEVEL4 = WA_MAT_HIER-NODENAME. 
 WHEN '04'. 
 WA_HIER-HIER_LEVEL3 = WA_MAT_HIER-NODENAME. 
 WHEN '03'. 
 WA_HIER-HIER_LEVEL2 = WA_MAT_HIER-NODENAME. 
 WHEN '02'. 
 WA_HIER-HIER_LEVEL1 = WA_MAT_HIER-NODENAME. 
 WHEN OTHERS. 
 CONTINUE. 
 ENDCASE. 
 ENDWHILE. 
 APPEND WA_HIER TO GT_HIER[]. 
 CLEAR WA_HIER. 
ENDLOOP. 
SORT GT_HIER BY MATERIAL.
 
Thanks in advance 
Cheers 
POPS 

Any other thoughts guys...
is there a standard function module where we can specify the lowest level article detail as input and request for level 1 - 5 values ??

Totals not Displaying at hierarchy Level.

Hi All,
There are 2 questions.:
1)I have a report G/L a/c wise profit center hierarchy report which shows as for this G/l ac this is the profit center hier and hence there corresponding currency key figure values.
I am nt able to c the total for each G/L account..The Totals Row gets displayed randomly after Some G/L Accounts.
Why is this??
2)When i drill down the hierarchy, it shows the Currency value only for the expanded level but in result row it displays as * (Star) ..I can C the Currency value as it gets Expanded, but in the totals i c as *..Please advice me on this to resolve this issue. Asap
Thanks

Hi,
1)I have a report G/L a/c wise profit center hierarchy report which shows as for this G/l ac this is the profit center hier and hence there corresponding currency key figure values.
I am nt able to c the total for each G/L account..The Totals Row gets displayed randomly after Some G/L Accounts.
Why is this??
---the hierarchy level the values will display like this and if you want gl accounts wise and total value then put GL account in the row section and take the remaining objects after that and see the results.
2)When i drill down the hierarchy, it shows the Currency value only for the expanded level but in result row it displays as * (Star) ..I can C the Currency value as it gets Expanded, but in the totals i c as *..Please advice me on this to resolve this issue. Asap
--- * will have some values. just place cursor and see the value.
Regs,
VAC
Assign points if usefull

Dynamic hierarchy-level entering dashboard & drill-down

Hi there,
I have a requirement to create a report which, depending on the user that opens the report, needs to start at a specific level within an organisation hierarchy. Once the user has opened the report (which will be part of a dashboard), he should be able to drill-down the organisation hierarchy from his entry-point down. I've been able to create that report but when drilling-down it doesn't quite work. No matter at which level a user opens the report, when drilling it will drill-down immediately to the lowest level of the hierarchy, skipping (= not showing) intermediate levels.
Here are the details:
Organization hierarchy:
- Org_Level_0
- Org_Level_1
- Org_Level_2
- Org_Level_3
- Org_Level_4
- Org_Level_5
- Org_Level_6
- Org_Level_7
- Org_Level_8
Using an InitBlock each user is assigned it's a session variable ENTRY_LEVEL which contains the user's organization hierarchy level (i.e. '5'). For Testuser5 the session variable contains '5'.
I've created the report containing two columns:
- A dimension column called 'Organization'
- A measure column called 'Availability%'
In the dimension column I've entered the following formula:
CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='0' THEN DIM_ORGANISATIE." Org_Level_0"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='1' THEN DIM_ORGANISATIE." Org_Level_1"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='2' THEN DIM_ORGANISATIE." Org_Level_2"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='3' THEN DIM_ORGANISATIE." Org_Level_3"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='4' THEN DIM_ORGANISATIE." Org_Level_4"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='5' THEN DIM_ORGANISATIE." Org_Level_5"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='6' THEN DIM_ORGANISATIE." Org_Level_6"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='7' THEN DIM_ORGANISATIE." Org_Level_7"
ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='8' THEN DIM_ORGANISATIE." Org_Level_8"
END END END END END END END END END
In the Column properties/Column Format tab for the dimension column I've disabled Column Heading Interaction but I've set Value Interaction to 'Drill'.
When opening the report as Testuser5, the Dimension column shows the correct dimension object from that user: Org_Level_5. However when then clicking on the dimensionvalue, the next dimension displayed is Org_Level_8, instead of Org_level_6.
Any suggestion on how to obtain the desired result?
Thanks!
Edited by: The_Dutchman on Oct 7, 2009 5:31 PM

Check in the RPD in the BMM in the dimension wheater all levels have a key that is set to use for drill down. It seems that only Org_Level_8 (the last level, detail) has key - use for drill down checked. This allow columns on the level to be displayed when driiling from up level to the current one. So maybe this is a reason that you get only Org_Level_8 data when driiling from any level from the case statement.
Regards
Goran
http://108obiee.blogspot.com

Activated Hierarchy Level

Hi Everyone,
Need to show the Activated Hierarchy Level in the reporting header (Upper left corner of the Excel Sheet). Is there any way. I tried out the option of activating the display option if the "Value of Nodes" in the properties of the hierarchy. Do give me a suggestion.
Thank you,

Hi Marc,
In the query designer screen when you choose an hierarchy. In the Properties below it you have the option of choosing 'Expand to Level'. It gives a number by default. But you can change that also. so I want this number to be displayed in the Excel sheet with the Hierarchy 'Text' or 'Key' which ever option we choose. Hope I am clear.
Thank you..

Hierarchy level

Hi all,
How I can explode the number of hierachy level in the query like in the below example?
Committente/vendite     Hierarchy level
DIVECO     1
> ELETTR.SICILIA            1
> ELETTR.CAMPANIA            1
> ELETTR.LIGURIA            1
> ELETTR.MARCHE                    1
    MEGA                    2
    ELETTRICA 88 S.N.C.            2
    F.E.D. FORN.ELETTR.            2
    ALESE LUIGI                    2
    VIMEL SRL                    2
    ELETTRICA CAROSI           2
Thanks a lot
Best regards
Gianmarco

> Hi all,
> How I can explode the number of hierachy level in the
> query like in the below example?
>
> Committente/vendite     Hierarchy level
> DIVECO     1
> > ELETTR.SICILIA            1
> > ELETTR.CAMPANIA            1
> > ELETTR.LIGURIA            1
> > ELETTR.MARCHE                    1
>     MEGA                    2
>     ELETTRICA 88 S.N.C.            2
>     F.E.D. FORN.ELETTR.            2
>     ALESE LUIGI                    2
>     VIMEL SRL                    2
>     ELETTRICA CAROSI           2
>
> Thanks a lot
>
> Best regards
>
> Gianmarco
> Hi all,
> How I can explode the number of hierachy level in the
> query like in the below example?
>
> Committente/vendite     Hierarchy level
> DIVECO     1
> > ELETTR.SICILIA            1
> > ELETTR.CAMPANIA            1
> > ELETTR.LIGURIA            1
> > ELETTR.MARCHE                    1
>     MEGA                    2
>     ELETTRICA 88 S.N.C.            2
>     F.E.D. FORN.ELETTR.            2
>     ALESE LUIGI                    2
>     VIMEL SRL                    2
>     ELETTRICA CAROSI           2
>
> Thanks a lot
>
> Best regards
>
> Gianmarco
> Hi all,
> How I can explode the number of hierachy level in the
> query like in the below example?
>
> Committente/vendite     Hierarchy level
> DIVECO     1
> > ELETTR.SICILIA            1
> > ELETTR.CAMPANIA            1
> > ELETTR.LIGURIA            1
> > ELETTR.MARCHE                    1
>     MEGA                    2
>     ELETTRICA 88 S.N.C.            2
>     F.E.D. FORN.ELETTR.            2
>     ALESE LUIGI                    2
>     VIMEL SRL                    2
>     ELETTRICA CAROSI           2
>
> Thanks a lot
>
> Best regards
>
> Gianmarco
Thank you,
but I need to explode a hierarchy level like characteristic or key figure:
Committente/vendite        Hierarchy level    QUANTITY
> ELETTR.MARCHE                     1             60
     MEGA                           2             15
     ELETTRICA 88 S.N.C.            2             15
     F.E.D. FORN.ELETTR.            2             15
     ALESE LUIGI                    2             15
Regard

Defining hierarchy level keys

Similar Messages

Maybe you are looking for