Key figure summation

Hi All
I searched SDN forums and could not find a solution for the same.
I have added a keyfigure as display attribute in 0costcenter masterdata. The same is available as display attribute in headcount cube (0papa_c02) via 0mast_cctr. Now at the reporting level, the values for the key figure is not summing up at the node level for costcenter hierarchy as a normal functionality of display attribute. It works fine for normal key figures.
So as a solution, I added this keyfigure in the headcount cube and populated the same via a routine from 0costcenter masterdata. The values are populating perfactly fine in the headcount cube. But the problem is that, as the headcount cube has multiple entries for the same costcenter, the values for the key figure is getting aggregated at the reporting level. I even tried using exception aggregation and non cumulative key figures to get the non aggregated value. But I am unable to solve this.
Could you please guide me how can I acheive this. I know I can achieve this if I use an ods. But this will affect the whole design. Plaese suggest.
Cheers
Chanda

Hi Jacob
I created one calculated key figure which contains the real key figure from the cube. When I press Ok, it will get saved. The only thing I could see is the properties of the calculated key figure/ key figure. Where I can see count all values <>0 in calculate result as.
I could not find below at the query level. Are you talking about the aggregation tab in the infoobject maintainance in BW side?
"on the next screen in bottom left corner, there is a button (I think it will say "Expand" if you log on in english). Click that one and now you get to set the aggregation behaviour. Set the exception aggregation to 'count all values 0' and the reference char to the costcenter (I think your mst. costcenter in this case)"
Cheers
Chanda

Similar Messages

  • Key figure summation for KF IN different cube of a MP

    Hi,
       I need to design a report on a Multiprovider. MP is based on two Cube Cube1 and Cube2.
       Cube 1 has field item and key figure total quatity.  Cube 2 has field item and key figure  quatity1.
       I need a report which will show
                      Item  quantity1  Total quantity   Percentage
    Percentage = (quantity1/total quantity)*100.
    I am surprised that percentage is X, though other two KF has value.
    Is it the case that it is not possible to make summation, subtraction or any opeartion between two KF in different cube.
    Could you please guide how to create percentage between two KF in different cube in a MP.
    Regards
    Deep

    Hey Deep,
    First confirm me what I understand... First you created a Mp which contains both KFs... Total quantity and Quantity one then in BEx query designer you created report in which you created a formula named "Percentage" and formula was (quantity1/totalquantity)*100... and in analyzer you are getting X instead of values. Then first try to check the properties of Formula (Percentage) in BEx query designer if decimal places etc are implemented and correct and second check if analyzer is reading these values as CHAR or Keyfigures and that you can check if there is a green arrow on left corner of each cell on both column's individual cells. If the green arrow kinda symbol is present there then it means that analyzer is not reading the values as CHAR thats why it is not doing any operation on both columns. Check these and let me know.

  • Key Figure Summation in Result Row with Cumulation Ticked

    Hi,
    I have a Bex question regarding the summation rows. 
    I need a Year To Date amount and a Period To Date amount in the report.  However, there is no Year To Date key figure available in the cube.  So in order to calculate YTD, I'm using the PTD key figure and have Cumulated box ticked mark in Bex. 
    All looks fine across columns per Vendor.  But the results row for the Cumulative Balance is always equal to the results row for Period Balances.  I believe this is because the same key figure is used, and it is only reading the amounts in the cube - not the ones calculated on the fly. 
    Does anyone know how to correct the results row for a cumulated key figure? 
    Regards,
    Rhonnie

    You have to create two restricted KF; one is PTD restricted to period; the second is PTD restricted in a period range from 01.yyyy to current period.
    Hope it helps.
    Regards

  • Impact of Delta Records on Key Figure Summation in DSO

    Hi experts,
    I have a key figure with aggregation type "summation" in a DSO. I would like to know the impact of delta records on the key figure.
    E.g.
    source DSO
    doc_id (key) | doc_pos | type | amount
    4711 | 1 | A | 100 USD
    4711 | 2 | B | 20 USD
    target DSO
    doc_id (key) | amount
    4711 | 120 USD
    If the first record is modified ("type" from A to C) as follows and delta-loaded to target DSO:
    4711 | 1 | C | 100 USD
    This will lead to incorrect amount:
    target DSO
    doc_id (key) | amount
    4711 | 220 USD
    How can I handle this situation?
    Thanks in advance.
    Regards,
    Meng

    Hi..
    I believe one document number and document Item will have only one type.
    Like 4711      1    should have only one type ( A / B / C).
    If the above assumption is true then just remove Doc Type from Key field of source DSO.
    Then From Source to Target Change Log table can handle this.
    Regards
    Anindya

  • Key Figure Summation in DSO

    Hi,
    I am loading data from Cube to DSO.
    In cube i have fields with 2 records below as example
    f1=1 f2=2 f3=3 f4=4 and key figure k1=1
    f1=1 f2=2 f3=3 f4=4 and key figure k1=1
    In DSO all these f1's fields are key fields as per requirement. And when i load now i get in DSO as
    f1=1 f2=2 f3=3 f4=4 and key figure k1=2
    I do not want k1=2 but i want k1=1 in DSO and not sure why this is getting summed up even though i have selected overwrite in Transfer rules.
    I have checked mapping and cube data. All are fine.
    I just want to avoid this and do not know what to do.
    A routine or formula or something else?
    Please help.

    Hi,
    Check your DSO Design
    Keep f1 ,f2, f3, f4, are in KeyFileds of DSO  and Keep key figure k1 in DataFields of DSO.
    Here I'm assuming that F1 to F4 are Charecteristics.And only K1 is Keyfigure. If this is the case then I hope it will work if you follw the above design.
    Thanks
    Reddy

  • DSO - Key figure  summation

    Hi Experts.
    I have a question on how BW is thinking when updating DSOs.
    If I mark the keyfigures in the DSO to summarize, what will then be the effect.
    If I compare to a SQL sentence I will sum the keyfigures for sure.
    But will i Group by all the others info-object, or only the info-objects that are in the key area of the DSO. 
    Thank you in advance !

    Husby,
    In your update rule you will specify Addition or Overwrite. This will play the major role in how the data is summed up or not. Again this summarization will happen only for the key figures.
    So if the keys match it will do the sum or not based on the condition set.
    Hope this helps.
    Alex(Arthur Samson)

  • Key Figure's Result Summation and SUMGT

    Goal: I need to capture the report’s  Results for KF1 and KF2 to use it in the same report for further calculations. However, the report should include into Results calculations only the records that have KF1 or KF2 with values greater than 0.
    Potential Solution: Create a Formula that uses Function SUMGT (or SUMCT, SUMRT) on the desired key figures and use conditions at the query level.
    KF1 Property:     Calculate Result As SUMMATION
    KF2 Property:     Calculate Result As SUMMATION
    Report with No Conditions:
    Year      KF1     SUMGT’KF1’     KF2     SUMGT’KF2’
    2001     10        70                         10        90
    2002     20        70                         20        90
    2003     0          70                         30        90
    2004     40        70                         30        90
    Result   70        70                         90        90
    Report with Conditions:
    KF1 > 0
    or
    KF2 > 0
    Year     KF1     SUMGT’KF1’     KF2     SUMGT’KF2’
    2001    10         70                        10         90
    2002    20         70                        20         90
    2004    40         70                        30         90
    Result  70         70                        60         90
    Problem: When Conditions apply the SUMGT (as well as SUMCT and SUMRT) do not take them into consideration and includes in its calculations the excluded records as well.
    Questions:
    1. How can I make SUMGT (or any of the other tow) return a result that take into consideration the specified conditions?  For KF2 the Result should be 60 and NOT 90.
    2. Is there any other way I can capture the Results for KF1 and KF2 when the above specified conditions are implemented?

    I think No of repair days is a characteristic..
    What you can do is create a formula variable with user input. User will enter no of repair days in it.
    Now create a variable on no of repair days of type customer exit.
    In the exit read the value of the formula variable and assign it to that variable.
    Restrict your key figure no of completed orders with that variable...

  • Key figures should be normally "summation" or "overwrite"

    Hi all,
    I know the answer to this question is "it depends on your requirement" but I want to know normally do we have to keep the key figures as summation or overwrite ?
    Thanks,
    KM

    Hi:
    Summation.
    Since most reports need a summation, keep the K-Figures as summation.
    If you want overwrite, you can use an ODS. Here, even though the K-Figure is summation, you can still overwrite by Modeling.
    Ram C.
    Message was edited by: Ram Chamarthy

  • Key Figure values in the Bex Report are different from the cube

    Hi all,
    When I tried to pull data of the cube, the values of the Key Figure 0Lotsize_cm was showing 100 EA. But when I try to run the query of the cube, then the key figure is LotSize is showing up as 500 EA. I don't understand why this is happening.
    When I checked for Aggregation in the Key Figure. It shows up as "Sum" under aggregation and "Last Value" under Exception aggregation.
    Could some one help me find a solution to this issue.
    I look forward to hearing from the experts.
    Regards,
    S.P

    Hi Arun and  Zegion,
    Thank you for your responses.
    Arun, I do not have any aggregates on the cube. I changed the aggregate properties of the Key Figure from SUM to Minimum. this has solved my problem temporarily.
    the reason I am saying temporarily because this is a SAP delivered InfoObject. This is for the datasource 0CO_PC_PCP_01. When I read through the documents, it said, SUMMation for Aggregation and Last value for "Exception Aggregation" will display the value of KF as the last value and does not add them up.
    Since this wasn't the happening in my query, I changed the Aggregation from SUM to Minimum.
    Regards,
    S.P

  • Key Figure Aggregate in Bex Query

    Hi Gurus
    I am using BI7.0; but 3.5x BEx tools
    I am loading 6 fields from a flat file.  I am loading data for tickets.  I have create an InfoObject that counts the number of tickets.  No problem.  Also I also have key figures that I am assigning the same value to all Charactersitics: 10,30 per ticket.
    The Key figures are (Sum) with a Summation aggregation type. 
    In my Query, the 10,30 aggregate up based on the number of tickets (characteristic) that are available.
    Question:  How do I remove/stop my key figures from aggregating up (sums) the values of 10, 30 based on the charactersitic?  I want only 10, 30 to be present regardless of the number of tickets (constant value applied to the key figure).
    Should I change my aggregation type?  If so, to what?  I see a number of options, such as Last Number, No aggregation, etc
    Thank you

    I found a solution to my requirement.

  • Key Figure Aggregate in Bex Query based on Charactersitic

    Hi Gurus
    I am using BI7.0; but 3.5x BEx tools
    I am loading 6 fields from a flat file.  I am loading data for tickets.  I have create an InfoObject that counts the number of tickets.  No problem.  Also I also have key figures that I am assigning the same value to all Charactersitics: 10,30 per ticket.
    The Key figures are (Sum) with a Summation aggregation type. 
    In my Query, the 10,30 aggregate up based on the number of tickets (characteristic) that are available.
    Question:  How do I remove/stop my key figures from aggregating up (sums) the values of 10, 30 based on the charactersitic?  I want only 10, 30 to be present regardless of the number of tickets (constant value applied to the key figure).
    Should I change my aggregation type?  If so, to what?  I see a number of options, such as Last Number, No aggregation, etc or can I override this in my Query property?
    Thank you

    Hi Client
    I would like to know how to avoid aggregation of a key figure in Bex 3.5?
    Thanks
    GS

  • Key figure flag in the planning layout

    Hi,
    Can anyone explain the importance of the key figure flag in the planning layout?
    Regds
    Pavan.

    Hi Arun and  Zegion,
    Thank you for your responses.
    Arun, I do not have any aggregates on the cube. I changed the aggregate properties of the Key Figure from SUM to Minimum. this has solved my problem temporarily.
    the reason I am saying temporarily because this is a SAP delivered InfoObject. This is for the datasource 0CO_PC_PCP_01. When I read through the documents, it said, SUMMation for Aggregation and Last value for "Exception Aggregation" will display the value of KF as the last value and does not add them up.
    Since this wasn't the happening in my query, I changed the Aggregation from SUM to Minimum.
    Regards,
    S.P

  • Key Figues - SUMMATION in Expert Routine

    Hi All,
    Is there any to way to have to aggregation of Key Figures as "Summation" in Expert Routine??
    Please let me know if there is any work around for this..
    Thanks,
    Kapil

    This type of routine is only intended for use in special cases. You can use the expert routine if there are not sufficient functions to perform a transformation. The expert routine should be used as an interim solution until the necessary functions are available in the standard routine.
    Hi Kapil,
          You can use expert routine to program the transformation yourself without using the available rule types. You must implement the message transfer to the monitor yourself.
         If you have already created transformation rules, the system deletes them once you have created an expert routine.
         If the target of the transformation is a DataStore object, key figures are updated by default with the aggregation behavior Overwrite (MOVE). So i think expert routine aggregation does not work for transformation to the standard DSO.
    For more details:
    [https://forums.sdn.sap.com/click.jspa?searchID=13078965&messageID=2823817]
       Hope it helps you.
    Regards,
    Yokesh

  • Currency Translation with a Calculate Key Figure

    Hi,
    Does anyone have experience with applying currency translation in BEX/Query Designer on a Calculated Key Figure? 
    I have a need for a calculated key figure to be converted to a target currency of USD (which is already defined via RRC1).  I also need the Results Row to display the summation in USD. 
    Currently, my calculated key figure displays two currencies (MYR and USD) and an incorrect summation of both currencies.
    Here is how I have defined my calculated key figure:
    NODIM ( 'Consumption (STOs)' ) * NDIV0 ( 'Material Source Plant Cost' / NODIM ( 'Source Plant Price Unit' ) )
    I am multiplying a quantity field by amount field and then dividing by a price per unit field.  I have applied NODIM on the other fields so that the amount field will retain it's properties.
    Running this query through transaction RSRT and clicking on the Generate Report button, I get the following message:
    "<b>Currency translation cannot be carried out for element 20 (my calculated key figure). Element 20 neither contains a Basic key figure nor a variable with type Amount. For this reason, you cannot and do not need to perform a currency translation</b>."
    From the above message, I must be setting my calculated key figure incorrectly. 
    Any ideas?
    Thanks!
    Hau

    Hello Ajeet and N Ganesh,
    Thank-you for your help.  I verified that the dimensions of my key figure 'Material Source Plant Cost' was of type 0AMOUNT, so that was not the issue.
    The issue was in the error message that was returned when I pressed the Generate Report button in RSRT.  Essentially, currency conversions in BEX can only be performed on basic key figures or simple replacement path variables. 
    I can perform the currency translation on a SIMPLE calculated key figure that contains only the replacement path variable (where 'Material Source Plant Cost' is an attribute of my master data characteristic ZMAT_SRC).  However, I found that I cannot perform the currency translation on COMPLEX calculated key figures, like in my example above. 
    To get around this currency translation issue and as suggested by the error message, I created a SIMPLE calculated key figure for replacement path variable 'Material Source Plant Cost' and performed the currency translation.  The problem with this solution is that while I get my currency translation, I also get a calculated key figure that is aggregated, according to the query layout.
    To get around the aggregation issue, I also created a dummy counter as a master data attribute (of ZMAT_SRC) to capture the aggregation.  I assign a value of ‘1’ to this dummy counter/master data attribute in the update rules to my ZMAT_SRC infoobject.
    I then divide my new (aggregated) calculated key figure for 'Material Source Plant Cost' by the dummy counter (which is also aggregated).  Essentially, I divided the aggregated replacement path variable by the scaling factor.  The result is that I get a new calculated key figure that has been translated into the target currency and in the correct scaling factor.  I can use the new calculated key figures in the above formula; regardless of the report is rolled-up.
    Again, thanks for your help.  It gave me the pieces to solve this puzzle.

  • Key Figure displays as rounded in BEx

    Hello,
    I have a report that is based off of InfoProvider/Object: 0MATERIAL.
    When I run the report, the key figures are displayed as rounded values, for example 15.000 LB, 0.000 LB, 2.000 FT3. 
    I would like to get 3 decimal places for example 15.255 LB, 1.531 FT3.  When I look at the Master Data for 0MATERIAL in RSA1 I see values with greater accuracy then the rounded number obtained in reporting.
    Details below...Can someone help?
    For infoObject 0MATERIAL, I have the attribute 0NET_WEIGHT key figure.
    0NET_WEIGHT has the following properties
    Type: QUANTITY
    Data type: QUAN - Quantity field, points to a unit field with format UN
    Unit of measure - 0UNIT OF WT
    Aggregation/Exception Agg: Summation
    Cumulative Val
    Decimal Places: 0.000
    Display "in 1"
    Bex Descript: Short description
    In BEX under 'Number Format' I have
    Scaling factor: (From Key Figure: 1)
    Number of Decimal Places: (From Key figure: 0.000)
    Thanks,
    Nick
    Message was edited by:
            Nick Bertz

    Hello Jaya,
    When I looked at the T006 table for the following units I obtained the value 0 in field ANDEC
    FT3
    LB
    When I look at tx: CUNI and I set the selection to 'Mass' > then I click on 'Units of Measurement' > Then I select 'LB' and click on 'Details' I see no value for 'Decimal pl. Rounding'
    When I look at tx: CUNI and I set the selection to 'Volume' > then I click on 'Units of Measurement' > Then I select 'FT3' and click on 'Details' I see no value for 'Decimal pl. Rounding'
    What i see in CUNI on BW matches what I see in CUNI on R3.
    None the less, on our development system I made the change via CUNI setting 'Decimal pl. Rounding' to 3 and it seems to be working now.
    I could have go to RSA1 > Source Systems > RC'd on my Source System > Chose 'Transfer Global Settings' > Selected the checkboxes for 'Units of Measurement' and then for mode selected 'Update tables' This updates the T006, T006A, T006B, T006C, T006D, T006I, T006J, T006T tables.
    But since on R3 the CUNI table had the same information, it wouldn't have helped.  That is why I went and updated CUNI directly on BW. When I saved the changes it prompted for a transport which will make it easy to transport to BW Production.
    Thanks for the Help!
    Nick
    Message was edited by:
            Nick Bertz

Maybe you are looking for