Charting on a specific hierarchy Level

Hi Experts,
I have created a Profit & Loss report based on an SAP Query. I've added a hierarchy group and a key figure summary.
The hierarchy has 8 levels represented in a single group. I'd like bar chart level 2 of this hierarchy in the report header.
How can I do this?
Best regards,
Andrew

Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551

Similar Messages

How to show specific hierarchy level in Query

Hi!
I have a planning query using a hierarchy based on the customer.
The customer is been showed in they query using a hierarchy. The hierarchy contains of 11 levels.
The user enters a number of hierarchy nodes for selection. These nodes can be from different levels.
Question 1:
How can I maintain the output of the query, so that the hierarchy shows data from level 2 nodes downwards?
E.g. Hierarchy looks like:
Root
     1234
          5678
               9101112
User enters 9101112 for hierarchy node selection
Output should be:
5678
     9101112
Question 2:
If there is a solution for Question 1, is there also any possibility to restrict the user from drilling down the hierarchy?
Thanks and regards
Marco

Suresh,
      I am not sure how you can search across all the transports for a specific value in one of the object(table) in the transport.Is your planning level defintion still the same that you would like to move it to production ? If it is, you could transport your level right now from Dev to QA and to PROD, you can do it for the entire level or selected objects within the level.
Hope this helps.
Cheers
Srini

How to only display specific members from dissimilar hierarchy levels?

Hi,
I have a Business Partner that routinely wants to build a report that displays members from dissimilar hierarchy levels. For example, she wants to display member "210_UNASSIGNED EXP/ACC" from level 8 and member "E090_ADVISOR SERVICES" from level 1. When she filters on just those two members, the reports displays as such:
She then must manually expand the "E020_CORPORATE AND EXECUTIVE" member 7 times to see "210_UNASSIGNED EXP/ACC":
Is there anyway to make her life easier and have the report display only the "210_UNASSIGNED EXP/ACC" member and the "E090_ADVISOR SERVICES" member, even though they are from different levels?
Thanks,
Michael J Titera
BI4.0 SP8.3
SQL Server 2012

Hello Michael
Displaying information from mixed hierarchy levels without the context of the parent members is a reporting workflow best suited to WebI and CR. The AOLAP content can be exported as an Analysis View and then this becomes a data source for WebI and CR.
Our previous product Voyager used to allow member selection from mixed levels without the context of parent members but it caused a lot of confusion and misinterpretation of the data, which is why we deliberately do not have it in AOLAP.
Worth noting that BI4.1 was a big release for AOLAP with many enhancements. One is "Expand to Level". So instead of having to click 7 times to expand the hierarchy, it now just requires one mouse right-click to do the same thing.
Regards
Ian

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?

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

Highlight hierarchy level rows in the query

Hi,
I have a requirement where I have to highlight the Hierarchy level specific rows.I have to highlight SAPBEXHLevel1,SAPBEXHLevel2,SAPBEXHLevel3 classes. Can someone explain me with a sample code on how to achieve this in ZCL_RSR_WWW_MODIFY_TABLE and to do what changes necessary. Points will be duly assigned.
Thanks,
Kal

Table interface:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/403c789a-aafb-2910-e5a4-835645f0721b
http://help.sap.com/saphelp_nw04/helpdata/en/d8/f3a83adae1a010e10000000a11402f/frameset.htm

Aggregating data loaded into different hierarchy levels

I have some problems when i try to aggregate a variable called PRUEBA2_IMPORTE dimensinated by time dimension (parent-child type).
I read the help in DML Reference of the OLAP Worksheet and it said the follow:
When data is loaded into dimension values that are at different levels of a hierarchy, then you need to be careful in how you set status in the PRECOMPUTE clause in a RELATION statement in your aggregation specification. Suppose that a time dimension has a hierarchy with three levels: months aggregate into quarters, and quarters aggregate into years. Some data is loaded into month dimension values, while other data is loaded into quarter dimension values. For example, Q1 is the parent of January, February, and March. Data for March is loaded into the March dimension value. But the sum of data for January and February is loaded directly into the Q1 dimension value. In fact, the January and February dimension values contain NA values instead of data. Your goal is to add the data in March to the data in Q1. When you attempt to aggregate January, February, and March into Q1, the data in March will simply replace the data in Q1. When this happens, Q1 will only contain the March data instead of the sum of January, February, and March. To aggregate data that is loaded into different levels of a hierarchy, create a valueset for only those dimension values that contain data. DEFINE all_but_q4 VALUESET time
LIMIT all_but_q4 TO ALL
LIMIT all_but_q4 REMOVE 'Q4'
Within the aggregation specification, use that valueset to specify that the detail-level data should be added to the data that already exists in its parent, Q1, as shown in the following statement. RELATION time.r PRECOMPUTE (all_but_q4)
How to do it this for more than one dimension?
Above i wrote my case of study:
DEFINE T_TIME DIMENSION TEXT
T_TIME
200401
200402
200403
200404
200405
200406
200407
200408
200409
200410
200411
2004
200412
200501
200502
200503
200504
200505
200506
200507
200508
200509
200510
200511
2005
200512
DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
-----------T_TIME_HIERLIST-------------
T_TIME H_TIME
200401 2004
200402 2004
200403 2004
200404 2004
200405 2004
200406 2004
200407 2004
200408 2004
200409 2004
200410 2004
200411 2004
2004 NA
200412 2004
200501 2005
200502 2005
200503 2005
200504 2005
200505 2005
200506 2005
200507 2005
200508 2005
200509 2005
200510 2005
200511 2005
2005 NA
200512 2005
DEFINE PRUEBA2_IMPORTE FORMULA DECIMAL <T_TIME>
EQ -
aggregate(this_aw!PRUEBA2_IMPORTE_STORED using this_aw!OBJ262568349 -
COUNTVAR this_aw!PRUEBA2_IMPORTE_COUNTVAR)
T_TIME PRUEBA2_IMPORTE
200401 NA
200402 NA
200403 2,00
200404 2,00
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
2004 4,00 ---> here its right!! but...
200412 NA
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
2005 10,00 ---> here must be 30,00 not 10,00
200512 NA
DEFINE PRUEBA2_IMPORTE_STORED VARIABLE DECIMAL <T_TIME>
T_TIME PRUEBA2_IMPORTE_STORED
200401 NA
200402 NA
200403 NA
200404 NA
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
2004 NA
200412 NA
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
2005 10,00
200512 NA
DEFINE OBJ262568349 AGGMAP
AGGMAP
RELATION this_aw!T_TIME_PARENTREL(this_aw!T_TIME_AGGRHIER_VSET1) PRECOMPUTE(this_aw!T_TIME_AGGRDIM_VSET1) OPERATOR SUM -
args DIVIDEBYZERO YES DECIMALOVERFLOW YES NASKIP YES
AGGINDEX NO
CACHE NONE
END
DEFINE T_TIME_AGGRHIER_VSET1 VALUESET T_TIME_HIERLIST
T_TIME_AGGRHIER_VSET1 = (H_TIME)
DEFINE T_TIME_AGGRDIM_VSET1 VALUESET T_TIME
T_TIME_AGGRDIM_VSET1 = (2005)
Regards,
Mel.

Mel,
There are several different types of "data loaded into different hierarchy levels" and the aproach to solving the issue is different depending on the needs of the application.
1. Data is loaded symmetrically at uniform mixed levels. Example would include loading data at "quarter" in historical years, but at "month" in the current year, it does /not/ include data loaded at both quarter and month within the same calendar period.
= solved by the setting of status, or in 10.2 or later with the load_status clause of the aggmap.
2. Data is loaded at both a detail level and it's ancestor, as in your example case.
= the aggregate command overwrites aggregate values based on the values of the children, this is the only repeatable thing that it can do. The recomended way to solve this problem is to create 'self' nodes in the hierarchy representing the data loaded at the aggregate level, which is then added as one of the children of the aggregate node. This enables repeatable calculation as well as auditability of the resultant value.
Also note the difference in behavior between the aggregate command and the aggregate function. In your example the aggregate function looks at '2005', finds a value and returns it for a result of 10, the aggregate command would recalculate based on january and february for a result of 20.
To solve your usage case I would suggest a hierarchy that looks more like this:
DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
-----------T_TIME_HIERLIST-------------
T_TIME H_TIME
200401 2004
200402 2004
200403 2004
200404 2004
200405 2004
200406 2004
200407 2004
200408 2004
200409 2004
200410 2004
200411 2004
200412 2004
2004_SELF 2004
2004 NA
200501 2005
200502 2005
200503 2005
200504 2005
200505 2005
200506 2005
200507 2005
200508 2005
200509 2005
200510 2005
200511 2005
200512 2005
2005_SELF 2005
2005 NA
Resulting in the following cube:
T_TIME PRUEBA2_IMPORTE
200401 NA
200402 NA
200403 2,00
200404 2,00
200405 NA
200406 NA
200407 NA
200408 NA
200409 NA
200410 NA
200411 NA
200412 NA
2004_SELF NA
2004 4,00
200501 5,00
200502 15,00
200503 NA
200504 NA
200505 NA
200506 NA
200507 NA
200508 NA
200509 NA
200510 NA
200511 NA
200512 NA
2005_SELF 10,00
2005 30,00
3. Data is loaded at a level based upon another dimension; for example product being loaded at 'UPC' in EMEA, but at 'BRAND' in APAC.
= this can currently only be solved by issuing multiple aggregate commands to aggregate the different regions with different input status, which unfortunately means that it is not compatable with compressed composites. We will likely add better support for this case in future releases.
4. Data is loaded at both an aggregate level and a detail level, but the calculation is more complicated than a simple SUM operator.
= often requires the use of ALLOCATE in order to push the data to the leaves in order to correctly calculate the aggregate values during aggregation.

Limitation on Hierarchy levels

Hi,
I want to find out what is the limitation on number of Hierarchy levels (Custom Hierarchies) that can be created in BO Universe?
And is this limitation oriented with the DB we connect?
As I am using Netezza DB so I want to know the number of hierarchy levels that I can create for objects in Netezza DB?

We have a BEx query, having 9 product Hierarchy levels. When we are creating Universe, there is no issue. But when we do integrity check, getting a lot of parse errors and could not make the universe to work.
Is there any limitation on number of herarchies to be supported from BEx query to Universe? Any OSS notes / Lessons learnt will be much appreciated. Please help urgently. Thanks.

Table relationship between hierarchy level and merchandise category

1) Want to find Merchadise Category from Merchandise Hierarchy level which is attached with same Merchandise category.
I am having data/TABLE as below.
my input: M_WWG1C_class
i want to fetch data matkl in T023 or matkl in MARA for the same article within same merchandise category.
How i can have link?
2) i am having input CAWN_atwrt(Characteristic Value) and how i can reach matkl in T023 or matkl in MARA for the same article within same merchandise category.

Oracle does not support REPEATABLE READ transaction isolation level. It only supports SERIALIZABLE, READ COMMITED and READ ONLY isolation levels.
The default is READ COMMITED.
While the READ COMMITED can access all the committed data till the point of execution in transaction, READ SERIALIZABLE can access committed data till the point of start of transaction.
Another difference between two with respect to ROW LEVEL LOCKING is
Both read committed and serializable transactions use row-level locking, and both will wait if they try to change a row updated by an uncommitted concurrent transaction. The second transaction that tries to update a given row waits for the other transaction to commit or roll back and release its lock. If that other transaction rolls back, the waiting transaction, regardless of its isolation mode, can proceed to change the previously locked row as if the other transaction had not existed.
However, if the other blocking transaction commits and releases its locks, a read committed transaction proceeds with its intended update. A serializable transaction, however, fails with the error "Cannot serialize access", because the other transaction has committed a change that was made since the serializable transaction began.
Read following for clearing your concepts on transaction isolation levels and locking mechanisms
http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/server.920/a96524/c21cnsis.htm#2414
Chandar

Drill in BW hierarchy level in webi based on input control selection

Hello Experts,
I have a requirement in Webi. The Webi report is based on BW hierarchy and it is using hierarhcy both in the report output block and also in the report prompts. We are are BI 4.0 SP5,Patch 6. The report has input controls in it based on the BW Hierarchy. When the report is first executed,the user can drill down the hierarchy by clicking on the "+" nodes to the max level as shown in the screenshot below.
Now, when the user selects an input control, the data gets filtered but the hierarchy level automatically expands. In other words, when they select a data hierarchy showed in the input control the hierarchy in table is shown expanded and they want to see the hierarchy in the table close automatically.
So ideally its like this when a value from input control is selected.
Whereas the user wants it to be like this automatically on selecting a particular value from the input control and not in expanded form.
I'm aware of the Hierarchy depth function but that only takes us to a particular node based on depth and then doesn't allow further drilling after that.
Is there any setting in webi/bex about always keeping all sub nodes closed to prevent this expansion on selection of input control?
Thanks and regards,
Abhishek

Just did some research on on this and the SAP best practice: The question itself is logically incorrect.
A report/table filter where there is a hierarchy may remove rows without respecting the hierarchy structure. For this reason, a filter can remove a parent node currently expanded and keep leaves or
nodes collapsed. To avoid returning an empty table in this case the system automatically expands the hierarchy in the block to shows the resulting members
Thats why it automoatically expands the hierarchy.
Closing this thread. Thanks.

Hierarchy Level in report

Hi GURUS,
I have a requirement in report i.e. I need to display the Hierarchy level from the 4th level only, I do not want to see the first 3 levels, where do I do the settings for that in reporting.
I was told that there can be some settings done in Hierarchy tab of that info object in report level in Values of Posted Nodes. But even that option is disabled. If this is the way I need to do it then how to enable that option or if there is a different option then would appreciate if you explain me in detail. Thanks in advance.

Hi ganesh,
for this same as normal procedure.. but in BEX analyser.. in the query designer window properties.. I mean select ur hierarchy and right click and > select Ristrict-> and there you can select particular level of nodes only...
so, there you can select all fourth level nodes..and drag and drop it into right side window... and save it.. and execute the query..
so, now you can get only Fourth level nodes only in the reporting level...
i think this will helpfull to u..if it's ok ... Reward me points..
Thanks
@jay

Material Group Hierarchy Level 1 - Description

Hi,
We required Material Group Hierarchy Level 1(0RPA_WGH1) DESCRIPTION. we find data source 0MATL_GRP_1_TEXT to
get description. that standard data source created based on table TVM1T. We did find any data in that table. kindly guide me
how to acheive this.
Thanks

hi rajendra,
just check table T023T, hope this will help u.
thanks

Regd:hierarchy level query

hi friends,
i have a one employee table.
empid mangid.
1 0
2 1
3 2
i wanted display hierarchy level of the employee like..
wanna display uppper & lower mangid of employee.
if suppose i pass empid=2
then it should display hierarchy like...
managerid
0
3
because empid=2 parent of empid=3 and Chiledid of mangid=0.

Hi,
For this you have to use Connect by clause and Start with Class ,
Using This we can get Hirarical Data.]
SELECT empno,
ename,
job,
mgr,
hiredate
FROM emp
START WITH mgr IS NULL
CONNECT BY PRIOR empno = mgr
try like this
Thanks,
Sanjeev.

Identify hierarchy level

hi experts
i need to know in my report the hierarchy level on which user is currently on, like if he selects year/quarter/or month....
how can i achieve this please help
thanks and regards

Hi Kart
thanks for your reply.... i have tried it but i am getting dim_level column blank ....
see the steps which i have followed:-
1) i have created three views on top of my times view( which is being created using my main time dimension ), i have created join on d_year of my d_date_year_level to times_view.d_year, d_quarter to d_date_quarter_level, d_monthno to d_date_monthno_level
2) after creating join in my physical layer with times_view... then i dragged all my three views to my fact table in BMM layer and removed all columns except dim_level.... in fact table source i created one inner join with time_view... in content tab i set the aggregation level to ltimes_view detail logical level.
when i created report using year, dim_level, sales dim_level column is coming blank.
could you please help me if i have missed any step or done something wrong..
regards

Charting on a specific hierarchy Level

Similar Messages

Maybe you are looking for