Display Aggregate Found in Transaction RSRT

[Former Member]

When I select "Display Aggregate Found" in transaction RSRT, in debug the system presents a dialog with 3 requested Aggregates for the same infoprovider. 2 have calweek and 1 has calday.

Anyone know why it would give me 3?

Do I need all 3 for the report to run in a quick manner?

Also, I have a selection in the query with a variable for 0FISCPER and that is not suggested as a characteristic in any of the requested aggregates. Any ideas why this would not be suggested?

Any direction is greatly appreciated!

Thanks,

Ken

Message was edited by: Kenneth Murray

[Former Member · Accepted solution]

Just to point a finer point on this - the display is showing you which aggregates it chose. Whether you should keep all three really depends on what those aggregates look like and resources required to maintain them (disk, CPU)- how different are they in size, characteristics in them, etc.

As Klaus Werner mentions, your query will actually exec three separate SQL stmts and then pull the results together. Depending on the design of the aggregates, data volumes, dimension sizes, etc, a single good aggregate could outperform the three you have. It, like much in Data Warehousing, all depends ........

[klaus_werner]

Hi Ken,

you have several selection in your query (restricted key figures), that's why there are different requests for aggregates. Yes you would need all three or one superset aggregate of the three (or two, with one being a superset of two others). 0FISCPER is maybe covered by 0CALDAY, that's why it may not appear separately.

Regards, Klaus