Bex Issue : before aggregation

Hi,
I have a problem in Bex that I thought to solve with the "before aggregration" option in Bex Analyzer but this doesn't seem to be possible.
My query looks initially like this for 1 shipment 1344601 that is linked to 2 deliveries
Shipment Delivery Del.Quantity Counter Del.Quantity/Count
1344601   81209721  41.160 KG     2      20.580 KG      
1344601   81209722  14.840 KG     1      14.840 KG
Resultrow .............56.000 KG     3       35.420 KG
This 35.420 KG is the right total delivery quantity for shipment 1344601. Note that counter is calculated via a formula with before aggregation. Also the Del. Quantity is included in a formula with before calculation.
When I now remove the drilldown on the delivery my result is wrong :
Shipment      Del.Quantity Counter Del.Quantity/Count
1344601       56.000 KG    3       18.666.67 KG
Resultrw     56.000 KG    3       18.666.67 KG
The system is dividing 56.000 KG by 3 which leads to an incorrect result of 18.666.67 KG.
==> My problem is that I can't put the Del.Quantity/Count on calculation before aggregation, although Del.Quantity and Counter that are used in the calculation have both calculation before aggregation.
Via a little trick (include the calculation in a new calculated keyfigure where I multiply it by 1) I could put it on calculation before aggregation but then the query execution fails.
Does anyone know a solution for this behaviour as I think lots of you might have faced similar situations and I would like to avoid to solve this in data staging as this doesn't seem unsolvable in Bex to me...
Message was edited by: Wim

Hi,
As per the my knowledge, we can use the properties of Before Aggregation in Bex Analyser.
for ex. when u excute your query, by default the result of the calculated key figure is generated after aggregation. But we can change this property to before aggregation by going to context menu of the calculated key figure for the analyer.
But it is considered as a bad practice in SAP.
If you want to use this option in query designer it not available,
because when we use calculated key figure in formulas it calculate as after aggregation. If you want to change it, we can change at analyser level.
Hope u understood.
Regards,
Vamsi
Assign points if useful.

Similar Messages

  • "Before Aggregation is Obsolete": BI 7, using BEx 3.x.

    Good day
    We have upgraded to BI 7 but is still using BEx 3.x.
    I received a problem on a BEx query. The Aggregation in the CKF's properties is set to "Before aggregation". Now with BI 7, it is not accepted. I have read through all the threads relating to this issue and exception aggregation, but nowhere could I find a clear answer for my related problem. I've found proposed solutions on SDN ie. (1) You have to change this setting in the "old" BEx Query desginer (3.5). (2) U need to use exception aggregation and set the properties on each infoobject level in BI 7.0"
    But what does the above really means?
    What I have done: I have created a new CKF with the aggregation setting to "After Aggregation". I added the new CKF to the query. Unfortunately the user cannot find a previous saved report in order for me to validate the figures between before the upgrade and after the upgrade, with the new setting, to BI 7.
    Question: Is this the only setting I need to change?
    Thanks in Advance.
    Cj

    >
    Cornelius Faurie wrote:
    > I have looked at the lowest level of detail, which is the following ie. this is the restrictions in my query/excel list extract from cube
    >
    > Invoice group restricted to 6 and 0
    > Vehicle class restricted to 2
    > Forecast Period 200823
    > Stock restricted to Y
    you're "lowest level of detail" for the calculation you are trying to accomplish, should either be: a product, a customer, a document number OR a combination of document number and item
    it totally depends on your specific case, so I cannot help you unless you tell me what kind of data you're reporting on... right now, all I know is that you have some kind of vehicle class and invoice group... so I'm assuming you have a level "vehicle" as well? now you need to ask yourself, what exactly am I trying to calculate... and try that in Excel... it should be clear from there how to "set it up" in BI

  • Before Aggregation in Bex

    Hi,
    My query is at a Calmonth level but I have to do the calculations at the Calday level.
    OverTime = Actual Hours - Planned Hours
    I have Cal Day in my MultiProvider. How can I use Before Aggregation in the query so that I can achieve the calculations at a day level.
    Thanks
    Deepthi.

    Hi Deepthi,
    Use Exception aggreation for the key figure calculating OverTime.
    with reference characteristic as 0CALDAY.
    If you are in BEx 3.x, you may creat a new calculated key figure , with the original key figure and in the properties of this calculated key figure, you can exception aggregate using enhanced properties...displayed with a button below...
    In BEx 7.x.. you can create a new selection and in aggregation tab in the selection properties mentione the exception aggregation as Sum with reference characteristic as 0CALDAY.
    Hope this helps,
    Best regards,
    Sunmit.

  • Time of calculation before aggregation is obsolete

    Hi Gurus,
    I have this message when i try to ejecute my query, can anyone help me to resolve this problem, i have the SAP 7.0 EHP 1, and i just have the upgrade from SAP 3.5.
    I have a lot of CKF's in my queries and all of those use BEFORE AGGREGATION option, when i put in the propietries of my CKF the option after aggregation and then i check my query i have a message "time of calculation before aggregation is obsolete", and then when i put the option before aggregation in my CKF i have the message "CALLATE = 0 is not allowed".
    I hope that someone have the same issue and can help me with this.
    note: i'm using the BEX 3.5 and the BW 7.01 because the client wants that.
    tnks
    regards
    Odiseo
    Edited by: Odiseo BW on Oct 18, 2010 7:46 PM

    hmmm... how about checking the differences between 3.X & 7.X???
    before aggregation is no longer possible in 7.X, hence the error messages

  • Warning before aggregation is osbsolete

    Hi guru's
    I'm migrating our BW system and in some queries we have the message Warning calculation before aggregation is obsolete.
    We still use BW 3.x analyzer.
    when i execute queries the message is only a warning and i can see result in my reports.
    i need to check the data but do you know if the message is a warning because this functionnality does not existe in BI 7 analyzer tool and if i use Bex 3.x will the data be correct ?
    Thanks
    Cyril

    Good day Cyril,
    When you migrate a query which has CKF with 'Before Aggregation', you will be requested to change it to 'after aggregation'. After turning on the option for 'After Aggregation query behaves same as what it used to do in BEx 3.5 with option 'B4 Ag'gregation'. Results are same.
    The use of BEFORE aggregation was removed as this can cause a drain on the system resources and therefore cause performance problems. For this reason it was made obsolete with the 7.x system. The OLAP processor handles data differently in the 7.x systems so removing the before aggregation option should not cause too many problems for customers migrating over.
    With this in mind, however, there are differences to BEFORE and AFTER aggregation. It may not affect the calculations you are using in your queries but you must be aware that some calculations are carried out at different times and this can cause hiccups. Most note-worthy would be when formulae are used and when replacement path variables are needed. In some cases, the necessary calculations may not be carried out and the figures may not be available which would not have been an issue in the 3.x system using before aggregation. 
    Check out SAP Note 1151957 which is excellent for understanding how the OLAP processor carries out calculations. It also details the differences between BEFORE and AFTER aggregation and should be very helpful for you going forward - particularly if you use formulae or replacement path functions.
    Be aware that there are differences and there may be queries where you get a red X instead of a value. In most cases, this means rewriting a formula so that the processor can now accomodate the aggregation you need to achieve.
    Hope this helps, Cyril.
    Regards,
    Karen

  • Before Aggregation in NW2004s(BI7)

    Hi Bex Gurus,
      We have upgraded our BI System to NW2004s and Bex version is still 3.5.
      Now we are also planning to migrate Bex to new version(NW2004s ).
      We have used "Before Aggregation" in some of the calculated KFs in the queries.  "Before Aggregation" is obsolete in NW2004s. So, I want to know whether these calculated KFs will give the same result when we migrate our front end to NW2004s.
    Please provide your experience.
    Regards
    MB

    Peter,
    Thank you for your reply.
    Is there a automatic way to do what you mentioned in below sentance?.
    " Using the new front end tools you can apply exception aggregation to all calculated key figures including those with formulas in them"
    Our scenario is,
    We have a many CKFs with "Before Aggregation" setting in BW 3.5 version.
    Example : CKF1 with "Before Aggregation" setting. This works irrespective of the drill down ( i.e Palnt, country or region) in BW 3.5. But, when I migrate the query  to NW2004s, CKF1 is not giving the expected result when we drill down on Palnt, country or region.
    So, Do I need to create three new CKFs (on Plant, Country and Region)  using exception aggregation and use corresponding CKF based on drill down  to get correct result in NW2004s?.
    Appreciate your help.
    Regards,
    Madhukar

  • Before aggregation with boolean operators

    Hi gurus,
    does someone know if there is a way to force a bex formula, defined by a boolean operator, to be executed in "before aggregation" mode?
    For example, let A and B two propositions, and KF1 and . We define the following formula key figure 
    <b>(A) * KF1 + (B) * KF2</b>
    where (A) = 1 if A is true and (A) = 0 if A is false.
    My question is: is there a way to force this formula to act before aggregation.
    Thank you very much
    Matteo

    I cannot do that, because you can set "before aggregation" property only for KF that are built on basis KF. But I have to built my formula using boolean operators that are not basis KF.
    That's why i cannote use "before aggregation" in the properties of my KF.
    thank you
    matteo

  • Calculation before aggregation

    Hello BW Guru's
    What does this calculation before aggregation mean ?
    In which situation we use the above setting ?
    when we can use this option in Modelling and when we can use this option in reporting ?
    I am zero with this.. please explain me with a real time example.
    Full points will be assured for the best answer
    many thanks in advance,
    NIru.

    Hi,
    An aggregate is a materialized, aggregated view of the data in an InfoCube. In an aggregate, the dataset of an InfoCube is saved redundantly and persistently in a consolidated form into the database.
    How to create Aggregate for the cube.(for the example shown below)
    step1
    go to rsa1 transaction code , right click on the cube --->maintain aggregates ---create by your self
    Step2
    in the dimension Drag Region give the name of the aggregate .
    after dragging in the aggregation selection type you will find * . that means it is assigned for all characteristics value.
    or
    right click on the * and select fixed value as NY( this will give aggregation values only for NY)
    but in the example i have take * it is for all characteristic value ( means for all values NY and CA)
    Step3
    Now place the curser on the sigma symbol and activate the aggregate.
    Step4
    Now load the data to the cube , befor loading the data to the cube it a good practice of switching of the aggregate and switch on after loading.
    this option can be obtain at top menu aggregate---> switch on of for queries that means the aggregates are available for the reporting to view.
    by doing this this will increase the load performance and also the execution of the query will be fast
    Step6
    now open the report and execute
    The scenario below shows you how to count the results of a calculated key figure in the BEx Query Designer.
    You have loaded the following data into your InfoCube:
    Before Aggregation
    Region/     Customer  /Sales Volume USD
    NY /     A     /400
    NY/     B     /200
    NY/     C     /50
    CA/     A     /800
    CA/     C     /300
    After Aggregation
    Region/                SalesVolumeUSD
    NY/                        650
    CA/                       1100
    Overall result                 1750
    hope this is clear
    Santosh
    Edited by: Santhosh Nagaraj on Oct 29, 2009 3:35 AM

  • Befor aggregation in query and  New functionality in BI7

    Hi,
    I want to find all the CKFs which is using 'Before aggregation ' property.
    Can somebody tell me the meta table used for this. I checked table RSZCALC..
    either I dont know which field to use or is of no use to my issue.
    Also in BI7 , i know that 'Befor agrregation properety no longer exist. What is the alternative
    for this functionality in BI7?
    Thanks.

    Hello,
    look at your table RSZCALC, and the fields :
    CALLATE : field = 0 (Before Aggragation)
    for BI7 :
    AGGRGEN : Aggregation type
    AGGREXC : Aggregation Exception
    AGGRCHA : Characteristic of reference

  • Before aggregation - versions

    Hi guys,
    I have been dealing with my issue for several months and havent found any solution.
    I have two basic key figures which I need to multiply between each other.
    Normaly it first aggregate and than multiply (which gives me wrong result) and when I use <b>before aggregation</b> It gives me <u>0 result</u> because those key figures are uploaded on different <b>Versions</b>. (one is actual - # and the other is version 20). So the it always multiply 0.
    The reason for different versions is that one is Standard per unit (uploaded on the version 20) while the other one is Actual number of Units ( version #)
    Do you have any idea how to work around this?
    Thank you very much!!

    You can try out this in your develpment system.
    Create a New keyfigure and Add it to Infocube and activate it. In update rules, Use update Method 'Formula'. there you can multiply already existing Keyfigures.Save the update rules and activate...makes ure update rules,transfer rules and infocube are active...
    Now reload the data again...no problem if you have data already.
    Filter the Qurey with 'last request loaded' its availabe under datapackage dimension..
    Check whether you got values as required.if it not,delete this request and delete remove keyfigurte from update rules and infoprovider..
    If it is working fine,you can try to reload all the data again without deleting,using export datasource.

  • Warning "Time of Calculation 'Before Aggregation' is obsolete" in BI 7.0

    Hi Friends,
    We have recently upgraded our BW system from BW 3.1 to BI 7.0. While executing one of the query in BI 7.0 i am getting the Warning Message "Time of Calculation 'Before Aggregation' is obsolete". I can run the query by ignoring the message and get the results. But I am not getting the correct result for some of the calculated key figures which has setting for Time of calculation as "Before Aggregation".
    After doing some research i found that before aggregation is not allowed in BI 7.0. We are using queries created in 3.x environment. There is some work around which talks about creating new calculated key figure with after aggregation setting and all. But in my case it not feasible as there are so many queries based on those calculated key figures.
    Does any one had the similar situation? Is there any other way to correct this problem?
    I would appreciate your help in this regards.
    Thanks,
    Manmit

    Hi
    Try SAP notes 935903.
    Symptom
    Calculated Key Figures "Existance Indicator" with aggregation behaviour "Before Aggregation" will get now with NW 2004s warning popup "Time of calculation 'Before Aggregation' is obsolete" during execution.
    this may be helpful.
    Also Check the below thread
    /message/2986338#2986338 [original link is broken]
    Regards
    Shilpa
    Edited by: Shilpa Vinayak on Oct 10, 2008 4:23 AM

  • My MacBook Pro just shut down without notice. It had about 40% of the battery life. It will not turn back on and I noticed when plugged in the little light on the power cord is blinking orange, not a solid green like normal.  Anyone have this issue before

    MacBook Pro just shut down without notice. It had about 40% of the battery life. It will not turn back on and I noticed when plugged in the little light on the power cord is blinking orange, not a solid green like normal.  Anyone have this issue before?  I've only had this for about 3mos.  I called apple support. They tried one thing then said I have to take to the apple store. Unfortunately I don't have one nearby. So before I travel an hour+ away I thought is give it a shot on here. Thank.

    Hi S,
    Did they have you try an SMC Reset: http://support.apple.com/kb/HT3964?

  • I just installed Lion and the newest version of Logic express 9 (9.1.5) and every time i playback audio I get this error message:  [Disk is too slow or System Overload. (-10010) . Never had any issues before now...

    I just installed OSX Lion (10.7.2) and updated to the newest version of Logic express (9.1.5) on a macbook and every time I playback audio I get this error message:  [Disk is too slow or System Overload. (-10010) The Sudden Motion Sensor may have parked the hard drive head, or the disk performance is not sufficient to read or write all audio tracks, or the system was not able to process all data in time]
    Never had any issues before now... any ideas?

    Have a look into the Preferences folder (YourUserFolder/Libraries/Preferences/) and trash all Logic preferences.
    You'll have to setup the program again.
    cheers
    rob

  • My iPhone 4S is not showing up in iTunes.  I've never had this issue before, but I'm finding it a little frustrating trying to figure out how to rectify the situation.  Any suggestions would be greatly appreciated.

    My iPhone 4S is not showing up in iTunes.  I've never had this issue before, and I'm finding it a little frustrating trying to figure out how to rectify the situation.  If anyone knows how to fix this problem, please advise.  Otherwise any suggestions would be greatly appreciated.

    Hi Josie,
    I understand that you are having issues with iTunes recognizing your iPhone 4S. Let's see if we can tackle this.
    The following resource will provide helpful steps in resolving this issue, pay specific attention to Steps 3-6 as these usually resolve this sort of issue.
    iOS: Device not recognized in iTunes for Windows
    http://support.apple.com/kb/TS1538
    Thanks,
    Matt M.

  • Mac cant see the wifi network if i dont get close enough which was not an issue before

    Hi. I have a macbook pro OSX 10.8.4
    At the office my mac can not see our network router if i dont get close enough.
    This was not an issue before i could directly connect it at my desk. now when i turn the
    computer on i need to take to mac as closest as i can get to the router ( in next room ) wait for connection
    and return to my room. and this way i still can get full signal.
    and also a windows laptop on my desk and even my iphone can find the router and connect with no problem
    at my office.
    any ideas ?

    Hi! It's been a while but here's the latest update on the case.
    (And yeah,I've been struggling until today to find a solution...Danny's personal advice: don't move to Italy if you don't wanna get lost in a Customer Service nightmare...)
    Anyhow, it turned out to be as simple as this:
    1) Create a location dedicated to the home network.
    2) Insert PPPoE user name and password given by ISP.
    3) Connect.
    4) Browse wirelessly.
    ...I feel a little dumb overlooking this option....but, I still have some doubts reg the procedure.
    Why did I have to create a dedicated location?
    Why do I have to use PPPoE rather than DHCP?
    Thanks mate,
    D

Maybe you are looking for