Calculation in Hierarchy

Hi,
I have a DSO, the structure is following,
Z_Org, Z_RN, Z_Value, Z_counter
'Z_Org' & 'Z_RN' are the keys of the DSO.
The data in DSO is following,
Org1-1      1          300           1
Org1-1      2          300           1
Org1-1      3          300           1
Org1-2      1          700           1
Org1-2      2          700           1
There is a hierarchy for 'Z_Org',
Org1
        Org1-1
        Org1-2
Now, I want to make a query with result as following,
Org1                        1000          .....( 300 + 300 + 300 + 700 + 700 ) / ( 1 + 1 + 1 + 1 + 1 ) = 460 (Wrong)
        Org1-1             300            .....( 300 + 300 + 300 ) / ( 1 + 1 + 1 ) = 300
        Org1-2             700            .....( 700 + 700 ) / ( 1 + 1 ) = 700
The problem is the value in the report has to be a calculated Key figures, The value for 'Org1' is calculated too.
But the result I want to see is 1000 which is following the Hierarchy summarizing rule. Just simple 300 + 700.
Please tell me how I can make this Query.
For the business reason, the 'Z_RN' has to be in the DSO.
Thank you very much.
Seven

Hi,
Create a keyfigure KF2 and have any dummy keyfigure with in it. Go to the properties of the keyfigure and choose the dispaly as properties of the keyfigure as unique count on Z_RN.
Create another keyfigure KF1 = Z_VALUE/ KF2 which will give
Org1-1 300
Org1-2 700
Org1 - 1000
This is posstible in BW 3.5 also we tried this for most of infoset queries when the values got doubled or tripled based on keyfields used over there.
Hope this helps for you.
Thanks,
Arun

Similar Messages

Wrong percentage calculation in Hierarchy

Dear All,
I have a hierarchy Customer Group->Customer Name->Document No. I am calculating percent of Total for top 20 customers.
Problem here is that percentage is calculated correct till the Customer Name Level but fails for document No level.
Please help.
Thanks, Franco.

Hi Franco,
According to your description, you are Crete a calculated measure to return the percentage on each hierarchy level, the problem is that percentage is calculated correct till the Customer Name Level but fails for document No level, right?
Based on my research, the issue can be caused by that there a unknown members on the document No leavel. So the total value is bigger than that on other hierarchy level. You can use exclude the unknown member to calculated percentage.
[Measures].[Sales LCY]/Sum({[DimCustLedgerEntry].[Customer].[All DimCustLedgerEntry]-[Dim].[Hierarchy].&[Unknown]
},[Measures].[Sales LCY]) ,FORMAT_STRING="PERCENT".
Reference
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0a4324af-dc41-4953-94b9-0c2f2a3d2668/mdx-custom-set-excluding-unknownmember
http://msdn.microsoft.com/en-us/library/ms170707.aspx
Regards,
Charlie Liao
TechNet Community Support

Calculations on hierarchy nodes

Hi,
We are developing Divisional P&L Report. We have created hierarchy in R/3 system for this and also loaded successfully in BW.
Now the problem is while designing the query, we have to do calcuation on Hierarchy nodes.
For e.g.
Sales
- W (Works)
- PD (Purchase items)
- Esc (Escallation)
Adjusted Turnover
- Change in stock
Now I want to do calculation for parent nodes (Sales + Adjusted Turnover). please guide me for the same.
Thanks & Regards,
Sameer Kulkarni

Hi Harpalsinh,
My FSV is in the Row and Key figures are in the coloumn.
Please tell me procedure or options for how to do addition of two parent nodes in query designer. I also have to apply allocation rules later on for the division.
For. e.g.
I have 1 parent node, below that i have 7 child nodes. Out of this I need to do addition of 2 child nodes and display it below these childs.Could you please suggest me how can i achieve this?
Also i am not able to see the grouping of hierarchy in Query designer please suggest on the same also.
Thanks & Regards,
Sameer Kulkarni

Calculation in hierarchy nodes

BW Experts,
We have a situation where an account can appear in an account hierarchy twice (i.e. an account is assigned to 2 nodes in the hierarchy). When we run the BEx report, the subtotals for the 2 nodes which contain the account are calculated correctly, but the parent node of the 2 subtotal nodes only includes the value of the account once, and not twice. For example, assume that we have 2 accounts with the following amounts:
Account Amount
A10         100
A20         200
and a hierarchy structure with 2 subtotal nodes, one containing A10 and one containing A10 and A20. So the hierarchy looks like this:
Total
   Subtotal 1
      A10
   Subtotal 2
      A10
      A20
In BEx, the report displays the following result:
Total                      300
   Subtotal 1           100
      A10                 100
   Subtotal 2           300
      A10                 100
      A20                 200
So BEx is not adding the A10 amount in to the Total node twice, which would give an answer of 400 instead of 300.
I did read in the BW Documentation that in cases like this, BEx recognizes that there is a duplicate entry in the hierarchy and so removes it from the totalling. But in our case we do not want the amount to be removed, we want it to be counted twice.
I have tried to use the link node function, but it returns the same result.
Does anyone know how to include a leaf in multiple nodes in a hierarchy and have BEx include the key figure amount in the all higher level nodes, even if it means doubling, tripling, etc. of the key figure amount?
Thanks very much for any help.

Hi Alberto,
Would you please post the resolution of the issue with the hierarchy node calculation? I too have a simillar requirement. It would be helpful if you share the solution for tha issue that you had.
Saravana

Calculations with hierarchy nodes

Hi ALL,
I am using a hierarchy in a query to show the amounts in profit center accounting. Is it possible to add amounts from two different nodes in a hierarchy to show a total amount. Please suggest any approcahes on how to do this. I would appreciate your suggestions
Thanks,
Dinesh

Did you try to work with Formulas? See LEAF operator.
This operator allows you to carry out various calculations on results rows and elementary rows.
Is 0 for results rows or real (inner) nodes of a hierarchy, and the value 1 for elementary rows or the leaves of a hierarchy.
Hope it helps
GFV

Average Calculation in Hierarchial ALV

Hi,
I need to calculate average mean in hierarchial alv. the standard menu for calculate totals is disabled in both in function module REUSE_ALV_HIERSEQ_LIST_DISPLAY and
in the class cl_salv_hierseq_table. Please help with this
Regards,
Mathivanan.G

Hi,
Check this post, may help you
https://forums.sdn.sap.com/click.jspa?searchID=7088080&messageID=2847524
Regards,
Satish

Use hierarchy in report

hi guys,
I want to make a financial report using hierarchy from R/3.
but there are some missing node from R/3 and I want to add it in BW
Exp :
Hierarchy at my R/3 is like this :
revenue
cogs
operating expenses
etc...
where I want to have report like this :
revenue
cogs
--gross profit ( revenue - cogs )
operating expenses
etc...
please advice on how to add --gross profit in my BW report
regards,
-dedys

Hi,
If you want to use hierarcy and hierarchy properties in your query it is impossible to add these kind of calculations in hierarchy.
But if this hierarcy is just for classification and your nodes are fixed, then you can create restricted key figures for each node coming from hierarchy and you can create formulas with using this key restricted keyfigures.
Creating Restricted Key Figures:
1. In the InfoProvider screen area, select the Key Figures entry and choose New Restricted Key Figure from the context menu (secondary mouse button).
If a restricted key figure has already been defined for this InfoProvider, you can also select the Restricted Key Figures entry and then choose New Restricted Key Figure from the context menu.
The entry New Restricted Key Figure is inserted and the properties for the restricted key figure are displayed in the Properties screen area.
2. Select the New Restricted Key Figure entry and choose Edit from the context menu (secondary mouse button).
The Change Restricted Key Figure dialog box appears.
You can also call the Change Restricted Key Figure dialog box from the Properties screen area by choosing the Edit pushbutton.
You make the basic settings on the General tab page.
Underneath the text field, to the left of the Detail View area, the directory of all objects available in the InfoProvider is displayed. The empty field for defining the restricted key figure (Details of the Selection) is on the right-hand side of the screen.
3. Using drag and drop, choose a key figure from the InfoProvider and restrict it by selecting one or more characteristic values. YOU WILL SELECT YOUR HIERARCHY FOR YOUR CHARACTERISTIC HERE
4. Make any necessary settings for the properties of the restricted key figure on the other tab pages.
5. Choose OK. The new restricted key figure is defined for the InfoProvider.
Creating Calculated Key Figures:
http://help.sap.com/saphelp_nw04/helpdata/EN/13/e072abaddb574284d22361f0b824bf/content.htm
This is a way to include calculations and hierarchy nodes coming from R/3 together.
Hope this helps...

Calculated members in Data Manager when run package

Hi All
Do you know why calculated members in C_ACCT dim (which has child and are calculated by hierarchy) are not available in data manager when I want to run package. I want copy this calculated members to another account by using script logic and run it by data manager.
Below is my script
*XDIM_MEMBERSET C_ACCT = IC_BSAS05
*WHEN ENTITY
*IS 1013
*REC(FACTOR=2,C_ACCT="ICX_BSCS02")
*ENDWHEN
*COMMIT
IC_BSAS05 is caclulated by hierarchy.
It works for non-calculated, please tell me if it is possible to run script also for calculated members.
Regards!

Hi Justyna,
When you say that IC_BSAS05 is "calculated by hierarchy" do you mean that IC_BSAS05 is hierarchy node?
If this is true then try replacing the first line of your script with
*XDIM_MEMBERSET C_ACCT = BAS(IC_BSAS05)
Regards,
Gersh

MDX and performance

I know dimension formulas impact performance drammatically but I don't really understan how i works.
I have formulas in two different hierarchies, but it seems as if the formulas in both hierarchies is calculated every time I run a report whether the report will only show data from one hierarchy. Must the system calculate all formulas everytime?

Our current hardware setup is like this
·         Single server
·         Processors: 2 x Intel(R) Xeon(R) CPU E5320 1.86GHz
·         Harddrives: One physical drive SAS 15000 rpm
o    C: 32 gb SAS Os
o    D: 35 gb SAS Program
o   E: 272 gb SAS Data.
·         4 GB Ram
·         System: Microsoft Windows Server Standard Edition 2003, SP2
·         SQL Server 2000
And this is our dimension formulas:
//This is where Stampen-specific MDX calculations begins
//Hierarchy 1
*Function Hir1(%Arg%)
     iif(Konto.H2.CurrentMember is .[H2].[All Konto.H2] and Konto.H3.CurrentMember is .[H3].[All Konto.H3] and Konto.H4.CurrentMember is .[H4].[All Konto.H4],%Arg%,Null)
*endfunction
*Function Hir2(%Arg%)
     iif(Konto.H1.CurrentMember is .[H1].[All Konto.H1] and Konto.H3.CurrentMember is .[H3].[All Konto.H3] and Konto.H4.CurrentMember is .[H4].[All Konto.H4],%Arg%,Null)
*endfunction
*Function Hir3(%Arg%)
     iif(Konto.H1.CurrentMember is .[H1].[All Konto.H1] and Konto.H2.CurrentMember is .[H2].[All Konto.H2] and Konto.H4.CurrentMember is .[H4].[All Konto.H4],%Arg%,Null)
*endfunction
*Function Hir4(%Arg%)
     iif(Konto.H1.CurrentMember is .[H1].[All Konto.H1] and Konto.H2.CurrentMember is .[H2].[All Konto.H2] and Konto.H3.CurrentMember is .[H3].[All Konto.H3],%Arg%,Null)
*endfunction
*Function ASTxxx_H2(%p1%,%p2%,%p3%)
     iif( .currentmember.name = "YTD", iif( (.[H2].[%p1%],[Measures].[YTD]) = 0, Null, ( (.[H2].[%p2%],[Measures].[YTD]) / (.[H2].[%p1%],[Measures].[YTD]) ) * %p3% ), iif( .currentmember.name = "M12", iif( (.[H2].[%p1%],[Measures].[M12]) = 0, Null, ( (.[H2].[%p2%],[Measures].[M12]) / (.[H2].[%p1%],[Measures].[M12]) ) * %p3% ), iif( .currentmember.name = "PERIODIC", iif( (.[H2].[%p1%],[Measures].[PERIODIC]) = 0, Null, ( (.[H2].[%p2%],[Measures].[PERIODIC]) / (.[H2].[%p1%],[Measures].[PERIODIC]) ) * %p3% ), Null))), solve_order=12
*endfunction
*Function TotalaIntakter_H2
     (HIR2(.[H2].[AS1000].[H2].[AS1100].[H2].[AS1200].[H2].[AS1300].[H2].[AS1400]))
*endfunction
*Function TB1_H2
     (TotalaIntakter_H2+HIR2(.[H2].[AS1500]))
*endfunction
*Function TB2_H2
     (TB1_H2+HIR2(.[H2].[AS1700]))
*endfunction
*Function Totalarorelsekostnader_H2
     (HIR2(.[H2].[AS1500].[H2].[AS1700].[H2].[AS1800].[H2].[AS1810].[H2].[AS1900].[H2].[AS1910].[H2].[AS1930].[H2].[AS1940].[H2].[AS1950].[H2].[AS2000].[H2].[AS2100]))
*endfunction
*Function EBITA_H2
     (TotalaIntakter_H2Totalarorelsekostnader_H2HIR2(.[H2].[AS2155]))
*endfunction
*Function EBITDA_H2
     (TotalaIntakter_H2Totalarorelsekostnader_H2HIR2(.[H2].[AS2155]-[KONTO].[H2].[AS2100]))
*endfunction
*Function EBIT_H2
     (TotalaIntakter_H2Totalarorelsekostnader_H2(HIR2(.[H2].[AS2155]+.[H2].[AS2185])))
*endfunction
*Function Finansnetto_H2
     (HIR2(.[H2].[AS2200]+.[H2].[AS2300]))
*endfunction
*Function EBT_H2
     (HIR2(.[H2].[AS1000].[H2].[AS1100].[H2].[AS1200].[H2].[AS1300].[H2].[AS1400].[H2].[AS1500].[H2].[AS1700].[H2].[AS1800].[H2].[AS1810].[H2].[AS1900].[H2].[AS1910].[H2].[AS1930].[H2].[AS1940].[H2].[AS1950].[H2].[AS2000].[H2].[AS2100].[H2].[AS2155].[H2].[AS2185].[H2].[AS2200]+.[H2].[AS2300]))
*endfunction
*Function Netresult_H2
     (HIR2(.[H2].[AS1000].[H2].[AS1100].[H2].[AS1200].[H2].[AS1300].[H2].[AS1400].[H2].[AS1500].[H2].[AS1700].[H2].[AS1800].[H2].[AS1810].[H2].[AS1900].[H2].[AS1910].[H2].[AS1930].[H2].[AS1940].[H2].[AS1950].[H2].[AS2000].[H2].[AS2100].[H2].[AS2155].[H2].[AS2185].[H2].[AS2200].[H2].[AS2300].[H2].[AS2400]))
*endfunction
*Function Foradlingsvarde_H2
     (HIR2(.[H2].[AS1000].[H2].[AS1100].[H2].[AS1200].[H2].[AS1300].[H2].[AS1400].[H2].[AS1500].[H2].[AS1700].[H2].[AS1810].[H2].[AS1900].[H2].[AS1910].[H2].[AS1930].[H2].[AS1940].[H2].[AS1950]+.[H2].[AS2000]))
*endfunction
*Function Foradlingsvarde_H2_PRO
     (HirPro2(.[H2].[AS1000].[H2].[AS1100].[H2].[AS1200].[H2].[AS1300].[H2].[AS1400].[H2].[AS1500].[H2].[AS1700].[H2].[AS1810].[H2].[AS1900].[H2].[AS1910].[H2].[AS1930].[H2].[AS1940].[H2].[AS1950]+.[H2].[AS2000]))
*endfunction
*Function DSO_H2
          iif(((.[H2].[AST610],[Part].[EXT_PART])(.[H2].[AST610],[Part].[PA_None]))=0,Null,((((.[H2].[AS1450],[TimeDim].lag(0),[Part].[EXT_PART],[Measures].[PERIODIC])(.[H2].[AS1450],[TimeDim].lag(0),[Part].[PA_None],[Measures].[PERIODIC])(.[H2].[AS1450],[TimeDim].lag(1),[Part].[EXT_PART],[Measures].[PERIODIC])(.[H2].[AS1450],[TimeDim].lag(1),[Part].[PA_None],[Measures].[PERIODIC])(.[H2].[AS1450],[TimeDim].lag(2),[Part].[EXT_PART],[Measures].[PERIODIC])(.[H2].[AS1450],[TimeDim].lag(2),[Part].[PA_None],[Measures].[PERIODIC]))/3)/((.[H2].[AST610],[Part].[EXT_PART])+(.[H2].[AST610],[Part].[PA_None]))*30))
*endfunction
//Hierarchy 2
*Function ASTxxxV_H4(%p1%,%p2%,%p3%)
     iif( .currentmember.name = "YTD", iif( (.[H4].[%p1%],[Measures].[YTD]) = 0, Null, ( (.[H4].[%p2%],[Measures].[YTD]) / (.[H4].[%p1%],[Measures].[YTD]) ) * %p3% ), iif( .currentmember.name = "M12", iif( (.[H4].[%p1%],[Measures].[M12]) = 0, Null, ( (.[H4].[%p2%],[Measures].[M12]) / (.[H4].[%p1%],[Measures].[M12]) ) * %p3% ), iif( .currentmember.name = "PERIODIC", iif( (.[H4].[%p1%],[Measures].[PERIODIC]) = 0, Null, ( (.[H4].[%p2%],[Measures].[PERIODIC]) / (.[H4].[%p1%],[Measures].[PERIODIC]) ) * %p3% ), Null))), solve_order=12
*endfunction
*Function ASTxxxV2_H4(%p1%,%p2%,%p3%,%p4%)
     iif( .currentmember.name = "YTD", iif( (.[H4].[%p1%],[Measures].[YTD]) = 0, Null, ( ((.[H4].[%p2%],[Measures].[YTD])(.[H4].[%p4%],[Measures].[YTD])) / (.[H4].[%p1%],[Measures].[YTD]) ) * %p3% ), iif( .currentmember.name = "M12", iif( (.[H4].[%p1%],[Measures].[M12]) = 0, Null, ( ((.[H4].[%p2%],[Measures].[M12])(.[H4].[%p4%],[Measures].[M12])) / (.[H4].[%p1%],[Measures].[M12]) ) * %p3% ), iif( .currentmember.name = "PERIODIC", iif( (.[H4].[%p1%],[Measures].[PERIODIC]) = 0, Null, ( ((.[H4].[%p2%],[Measures].[PERIODIC])+(.[H4].[%p4%],[Measures].[PERIODIC])) / (.[H4].[%p1%],[Measures].[PERIODIC]) ) * %p3% ), Null))), solve_order=12
*endfunction
*Function ASTB1_H4
     (HIR4(.[H4].[AS3V]+.[H4].[AS4V]))
*endfunction
*Function ASTB1P_H4
     iif(HIR4(.[H4].[AS3V])=0,Null,ASTB1_H4/HIR4(.[H4].[AS3V])),solve_order=12
*endfunction
*Function ASEBITA_H4
     (ASTB1_H4(HIR4(.[H4].[ASFK].[H4].[ASINTBOLV])))
*endfunction
*Function ASEBITAP_H4
     iif(HIR4(.[H4].[AS3V])=0,Null,ASEBITA_H4/HIR4(.[H4].[AS3V])),solve_order=12
*endfunction
*Function ASEBT_H4
     (ASEBITA_H4+(HIR4(.[H4].[AS8V])))
*endfunction
*Function ASEBTP_H4
     iif(HIR4(.[H4].[AS3V])=0,Null,ASEBT_H4/HIR4(.[H4].[AS3V])),solve_order=12
*endfunction
*Function AST902v_H4
     iif(HIR4(.[H4].[AS34V])=0,Null,HIR4(.[H4].[AST001V])/HIR4(.[H4].[AS34V])),solve_order=12
*endfunction
*Function AST907v_H4
     iif((HIR4(.[H4].[AS101v].[H4].[AS35V]))=0,Null,ASEBITA_H4/(HIR4(.[H4].[AS101v])(.[H4].[AS35V]))),solve_order=12
*endfunction
Edited by: Daniel Svensson on Aug 12, 2008 1:29 PM

Hierarchy on HANA Calculation View with Optional Input Parameters Fails

Hi,
Has anyone succeeded in building a hierarchy on top of a calculation view with optional input parameters, where an input parameter is not filled?
The original requirement came from the wish to create a parent child hierarchy on a calculation view that was copied into the customer space from a HANA Live Financial Statement query view, but I have found the following when creating a simple level hierarchy on a calculation view that consumes one table. The Calculation View has one Input Parameter where the 'mandatory' box is unchecked.
Calculation view reads ECC table FAGLFLEXT
Simple level based hierarchy on fields PRCTR, RACCT and SEGMENT
Input parameter is used as a filter for PRCTR with logic ("EMPTY" = '$$P_PROFITCTR$$' or "PRCTR" = '$$P_PROFITCTR$$')
When I run the view I see the following behaviour in HANA Studio and Analysis for Excel
Before building the hierarchy I could run the view with or without the Input Parameter
After building the hierarchy I can run the view with the Input Parameter filled, but it fails when the Input Parameter is not filled.
Error message is "error: search table error: [2426] missing placeholder; missing value for mandatory parameter P_PROFITCTR"
P_PROFITCTR is not a mandatory parameter, but the selection for the hierarchy view thinks it should be. I don't find any notes around this issue, so I don't think it's version related, however the version I have used for this test is 1.00.70.
It's a shame we can't currently build the hierarchy as the parent child relationship is provided in HANA Live view NewGLFinancialStatementQuery.
Thanks,
Ken

Hi Ken,
We have been facing similar issue. We have even tried to set default value and as optional parameter. View still fails to create hierarchy (we are not using HANA live). As mentioned on page 97 of HANA modelling guide input parameter is mandatory from engine point of view. Hierarchy is generated as column view during the initial activation of calculation view and therefore expect a value by caller.
This seems to be a product error. Some one from HANA development team should explain this issue in detail. I would expect someone like Thomas Jung reply to us.
At the moment, we cant use input parameter for date prompt which gives us calendar popup feature for date selection. Hierarchies just don't work with input parameter. We are missing something.
Regards
Angad

Calculation in BEx on Hierarchy Link Nodes

Hello everyone. I am working on a BEx query that involves a hierarchy based on Controlling Area, Cost Center, and Cost Element. There is a case where I have 5 Cost Elements that belong to 2 Cost Centers. I can successfully create the duplicate nodes at the different Cost Center levels and activate the hierarchy. Where I am having difficulty is assigning a percentage factor to the key-figure at the parent-node (80%) and the link-node (20%). The high-level node at CO_AREA is correct. However, the COST_CENTER nodes show the total original value. I would like to apply these factors dynamically in the BEx query. I have tried structures and cell definitions and was able to apply the 80% and 20% factors correctly to the corresponding hierarchy nodes. Unfortunately, the amounts are not broken down as I would like to see them.
I have looked at the documentation on "Link Nodes" and "Modeling Nodes and Leaves: at help.sap.com.
http://help.sap.com/saphelp_nw04/helpdata/en/b3/fa3d3806136268e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6743e07211d2acb80000e829fbfe/content.htm
This is from one of the above links:
"For both duplicate leaves and leaves in subtrees under link nodes, the values of the duplicate leaves are only considered once by the system internally. When aggregating, the system automatically calculates what are called correction leaves for the superordinate node.
If a leaf Lo lies three times amongst the descendants of a node No, the value is added three times internally and then subtracted twice by the correction node."
I'm wondering if it is even possible to do what I would like to accomplish.
I would appreciate any feedback and suggestions on how to solve this issue if you have done something similar.
Best Regards,
Albert Pecoraro
Sr.SAP BW Specialist
Ferro Corporation
Example:
CO_AREA_1000 = Total = $1000 (AAAA = $800, BBBB = $200)
-->COST_CENTER_AAAA = $1000 @ 80% = $800
>COST_ELEMENT_100 = 100 @ 80% = $80
>COST_ELEMENT_101 = 200 @ 80% = $160
>COST_ELEMENT_102 = 300 @ 80% = $240
>COST_ELEMENT_103 = 150 @ 80% = $120
>COST_ELEMENT_104 = 250 @ 80% = $200
-->COST_CENTER_BBBB = $1000 @ 20% = $200
>COST_ELEMENT_100 = 100 @ 20% = $20
>COST_ELEMENT_101 = 200 @ 20% = $40
>COST_ELEMENT_102 = 300 @ 20% = $60
>COST_ELEMENT_103 = 150 @ 20% = $30
>COST_ELEMENT_104 = 250 @ 20% = $50

Hi Alberto,
Would you please post the resolution of the issue with the hierarchy node calculation? I too have a simillar requirement. It would be helpful if you share the solution for tha issue that you had.
Saravana

Rollup calculations in Account hierarchy (parent-child type)

Hi,
I want to create a parent-child relationship type Account hierarchy using Universe. The hierarchy has to support different set of calculations for roll ups action for different branches in the same level.
Eg.
      Balance Sheet
          (+)Assets
          (-)Liabilities and Owners Equity
      Net Income
       (+)Operating Profit
       (+)Other Income and Expenses
       (-)Taxes
Balance Sheet = Assets -Liabilities and Owners Equity
Net Income = Operating Profit + Other Income and Expenses - Taxes
Regards, Sujeev

Measures automatically roll up.
Whether you define your measure with an aggregate or not, if the projection is set to Sum, it will roll up.
Measures that are to be summed should have Sum() wrapped round them at the universe level though.
What you may have is a lot of positive values in your database and no negatives.
If that's the case, you will need to use a case statement to determine the sign of the value.
E.g.
Sum(CASE WHEN Type='Asset' THEN table.value WHEN Type='Liability' THEN -1*table.value ELSE 0 END)

Using Hierarchy in Calculation View

Hi guys,
Can any one let me know the importance of Hierachy in the Calculation View.
I have created a Hierachy with the Hierachy type as Level Hierarchy and have set the elements manually in it.
I dont see any changes in the resultant data. Preview of data is as such similar to that when i was not using the Hierachy level.
Can any one guide me in this!!
Thanks and regards
Sanjay

You wil not find any difference in the "Data Preview".
Tools like Excel or Analysis office will help you to see the difference
Regards,
Krishna Tangudu

How to see Summarized Hierarchy for Variances after variance calculation

Hi,
How to see Summarized Hierarchy for Variances after variance calculation.
Thanks
Sunitha

hi Sunitha,
KOB3 is the t.code. assign me kindly.
regards
Sirisha

Measure calculation based on hierarchy

Hi
I have flatten an account table to form a hierarchy of 5 levels, each level in this hierarchy will have a flag about account type,
So what I need now is a calculation which has to dynamically change according to this account flag object.
For instance, when account flag is u201CEu201D then the calculation should multiplied with minus. But I have 5 levels of hierarchy also with 5 account flags.
How can I consider these 5 account flags at a time to update the measure, is that possible in Web Intelligence?
I hope the following example for table structure can help to understand the problem.
Acct 1     flag1     acct2     flag2     acct3     flag3     acct4     flag4     acct5     flag5
AAA     R     AAf     E     AAD     E     AAD     E     VVv     L
BBB     R     DDG     E     EFR     R     AAD     L     ERR     R
CCC     E     FGF     R     DFS     E     SDD     R     FDF     E
I have created the five levels accts and flags as individual objects in universe and using it in the webi report as follows,
Report:
Account ( drillable to 5 level)                 Calculate.measure
AAA                                           545464
BBB                                          1654546
CCC                                           - 4674697
The above report should work in a way like when I drill down into account for the next level say. Acct2 , then it should check with corresponding flag (flag2 ) for its calculations (whether to add u2013 or + symbol)
Similarly on entering each level by drilling down, the calculation or formula should behave like above scenario, like it should check the flag and update the calculation
Is this possible ?
What kind calculation should I use ?
Thanks
Dineshkumar

Thanks for the your time and response.we don't have a year range column i might need to create one in rpd wondering if there is a way to do it in the analyses directly. I created a year range in the analyses by writing a case statement in one of the year columns. As per your suggestion here i might not be able to use a yer range in the measure denominator By year range.

Calculation in Hierarchy

Similar Messages

Maybe you are looking for