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?

Similar Messages

Regarding exception aggregation based on 2 infobjects

Hi All,
I have a report in which I have to use Exception aggregation based on two Infoobjects.
How we can do it ?
I have tried using nested aggregation but its not working.
Example:
I have three Infoobject :
0Material
0Sold_To
ZSalesRep (Sales representative of Sold to)
In Report:
Rows section, I will have only ZSalesRep Infoobject.
Column Section (i.e. the Keyfigures) I will have one keyfigure which should be calculated based on 0Sold_to and 0Material.
Any inputs will be helpful.
Thank you.
Vamsi.

Hi,
I think exception aggregation should work in your scenario, first you get the total with reference to material and then put that key figure in reference to sold to party.
Just check the below article for more information,
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d08b56a8-daf5-2e10-2397-904d6aeb55c2?QuickLink=index&overridelayout=true]
Regards,
Durgesh.

Exception Reporting based on a characteristic of type DATE

Hi Friends,
I am new to this community. Please help me in solving the below problem about exception.
There is an infoobject 0CSM_PLDA (Planned closed date). It is an charactesitic of data type 'DATE'. And my requirement is that for an infoobject 0CSM_PLDA <b>I have to create an alert based on difference between SYSDAT and 0CSM_PLDA :</b>
Good - < 5 days
Medium between 5 and 2 days
Bad <1 day
So please tell me
1. How to find out the difference between SYSDAT and 0CSM_PLDA ? Where does Sysdat is avaialble in BW?
2. 0CSM_PLDA is a characteristic of type DATE and as you know Exception generally supports keyfigure...then tell me how to solve this?
Please answer in detail. Thanks----Sasi.<b></b>

Hi Stefan,
Still I couldn't find the solution.
0CRM_PLDA is a characteristic of type DATE. And SYSDAT we can assume it as a characteristic of type DATE.
How can you find out the difference between two characteristic of type DATE. In formula, its possible to perform calculations only on keyfigures. So finding the difference is the complex one for me.
Even I tried with formula replacement for an 0crm_plda. Its not helpful.
please guide me in solving the problem.
Thanks,
Sasi

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

Exception aggregation doesn't work correctly

Hi,
Here we have a problem about exception aggregation, we created two queries. One is based on the
InfoCube, another is based on the DSO.
Both queries have the same definiation. And the data of the InfoCube is from the DSO.
In the query definition we created a formula and in this formula we used a exception aggregation.
For example, we used count all value <> 0 and reference to city in exception aggregation to count
all city which sales value above certain value.
We got the different result from these two queries.
The result in the DSO is what we neend.
Can you tell me why I got the different result?
Our system information is:
SAP NetWeaver 2004s
SAP_ABA     700     0009     SAPKA70009     Cross-Application Component
SAP_BASIS     700     0009     SAPKB70009     SAP Basis Component
PI_BASIS     2005_1_700     0009     SAPKIPYJ79     PI_BASIS 2005_1_700
SAP_BW     700     0009     SAPKW70009     SAP NetWeaver BI 7.0
BI_CONT     703     0000          -     Business Intelligence Content
Thanks

Jin,
Ideally one way to find out if exception aggregation is working fine is to drill down based on the exception aggregation characteristic and see if the formula is being calculated right...
Arun

Problem in Nested Exception Aggregation

Hi Experts,
Can you please give me an idea of how & Steps to do the nested exception aggregation based on the 3 to 4 characteristic and agregate the volume for 1 key figure,
Thanks Regards
Dolly.

Hi AL,
here is my requirement what i have been asked to get this output result.
i have keyfigures KF1, KF2 and total KF.
three characteristics dist,inch,load.
dist-inch-load--KF1-KF2-Total KF
5---A--010-0-----10=10
5---A--120-20----20+10=30
10--B---050-0-----50
12--C---160-60----60
13--D---270-70----70
14--E---080-0-----80
15--E---120-20----20+80=100
15--E---230-30----302080=130
KF1 is the initial volume coming from the file directily.based on this keyfigure i have to calculate KF2,Total KF.
In order to calcuate KF2 and Total KF i have some conditions.which are mentioned below;
KF2---> if load=0 then KF2=0 elseif load>0 then KF2=KF1 ;
Total KF--->if load=0 then Total KF=KF2KF1 elseif load>0 then KF2=KF2KF1
How to achieve this dynamic summation.Do i have to do nested exception aggregation based on the above three characteristics. what would be the open options.please do help me.

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

Exception aggregation with two characteristics

hi:
I need get the average value of a KF, based on the unique combinations of two characteristics.
material and color are two characteristics.
The base data is
m1 c1 $
m1 c2 $
m1 c3 $
m2 c4 $
m2 c1 $
Now there is 5 unique combination of mtl and color. but when I average the $ it is averaging it with dividing the $ sum by 4 as there is only 4 unique colors (with except.aggr. for color char). How can I make it to consider all the unique combinations of mtl and color and get the average even with duplicate colors?
thanks.

What is going to be record count for unique combination?
If its going to be 1 then you can create a pre query which will give only unique combination (record count =1 using condition), further sum of those record counts will give you the total unique combinations.
Further it can be used for averaging purpose w/o using exception aggregation.
Hope it helps.
Abhijeet

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.

FBL5 FIAR - exception aggregation - count customers with open items at key

Hello gurus,
I have read the information about counting all values in reference to a characteristic. I manage to count how many customers have a FIAR open item 'billing status' = Open in my FIAR cube.
Now I am asked to replicate transaction FBL5 of R3. This transaction will give you open items at a given key date by adding
the items with
A) Item status = 'O' and posting date <= key date
and the items with
B) Item status = 'C' and posting date < =key date and clearing date > key date.
I calculate the net value by creating 2 restricted key figures and then adding them in a CKF.
But for counting I have a problem. I can count how many customer make up the open items (case A)
and how many customers makeup items that where cleared between key date and today.(case B).
But I cannot sum the two numbers as there might be customers that are counted in both cases.
For example I have 4 customers that correspond to case A : 1000 1011, 1012 and 1014
And I have 3 customers that correspond to case B 1000 , 1011 and 1013
I would like to get 5 as the number of customers that verify either case A or case B (or both).
Is there a way to do this with the exception 'aggregation 'and 'count all values' property of CKF ?
Claudio

Hi,
The logic given in the above post may be a bit confusing to you. Check out this explanation and try to understand what I mean.
Posting Date - PD
Key Date - KD
Clearing Date - CD
PD--KD--
CD
-O(Status)-C--O-----C
-5107-----8
Let me explain the above table.
Between PD & KD there are 5 count with status'O' and 10 counts with status 'C'.
Between KD & CD there are c counts with status 'O' & 8 counts with status 'C'.
This means 5 with status 'C' becomes 7 between KD & CD.
Similarly, 10 status with 'O' becomes 8.
The logic I am trying to say is..
If you don't want to get counts with status 'C'(repeated) as I understood) 7-5 = 2. Show this 2 as count for status 'C' between KD & CD.
So the table will become like this now.
PD--KD--
CD
-O(Status)-C--O-----C
-5102(7)---2(8).
In braces shown are the total with status 'O'/'C' for the dates.
I hope this will solve your problem.
Message was edited by: AVR - IGA

Exception aggregation in one CKF causing problem in Result row of other CKF

Here is my scenario in 3.5x BW:
I have a CKF A which has exception aggregation (to select maximum value) based on a reference characteristic..
Now this CKF A is used in another CKF B and a third CKF C is being calculated based on CKF B. SInce I am using exception aggregation in CKF A, CKF B and C had to be set to be calculated 'after aggregation'.
Formula for CKF C = 100*B/ D (D is another constant CKF, with value 1 for each row).
Now my requirement is that the result row of CKF C should be calculated using the same formula on result row of B and D. This was working when I was calculating A without exception aggregation. But now I need to use exception aggregation aswell as I want the result of C = 100 * Sum(B)/ Sum(D).
I have tried the alternative of using a Formula selection (with formula collision - Result from this Formula)instead of CKF for calculating 'C', but didnot find any success in getting result row of C as per my requirement.
Any suggestions in resolving the issue will be higly appreciated..
Thanks
Shikha

you have created a calculated key figure A in your query, and in the properties of this calculated key figure you have defined the exception aggregation right?
so you can create a second calculated key figure (say A') with the same definition as ckf A, but you don't put any exception aggregation in it. then you need to create a second calculated key figure (say B') to replace the calculated key figure B, and use ckf B' in this new ckf.
when you use now the calculated key figure B' in the formula of ckf C, it should be correct as you use ckf A' as basis, which has no aggregation...
quite straight forward, no?
M.

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.

Query Designer: Calculate a % based on two other totals

Hi Gurus,
Here is the scenario of my query:
A     B     C     D     E
2      3     6     4     150%
1      2     2     4     50%
2      2     4     8     50%
1      1     1     10   10%
6      8     13    26   50%
Column C is calulated by AB and I am able to get the total 13 instead of 48 (68) by using the "Total" calculation function.
The problem is about the Total of Column E. It is a % based on columns C versus D. There's no problem for individual results, but for the total I cannot get the 50% because my query calculates the total result comparing 48 (6*8) Vs 26.
If I also use the Total function for the E Column, what it shows is an addition of all the individual results, so 260%.
I can't find the way to get the Total 50% that takes the "Total" function of Column C and Column D.
Please, any idea so solve this scenario?
Many thanks!!
Regards,
Jordi

Hi,
The "Calculate Result As" is a Display option. That value is not considered in the calculations, only for display.
You may try "Exception Aggregation" , 'Total' for Column C with Ref Characteristic being the Char at the lowest level of which you see the data and try.
For eg: you can to calculate A x B for Materials, but at all levels higher than material you want A1 x B1 + A2 x B2 + .....
Then you create CKF/Formula C = A x B with Exp Aggregation, Total, Ref Char = Material.

Explain Exception Aggregation and Aggregation?

Please search forums
Hi eXPERTS,
While creating Keyfigure infoobject there is an additional option called
Aggregation and it has Exception Aggregation plz explain abt this topics briefly.
Thank u,
Edited by: Pravender on May 21, 2010 1:19 PM

Hi,
there is a slight difference in between them.
When you select the Aggregation as Minimum then it will pass only the minimum values into the target.
Where as Exception Aggregation will be always based on some ref Characteristic, in this if you select the option as Minimum based on 0CALDAY Characteristic then it will show you the minimum values in the report but not in the target based upon the 0CALDAY Characteristic..
Aggregation will fetches the data into cube from PSA and exception aggr will fetches the data into report from cube.
just go through the example which was explained by some of our techie..
For Ex in PSA u have data like dis.
01.01.2007 1000
01.01.2007 2000 it will take only the minimum value into cube
In case if you have many records based on that particular date then it wont do the aggregation. Since you have chosen the ref char as 0CALDAY, there might be lot of records which have generated on the same day, so when you select this option then it wont do the aggregation and further it will place X in that area.
assign points if it helps..
regards,
ashok

Exception aggregation based on two characteristic

Similar Messages

Maybe you are looking for