Skip to Content
avatar image
Former Member

Exception Aggregation - strange behavior

Hi Gurus,

I have a cube with the following structure:

CATEGORY  FISCPER    KF1   KF2   KF3
BEGIN     01.2016    3000 300 -140
...
BEGIN     05.2016    3400 200 -150
BEGIN     06.2016    3100 180 -130
INBETWEEN 01.2016    100
...
INBETWEEN 05.2016    500
INBETWEEN 06.2016    600
END       01.2016    1000 300 -140
...
END       05.2016    5000 200 -150
END       06.2016    5500 180 -130

I want to build a query with restrictions (FISCPER 05.2016-06.2016) which will show me:

CATEGORY  KF1   KF2   KF3   Comment
BEGIN     3400  200  -150  <- Line 05.2016 with MAX - Exc.Agg. by FISCPER 
INBETWEEN 2100             <- Just a sum of all values
END       6000  180  -130  <- Line 06.2016 with MIN - Exc.Agg. by FISCPER 

But I get an unpredictable behavior of the last KF:

CATEGORY  KF1   KF2   KF3   Comment
BEGIN     3400  200  -130  <- KF3 shows value from line 06.2016
INBETWEEN 2100             <- All ok
END       6000  180  -150  <- KF3 shows value from line 05.2016

What I can't understand, why only one KF3 has a reversed logic, despite all of them have the same settings on a query level and on an info-object level in rsa1 as well, where no exception aggregation is maintained!


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 12, 2017 at 11:51 AM

    hi,

    minus 130 is correct because it is your max value, if you want to see minus 150, you chould have min in stead of max as ex agg on that KF

    grtz

    Koen

    Add comment
    10|10000 characters needed characters exceeded