Hierarchy Results
I have a problem with the results being returned for a hierarchy. The hierarchy is based on 0costcenter and it is used to identify, in effect, a headcount.
The problem I have is that for the first 6 nodes of the hierarchy, the results are bringing back the 'LAST' value posted, whereas the final 3 nodes are summing up the values to provide a total (which is what I want to do).
Does anyone know why this is happening or how I can display the totals for each hierarchy node?
Select the properties for the Key Figure that contains the incorrect value. Ensure the Cumulated check box is selected. Also ensure Apply To Results check box is selected and Calculate Along The Columns is selected from the drop down box.
This should ensure the Node totals are calculated correctly.
Similar Messages
-
Hi All,
I have a Hierarchy on infoobject 0MATERIAL. When we execute the report, the results rows are only shown for some nodes but not for others of the same level. The setting "Root/Totals Item Appears Above" is set. Also, the characteristic 0MATERIAL is set in the query to always display results.
Can you help me in sorting this out?
CheersHello,
Please let me know how did you set the following setting in query :
"Root/Totals Item Appears Above"
Thanks in advance.
WIth regards,
Anand -
Hi all,
Once Usage decision is done , the inspection lot is closed.Then i want to see result recorded for that lot,How to see the Result?
Thanks,
Sidhi,
You may also use QGA2, for hierarchial Result display against the lots.
Regards -
I've noticed something strange in our system.
We have queries defined using a time-dependent hierarchy for which we specified a key date different from the query date.
Now I cannot change it because the selection options for key date are greyed-out. Even creating a query from scratch with the hierarchy results in greyed-out key-date options on the hierarchy. It defaults to the key-date of the query. Can this be a change in behaviour after upgrade to 3.5?
Regards,
EricHi,
Ive made an additional search for OSS notes. Found a lot, concerned mainly on incorrect hierarchy or query key date.
Found also very strange note, # 674220 Date entry not valid for time-dependent hierarchy structure:
<b>Symptom
For characteristics with time-dependent hierarchy structures, the
hierarchy validity date is always the key date of the query
Other terms
Query, time-dependent hierarchy structures
Reason and Prerequisites
Programm Error
Solution
The date radio group buttons available for Key date
has no meaning, when hierarchy structure is time-dependent. The validity
date for hierarchy will always be taken as the key date of the query.
in this case. Hence, kindly ignore any other date entered in this field.
A corrective action will be taken in the future release to stop
entering any other date.</b>
It might be understood that hierarchy key date should always be as a query key date. Though the note was applicable to earlier releases but it could be read as that in future releases this option for hierarchy key date is going to be disabled.
Ive searched BW for 3.5 SP notes. Found nothing about this option to be disabled. Moreover, in my system this option is enabled. So, if there is a bug, I couldnt find anything usefull.
Documentation says that this option is to be enabled for time-dependent hierarchies only. So, if your situation is not caused by a bug, then something might be wrong with your hierarchies. Please look directly in SE16 at your H, I, J & K hierarchies tables, try to find something unusual. Maybe DATEFROM or DATETO values are missing in H table. Maybe the hierarchy is not active or corrupt. Or something.
Should you have found nothing, the last resort is to raise OSS note to SAP.
Best regards,
Eugene
Message was edited by: Eugene Khusainov -
No interval is loaded for hierarchy
Hi,
I am trying to upload a hierarchy for ZSNIKOD (basically a copy of 0IND_CODE). Some of the "leaves" are supposed to be single and some are supposed to be interval.
I am loading this data in a csv-file:
NODEID;INFOOBJECT;NODENAME;LINK;PARENTID;LEAFTO;LEAFFRO;LANGU;TXTSH;TXTMD;TXTLG
1;0HIER_NODE;AVD_A;;0;;;V;JORDBRUK;JORDBRUK;JORDBRUK
2;0HIER_NODE;AVD_B;;0;;;V;MINERAL;MINERAL;MINERAL
3;0HIER_NODE;AVD_C;;0;;;V;TILLVERKNING;TILLVERKNING;TILLVERKNING
4;0HIER_NODE;C_10;;3;;;V;LIVSMEDEL;LIVSMEDEL;LIVSMEDEL
5;0HIER_NODE;C_101;;4;;;V;Varor;Varor;Varor
6;ZSNIKOD;;;5;51130;51110;;;;
7;ZSNIKOD;10200;;5;;;;;
The hierarchy result in BI should be:
AVD_A - (0HIER_NODE)
AVD_B - (0HIER_NODE)
AVD_C - (0HIER_NODE)
-- C_10 - (0HIER_NODE)
--- C_101 - (0HIER_NODE)
[] 51110 - 51130 - (ZSNIKOD) 51110 - 51130
* 'infoobject text' - (ZSNIKOD) 10200
That is NOT the case. The result I get is:
AVD_A - (0HIER_NODE)
AVD_B - (0HIER_NODE)
AVD_C - (0HIER_NODE)
-- C_10 - (0HIER_NODE)
--- C_101 - (0HIER_NODE)
* Not assigned - (ZSNIKOD) #
* 'infoobject text' - (ZSNIKOD) 10200
It seems like the interval is not correct assigned when loading. I have marked the infoobject to accept intervals. I have also checked that "interval" is selected in the "Hierarchy selection" tab in the info package.
If anyone is interested in helping me I can send screenshots and further information...
Thanks!
//Sofie
Edited by: Sofie Havgard on Oct 7, 2009 12:00 PM
Edited by: Sofie Havgard on Oct 7, 2009 12:04 PMThere was a bug in our SAP system...
//sofie -
dear all,
i want the detail configuration for customer hireachy how to do it?
Regards.
DebeshHi,
Customer Heirarchy representation of complex customer structures. For example, you can display the regional structure of a buying group as a customer hierarchy. The customer hierarchy contains pricing information that is valid for all customers in the hierarchy.Customer hierarchies represent complex customer structures in the system and are used for the organizational structures of buying groups or chains of retail outlets, for example.
A customer hierarchy consists of individual hierarchy nodes which are allocated hierarchically to each other on different levels to produce lower-level and higher-level nodes. The structure of the customer hierarchy can be kept flexible and and adapt to change at any time by means of the option to move hierarchy nodes dynamically.
The customer hierarchy function in the R/3 system is carried out using the partner concept. The individual nodes are defined as partners and linked to a higher level partner.
During sales order and billing processing, customer hierarchies are used in pricing to take into account every aspect relevant to pricing and rebates for customers with a complex group and association structure in particular.
For example, if a sales order is edited for a customer who is allocated to a customer hierarchy relevant for pricing, the relevant hierarchy path, which displays the chain of hierarchy nodes to which the initial hierarchy node is related, is determined automatically. If condition records exist for a higher-level node, pricing is carried out with reference to the conditions available there.
The hierarchy nodes of a customer hierarchy are created as customer master records with account group (0012). The structure of the hierarchy results from allocating the hierarchy node master records. It is also possible to create customers with different account groups as hierarchy nodes (for example, 0001 for the sold-to party).
If you want to make your own settings for customer hierarchies, you must edit the following points:
Define hierarchy types with default partner function
Define allowed account group allocations for each hierarchy type
Allocate sales areas to each other
If necessary, allocate the hierarchy type relevant for pricing for each sales document type
Then check the partner functions to determine whether they suffice for the hierarchy levels you require and, if necessary, create further partner functions
Transaction: OVH1--Define Hierarchy Types
Only create a new hierarchy type if you:
need your own evaluations for customer hierarchies or
need different hierarchies for different business transactions.
The R/3 System uses the partner concept to realize the customer hierarchy function. Individual points are defined as partners and connected with a link to a higher-level partner.
The hierarchy type controls the following points:
It specifies the purpose of a certain hierarchy.
It specifies the default partner function.
2.Set Partner Determination For Hierarchy Categories
PATH-- SPRO-IMG-SALES AND DISTRIBUTION-MASTER DATA-BUSINESS PARTNERS-CUSTOMERS-CUSTOMER HEIRARCHIES-
SET PARTNER DETERMINATION FOR HEIRARCHY CATEGORIES.
When making settings for customer hierarchy, you must not only take hierarchy category into account. You must also consider higher-level partner functions which are maintained in partner determination.
Depending on hierarchy category, special partner functions are determined during order processing for each node on the hierarchy path. Starting with the initial partner function (in standard versions such as 1A), higher-level partner functions are determined and assigned to nodes in the customer hierarchy path.
Partner functions 1A - 1C have been defined in the standard release with the initial partner function appearing on the lowest level.
If you wish to use more than three customer hierarchy levels, you must first extend the partner functions (Table TPAR). Keep in mind that the system can process only up to 26 hierarchy levels.
Note
Use at least the same amount of higher-level partner function levels as you use customer hierarchy levels. During path determination and price determination only the same amount of customer hierarchy levels are taken into account as there are higher-level partner function levels available. This is why there may be some remaining customers not taken into account.
Standard settings
In the SAP standard system, there is a hierarchy category as well as three partner functions which are set for the customer hierarchy and are available for you to use.
1. If necessary, create additional partner functions in order to use additional hierarchy levels.
2. Assign the account groups to the partner functions.
The path to the account group assignment is: Partner functions -> Environment -> Account group function assignment.
3. Maintain a partner determination procedure and assign order types and and billing types. You should also make the following settings:
a) Cannot be changed
b) Mandatory function blank
c) Access: B for customer hierarchy
3. Assign Accounts- OVH2
you assign the possible higher-level account groups to the account groups permitted for each customer hierarchy type. Therefore, both the valid account groups for each hierarchy type are defined and the higher-level account groups of the valid account groups.
This will prevent the system assigning a ship-to party above a sold-to party.
4. OVH3-Assign Sales Areas
In this step, you assign sales areas to each other which allows you to determine whether a sales area uses its own customer hierarchies or shares one with another sales area.
5. OVH4- Assign Hierarchy Type For Pricing By Sales Document Type
In this step, you can assign a hierarchy type relevant for pricing for each sales document type. This way you can define the sales document types for which pricing data is taken into account if the data was determined on a level higher than the customer.
For every hierarchy node which is selected as relevant for pricing, you can create condition records. During pricing, the customer hierarchy allows the use of price and rebate agreements which were determined on a level higher than the customer. If one or more hierarchy nodes in the hierarchy path of a sales order contain pricing data, these are automatically taken into account in the sales order during pricing.
Requirements
If you want the pricing data of one or more hierarchy nodes in a hierarchy path to be taken into account automatically during pricing, the following requirements must be fulfilled:
You must have marked the hierarchy node as relevant for pricing in the master record.
Condition records must exist for the hierarchy node(s).
You must check whether the partner functions in the system are sufficient for the hierarchy levels which you require. If necessary, create new partner functions.
Actions
Transaction -VDH1- Display Customer Heirarchy
Kindly please let me know If you need any more information on this.
Regards
Ram Pedarla -
No Results after build a Parent-Child Hierarchy in OBIEE11G
Hi All:
Here's an problem. I followed the "http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/" this article step by step to create a parent-child hierarchy in admin tool in OBIEE11G.
But after check in and try to retrieve the hierarchy data in Answer. There's always displays "No Results."
Is there any suggestions for this ? Really urgent and thanks for your help.
Best regards
Sunny@Aketi
It is One way that We derive
"sys_connect_by_path(RowIDToChar(RowID),'.') as
RowIDList"
Then
We use Left Join Using
"instr(RowIDList,RowIDToChar(RowID))".sorry, didn't catch what you mean.
my site :-)
http://oraclesqlpuzzle.hp.infoseek.co.jp/4-13.html
pity, I don't know Japanese :(
@Rob
your query is good and simple :) probably it's the best alternative for the OP.
But it won't work with not a plain hierarchy, e.g.:
1
2 3
4
5 6
SQL> create table hierarchy (child,parent)
2 as
3 select 1, null from dual union all
4 select 2, 1 from dual union all
5 select 3, 1 from dual union all
6 select 4, 3 from dual union all
7 select 4, 2 from dual union all
8 select 5, 4 from dual union all
9 select 6, 4 from dual
10 /
Table created
SQL>
SQL> create table data (hierarchyid,value)
2 as
3 select 5, 10 from dual union all
4 select 6, 25 from dual
5 /
Table created
SQL>
SQL> select h.child
2 , sum(connect_by_root d.value)
3 from hierarchy h
4 , data d
5 where h.child = d.hierarchyid (+)
6 connect by prior h.parent = h.child
7 group by h.child
8 order by h.child
9 /
CHILD SUM(CONNECT_BY_ROOTD.VALUE)
1 70
2 35
3 35
4 70
5 10
6 25
6 rows selected
SQL> -
Problem in positioning of the Overall Result Row when using a hierarchy
Hello All,
i've built a query on a hierarchy and i want the 'Overall Result' to be displayed at the bottom.
I've made the following setting in the Query Designer
<b>Query Properties -> Display -> Results Position -> Bottom/Right</b>
but still, the 'Overall Result' is displayed at the top of the result rows.
Could some one please tell me if this is how the functionality is expected to work when a hierarchy is used for display ?
We are on BW3.1 SP 9
Best Regards,
Sanjay<b></b>Hi Roberto,
could you please let me know if the following analysis of mine is correct.
The Overall Result will be dispalyed at the top if the 'Position of Lower-Level Nodes' is set to 'Down'(default setting) in the Hierarchy Properties of
the characteristic. If the 'Overall Result' is required to be at the bottom then 'Position of Lower-Level Nodes' has to be set to 'Up'. It is not possible to display the Overall Result at the bottom with the 'Position of Lower-Level Nodes' set to 'Down'
Will greatly appreciate your help !
Best Regards,
Sanjay -
Query with Cost Center Hierarchy giving incorrect results
Hi All,
I have a universe built based on BEx query on Cost Center cubes. When enabling hierarchy in BEx Query and building Web intelligence Report based on the universe, I get incorrect results. The levels of the hierarchy is incorrect, many of the cost centers are missing etc. I checked the universe and confirmed that all levels of hierarchy are generated correctly. The Lov generated for these levels are correct and I see the complete hierarchy when using the BEx Variable in Universe for filtering.
I tried the same query with Hierarchy disabled with a different universe and it is providing correct results. Not sure what I'm missing here. Any inputs regarding this is appreciated.
Thanks & Regards,
SreeIngo, Thanks for your suggestion. Of course, I did update the Universe after any changes in the query. Tried different query setting related to hierarchy to make it work, but didn't many any difference and I get consistently incorrect results.
One thing what I wanted to confirm is, if there is any known bug in SP 2 Fix Pack 2.7 related to hierarchies. If not, it might be me doing some thing wrong and I will look into in more detail.
Thanks & Regards,
Sree -
Exception (Aggregation) in Hierarchy nodes results
Hi All,
We have a requirement to sum all values (as results in hierarchy levels) based on the value of a specific characteristics. example as below is what we want to achieve. Country, Product group, materials are all characteristics and this is viewed as hierarchy in the query. In each material there is a calculation components that will shown the value of Sales Qty, Price/unit and Amount. What we want is to sum up ONLY the Amount value and presented in the hierarchy nodes so that we can see how much sales we did by product group and subsequently by country as whole. If we drill across we will be able to achieve this but we want to drill down as we have the time characteristics and variances at the columns. and no, we do not want user to drill across the calculation components. This query is used in Integrated Planning for planning purposes integrated with BO and that is the structure of the planning layout we want. "Calculation component" is a infoobject that contains 'sales qty', 'price/unit' and 'sales amount' as master data values.
I have tried exception aggregation on calc component infoobject for 'LAST VALUE'. and it did capture only the Sales Amount value as result for node Calc Components. But the other results node State, country and Region also takes LAST VALUE.. which is not what i want. what i want is esseentially summation of all Sales amount for each calculation components by state, country and region.
Last Year | Variance | Current Year | Jan | Feb | Mar |......
Region X 200 (sum of all country's sales amount)
->Country A 200 (sum of all states' sales amount)
-> State Y1 80 (sum of all components's sales amount)
->Calc Components Z1 30
- Sales Qty 10
- Price/Unit 3
- Sales Amount 30
->Calc Components Z2 50
- Sales Qty 5
- Price/Unit 10
- Sales Amount 50
-> State Y2 120
->Calc Components Z1 40
- Sales Qty 10
- Price/Unit 4
- Sales Amount 40
->Calc Components Z2 80
- Sales Qty 10
- Price/Unit 8
- Sales Amount 80
any help would be appreciated...
eddiePlease try the below steps and I hope it should work for you.
Instead of calculated keyfigures,try to use local formula .Because i think sometimes CKF will not give the expected result if you use exception aggregation (not sure though,but i used only local formulas)
1. Create a first local keyfigure (Say F1)for the calculation and use exception aggreagation as 'Average' and reference characteristics as 'PDU'.
2. Create a second keyfigure ( Say F2) using the first keyfigure(F1) and use exception aggregation as 'Average' and reference characteristics as 'Sales Document', if you need the values based on average of the sales documents and hide the first keyfigure(F1)
I consider Sales document is the first level and PDU is the second level ( i mean lowest level) . Because you need to consider these sequencens as well when you design the exception aggregation.
Likewise you can create nested aggregations based on your requirements.
Please do let me know if it works.
Thanks. -
Result row while using hierarchy
Hi All
In one of the reports I have brought a hierarchy from the free characteristic.Although KF values are showing up for the nodes within the hiearchy ,The hiearchy main node shows a * against it.
Does any body have any idea on whats going wrong?
Is there any way to get the result row activated.
Thanks
JP JPHi,
the '*' symbol is because of diffrent units or currencies in underlying data.
You can do a conversation for unit/currency or use NO DIM for a formula in query.
NO DIM delivers purely numerical values of the expression and suppresses units and currencies.
Regards
Andreas -
Using measure at a certain hierarchy level and summarizing calculated results
Hi,
I have a four-level hierarchy structure (Category, SubCategory, SubSubCategory and Item) in a PivotTable containing two measures (measure 1, measure2). I need a third measure that compares results of those two measures at SubSubCategory level to
choose the maximum of those two measures. Selection should not be done at Item level or SubCategory or Category level.
Item level results should give blank values as result. After choosing the bigger measure value at SubSubCategory level, measure 3 should calculate the sum of measure 3 at SubCategory level and of course at Category level.
BR,
HeidiHi Heidi,
Thanks for providing the additional information. If I've understood your requirement correctly then the following DAX formula should give the desired result:
Measure 3:=IF(
NOT ISFILTERED('Data'[Item]),
SUMX(
ADDCOLUMNS(
VALUES('Data'[SubSubCategory]),
"Greater Measure", IF([Measure 1] >= [Measure 2], [Measure 1], [Measure 2])
[Greater Measure]
The formula is always comparing the measures at the SubSubCategory granularity and picking the highest measure value for each SubSubCategory. The result is then rolled up to higher levels i.e. Sub Category and Category. The outermost IF function has
been used to stop any result from being returned for the Item level in Pivot Tables.
This is the output that I got after dragging it onto the Pivot Table:
Edit: I noticed that the language setting that you are using means your DAX parameter delimiter is ';'. Simply replace all of the ',' in the formula I provide with ';' and it should work for you :)
Regards,
Michael Amadi
Please use the 'Mark as answer' link to mark a post that answers your question. If you find a reply helpful, please remember to vote it as helpful :)
Website: http://www.nimblelearn.com, Twitter:
@nimblelearn -
Hierarchy Node- Overall query result
Hi Gurus,
I have a query with hierarchy nodes. For example
Measure
overall result
Measure set 1
ASA
ACEI
Measure set 2
HF
AMI
In the above result the option I chose for node position is ABOVE and I get the overall result below Measure.
But i need the following result:
Measure
Measure set 1
ASA
ACEI
Measure set 2
HF
AMI
overall result
I get the desired query if my option is Node selection 'BELOW' but the result is different which is not how I wanted
Measure
ASA
ACEI
Measure set 1
HF
AMI
Measure set 2
overall result
The actual scenario has arrow marks shown upwards or downwards but hope the overall picture is clear.
Any help would be greatly appreciated.
Thanks,
NikkiHi Nikki,
I also have the same requirement. And i think this is how the output is going to be(ie. the overall result row at the top) when you use the option Node Position 'Above'. I don't think it is directly possible in BEx to have the Overall Result at the end with the option Node position 'Above'.
Best Regards,
Sanjay -
Furmula displaying incorrect result at Hierarchy Node level
Hi Experts,
I have created query which is using simple formula as Amount = Price * Quantity.
The query is using hierarchy on Material.
When I drill down to the lowesr level (leaf node) the formula is showing correct result.
But at all the node levels its displaying incorrect result.
Ex.
Mataterial 1 Rate = 4 Quantity = 10
Maaterial 2 Rate = 3 Quantity = 10
In hierarchy both the se materials are under same node (Parent node) say Node 1
The query output is
Material Amount
Node 1 140 (7 * 20)
Material 1 40 (4 * 10)
Material 2 30 (3 * 10)
It should be
Material Amount
Node 1 70
Material 1 40
Material 2 30
Please suggest how can this be achieved.
Regards
SSSHi SSS,
Have you ben able to resolve this?? I am also facing the same issue..If you have resolved pls reply.
Regards,
Tapan -
MDX missing out 'All' level results for attribute joined to leaf level of a hierarchy
I have an MDX query with a cross-join of a hierarchy and a simple attribute on rows. The leaf level of the hierarchy maps one-to-one with the simple hierarchy, while the other levels map onto multiple values of the simple attribute. In the results,
an 'All' level row of the simple hierarchy is produced for all values of the hierarchy. However:
1. if the rows are numbered using Rank, the row number that the 'All' rows of the root level values of the hierarchy should have is skipped, and the rows that should have it have a repeat of the single child's row number.
2. in SSRS no 'All' level of the simple attribute is found for the root level of the hierarchy.
My reading of this is that the All level is not being produced for the one-to-one root level relationship, and the query is reading the first non-empty value.
Any thoughts on (1) how to force the production of the missing 'All' level values; and (2) how to use Scope or some other means to place values in the positions where they are missing.
KenIt would be helpful to see your MDX query and a screenshot illustrating the results!
Thanks! Josh
Maybe you are looking for
-
help me!
-
Bad connectivity with T510 minidock
I've actually been using the dock for quite awhile now; normally it works great, and I have my external monitor attached (1920 x 1080 @ 60 Hz, 2 ms response) and it all works great. There's just one problem though -- my USB connectivity seems to be p
-
Call PCH screen from PNP screen
Hello. In my program I need a PNP selection as well as a PCH selection. Does anyone know how I can realise that? I've created a seperate report for the PCH selection. I was trying with Submit report_test. But it doesn't show the output screen. Greets
-
Regarding in FI posting program rfbibl00
Hi all, when i use the submit program RFBIBL00, it is not creating the session i want to capture the message and data record in this case. how and where can i do this. Please help me with your suggestions thanks in advance. regards, Selvi
-
How to create a control with two terminals?
Hi there! I need to create a control that has got to terminal in the diagram window. The terminal must not be connected to each other by wire but the both must respond to the control instruction the same way. Is that possible to be done? Thanks Tiano