Exception aggregation for averaging

Hello,
I am having some issues understanding how to model key figures with exception aggregation.
For example: Lets say that I need to filter by age of employee per cost-center and calculate the average age of all employees belonging to each cost-center.
What is the appropriate way to model this in a report. Exception aggregation or variable? Is there any justification on which way to model this?
Any thoughts?
Regards to all

Ideally model the same in the query because if you model the same at the Key figure level - you cannot change the same without deleting data. Also if you model the same at the query level you can change the aggregation behavior depending on requirements.

Similar Messages

Exception aggregation for info object

Hi all,
I have problem using exception aggregation for info object (zabarb) :
The data :
wbs element      zabarb
        1                    100
        1                    100
In query i want to show the data wbs element: 1; zarbarb:100
But in fact i got in query wbs element 1; zabarb :200
I've tried to change info object exception aggregation : average all value with reference char. wbs_element, but still the result in query is 200.
I hope someone can help me.
Thanks.

Hi,
Make these Changes to the Info Object
Aggregation--MAximum
Exception Agg-Summation
Agg Ref Char- wbs_element
Thry this..........
Rgds
SVU

What is the default exception aggregation for the NCKF IO STOCK

Hi all of you,
What is the default exception aggregation for the Non Cumulative Key Figure info object Stock?
When I am selecting Maximum, or minimum or Avereage (all values) its not selecting any of these values but only Average (weighted with the number of days) is getting selected.
Please explain.
Thank you.
TR.

Hi Vinod,
Thank you for your reply.
I had selected Last value as exception aggregation and activated it. But again when I double click on the IO STock, in the aggregation tab besides exception aggregation I find the option Average (Weighted with the number of days).
Is it getting selected by default when I check the radio button Ncum. value with in- and out-flow?
Please explain.
Thank you.
TR.

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

Exception aggregation for calculated key figure

Is it possible to have exception aggregation for calculated key figure in BW 3.5? As per Note 1151857, it is possible, however this note applies to BI 7.0.
As per note 152638, it is possible in older version only simple ckfs like 'CKF = Base key figure'.
Is there any workaround to define exception aggregation for complex CKFs in BW 3.5?
My requirement is like this -
CKF = (sales quantity - forecast) %share (sales quantity).
Aggregation for CKF over time should be sum whereas, for all other characteristics calculation of CKF should be done after aggregation(normal scenario).
So, defining exception aggregation of CKF as 'Summation' over time should fulfil my requirement.
I can not use calculate result as 'summation' setting for CKF because of following design of report.
Report contains structure(characteristic)
Elements of structure are -
Last 3 months(April - June)
Last 3 months - 1 (Mar - May)
Last 3 months - 2 (Feb - Apr)
and so on...
When data is aggregated for each element of structure, base KFs will be aggregated and calculations will be done on that.
Changes in the backend are also not possible because, normal aggregation of CKF-alike in backend will be summation for all characteristics.
Is there any way in BW 3.5 to model such a scenario?
Thanks and Regards,
Anup Kulkarni

Sum of individual values of CKFs is not same as the Calculation on 'sum of basic key figures(result of basic key figures)'. - Yes, you are right.
I need to aggregate CKF over time as SUM. However, calculation for result of all other characteristics should be based on results of basic key figures and not the 'Sum of individual values of CKF'. -
What i understood is that whenever the time char is in row, then result should be simple on the sum what ur getting but when other char are there then it should go for calculation based on the sum of key figure.
If im not wrong in getting ur point.
How can two differenct activites be perofrmed on same key figure depending on the characteristic .....!. For this u have to think some other possibility or let somebody else update the thread.

Exception Aggregation for a Calculated Key Figure in a Structure

Hello BI world,
Please can someone tell me if it is technically possible to use "exception aggregation (count) in a calculated key figure within a structure.
The definition of the structure is:
Rows: Characteristic (Selection) = Problem type (0CATCODE_FE) = "AF01"
Colums (Selections) Month 1 , Month 2, Month 3, etc .. Total
             Details of the selection for each month
                       0CALMONTH = Variable (offset+1 for Month 2 , 3 etc)
                               1KYFNM = CKF
Calculated Key Figure (CKF) =
                   General Tab: = Key Figure "0CAUSE_CNT"
                   Aggregation Tab - Exception Aggregation = Count All Values
                                             Ref Characteristic = Problem type (0CATCODE_FE)
                                                Calculation After Aggregation = not ticked
                   Local Calculations Tab = All "Nothing Defined"
What I am trying to achieve is the "count" of "Category codes" for each month specified in the structure.
I have looked in the cube and there should be a "category Code" count of "9" for Jan 2008 for notifcation type AF01 but the query shows 0?
Thanks in advance, points will be awarded.
Steve

Still not working? Not sure why? Have tried both answers and just not counting...
Is there any restrictions on using "exception aggregation" in a calculated key figures in a structure?
The structure is in the columns and it is a selection that includes the CKF with the exception aggregation plus a restriction on calendar month using a variable?
Any help greatly appreciated.
Thanks in advance.
Steve

Exception (Aggregation) in Hierarchy nodes results

Hi All,
We have a requirement to sum all values (as results in hierarchy levels) based on the value of a specific characteristics. example as below is what we want to achieve. Country, Product group, materials are all characteristics and this is viewed as hierarchy in the query. In each material there is a calculation components that will shown the value of Sales Qty, Price/unit and Amount. What we want is to sum up ONLY the Amount value and presented in the hierarchy nodes so that we can see how much sales we did by product group and subsequently by country as whole. If we drill across we will be able to achieve this but we want to drill down as we have the time characteristics and variances at the columns. and no, we do not want user to drill across the calculation components. This query is used in Integrated Planning for planning purposes integrated with BO and that is the structure of the planning layout we want. "Calculation component" is a infoobject that contains 'sales qty', 'price/unit' and 'sales amount' as master data values.
I have tried exception aggregation on calc component infoobject for 'LAST VALUE'. and it did capture only the Sales Amount value as result for node Calc Components. But the other results node State, country and Region also takes LAST VALUE.. which is not what i want. what i want is esseentially summation of all Sales amount for each calculation components by state, country and region.
                                                   Last Year | Variance   | Current Year |   Jan | Feb | Mar |......
Region X                                              200 (sum of all country's sales amount)
->Country A                                          200 (sum of all states' sales amount)
   -> State Y1                                          80 (sum of all components's sales amount)
       ->Calc Components Z1                    30
          - Sales Qty                                   10
          - Price/Unit                                     3
          - Sales Amount                             30
      ->Calc Components Z2                    50
          - Sales Qty                                     5
          - Price/Unit                                   10
          - Sales Amount                             50
   -> State Y2                                        120
       ->Calc Components Z1                   40
          - Sales Qty                                   10
          - Price/Unit                                     4
          - Sales Amount                             40
      ->Calc Components Z2                    80
          - Sales Qty                                   10
          - Price/Unit                                     8
          - Sales Amount                             80
any help would be appreciated...
eddie

Please try the below steps and I hope it should work for you.
Instead of calculated keyfigures,try to use local formula .Because i think sometimes CKF will not give the expected result if you use exception aggregation (not sure though,but i used only local formulas)
1. Create a first local keyfigure (Say F1)for the calculation and use exception aggreagation as 'Average' and reference characteristics as 'PDU'.
2. Create a second keyfigure ( Say F2) using the first keyfigure(F1) and use exception aggregation as 'Average' and reference characteristics as 'Sales Document', if you need the values based on average of the sales documents and hide the first keyfigure(F1)
I consider Sales document is the first level and PDU is the second level ( i mean lowest level) . Because you need to consider these sequencens as well when you design the exception aggregation.
Likewise you can create nested aggregations based on your requirements.
Please do let me know if it works.
Thanks.

No correct exception when using "average of all values"

Hello all,
I have created a query with different duration days as key figures. The result row is displayed for the main characteristic and in the key figures I have select "Average of all values".
The avergae value is calculated correctly in the result row at the end, but the exception is just take sums of the days into consideration, not the average values. Some values are red because there sum would be red, but just the avergae is displayed.
Is there a way how I can apply exceptions also on avergae values?
Th eBW release is 3.5.
Any help would be great.
Best regards,
Stefan from Munich/Germany

Instead of creating a Formula Key Figure, create a Calculated Key Figure .
In that from the Enhance option select Exception Aggregation as Average of all values.
Now use this Calculated Key figure in your query and for creating exception.

Constant Selections and Exception Aggregation

Hi,
Can You please tell me
1) what is constant selections?
2) what is Exception Aggregations?
Thanks and Regards.
Naresh.

Hi,
example for the use of standard aggregation and exception aggregation for a key figure is a key figure for the non-cumulative value
with non-cumulative values such as warehouse stock, you want to total up the warehouse stock for various articles and warehouses (standard aggregation), but for the month you want to determine the ending inventory (LAST aggregation) (exception aggregation in regard to the time characteristic Calendar Month)
for more info go through the below link
http://help.sap.com/saphelp_nw04/helpdata/EN/d2/e0173f5ff48443e10000000a114084/content.htm
For constant selection go through the belwo link
http://help.sap.com/saphelp_nw70/helpdata/EN/46/91f0f090ea13e8e10000000a155369/content.htm
Regards,
Marasa.

Exception Aggregation takes a lot of time

Hello, guys!
I'm having problems with exception aggregation for some of my key figures in BEX Query Designer.
Well, they are working properly (Summation and Counting), but it takes up to ten minutes for them to calculate, and this is not acceptable for both me and my client.
Without those Exception Aggregations, query runs in a seconds.
Do you know any way to avoid those problems? Maybe it is possible to do something on BW side?
I'd appreciate any advise on this.
Thank you in advance for your help,
Nik.

Nikita,Exception aggregation definitely takes a toll on the performance.There might be a situation where it is aggregation huge number of records with the unique combination of reference characteristic.
You can either try to filter out the data as much as possible after analyzing the data in cube.
Also i can suggest to do a close health check up of your cube with the help of program
SAP_INFOCUBE_DESIGNS
Regards,
AL

Exception Aggregation (Average of all values 0) - Non cumulative KF

Hi Experts,
I am using the Exception Aggregation (Average of all values <> 0) on a Non Cumulative KF. Most of the times i am not getting the desired results but some times it gives me the desired result.
my doubt is whether we can use Exception Aggregation on Non cumulatives?????
Thanks for any help
boobal

Hi,
Non-cumulative valuesare those key figures that are measured in relation to a period in time; that is to say they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so-called exception aggregation.
Example:stock quantities/-values, number of employees, account balances, etc.
Please check this document:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d61b1e95-0501-0010-dfbe-a03970712ef1
Hope this helps.
Regards,
Mona
Edited by: Mona Kapur on Jan 17, 2008 10:45 AM

Scenarios for some of the Exception Aggregation

hello Experts,
Please explain some scenarios for the following Exception Aggregation:
1. Counter (value not equal to zero)
2. Counter (all values)
3. Average (value not equal to zero)
4. Average (weighted with no. of days)
5. Average (weighted with the number of workdays; factory calendar)
Thanks in advance.
Regards
Lavanya.

Hi,
check this link
http://help.sap.com/saphelp_nw70/helpdata/en/82/f2dc37f0f12313e10000009b38f8cf/frameset.htm
hope this helps you
Best regards,
Ramesh.

'Average Weighted with Calendar Days' in Exception Aggregation

Dear specialists,
I have created a query with a lot of calculated keyfigures.
One of my calculated keyfigures shows percentage values.
When I select a calendar day, my report shows correct results
for the percentage values.
But when I execute the report without selecting a calendar day,
I get strange results like 3,21 % instead of 97,49 %.
There is a new functionality with version 7.0, where we can set
Aggregation properties like 'Average Weighted with Calendar Days' .
But when I select this with Ref. characteristic 'calendar day',
my report does not show any value or any result.
Are there any other properties to set in Aggregation or Calculations.
Please give me more information about this issue
regards Osman Akuzun

Hi,
       When you define an Exception aggregation on number of work days. There might be some reference characteristic defined in your Bex.
For exmaple, take a scenario like below. Your BW data is like below
0Employee           StockIssued
XXX                            50
XXX                            10
YYY                           20
YYY                            30
YYY                            40
ZZZ                            50
ZZZ                            100
ZZZ                            30
Suppose the first row which has values like XXX and 50 is not a working day and remaining all are working days then the exception aggregation applied using AV2 on the characteristic 0Employee will be caluclated in your Report as below
For XXX, it will       10/1 = 10 (because only 1 working day for the employee XXX)
For YYY, it will       90/3 = 30 (because all 3 are working days for the employee YYY)
For ZZZ, it will       180/3 = 60 (because all 3 are working days for the employee ZZZ)
This is how the exception aggregation works. Try to see the similar kind of example in your system and try to relate in the same lines explained by me. You can understand.
Regards
Sunil

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

Exception Aggregation (Average) displaying incorrect values after EHP1 Upgr

Hi All,
Exception Aggregation (Average) displaying incorrect values after EHP1 Upgrade in our BW system
We have recently upgraded the system to EHP1. After the upgrade some of the queries where we are using Exception Aggregation (Average) started giving the incorrect values.
Eg. We are displaying three Key Figures KF1, KF2 and KF3 (=KF1 %A KF2) against Store Hierarchy. In KF3 we are using Exception Aggregation (Average) on a characteristic 0PLANT.
There are 14 rows against 0PLANT and out of those 2 rows are blank for KF1, so for KF3. When it is calculating the average of these key figures its dividing the total value by 12 instead of 14 which is not correct in our case. Earlier it was dividing the total by 14.
So in this case 'Average' and "Average of all values <>0" are behaving the same way.
Kindly provide some inputs on this.
Best Regards,
Sachin Verma
+44 7506740018

Hi,
Thanks for viewing the thread. And happy to let you know that the issue was resolved.
The solution was:
Two formulas (local) were created, one including the formula variable with replacement path for ZD1, with exception aggregation on ZD1, and the other with formula variable with replacement path for ZD2, with exception aggregation on ZD2. Both these formulas are hidden.
Another formula (local) was created for u2018time takenu2019 = formula with ZD1 u2013 formula with ZD2, with exception aggregation total on u2018ZDOCNOu2019.
For the second instance, when one requires exception aggregation on records that has multiple values for keys, a nesting of formulas can be done displaying only the ones required.
For e.g. a formula with exception aggregation on say characteristic u2018item no.u2019 can be hidden, and included in another formula for exception aggregation on characteristic u2018document no.u2019. This is a typical case where one can achieve calculation before aggregation for a calculated key figure, formula or a counter.
Hope it might help someone, and saves time and effort for a similar issue posted.
Also would like to keep this thread open for exploring better solutions.
Regards,
Vijay

Exception aggregation for averaging

Similar Messages

Maybe you are looking for