Reporting on Aggregation Levels

[sap_cohort]

Hi, Is is ok to create non-planning reports using aggregation levels or should they be created on the multiprovider. The reaons I ask are:

1. Would reporting on Aggregation Levels be slower?

2. I have a lot of CKF on my aggregation Levels that I would have to rebuild on the MultiProvider so I would like to use the Aggregation Level for reporting to ease the development effort.

Thanks

[Former Member · Accepted solution]

Hi Kenneth,

Yes, if your requirement is reporting , it is always good you report directly on the Multiprovider, instead of having one more logical layer (Aggregation level).

But,as mentioned by you, if you have to build a query on the Multiprovider, you have to do lots of rework.

So instaed of that , try to enhance the performance by other methods.

Ex: ->Try to use Compounding characteristics as less as possible.

-> store planning data and actual data in different

InfoCubes and use aggregation levels on a MultiProvider for planning.

-> use characteristic relationships sparingly.

->Use redundant time characteristics,navigation attributes and compound characteristics.

as less as possible in the real-time InfoCube.

-->Try to have restrictions on the characteristics as much as possible in the Query.

For more info:

/message/4191143#4191143 [original link is broken]

Please go through the note:1056259 which gives detailed information on Performance tuning for Planning applications.

Best Regards,

Akshata

[sap_cohort · Accepted solution]

I was able to copy the CKF's from the Aggregate directly to the MultiProvider and then recreate the queries for reporting to be on the MultiProvider instead...

Thanks