How to work force calculation before aggregation in 2004s

I have a calculated key figure that has a variable in the calculation entered at time of query execution. I have tried every setting I can think of to force the calculation before aggregation with no luck. If I create the CKF in 3.5 without a variable it will work, but I cannot get this to work in 2004s.
Does anyone know how in 2004s to force the calculation to take place at the automic level before aggregation and indepenent of drill-downs?
I have referred to note:922727 but none of the exception aggregation options seem to behave as 3.5 does with calculate before aggregation.

Hi, Sudeepta
Thanks for your reply.
I did try to set 'No display' for 'Hour'. The result is that the Characteristics 'Hour' doesn't appear on the query result, but the detailed line of key figures still display on the result. It looks like the followings: (I put summaries on the top/right)
Date 1/1 1/2 Overall result
KPI1    10        11   22 (sum line)
KPI2    20        21   41 (sum line)
KPI1    12        13   25 (detailed line)
KPI2    13        13   26 (detailed line)
KPI1    11        12   23 (detailed line)
KPI2    12        12   24 (detailed line)
I want to suppress all the detailed lines and leave sum lines on the result.

Similar Messages

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

How to calculate key figure before aggregation for complex formular?

Hi, buddies
Here's the simplified senario:
I have a cube, in which the characteristics are 'Calendar Day' and 'Hour' (values are 01~24), and the key figures are stored by day and by hour.
What I need is very simple, a query to display calculated key figures only by Calendar Day. I don't need Hour information.
So I create a query: column charact is Calendar Day, rows are several calculated key figures.
Now the problem is that:
if I don't put 'Hour' as row in the query, I'll get WRONG result. But if I put 'Hour' as row in the query, I'll get CORRECT result, but all the 'Hour' details will display, which should be hided.
I know the reason is that:
the calculated key figure that I create should be calucated before aggregation, not after. But since the formular is pretty complex, I can't change the 'Time of Aggregation Calculation' in key figure's property. (It's greyed out.) So I have to put 'Hour' as row in the query to force calcuation 'before aggregation' in query and set the property 'Calculate Result As...' as 'Summary'.
My question is:
whether there's any other way to force calcuation 'before aggregation', so I don't have to put 'Hour' in the query.
If no, is there a simple way to hide the 'Hour' details and only display summary result ON THE QUERY LEVEL? (
I can hide detail lines by using web template, or maybe using VB in excel. But I can't use either of them. I want to hide the details on the QUERY LEVEL. So I can use the query directly in any other reporting tools, like Visual Composer.)
Any idea?
Wei

Hi, Sudeepta
Thanks for your reply.
I did try to set 'No display' for 'Hour'. The result is that the Characteristics 'Hour' doesn't appear on the query result, but the detailed line of key figures still display on the result. It looks like the followings: (I put summaries on the top/right)
Date 1/1 1/2 Overall result
KPI1 10 11 22 (sum line)
KPI2 20 21 41 (sum line)
KPI1 12 13 25 (detailed line)
KPI2 13 13 26 (detailed line)
KPI1 11 12 23 (detailed line)
KPI2 12 12 24 (detailed line)
I want to suppress all the detailed lines and leave sum lines on the result.

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

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

Calculation Before Aggregation obsolete in NW2004s

We are upgrading our sandbox from BW 3.5 to NW2004s and several of our queries use the obsolete Time of Calculation 'Before Aggregation' technique. I searched and found a thread Time of Calculation "Before Aggregation" obsolete in NW2004s in which Klaus Werner recommended the use of exception aggregation in place of the calculation before aggregation method.
We do not yet have our BI Java up and running and I do not yet have access to the Query Designer 7.0, just the Query Designer 3.5 under NW2004s. I have not been able to create the solution proposed by Klaus Werner and I think his solution is only possible using Query Designer 7.0. Is this right or am I missing something and should be able to modify my Query Designer 3.5 queries to utilize the exception aggregation solution as proposed by Werner.
An example of our CKF which currently uses the calculation before aggregation technique is
CKF1 is defined as ((KFa >0) AND (KFa < 1000) * KFb + 0)
and we want that resolved at the document level (before multiple documents are summed) to determine if KFa is in this range for a single document. For every document in which KFa is in the above range, we want to sum together KFb. When I input my formula into CKF1 I am not given a choice where I see any exception aggregation options using Query Designer 3.5 under NW2004s. Am I just missing something or do I need to wait until I have Query Designer 7.0 to change my method of calculation this?
Thanks for your help,
Jeri

Hi Jeri,
Could you tell me where you found the document of Klaus Werner?
Answer:
I found it in the other thread.
Thanks,
Eelco
Message was edited by:
Eelco de Vries

Warning Time calculation "Before Aggregation" is obsolete

Hi,
Recently in our project we have upgraded BW 3.0B to BI7.
After upgrade to BI7, when we run some of the reports we are getting a warning message as below -
Warning Time calculation "Before Aggregation" is obsolete.
Pls refer to the attachment.
Any of our satyam colleagues encounter this warning, if so what was the solution you applied.
Note : I found some notes in Forum like saying use ' Exception Aggregation' for the Before Aggregation.. etc etc., but my problem is in our project thre are many CKFs are there which are using 'Before Aggregation'.
Please let me know if you have any other alternatives.
Thanks !!!!!!!!!

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.
thanks,
JituK

I pad 2 updated to iOS 6.1.3 and now wifi is greyed out. Apple support engineers say replace but my warranty exited 09/12. Funny how it worked perfectly fine before the update.

I just updated to6.1.3 and now my wifi button is greyed out. Apple support said it is a hardware issue. Funny how it worked just fine on the previous iOS. Now apple wants me to buy a replace not because my warranty expired 09/12. Seems to me like ios6.1.3 was an update to sell more products. Tried all suggested fixes with no success. With all the noted issues with ios6 there may be another class action lawsuit coming. Apple tech senior advisor unwilling to help. First advisor told me just buy a new I pad. Second advisor wants me to pay for a replacement. Can someone explain to me how an apple approved software upgrade that damaged my i pad is classified as my fault. I've seen some shady selling techniques but this one takes the cake in my book. Anyone have the contact information to higher up executives in apple for me to speak with about my issues?

Have you check the following?
Verify that airplane mode is off by tapping Settings > Airplane Mode.
Reset the network settings by tapping Settings > General > Reset > Reset Network Settings. Note: This will reset all network settings, including Bluetooth pairing records, Wi-Fi passwords, VPN, and APN settings
Ensure that your device is using the latest software.
If your issue is still unresolved, perform a software restore in iTune

Calculated key figures from multicubes before aggregation

Hi,
I am calculating a total using a calculated key figure
that has one key figure from a multicube and two other key figures from another multicube.
Also I factor the total using a variable with a replacement path on the dummy attribute (Constant) to "force" the calculation at the material level.
Cost = Cost(CUBE1) / Quantity(CUBE1) * Quantity(Cube2) * ZVRMATER1
Problem:
If I split the calculation this works before aggregation at the material level. Also this works fine using calculations that use key figures that must be calculated before aggregation if they all are from the same cube at the time. The required formula above will not work (zero divide) since during selection the OLAP processor retrieves in phases and with value 0 from the key figure of CUBE2.
Any suggestion on how to solve this without new back-end development?
Thanks.

Hi,
I am calculating a total using a calculated key figure
that has one key figure from a multicube and two other key figures from another multicube.
Also I factor the total using a variable with a replacement path on the dummy attribute (Constant) to "force" the calculation at the material level.
Cost = Cost(CUBE1) / Quantity(CUBE1) * Quantity(Cube2) * ZVRMATER1
Problem:
If I split the calculation this works before aggregation at the material level. Also this works fine using calculations that use key figures that must be calculated before aggregation if they all are from the same cube at the time. The required formula above will not work (zero divide) since during selection the OLAP processor retrieves in phases and with value 0 from the key figure of CUBE2.
Any suggestion on how to solve this without new back-end development?
Thanks.

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 - incorrect values

Hello,
I am using Calculated Key Figure with time of aggregation calculation = "before aggregation" and then I use this CKF in columns. Some rows are calculated correctly, but some of them are not. And when I check the key figure definition for those incorrect in monitor query I can see the way how it is calculated and everything seems to be OK in the row 1 (picture) , but in row 2 the value is incorrect.
<a href="http://raisik.webz.cz/key_fig1.JPG">http://raisik.webz.cz/key_fig1.JPG</a>
Any idea why?
Thanks for any help.
Regards
Pavel

Hi Agrima,
Check here.....
http://help.sap.com/saphelp_nw04/helpdata/en/6f/56853c08c7aa11e10000000a11405a/content.htm
Thanks,
Vijay.

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.

Calculated key figures before aggregation

Hi,
I'm having trouble creating a new calculated key figure. Here's the situation.
I have two key figures: stock, value A. Now I want to create a new calculated key figure (in 3.x) using both key figures. The calculation would look something like: "stock * (value A == 0)". Now I want this key figure to work before aggregation. When creating this calculated key figure however I am unable to set the aggregation setting to before aggregation. Now, with any other key figure besides stock, this is no problem. Something like "profit * value A == 0)" works fine and I can set the aggregation setting to before aggregation. I suspect the reason I can't use stock in a calculated key figure set the calculate before aggregation is because of the exception aggregation of the stock key figure. It's set to last value in exception aggregation.
Does anyone know how to solve this problem? Thanks in advance.
Alex

Hi Alex,
please read this:
http://help.sap.com/saphelp_nw2004s/helpdata/en/75/21054da1392649948e5b94e4fc4bce/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
The reason that somtimes the propertie is available or not depends on the key figure type - e.g. if it is complex or not. I think that here is a lot of info available in the forum.
Regards,
Adem

How do I force/re-install failed Leopard update (USB no longer works)?

Hi everyone,
The last Leopard update last week went smooth with two out of three of my Macs.
Unfortunately the update did not work well on my MacBook Pro 17". I let the update
run over night and in the morning it was still stuck on an "installing" screen. I had no
choice but to force a reboot. From what I can tell a lot of the system .kext files were
updated, but my kernel was not. How do I know this? Well my USB ports no longer work
(well at least with USB memory sticks). I checked my kernel version and it says 9.3.0. The
versions for the System.kext file under /System/Library/Extensions is showing 9.4.0.
Obviously I got far enough into the update that the newer system file works (almost)
with the older kernel.......
So how can I force this update to run again??? I really don't want to reload my MacBook Pro
from scratch. There must be a fix... Please help!
Thanks,
Mike Bender
Orlando, FL

Alternatively, restore your previous good and tested bootable backup/clone, then run the COMBO update again. Don't have one? Then take some time to peruse:
http://docs.info.apple.com/article.html?artnum=106941
http://www.macmaps.com/upgradefaq.html
http://www.macmaps.com/backup.html
http://www.thexlab.com/faqs/installswupdates.html
http://www.thexlab.com/faqs/backuprecovery.html

How I can force to Catalyst 3750G to work like SLAVE

Hi,
Help me, how I can force to Catalyst 3750G to work like SLAVE, I can't find the command..

Hello Friend
You have to set the slave switch's priority to be lower than the master switch.
3750-Stk>show switch
Current
Switch# Role Mac Address Priority State
1 Slave 0016.4748.dc80 1 Ready
*2 Master 0016.9d59.db00 5 Ready
This following link is a good read
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00807811ad.shtml#pval
Thanks
Suresh

How to work force calculation before aggregation in 2004s

Similar Messages

Maybe you are looking for