cancel
Showing results for 
Search instead for 
Did you mean: 

Exception Aggregation

Former Member
0 Kudos

Guys,

I have a query in which the calculated KFs were using before aggregation. After upgrade to 2004s, when i execute the query it gives me a warning "Time of calculation 'Before Aggregation' is obsolete"

I read a few notes and found out I have to use exception aggregation now. Which selection should i be making in the drop down under exception aggregation and what is the calculation after aggregation for?

Thanks in advance.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

It is a simple warning (not error) message that if the cube over which the query built is having any aggregates and that is not aggregated then as per the warning it won't fetch for you the refreshed data rather it will go to aggregates (as per OLAP manipulation) and so there may be a data mismatch.

I guess there is no relationship between exception aggregation of keyfigures. Can you share me the note number so that i can have a look. As per my understanding The purpose of Exception aggrgation for a particular key figure is that if you don't want to sum up in the query result instead you need the count/max/min of the rows. Accordingly you have to select the options.

Hope this is clear. Any ways can you let me know the note number.

Vijay

Former Member
0 Kudos

These are the two warnings I get: the first one is a system error message which kicks me out of BW and the second one is just a warning but the warning suggests that I use exception aggregation and the cube doesnt have any aggregates...

System error in program SAPLRRI2 and form SPDEP_SETZEN-06- (see long text)

Message no. BRAIN299

Diagnosis

This internal error is an intended termination resulting from a program

state that is not permitted.

Procedure

Analyze the situation and inform SAP.

If the termination occurred when you executed a query or Web template,

or during interaction in the planning modeler, and if you can reproduce

this termination, record a trace (transaction RSTT).

For more information about recording a trace, see the documentation for

the trace tool environment as well as SAP Note 899572.

(This is due to some hierarchy used in a query)

Time of calculation 'Before Aggregation' is obsolete

Message no. BRAIN447

Diagnosis

The calculation time is set before aggregation for the key figure Active

Status Counter. This setting is obsolete and must no longer be used.

In some situations, this calculation time is not defined. Therefore, an

aggregation can take place when the data is loaded. The compression of

an InfoCube is also an aggregation that uses the request ID. This is why

a key figure can produce different results before and after compression.

System Response

Procedure

Use instead the Exception Aggregation function for calculated key

figures and formulas. You achieve an exception aggregation across

multiple characteristics by using the output formula in another formula

and then setting a further exception aggregation.

Procedure for System Administration

(This is a warning and I want to eliminate this warning by design and not using RSRT... which functionality in 2004s workins like before aggregation...

Former Member
0 Kudos

1)Brain 299 is due to the Hiearchy error.

Are you on SP-09??

Might want to check this Note 945895 - RSCRM:Empty filters results in dump.

TO cross check remove the hiearchy and execute the query.

2)Exception Aggregation Brain 447 error

Follow the Note 922727 - Content BI: Calculated key figures.

Scenarios for Exception aggregation-

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm">http://help.sap.com/saphelp_nw04/helpdata/en/d2/e0173f5ff48443e10000000a114084/content.htm</a>

Hope it Helps

Chetan

@CP..

Former Member
0 Kudos

If I am using Before Aggregation, which drop menu itme under exception aggregation should i select?

Former Member
0 Kudos

It depends if its non-cumulative KF then you may have to chose "LAST VALUE" from drop down.

<b>Example of the difference between non-cumulative and cumulative key figures:</b>

<b>Sales volume (cumulative value): </b>

Sales volume 01.20 + sales volume 01.21 + sales volume 01.23 gives the total sales volume for these three days.

<b>Warehouse stock (non-cumulative key figure):</b>

Stock 01.20 + stock 01.21 + stock 01.23 does not give the total stock for these three days.

Example - Inventory controlling

Check key figure= 0VALSTCKVAL

Aggregation = SUM

Exception Aggregation = Last value

Hope it Helps

Chetan

@CP..

Former Member
0 Kudos

Basically, the old query was using an enhanced CKF which had its aggregation set to (Time of Calculation - Before Aggregation)...

The hierarchy is not causing the problem... its something to do with aggregation.

This CKF is using the COUNT function... eg., if days >= 20 then active...

I do not know what to do about this CKF in 2004s to prevent the dump

Former Member
0 Kudos

Issue solved with SP10.

Former Member
0 Kudos

Thanks for the update..

Chetan

@CP..

Former Member
0 Kudos

Hello KWuser....SP 10 is out in November. Can you please update how did you manage in the meantime? Do you have advance correction?

Rakesh

Former Member
0 Kudos

Note 973505

Former Member
0 Kudos

Thanks for your response. We have however implemented this note (we are on SP9) and still get the warning message "Time of calculation "before aggregation" is obsolete ".

Former Member
0 Kudos

Supress the message for that particular query using RSRT