Zero-Elimination And Exception Aggregation

Hi experts,
I'd like to compress a cube with the option of zero-elimination. Online help says: "Zero-elimination is only allowed for InfoCubes that contain key figures with aggregation behavior u2018SUMu2019 exclusively." (http://help.sap.com/saphelp_nw70/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/frameset.htm)
The key figures of the cube I like to compress all have aggregation = SUM but some of the key figures have exception aggregation <> SUM. Will the data of a cube still be fine after that compression?
Thank you for your ideas!
Volker

Dear Andrei Bushkevich and Swapnil Dharia,
thank you for your response! In my question there is a double ** wich originally stands for the sign of "NOT EQUAL".
So the sentence is:
"The key figures of the cube I like to compress all have aggregation = SUM but some of the key figures have exception aggregation NOT EQUAL SUM."
@Andrei Bushkevich
No that I've corrected the text - are you still sure that I can do the compression with zero-elimination?
Best Regards,
Volker

Similar Messages

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.

What is standard and exception aggregation?

What is standard and exception aggregation?

hi there ,
check out this link for scenarios of exception aggregation :
http://help.sap.com/saphelp_nw04/helpdata/EN/d2/e0173f5ff48443e10000000a114084/content.htm
regards,
Supriya

Formula Variable and Exception Aggregation

Hello
Please can you explain me how this works.
There is formula variable created on a change date.(Replacement Path) with replace with Key.
Then this formula variable is put in a formula as NODIM(Formula Var) and the exception aggregation is set as Total with Ref Char selected on the same date(Change Date).
Now this is coming up with values like 2202374. If i remove the exception aggregation then i get an X in the values. If i then include the change date in the rows i get the date.
Please can anyone let me know how this would be working. Effort Appreciated.
Thanks

Here is a scenario that might fit:
Formula is trying to show the latest change date without adding it as a drill down. The only discrepancy is that the exception aggregation would need to be set to maximum value instead of Total.

How important are Aggregation and Exceptional aggregation

Hai All,
When defining a key figure, we define the aggregations, Aggregation (Min, Max etc.)and Exceptional Aggreagtion (Min, Max etc.).
How important are these. For example,for delivery dates, I know that thats the way the result row is calculated, either to display the min or max value. But except this, is there any other effect such as if there are more than one delivery date then defining Min. would take the earliest delivery date???
Please correct me if I am wrong. But I am just trying to find out the complete use of that definition of aggregation when creating key figures.
Thanks.

there are diffferent settings for keyfigure aggreation and bex display settings
rsa1 > change kf > aggregation tab:
this is the one which determince if the kf is a cumulative or non-cumulative.
rsa1 > change kf > additional properties :
here are the bex display settings.
Regards,
BWer
Assign points if helpful.

How to display top Position Level using conditions / Exception Aggregation

Hello,
I have the following problem where I need to list out the row with the highest POSITION LEVEL (with reference to BUSINESS PARTNER). I have tried out all possibilities including Conditions and Exception Aggregation (MAX) but nothing seems to work. Conditions work to an extent i.e. it shows the top position level but unfortunately for the entire query result i.e. only one row is displayed in the result (the first row to satisfy the condition) instead of all the rows for each Business Partner. POSITION LEVEL is a KEY FIGURE value. It also exists as a CHARACTERISTIC under a diferent name in the cube. How can I solve this? Pls help.
This is how the report looks at present...
First Name     Last Name     Business Partner Nr.     Date of Birth     Postalcode     City     Position Level
Testfallini     Enzweiler     3000000020     21.10.1990     63674     New York     1
Tamara     Dimmer     3000179274     10.09.1987     54689     Chicago     2
Tamara     Dimmer     3000179274     10.09.1987     54689     Chicago     1
Tamara     Dimmer     3000179274     10.09.1987     54689     Chicago     1
Thu-Ha     Tran     3000069951     25.12.1988     93047     Atlanta     2
Thu-Ha     Tran     3000069951     25.12.1988     93047     Atlanta     1
This is how the report looks when I use conditions...
First Name     Last Name     Business Partner Nr.     Date of Birth     Postalcode     City     Position Level
Tamara     Dimmer     3000179274     10.09.1987     54689     Chicago     2
This is how the report should look...
First Name     Last Name     Business Partner Nr.     Date of Birth     Postalcode     City     Position Level
Testfallini     Enzweiler     3000000020     21.10.1990     63674     New York     1
Tamara     Dimmer     3000179274     10.09.1987     54689     Chicago     2
Thu-Ha     Tran     3000069951     25.12.1988     93047     Atlanta     2
Thanks in advance,
SD

Hi Sebastian,
I thought you need to display all the records with the highest position level at top. But now I realize your requirement.
It should only display only the maximum position level for each level.
You can try using the Condition for the position level KF, with Top N operator and value = '1'
And then go to char assignement tab in the exception and select Most Detail Chars along Rows/Individual Chars. and combinations for the required combination of Chars.
[List Condition for All Characteristics in Drilldown Independent|http://help.sap.com/saphelp_nw04/helpdata/en/86/dfc405ab60524ea0d3e89db15fb2e7/content.htm]
[Defining Conditions |http://help.sap.com/saphelp_nw04/helpdata/en/73/702e39074dc93de10000000a114084/frameset.htm]
Hope this helps....
Rgs,
Ravikanth.

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 and Aggregates

Hello,
I have a Query (Material Stocks movements) with one key figure with exception aggregation by 0material. I build an aggregate to run this query faster, but I notice that with exception aggregation the query doesn't read the aggregate. When I run this query without exception aggregation, my query read the aggregate.
Is it possible to run this query with exception aggregation on aggregates?
Thanks,
Fabio.

Hi Brian,
I already checked in RSRT + Debug, When you run RSRT + Debug appears both, the aggregate and Infocube, but if you see in SM50 the process read just the Infocube. My aggregate has all characteristcs from my query, including the characteristic that I'm using like exception aggregation.
Thanks
Fabio.

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

What is a Zero elimination in infocube compression?

Can any body please explain me in detail what is a Zero elimination in infocube compression? when and why we need to switch this on? i appreciate your help. Thank you.

Hi Rafi,
If you want to avoid the InfoCube containing entries whose key figures are zero values (in reverse posting for example) you can run a zero-elimination at the same time as the compression. In this case, the entries where all key figures are equal to 0 are deleted from the fact table.
Zero-elimination is permitted only for InfoCubes, where key figures with the aggregation behavior SUM appear exclusively. In particular, you are not permitted to run zero-elimination with non-cumulative values.
More info at:
http://help.sap.com/saphelp_nw04/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/content.htm
Hope it Helps
Srini

Zero elimination failing

Hi,
We are compressing a cube with zero elimination. All KFs are cumulatives with aggregation behavior of SUM.
For some reason certain rows for which all KFs are zero are not being eliminated from the E fact table. I have looked back over past requests and do not see any compression failures.
Has anyone ever encountered this issue? Any theories on why the zero elimination isn't working? Better yet, any recommendations for how these records can be eliminated from the E table now that the data have already been compressed?
Thanks,
Bob

All,
It appears that the SID_0CALMONTH issue was a red herring. I checked the job log for a recent compression and SID_0CALMONTH is not being taken into account when flagging records for zero elimination. Here's a snippet of the PL-SQL:
CREATE OR REPLACE TRIGGER "/BI0/0500002603" AFTER
UPDATE ON "/BIC/EBOF_C30" FOR EACH ROW WHEN (
NEW."CML_OR_QTY" = 0 AND   NEW."DLV_QTY" = 0 AND
NEW."GR_QTY" = 0 AND   NEW."NET_PRICE" = 0 AND
NEW."NET_VALUE" = 0 AND   NEW."PCONF_QTY" = 0 AND
NEW."/BIC/BACTSHIP" = 0 AND
NEW."/BIC/BCOUNTER" = 0 AND
NEW."/BIC/BDISCPQTY" = 0 AND   NEW."/BIC/BMOQ" =
0 AND   NEW."/BIC/BMRA_QTY" = 0 AND
NEW."/BIC/BSHIP_QTY" = 0 AND
NEW."/BIC/BTGTSHIP" = 0 AND
NEW."/BIC/BTKILLQTY" = 0 AND
NEW."/BIC/BTORDQTY" = 0 ) BEGIN INSERT INTO
"/BI0/0100000097" VALUES ( :NEW.ROWID ,
:NEW."KEY_BOF_C30P" ); END;
Also, I looked back at the notes mentioned previously, and it is possible that we could have been impacted in the past by the MERGE statement issue (Notes 61370 and 639253), although we are now at a SP level where this should no longer be an issue.
Finally, the only recent examples of this problem I can find have been traced to cases where compression was run manually without zero compression being specified. So, those are operator error.
Bottom line: While we may have suffered in the past from an issue SAP has subsequently corrected, there is no evidence of any previously undetected problems with zero elimination.
Bob

Before and After Aggregation

Hi Gurus'
Where can we find the options "Before Aggregation" and "After Aggregation"?What is the basic use of these aggregations?Why we should not use the option called Before Aggregation in a Multiprovider?
Could any one please let me know the above..
Thanks!
James

Hi James,
Aggregation
This function is only available for formulas and calculated key figures.
You can make settings for aggregation and calculation time (for the detail level of the calculated key figure or formula) here. By default, the data is first aggregated to the display level; the formula is then calculated (= standard aggregation). The exception aggregation setting allows the formula to be calculated before aggregation using a reference characteristic, and to be then aggregated with the exception aggregation.
You can select the following settings in the Exception Aggregation field.
●      Use Standard Aggregation: You use this setting to specify that aggregation is to take place before calculating the formula. Therefore, you do not use exception aggregation.
●      Sum
●      Maximum
●      Minimum
●      Exception If More Than One Record Occurs
●      Exception If More Than One Value Occurs
●      Exception If More Than One Value <> 0 Occurs
●      Average of All Values
●      Average of All Values <> 0
●      Average Weighted with Calendar Days
●      Average Weighted with Working Days
You can specify the ID of the factory calendar in Customizing. For more information see the SAP Reference IMG ® SAP Customizing Implementation Guide ® SAP NetWeaver ® Business Intelligence ® Settings for Reporting and Analysis ® General Settings for Reporting and Analysis Set F4 Help and Hierarchies for Time Characteristics/OLAP Settings.
●      Counter for All Detailed Values
●      Counter for All Detailed Values That Are Not Zero, Null, or Error
●      First Value
●      Last Value
●      Standard Deviation
●      Variance
If you use exception aggregation, you must select a characteristic from the Reference Characteristic field, using which the system can calculate the formula before aggregation. In the Reference Characteristic field, you can select from all characteristics that are available in the InfoProvider.
For more information about the setting for exception aggregation, see the documentation for InfoObject maintenance under Tab Page: Aggregation.
Calculate After Aggregation: This field is only displayed for calculated key figures; it is not displayed for formulas. It is used for display and stipulates that the formula of the calculated key figure is calculated after aggregation. If you use calculated key figures that you defined in SAP BW 3.5, you can use this field to specify whether the formula is to be calculated before or after aggregation.
Calculating before aggregation results in poor performance because the database reads the data at the most detailed level and the formula is calculated for every record. In formula calculations, often the single record information for just one or two specific characteristics is required; the remaining data from the InfoProvider can be aggregated.
We recommend that you control the calculation level using an exception aggregation with the corresponding reference characteristic. If you require multiple exception aggregations or reference characteristics, you can nest formulas and calculated key figures in one another and specify an exception aggregation for each formula or calculated key figure.
For more information,
Examples of Exception Aggregation Last Value (LAS) and Average (AV0)
Tab Page: Aggregation
Hope it Helps
Srini

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

How to find the value of date char used as exception aggregation reference

Hi BI Gurus,
On a BEx report I need to list three things by material:
1)   the open (not yet delivered) Purchase Order quantities
2)   the PO quantity to be delivered next and
3)   the date that belongs to the next delivery
The model supports these data i.e. for each material I can list all open quantities by Purchase Order / Item / Schedule line and the scheduled delivery dates are also available as a characteristic.
Determining 1) is easy as the drilldown is fixed (materials only) the open quantities get summarized for all PO-s belonging to the materials.
To determine 2) I used a Calculated KF simply including KF 1) =Open PO Qty in the definition and setting Exception Aggregation (first value) with a reference char of the delivery date. This gives back the Open PO Quantity to be delivered first.
My question is about how to determine the 3rd value (actually this is not a KPI but a characteristic value). In other words, for each materials I would need to determine the first among all of the possible delivery date char values of the open PO Items / schedule lines. This is the date the quantity shown in the 2nd KPI will be delivered on.
Does anybody have an idea how to approach this issue?
Thanks for you help in advance,
Attila

Hi Olivier,
Thanks for your suggestion. I got a bit closer with the replacement path formula variable and the CKF. I tried to apply the same logic of KPI 2) but for some reason it did not work. Actually, it delivers the right value but only when 0SCL_DELDAT (Scheduled delivery date) is in the drilldown But what I need is the first delivery date by Material only, and without this 0SCL_DELDAT drilldown.
Any other ideas?
Thanks and bye,
Attila

How to find the list of Queries/Reports which are using Exceptional Aggregation in SAP BI?

Hi All,
We are interested to know how to find the list of Queries/ Reports which are using Exceptional aggregation in SAP BI.
Please let us know is there any table's to check the list of reports using Exceptional Aggregation in SAP BI.

Hi,
Here you go..
1) Go to table RSZCALC and get list of ELTUID where AGGREXC is not INITIAL and AGGRCHA is not initial; now you get only exception aggregation set based on some chars. Also you can further add STEPNR = 1 since your intention is just to get query name , not the calculation details; this will reduce number of entries to lookup and save DB time for next steps.
Here you will get list of exception aggregation UUID numbers from which you can get properties from RSZELTDIR.
2) Pass list of RSZCALC-ELTUID to table RSZELTXREF - TELTUID and get list of RSZELTXREF -SELTUID - this table stores query to it's elements maping kind.
3) Now again pass RSZELTXREF - SELTUID into same table but into different field RSZELTZREF - TELTUID and get RSZELTXREF - SELTUID
This step you get query reference sheet or column or query general UUID for next step.
4) Pass list of RSZELTXREF - SELTUID into RSZELTDIR - ELTUID with DEFTP as 'REP'. Now you get list of query names in RSZELTDIR - MAPNAME and description in TXTLG.
Note: you can also get the reference chars used for exception aggregation from RSZCALC - AGGRCHA field.
Hope this helps.
Please keep in mind, it might take more time depends on how many query elements you have in the system...
Comments added for better DB performance by: Arun Thangaraj

Zero-Elimination And Exception Aggregation

Similar Messages

Maybe you are looking for