Exception Aggregation

[Former Member]

Hi,Experts

what is the difference b/w standard aggregation and Exception Aggregation?

and what are Cumulative & Non-Cumulative KeyFigures?

please Give me a Scenarios in which situation we wold go for Expetion Aggregation

and in which situation we wold go for Standard Aggregation.

Please Clarify my dobt

Thanks in Advance,

PRIYA KODALI.

[llamitll · Accepted solution]

Aggregation semantically means collecting together into a mass or sum. So when we say standard aggregation, we are summing it up, as SAP BW by default gives you SUM option under the field Aggregation.

Just to give you an example

Customer No. Product code Month Quantity Sold

100001 1001 01.2011 500

100001 1001 02.2011 400

100001 1001 03.2011 300

100001 1002 01.2011 10

100001 1002 02.2011 20

100001 1002 03.2011 30

So if we just want to keep our focus on Product code and quantity sold, we remove the characteristics month and if our aggregation and exception aggregation settings reflect u201CSumu201D or u201CSummationu201D as the options selected. Then you will get the data aggregated like below which is nothing but summation.

Customer No. Product code Quantity Sold

100001 1001 1200

100001 1002 60

Now in Exception aggregation, let me make it clear by taking the example of a conglomerate group having many companies, wherein we are interested in data of one company, whose department wise employee strength we want to see.

Company Department Cal Year No. Of Employees

ABC Finance 2009 100

ABC Finance 2010 150

ABC Finance 2011 200

ABC HR 2009 50

ABC HR 2010 60

ABC HR 2011 70

Now here in this example if you just want to focus on department and number of employees and you remove Cal year from the column from the report maintaining the same settings of u201CSumu201D and u201Csummationu201D in aggregation and exception aggregation field, we will get an erroneous result like below.

Company Department No. Of Employees

ABC Finance 450

ABC HR 180

But what has happened is that the employee strength is 200 at the end of FY 2011 in finance deptt. So when we cannot aggregate or combine together the value of key figures for different characteristics, we use exception aggregation and select value for the field/selection u201CException Aggregationu201D as Last Value. Then the output will be like below

Company Department No. Of Employees

ABC Finance 200

ABC HR 70

Since the exception aggregation needs to be done with reference to some characteristics (generally time char) so we will use Calendar year as the reference Characteristics.

Now difference between cumulative and non cumulative KF is only of the things/objects which can or cannot be accumulated over time. Eg. Quantity sold can be cumulative as it can be accumulated whereas No. Of Employees in the above context cant be.

Further Aggregation and Exception Aggregation is for the purpose of BeX reporting whereas Cumulative/Non-cumulative is from the point of storage in database.

[former_member205400 · Accepted solution]

I was just doing some testing ... on aggregation points

I had a calculated key fig and when the aggregation is "std" then it works fine and my result is 1, but when I change it to "counter for all detailed values that are not zero, null, or error" then I get 0.

I have to mention that my ref char is a 'line item dim'.

When I change my ref char to NOT be a line item dim it seems to work fine.

Is this a bug? Shouldn't ir continue to work fine?

Mike

[Former Member · Accepted solution]

Excellent example regarding Standard and Exception Aggregation! Thanks Amit!

[former_member182467 · Accepted solution]

Wow Abhishek,

Awesome example to explain exception aggregation and non-cumulative and cumulative KF. I love it.

Cheers

DR

[Former Member]

standard aggregation - sum up the value dont have depend on any char

exception aggregate - sum up the value depending on time char..

ex - say i have 5 depot in my company from 2005 year and a new depot AB is introduced..

if i run the query for AB depot for year 2007 it will fetch me no appilicable data - if standard aggregate is used

In case of excemption aggreagte it will fetch you value zero.

Cummulative key figure - will give aggregate value in meaning ful way

Non cummulative - say at run time i need to calculate from value with some reference (marker concept)

ex- calculating closing stock = receipt - dispactches - at runtime in report

let me if any doubt will try to clarify it further

[Former Member]

Standard Aggregation : aggregation functions like summation average, etc. e.g. Monthly sales : Normal Summation will give total sales

Exception Aggregation: Where in normal summation would not yield correct result. aggrgation is done with reference to a external char. (mostly time char.) e.g. Yearly Population: Normal summation will not give correct result. We use exception aggregation as Last Value and year as reference.

refer below link for example on exception aggregation:

http://help.sap.com/saphelp_nw04/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm

Non Cumulative KF: These kinds of key figures are not summaized (unlike sales, etc); examples are head count, inventory amount; these are always in relation to a point in time; for example we will ask how many employees we had as of last quarter. We don't add up the head count.

[former_member182343]

This message was moderated.

[ravi_chandra3]

This message was moderated.