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

Similar Messages

  • 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

  • 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 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.

  • Changing key figure values in DSO/Cube

    Experts,
    I have a DSO and a Cube and the data has been already loaded in to a amount Key Figure. By default it is 2 decimal places. I want to change the decimals to 7. I cannot delete data from the cube or the DSO.
    Can you please suggest some ideas to do this.
    I came accross this note 579342 which talks about realigning this but as I have not implemented this before, I wanted to get your thoughts on if this is safe to do.
    Thanks
    Yashu raj

    Hi Yashu,
    I did this with using system message board and I put message on EP tooo.
    So you do a small R&D. Run this report and let me know too if amount data is reflecting in the cube or not.
    Logically it should not but have a try?
    Regards,
    Mahesh

  • 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

  • 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

  • Key Figure values based on characteristic Drill-downs

    Hello All,
    I have Issue with my drilldown options in the report. The values of Sales qty need to change at particular drilldown.
    I have Sales Revenue and Sales QTY key figures in my DSO with  plant, factory, customer and Business type (Values A, B, C and D) characteristics.
    IN the report requirement I want to show the SALES QTY for only Business Type  "A" at Plant , factory and customer level, but when I am at the Business code level, then I am to show all the quantities by that level.
    THe sales revenue should always show values for all Business code irrespective of the drilldowns.
    please provide suggestions and code on how to go about the issue.
    thanks,
    pra.

    Hello Guys,
    Thanks for your response.
    Let me explain clearly...with an example.
    We have DSO which has 5 chars and 2 KFs.
    Chars - Company Code, Plant, Customer, Material and Business Code (which has values A, B and T).
    KFs - Sales Qty and Sales Revenue.
    Report output ---
    Customer
    Company Code
    Plant
    Material
    Business Code
    Sales Qty and Sales Rev
    Requirement is a follows -
    When the report is run.... the report will display on Customer with KFs.
    then if user wants to pull company code he can do so...as will other chars (Plant, Material and Business Code)
    but the condition is that when the user is seeing the report at customer with KFs ,....the KFs should only show values where business code = "A"
    so is the same with other chars - Company code, Plant and Material.
    But when user drags and drops the Business Code char in the report against the KFs .then the report should include all Business Codes ( A, B and T) with corresponding sales qty and sales rev for all business codes.
    Solution - Partially working--
    What I have done..is restricted the sales qty and rev with Business code = A, its working fine for all drill downs except that, when I am at business code level its showing as
    Business Code QTY REV
    A             300          3000
    B                0              00
    T                0               00 .
    Hope you got the issue. Please let me ,,if you need any information.
    Thanks,
    Pra

  • 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

  • Converting key figures from rows to column using DSO and start routine

    Hi SDNer:
    I need some help to convert key figures from rows to column.
    The source is DSO 1 and I am thinking about writing ABAP in the start routine to do the conversion. The target is DSO2.
    Below is the  more detail information with example. Basically, for each record in DSO 1 I need to create 3 records (because there are 3 KF's) and output to DSO2.
    I would really appreciate some help on this.Thank you.
    Tony
    DSO 1 data format (SOURCE)
    Period   ID   KF1  KF2  KF3
    200702 100  300  200   750
    Output to DSO 2 (TARGET)
    Period   ID    KF  LABEL
    200702 100  300  KF1
    200702 100  200  KF2
    200702 100  750  KF3

    This is the code in BI 7.0.
    u need to put a field "Label" in DSO1. u dont need to populate this in DSO1 but it helps the code to populate the field in DSO2.
    DATA: wa_result TYPE _ty_s_sc_1,
    t_result TYPE STANDARD TABLE OF _ty_s_sc_1.
    DATA:counter(2) TYPE n.
    LOOP AT SOURCE_PACKAGE INTO wa_result.
    counter =0.
    while counter < 3 .
    wa_result- Period = wa_result-Period.
    wa_result- ID = wa_result-ID.
    if counter  = 0.
    wa_result- KF1 = wa_result-KF1.
    wa_result- Label = 'KF1'.
    elseif counter = 1.
    wa_result- KF1 = wa_result-KF2.
    wa_result- Label = 'KF2'.
    else.
    wa_result- KF1 = wa_result-KF3.
    wa_result- Label = 'KF3'.
    endif.
    APPEND wa_result TO t_result.
    counter = counter+1.
    endwhile.
    endloop.
    CLEAR: SOURCE_PACKAGE,wa_result.
    LOOP AT t_result INTO wa_result.
    APPEND wa_result TO SOURCE_PACKAGE.
    ENDLOOP.

  • Help with Aggregation Summation into DSO

    Hi, I have a question about Key Figure Aggregation Summation in transformation rules into a DSO from 2LIS_11_VAITM.
    Currently had an old order for Order Qty of 600 pcs.  Recent request came in to change it to 400.  After Delta our Order Qty was -200.  The Rule is for Summation and I figure it should work like 600 + -600 +400 = 400, but that is not what happened.  It's almost like the rule considered the original order qty to be 0 and when the -600 and +400 delta came in they get summarized to get the -200.  Does it have anything to do with the change logs only having recent last 30 days available?
    Can anyone tell me what is wrong here?

    Kennet:
        Could you please provide more details? For example:
    - Is the problem (differences on the Key Figure values) at the DSO level or at the Cube level?
    - Does your DataSource version have DSO capability? (please refer to SAP Note 440416 - "BW OLTP: Correction report for change of delta process").
    - If your DataSource supports "ABR" extraction, Does the Data on the PSA looks ok? (After / Before and Reverse images).
    - Have you enhanced the DataSource to include Custom Fields? If so, Does the ABAP Routine uses the SORT command?
    - Do you update the DSO with the 2LIS_11_VAITM DataSource only? or Do you use another DataSource to send data to the same DSO?
    - Have you considered changing the Rules to "Overwrite" instead of "Summation"?
    - What fields are included as part your DSO Key?
    - Do you have the ROCANCEL field mapped to 0STORNO / 0RECORDMODE InfoObjects?
    Regards,
    Francisco Milán.
    Edited by: Francisco Milan on Jul 1, 2010 9:13 AM

  • 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

  • How to ignore blank/null key figure value in BI Queries

    Reports on Multiprovider - we see some cells of a Key figure as blanks. These blanks are interpreted as zeros by the system and calculated accordingly resulting in incorrect values. As per our requirement, we need a count of all hard/real zeros only, not the blanks. For example, if there are 10 rows of which 6 are real zeros and 4 are blanks - our count should be 6 and not 10.
    How to ignore the blanks in BEx queries please?
    Thanks for your help.
    Upender

    Rakesh,
    It is not possible to find a pattern because the report is on a MultiProvider with 2 InfoProviders- Purchasing documents DSO and Material Movements InfoCube.
    Every Purchasing Document has several materials associated with it. These materials are compared with materials in Materials Movement. Not all materials in Purchasing Document are found in Materials Movement. For those Materials found in Materials Movement, the Quantity is obtained. For these found rows, the correct value is showing up - if the quantity is zero, it is showing in reports as zero. If the material is not found in Material Movements then Quantity shows up as blank values.
    My requirement is ignore such blank quantities and not count them. Only Quantities with 0 values should be counted. Currently both blanks and zero values are counted showing inflated count.
    Thanks,
    Upender

  • InfoSet in SAP BI 7.10 and Key figure aggregation

    HI SAP Gurus,
    I am new in SAP BI area. I have my first problem.
    I want to create a report for the profit of goods. 
    The cost of goods(cogs) are constant for each material for one month.
    The formula to calculate the profit of goods = sales turn over u2013 cogs of month *sales amount.
    I have defined in BW time dependent infoObejct with attribute cogs.
    I have 2 info Sources.  InfoCube for transactional sales data from R/3 and material cogs master data loaded from csv file each month to infoObject.
    The info Provider for report is InfoSet (transactional Cube and cogs infoObject) .
    My problems are
    1) When I create an InfoSet, SAP BW create automatically new technical name for all characteristics and key figures and the first technical name should be alias fr each InfoCube and InfoObject in the InfoSet.
    2) The new technical name infoSet erased my aggregation references characteristic (=calmonth)
    3) In the report the key figure cogs was aggregated for each customer sales and customers,    that means the value of cogs is not constant, when it is aggregated according to customer sales order.
    Thanks a lot for your support
    Solomon Kassaye
    Munich Germany

    Solomon find some code below for the start routine, change the fields and edit code to suit your exact structure and requirements but the logic is all there.
    4) Create a Start Routine on the transformation from sales DSO to Profit of Goods InfoCube.
    Use a lookup from the the COG DSO to populate the monthly COG field in the COG DSO.
    **Global Declaration
    TYPES: BEGIN OF I_S_COG,
    /BIC/GOODS_NUMBER TYPE /BIC/A<DSO Table name>-/BIC/GOODS_NUMBER,
    /BIC/GOODS_NAME TYPE /BIC/A<DSO Table name>-/BIC/GOODS_NAME,
    /BIC/COG TYPE /BIC/A<DSO Table name>-/BIC/COG,
    /BIC/PERIOD TYPE /BIC/A<DSO Table name>-/BIC/PERIOD,
    END OF I_S_COG.
    DATA: I_T_COG type standard table of I_S_COG,
    wa_COG like line of i_t_COG.
    *Local Declaration
    data: temp  type _ty_t_SC_1.
    *move SOURCE_PACKAGE[] to temp[].
    temp[] = SOURCE_PACKAGE.
    select /BIC/GOODS_NUMBER /BIC/GOODS_NAME /BIC/COG /BIC/PERIOD  from
    /BIC/A<DSO Table name>
    into corresponding fields of table i_t_COG for all entries in
    temp where /BIC/GOODS_NUMBER = temp-/BIC/GOODS_NUMBER.
    sort i_t_COG by /BIC/GOODS_NUMBER.
    loop at SOURCE_PACKAGE assigning <source_fields>.
    move-corresponding <source_fields> to wa.
    loop at i_t_COG into wa_COG where /BIC/GOODS_NUMBER =
    <source_fields>-/BIC/GOODS_NUMBER and /BIC/PERIOD =
    <source_fields>-/BIC/PERIOD.
    modify SOURCE_PACKAGE from wa transporting /bic/COG.
    endloop.
    endloop.
    5) Create an End Routine which calculates Profit using the formula and updates the result set with the value in the Profit column.
    Given your requirement for the profit calculation
    profit of goods = sales turn over u2013 cogs of month * sales amount
    Write a simple end routine yourself
    *Local Declaration
    loop at RESULT_PACKAGE.
    <result_fields>-profit = <result_fields>-sales turn over - <result_fields>-COG * <result_fields>-sales amount.
    modify RESULT_PACKAGE from <result_fields> transporting profit.
    endloop.
    As the above start and end routines are used to enhance your sales DSO, your fields for customer number and the sales order should already be in your DSO for drilldown.
    Let me know how you get on.

Maybe you are looking for