Exception Aggregation on non-Time Characteristic

Hey all,
I am doing exception aggregation on the following scenario:
Cube XYZ:
Doc #; LI #; ALI #; Total Contract Value; Total Potential Value
Doc1; 1; 1; 200,000; 200,000
Doc1; 2; 1; 0; 15,000
Doc1; 2; 2; 0; 15,000
How I want this to work is as follows. I want in the query, whenever the LI appears more than once (repeats), average the Total Contract Value and Total Potential Value.
So let's say I run the query 1 against cube xyz with only Doc # in the Results Area and it pulls out those exact rows, I want it to display as follows:
Doc #; Total Contract Value, Total Potential Value
Doc1; 200,000; 215,000
Would exception aggregation accomplish this? I really need to have both LI # and ALI # in the cube because this keeps the integrity of another key figure that I have in the cube which I want to sum for each Doc #, LI #, ALI # combination, but for the other 2 key figures (Total Current Value, Total Potential Value), I want it to sum in all cases except when there are rows when the Doc # and LI # are alike, to average.
Any help would be appreciated, by the way, Doc # is compounded into the LI # characteristic, but ALI # does not have Doc # and LI # compounded in it. Let me know if I need to change my model for this...
Thanks in advance,
Angel Henriquez

Maybe a solution with virtual key figures is an option?
Please help me out!
Best regards, Hans de Klein

Similar Messages

Exception aggregation on Non-cumulative key figure

Dear experts,
I have a problem. We have an InfoCube in BW in which the Activity Journals are loaded every day. In this Activity Journals it is registered that a Material was listed (available) at a customer (value 0 or 1).
We have a non-cumulative key figure MXW_LISTN with inflow (MXW_LISTI) and outflow (MXW_LISTO). In time this key figure receives +1 or -1 for a customer, material combination.
I want to use MXW_LISTN in the query in a specific way. The key figure on itselve tells me how many listings there are. However, I want to know how many business partners there are with a listing.
I was thinking about an exception aggregation on MXW_LISTN with reference characteristic 0BPARTNER and "Count <> 0". BW however refuses to do so and only lets me do simple aggregations such as AVG, MIN, MAX etc.
Can you think with me and come with an proper solution to count the number of business partners with a listing?
Your help is very much appreciated and rewarded!
Best regards, Hans de Klein

Maybe a solution with virtual key figures is an option?
Please help me out!
Best regards, Hans de Klein

Exceptional aggregation on Non *** KF - Aggregation issue in the Query

Hi Gurus,
Can anyone tell me a solution for the below scenario. I am using BW 3.5 front end.
I have a non cumulative KF coming from my Stock cube and Pricing KF coming from my
Pricing Cube.(Both the cubes are in Multiprovider and my Query is on top of it).
I want to multiply both the KF's to get WSL Value CKF but my query is not at the material level
it is at the Plant level.
So it is behaving like this: for Eg: ( Remember my Qty is Non-*** KF)
               QTY PRC
P1 M1      10     50
P1 M2       0     25
P1 M3      5      20
My WSL val should be 600 but it is giving me 15 * 95 which is way too high.
I have tried out all options of storing the QTY and PRC in two separate CKF and setting the aggregation
as before aggregation and then multiplying them but it din't work.
I also tried to use Exceptional Aggregation but we don't have option of ' TOTAL' as we have in BI 7.0
front end here.
So any other ideas guys. Any responses would be appreciated.
Thanks
Jay.

I dont think you are able to solve this issue on the query level
This type of calculation should be done before agregation and this feature doesnt exist in BI 7.0 any longer. Any kind of exceptional aggregation wont help here
It should be be done either through virtual KF (see below ) or use stock snapshot approach
Key figure QTY*PRC should be virtual key figure. In this case U just need to one cbe (stock quantity) and pick up PRC on the query run time
QTY PRC
P1 M1 10 50
P1 M2 0 25
P1 M3 5 20

Exception aggregation based on two characteristic

Hi Guys
i have enhanced the datasource i.e 2lis_12_vcitm for sales order qty
now i have to get the unique qty based on order no and item no to devide it to get a ratio
how can i do the exception aggregation to take one value based on two characteristics that is order no and item no
Regards
Amiya

hi
Exception aggregation based on 1 characteristics i know very well but my requirement is different i have to get unique data based on two characteristics i.e
order    item   qty
100      10      5
100      20      3
100      10      5
100      10      5
100      20      3
200     10       15
200     10       15
now i want to get 5 for order 100 and item 10
and 3 fro 100 and 20
i think by exception aggregation its not possible is there another way?

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

First and last exception aggregation

From one of the doc, I got the below info:
For FIR, LAS Exception Aggregation,
If being used for cumulative key figures: Completeness of values with respect to reference characteristic necessary.
If the reference charac being used is non time char. then Sorting is done ascending according to key (internal presentation)
Whatdo the above two points mean?
Thanks
Simmi

hi Simmi,
can please point the doc ?
1st point, with respect to reference characteristic, i think it means which characteristic to be used for reference, normally date (time characteristic);
date----
key figure
01.01.2007---- 10
02.01.2007-----20
10.01.2007-----30
then FIR/first will be 10; and LAS/last = 30
2nd point
if reference characteristic is non time characteristic, e.g zcustomer, then sort is done ascending according to key, e.g
zcustomer-key---description
001----
Simmi
002----
Linggam
003----
Prakash
and we have data
zcustomer------key figure
003----
10
001----
25
002----
70
then consider to FIR/LAS, this will be sorted as
zcustomer------key figure
001----
25
002----
70
003----
10
then FIR is 25 and LAS = 10
hope it's clear for you and help.

Exception aggregation

Hello all,
I have a problem with my query, i don't want to aggregate on a characteristic, i've tested many options by creating a formula with my characteritic and tried with several possibilities on exception aggregation but none is working.
If someone can help me.
Thank you by advance.

hello, here my report result:
Division     Material     Qty mouvement        mouvement value     Coût matière standard lot
1000        HB9754      2                               250 EUR                     200EUR
and i would like to obtain :
Division     Material     Qty mouvement        mouvement value     Coût matière standard lot
1000        HB9754      1                              150 EUR                     100EUR
1000        HB9754      1                              100 EUR                     100EUR
If you have more questions don't hesitate.
thanks by advance.

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

Misuse of the exception aggregation

Hi Expert
I have a little particular need which I have of the evil to carry out. I explain you, you certainly already had it.
In my cube I have collect, sold to, orders attached to contracts and a surface of contract like this:
                    Surface
R1     Soldto1     Cmd1     Ctr1     10
R1     Soldto1      Cmd2     Ctr1     10
R1     Soldto1     Cmd3     Ctr1     10
R1     Soldto2     Cmd1     Ctr2     20
In my request, I would wish to have:
R1     Soldto1     10
                     Soldto2     20
R1 (next level aggregation) 30
I use the exception aggregation on the contract (exception average by contract) but I don't succed to have the results expected.
My query sends me the result below:
R1     Soldto1     30
                     Soldto2     20
R1 (next level aggregation) 50
How then I to solve this problem? Please help
Best regrads
Eric

Hi Eric,
For your expected result, I think you should use exception aggregation Average with reference characteristic Cmd
as it is the one which differs for the three 10 values.
With this setting, R1 level should also be 30 as you expect.
If you use "Ctr" as reference characteristic, then the three Cmds get aggregated (summation) for Ctr1, that's why you get 30
like "R1 Soldto1 30".
Hope this helps.
Regards,
Patricia

Non Cumulative KF VS Normal KF with exception aggregation

What is the purpose that is served by "non-cumulative key figures" and is not served by "normal key figures with exception aggregation"?
Inflow and Outflow can also be mapped into a single key figure at update rules level.
Why un-necessary complications like two additional KFs and marker update etc?
Why can't we store actual inventory value on daily basis in a NORMAL key figure with exception aggregation on time?
Also, I heard that data amount will be huge if you don't use non-cumulative key figure. I am not able to understand why?
I HAVE ALREADY GONE THROUGH ALL THE HELP DOCUMENTATION AND ALL THE PREVIOUS THREADS. I DID NOT GET ANSWER TO THESE QUESTIONS.
THANKS IN ADVANCE,
Anup

Anup,
Q1: Why can we not store the actual inventory against the person -
In this case you will end up storing day wise information of stock for the person / material - this will lead to increase of your data volumes depending on the scenario.
Example :
Day Level stock only
Record Structure :
Material | End of day snapshot Stock| date
pipe | 100|20.2.2008
pipe|100|21.02.2008
pipe|100|22.02.2008
pipe|80|23.02.2008
Here you can notice that the material pipe has been sold on 23.03.3008 and no sale has happened previously - however since your extractor will give you end of day stock for all materials you will get 2 additional records
In an opening and closing stock scenario
Opening stock
Marker|
pipe|100|20.02.2008
opening stock|closing stock
pipe|100|100
pipe|100|100
pipe|100|80
Here the values will get overwritten and compared with the marker and calculate that the stock is 80 or 100 depending on the date. I am not able to give a proper example but hope I have addressed it in part.
Also it is a Non *** KF because if you look at stock for pipe over 3 days you will get 300 in the first scenario - this is wrong
and for the next scenario with opening and closing stock
it will ideally be
100 ( your marker) -100100-100100-100+80 = 80
this calculation is done at runtime and gives the right output.
In the other case you can check stock only on a date basis and with the assumption that the stock data is current for that day.
Hope it addresses youor question.
Arun
Day 1:

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

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 '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 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.

What is Exception Aggregation?

Hi,
What is the use of Exception Aggregation? In which scenarios it is used?
Regards,
Rajesh

Hi......
Exception Aggregation is mainly use for non cumulative keyfigure......
Suppose in a report u want to see total sales and also Product wise sell............
Then u will put Product as Aggregation Reference Characteristic......And in Exception Aggregation u put Summation............Then in the Report it will show u Product wise sell.........u can also make this settings in query designer.......
Check this...........
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bi/exception%252baggregation%252bin%252bqueries
Search in Forum and help.sap.com.........u will get lots of answers.........
Regards,
Debjani.....

Exception Aggregation on non-Time Characteristic

Similar Messages

Maybe you are looking for