SAP BW Query - Efficient Use of Filters With Large Data Volumes, Or: “How Do I Speed Up the Filters?”

SAP BW Query - Efficient Use of Filters With Large Data Volumes, Or: “How Do I Speed Up the Filters?”

As a business intelligence package, SAP BW provides many opportunities for efficient reporting – but also contains numerous barriers which significantly slow down performance. Using the example of report filters available in the application, this article shows how the smallest adaptations impair SAP BW performance, and how efficient settings for filtering options can improve results.

Table of Contents

Through definitions of specialized and technical content, a use of SAP BW queries enables perfect preparation of interaction between users and data. What many users - especially professionally oriented power users - usually do not know, however: Any setting, however small, can sometimes have an immense impact on report performance. In the case of filters, for example, the outcome can vary from simply useless to highly efficient and fast reports.

The following example shows a filter selection from the area EC-PCA with the InfoObject "Document type" in Analysis for Office:

Filtration Yes, but What Is the Right Way?

When considering a use of report filters, the following question first arises: Where can the filtration behaviour be defined, and what are the reasons for adapting the relevant settings to one's own reporting requirements? As is usual with SAP BW, there are numerous ways of defining the behaviour of selected filters in order to maximize reusability. This can significantly facilitate work, especially for query developers who would ideally not need to change any settings. What is clear: Users should be familiar with and utilize available filtering options, because the selection predefined by SAP provides the least efficient solution and often leaves something to be desired in terms of speed.

The filter behaviour can be set in the following objects:

1. The InfoObject, and thus globally for CompositeProvider and Query:

2. The CompositeProvider, to respond to adjustments based on the explicit data model:

3. The Query, if special features require a change in the query structure:

The selection made above changes the behaviour of SAP BW queries to the database and, thus, the number of visible entries. Filters from master data can be determined at a very high rate, for example, though features without data are also displayed here, thus possibly irritating the user.

The following filter options are available

Practical Examples

The following practical examples demonstrate the causes and solutions of potential problems:

Implementation in the Case of Third-Party Solutions With MDX Access Such as Longview

Because these settings are only considered in SAP BI clients such as Design Studio, Analysis for Office, etc., third-party tools must control behaviour themselves.

Conclusion

Small change, large effect – to minimize expenditure in query development, the relevant department and BI should regularly have exchanges, discuss problems with query settings and deploy the solution centrally. However, power users should also be aware here of the behaviour of filters and their effects, to be able to identify and communicate any potential for optimization.

Do you frequently encounter performance issues? Do not hesitate to contact us. In an initial analysis or our BI quick check, we identify stumbling blocks and provide you with opportunities for fast and uncomplicated self-help.

Want To Learn More? Contact Us!

Olaf Bowe

Your contact person

Olaf Bowe

Domain Lead Insights & Information Design

Related Posts

chevron left icon
Previous post
Next post
chevron right icon

No previous post

No next post