Invoice line items report from DSO compared to Infocube (in HANA)
As you know Invoice line items are very granular level information. We are facing performance issues on reports based on the Infocubes to display this information. We are migrating to HANA and looking for options to improve the performance. One of the option we are looking at is instead of Infocube can we we report directly on the DSO. I would like to know whether it will help and its Pro & Con's. Please help.
Kevin Small replied
Reading data from a DSO instead of an InfoCube will not improve reporting performance. The benefit in getting rid of the cube is that you have less loading to do. You still need cubes for planning and inventory scenarios.
You do not need a composite provider to report from DSOs in BW. Once you've migrated to HANA you use DSOs just as you would today, and you can report from a multiprovider. Yes, you can use a composite provider, but it is not necessary.
If your report is slow today, you need to find out where it is slow. HANA could provide a huge benefit as soon as you migrate, or it might not help much. It depends on the scenario. OSS 1681396 is a good place to start.
If the DB time is long, and you're not using BWA today, you can expect big benefits when you migrate to HANA.
If the OLAP time is long, you might see big benefits when you migrate, as the OLAP engine during query execution is pushing more to HANA.
If the frontend time is long, migrating to a different database isn't likely to change that, you'd need to address that separately.
Finally, an important point to remember is that once you've migrated you open up additional possibilities for improvement that are not available to you in BW-on-non-HANA. For example, you might be able to rewrite queries as HANA models. I did some performance tests on this in a very simple case of exception aggregation.