AGGREGATION PROBELM..in BEX

Hi All,
I have PO items under Pur doc. No in cube.
In Cube:
Contarct      Pur doc. No      Pur doc.Item       ZCum.Pln.Val
100              50000               10                         40k
100               50000               20                         40k
100                   50000               30                         40k
100              50001               10                         40k
100               50002               10                         40k
100                   50002               20                         40k
In Report I want to see : (over all picture i.e Client needs without Po items & Doc_numbers)
100              50000                                             40k
100              50001                                             40k
100              50002                                             40k
But it shows NOW :
100              50000                                             120k ( It is summed up , WRONG VALUE)
100              50001                                               40k (Right value)
100              50002                                               80k ( It is summed up , WRONG VALUE)
In RSA1 --> Zcum.pln.val Key Figure  info object’s AGGREGATE Tab properties are:
Aggregation : SUM
Exception Aggregation: Summation.
Cummulative value option is also selected.
1. What changes shall I do, to get my required result in RSA1- infoobject properties.? Pls. advise step wise.
2. If I change properties to this Zcum.pln.val  object , Will it effects to existing Cube data?
3. without changing properties to this Zcum.pln.val  object, what options shall I use in BEx level, to get required result.
Please help me and tell step wise.
Thanks & Regards,
siri

Hi,
try this -
right click  Zcum.pln.val in BEx & choose contant selection.
or
choose claculate result as First value.
hope it helps
regards
VC

Similar Messages

  • Aggregation Behaviour in BEX Analyzer

    Hi Experts,
    using an Info-Set I combine information from to Info-Provider.
    One Info-Provider contains key-figure "amount" while the other Info-Provider contains key-figure "factor".
    Within a Query based on my Info-Set I multiply "amount" with "key-figure". This works fine for the smallest granularity.
    The Problem appears when I start aggregation in BEX.
    Now the cumulated "amount" is multiplied with the cumulated "factor". The results are wrong.
    What can I do?
    Exception aggregation is in my point of view not an answer, since "amount" has to be weighted with "factor".
    BR,
    Thorsten

    Hi Thorsten,
    how umulated "amount" is multiplied with the cumulated "factor". in query, in calulated key figure you have options.
    right on Calculted keyfigure which useing for mutiplication -> proprties -> botttom of properties you have option before aggregation. check this option.
    hope this helps
    Regards
    Daya Sagar

  • Keyfigure aggregation problem in BEX

    Dear gurus,
    I am creating a vendor performance report. In the report I will have SLA derived from formula "Goods Issued / PO Requested Qty"
    The output of my report as follow
    Vendor     |     SLA   |   Goods Issued  |  PO Qty Requested

    Dear gurus,
    I am creating a vendor performance report. In the report I will have SLA derived from formula "Goods Issued / PO Requested Qty"
    The output of my report as follow (drill down by Vendor Level)
    Site....Vendor......SLA.......Goods Issue....PO Qty
    101.....90203.......100%......800 CV..........800 CV
    101.....90202........80%......160 CV..........200 CV
    102.....90201........50%........20 CV............40 CV
    102.....90199........33%........30 CV..........100 CV
    Result............... (   A    )
    I would like to know what is the output for result row A ?
    I have tried several methods of aggregation, but the output is not relevant.

  • How to view individual records instead of aggregated view in BEx report

    hi,
    i see my key figures as an aggregated view in the report. I wish to see each record separately. How can I do this? Pls help.
    For eg:
    In Cube Content I see the records like...
    Material           Cost
    M1                  1000
    M1                  2000
    M1                  3000
    M2                  7000
    In the Report I see the following...
    Material           Cost
    M1                  6000
    M2                  7000
    Thanks,
    SD

    Hi Sebastian,
    To get the records in the query result without aggregation,
    1. give the characteristics in the rows and key figures in columns.
    (or)
    2. assign with a request number for each record, since no two records will have same request number, there is no chance of getting aggregation.
    (or) are u using any DSO in ur data flow, if so remove that and directly map to info cube and see the result.
    Thanks,
    Sai Chand
    Edited by: sai chand on Jan 15, 2009 8:38 PM

  • Exception Aggregation help in Bex !

    Hi Experts
        Iam creating a query with date calculations. I have the following calculations in my qry...
    1 . Cycle Time      :  ( Doc Date - Quote sent date) ....I created two replacement path variables and use them in formula.
    2 . Nr of Quotes    :  ( Count of all sales orders with Block L1 & L2) ...I created a CKF for counting the nr of docs then used that CKF in an RKF to filter by block. 
    3 . Avg Tender Time :  ( Nr of Quotes / Doc date - Quote rec Dt) .........Created a formula same as 1 with Quote rec dt instead of Quote sent then created another formula to make 2/3.
        Now when I execute the query Iam getting numbers but
        Cycle Time I took Exception Aggregation as Counter for all detailed values and ref char as Doc Date....Its giving some nr as output...but my question is if I take doc date as Ref char how it gets the calculation from replacement
        Does any one have worked on date calculations as the above situation / any one have any how to's which explaines how to find date calculations with exception aggregations?
    Thanks in advance...

    fixed

  • Aggregation issue in Bex

    "A” is an IT application
    (name) this IT application has a total of 50 users (Number of Users) . So the Number of users need to be aggregated to the IT application
    level. This application provides different Applications Functionalities, which
    belong to certain Application functionality groups for instance “SC”,
    “PO”, etc. The relation between Application Functionality
    and Application Functionality Group is 1:n!
    Application Functionality Group
    “PO” will also be associated with other IT applications
    (name), e.g. “B”.  Due to the relationship that multiple
    Application Functionality can be related to one Application functionality
    group, if a query is created for Number of Users per Application Functionality
    group, the Number of users does not have to be duplicated!
    Example (this is just to display
    the above, not actual data):
      Name
      Number of Users
      Application Functionality
      Application functionality Group
       A
      50
      OCP
      SC 
      A
      50
      DS
      PO
      A
      50
      WM
      PO
      A
      50
      PMD
      MDM
      A
      50
      RPC
      SC
      A
      50
      IM
      SM
      B
      222
      DS
      PO
      B
      222
      WM
      PO
      B
      222
      RPC
      SC
    If I look at Names and Number of
    Users only, I would expect the report to show this:
      Name
      Number of Users
      A
      50
      B 
      222
    If I look at Application
    Functionality Groups and Number of Users only, I would expect to see this:
      Application functionality Group
      Number of Users
      PO
      272
      SC
      272
      MDM
      50
      SM
      50

    Hi,
    No need confusion.
    first create the selection then apply the new formula -> apply the formula -> use the exception aggregations based on the your requirements like summation/total -> try with the different char with reference char.
    fine the below doc.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b8ed5b-1025-2d10-b193-839cfdf7362a?overridelayout=t…
    Thanks,
    Phani.

  • Aggregation Problem on BEx Report

    I have a query that I want to display key figs that will aggregate.
    For example:
    char -> 0DF_PREQ
    char -> 0DF_PREQITM
    char -> 0pur_group
    char -> pr_rlsdt
    char -> zprrlsta
    key_fig -> 0netprice
    cal_key_fig-> z_mike_test
    cal_key_fig -> ckf_mike_test
    z_mike_test is defined as:
    general calculation: abs(date1 - date2)
    aggregation: std
    aggregation reference_char: 'none'
    calcuate after aggregation - checked
    cal_key_fig is defined as:
    general calculation: z_mike_test > 40
    aggregation: std
    aggregation reference_char: 0DF_PREQ
    When I run it I get 8 rows. The days are calculating properly, and my counter displays 1 in the ckf_mike_test column for 6 of the 8 records so I'm all happy. 0DF_PREQ is unique for 6  occurrences (i.e. one 0DF_PREQ has 3 0DF_PREQITM)
    However, when I take out 0DF_PREQ I get 7 rows and my counter displays 1 in the ckf_mike_test column for 5 rows. What I expected to happen is for one row to have a 2 in it, i.e. there should have been an aggregation still by 0DF_PREQ.
    What am I doing wrong?
    Mike

    Al,
    When I remove PReq# I get
    Item# PurGrp    Buyr    POP Date   PR Date   Stat Date  Price  Days Counter 
    10     XYZ   Doe, John 05/03/2011 10/12/2011 10/12/2011     27.96     51     1
    10     XYZ   Doe, John 05/03/2011 10/21/2011 10/26/2011     27.96     37     0
    10     XYZ   Doe, John 10/10/2011 10/10/2011 10/26/2011     27.96     37     0
    10     XYZ   Doe, John 10/12/2011 10/12/2011 10/12/2011     27.96     51     1
    10     XYZ   Doe, John 10/13/2011 10/13/2011 10/13/2011     55.92     50     1
    20     XYZ   Doe, John 10/13/2011 10/13/2011 10/13/2011     27.96     50     1
    30     XYZ   Doe, John 10/13/2011 10/13/2011 10/13/2011     27.96     50     1
    I'm thinking this record:
    10     XYZ   Doe, John 10/13/2011 10/13/2011 10/13/2011     55.92     50     1
    should be
    10     XYZ   Doe, John 10/13/2011 10/13/2011 10/13/2011     55.92     50     2 <-
    Mike

  • Exception Aggregation for RKF

    Hi Experts,
    Is there a way to set Exception aggregation for a restricted key figure?
    Thanks
    GMS

    Hi Prasad,
      A restricted key figure is a normal key figure, so u can set the exception aggregation in the Bex Options in the Key figure properties.
    Thanks,
    Krish

  • Reporting-Keyfigure Properties-Enhance -Aggregation-Exception aggregation T

    Hi All,
    What is the use of Keyfigure properties-enhance-aggregarion-exception aggregation use in Bex reporting.
    I can see values like Exception if more than one record occurs,Exception if only one record occurs,Counting values and so on.
    Can any give me clear example please.
    if you have any documents please send to [email protected]
    Thanks

    Hi.
    I take it you have read through the SAP Help documents for this? They include examples, generally I find it pretty helpful when you have a question as specific as yours... here's the link for the area you are looking at.
    http://help.sap.com/saphelp_nw04s/helpdata/en/9d/76563cc368b60fe10000000a114084/frameset.htm
    Patrick

  • SAP Bex Bi4.0 Integration - Data delegation

    Hi Experts,
    SAP Bex Bi4.0 Integration
    The Key Figures which uses Standard Aggregation or exception aggregation in SAP Bex appear as Data Delegated in Webi.
    Thus we are unable to add any conditions on such variables which lead to "#Unavailable" error.
    Is there any solution or work around for the same??
    Many Thanks
    Akshay

    What is your BO version? If you are above SP4, this issue should not be a problem with SUM aggregation type Key Figures.
    If you are still having problem, you can create variables and set it as Detail object to related dimension. In your report block, you can put both the dimension and your detailed variable. After that, hide the dimension.

  • Exception aggregation 'Average of all values'

    Hi,
    What is Exception aggregation 'Average of all values' wrt a reference characteristic. an how do I use it in Bex?
    -Simmi

    hi,
    it determines how the key figure is aggregated in the BEx in relation to the exception characteristic, in your case it's averaged for all values.
    another case sample maybe you need to report stock, which should not accumulated, but the last value, then you can choose 'last value', with reference chacarteristic to certain time characteristic.
    you may also use it for 'calculated key figure' in BEx to get average value.
    http://help.sap.com/saphelp_nw04s/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/6f/56853c08c7aa11e10000000a11405a/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/9d/76563cc368b60fe10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm

  • Inverse Normal Distribution function SAP Bex Query

    Hi All
    In BEx Query designer there are different aggregation  types available i.e. min, max,average, standard deviation etc.  for
    formula or calculated key figure.There are not any additional statistical functions such normal distribution, inverse normal distribution available in Bex query designer.  How to achieve normal distribution, inverse normal distribution as aggregation
    type in Bex Query designer? Your help is appreciated.
    Thanks

    Hi Dennis,
    We have done the similar thing recently but performance of crystal reports is very poor on bex query. Did you face the same thing? Any suggestions/ideas to improve performance..
    Thanks,

  • #MULTIVALUE on ratios with navigation attributes

    Dear All,
    I have some problem with table where I put only navigation attributes and ratios... the colomns ratio is "MULTIVALUE" value..
    I would like aggregate ratio on the table...
    Workaround ? Solution ?
    Thanks
    Cédric
    BO edge 3.1 SP3
    SAP BW EHP4

    Hi Igno,
    I agree that it still says that in the best practise (dated back in 2009!), but in my experience in the past years it doesn't work that well. Unless you tailor your BEX query one to one with a report that is... Not the intention of a universe i.m.h.o.
    For standard aggregation keyfigures I always set the aggregation to sum. So I only use database delegation if I really need it because it would not be possible for WebI (for example counts like number of stores with sales).
    Note that I also make sure that I retrieve data on the level that I need (by checking the number of rows retrieved for instance and comparing that with the number of lines in the report. So the database will do all of the aggregation it can do already!
    So you do NOT get the sum a second time! You get it only once, only who handles the summing within the results is different, with database delegated, it is BW, with sum it is WebI. For a plain sum it is Webi and summing within the retrieved results can be handled by WebI perfectly fine (and will match with sums by BEX where you have them) !!!
    Letting BW handle the aggregations means it will retrieve all the extra aggregation points it can find in the report, but only if it can!
    In this particular case the attribute country of the customer is not a known aggregation level for BEX, so it cannot calculate it.
    Also if you create webi based groupings of dimension objects, or even want to re-format one (like month) it does not work.
    Furthermore, if you read my post correctly I do not mention "GROUP BY" but I do say grouping.
    For totals you will always have a certain grouping/combination of dimensions (whether you call them dimension objects (in WebI) or characteristics (in BEX)). I state that to calculate an aggregation for that combination the BEX query needs to have knowledge about it. If it has not, it cannot calculate...
    So I say it should be the preferred way to let WebI handle the aggregation,
    unless it cannot do this correctly, not the other way around.
    Thanks,
    Marianne

  • Cumulative value with Agg. reference char.

    hi,
      If you go to the display of the key figure, in the second tab Aggregation, how should we use Agg. reference char with Cumulative value radio button checked.
    I read SAP help but could not get it.Please explain with examples.
    Thanks in advance.

    Hi
    Aggregation :
    This flied is the standard aggregation with three options - Min,Max,Sum
    Exception Aggregation :
    This field determines how the KF is aggregated in the BEx in relation to the
    exception characteristic.
    The key figure ‘Number of Employees’ can be aggregated using the ref .characteristic ‘Cost Center’ (Non-time characteristic).
    Here you would determine a time characteristic as an exception characteristic with, for example, the aggregation ‘last value’.
    For Non Cumulative values:
    If you want to aggregate the KF value in business explorer using the non time characteristics like 0person.... then your standard aggrgation field should have summation value
    and if you want to aggregate the KF value in the  business explorer using the time char.
    like 0calmonth, then your exception aggregation field should have last,average.... values (not equal to summation)
    Assign points if helpful.
    Thanks

  • Difference between  aggregation and calculation tab in BEx Query Designer

    HI,
    I am using BEx Query Designer for my report, for the key figures in the coloumn area i slected one numeric key figures, in  the properties tab i found aggregation tab and calculation tab.
    I need to sum up the total values for that particualar coloumn, when i used calculation tab i found to sum all the values for a particular coloumn, then what is the use the aggreagation tab?
    I not able to used that Aggregation tab it is showing as a hidden fields...
    can any one tell me whats the exact difference between these tabs and when we need to use which tab?
    With Regards,
    Thanesh Kumar.

    Hi Thanesh Kumar,
    I moved this thread from forum Data Warehousing to Business Explorer since it is a query related question (as SDN moderator).
    I could explain to you the difference between these two tabs.
    For "calculation" tab, it changes the display of result and does not change the calculation logic.
    It means that, if this key figure is used further in formula, still the original number (without "calculation" tab setting)  is used for further formula calculation.
    For "aggregation" tab, it changes the real calculation logic.
    The system takes the setting as the aggregation rule for records.
    The most common aggregation rule is of course summation. If you set to e.g. Average here, the system does the
    Average instead of summation when aggregating records. And the Average value will be taken for calculation
    in further formulas or other calculations.
    For "aggregation" tab, you could only use it for CKF (calculated key figure) or formula and you could not use it for
    a basic key figure. That should be the reason why you see it greyed-out.
    Regards,
    Patricia

Maybe you are looking for