SAP BW|BOBJ|Project Management Blog

9 SAP BW Query Design Mistakes That Make You Look Dumb [Template]

Written by Lonnie D. Ayers, PMP | Thu, Jan, 05, 2012 @ 03:32 PM

Avoid Common Query Design Mistakes

 

Do you want to avoid looking dumb as a SAP BW Query designer?  We all do, and to help you avoid that fate we recommend you avoid the following common mistakes when building Queries:

 

 


Nine Big Query Design Mistakes To Avoid


  • Not using authorization variables to automate query execution.

  • Not using query views or variants to speed up execution of a query to the desired navigation view without having to create new queries in the system

  • Not enabling query statistics in order to view the efficacy of aggregates and designing correct aggregates to speed up query execution

  • Not minimizing the data set result size if possible

    How do you minimize the data result set?  By being smart about what filters to include at the query execution time

  • Not having the system cache settings properly configured in order to reduce the db access times for frequently accessed queries

    Remember: T-Code rsrcache is where you can check it!

  • Forgetting to use exceptions to make query results 'pop-out'.  For example, if you were running a query on profitability by product, you would want to set up exceptions to flag drops or increases in profitability.

  • Failing to use alerts to automate query execution and delivery to the right people in a timely fashion.

  • Not pre-warming up the cache in your overnight process chains to improve performance

  • Not making your users life simple by not arranging the queries in nice menus for the users so they don't have to look for their particular queries.

Get Our Query Design Template

 

There are many issues to consider when designing a SAP BW Query.  We have developed a Query Design Template which will help you do it right.