Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member

Ways by which you can improve the performance of Business Objects. These are:

  1. Improving performance of Universe
  2. Improving Performance of Reports
  3. Improving Performance of Business Objects servers
  4. Improving Performance of Database 

1. Improving performance of Universe   · Reduce the use of unnecessary joins- Unnecessary joins will degrade the performance as it increases the execution time of query. Explore the universe properly and take out unnecessary joins. 

  • Use @Aggregate_Aware- @Aggregate_Aware is a function used in BO universe, by which universe can use aggregate tables in a database. It drastically reduces the query execution time and in turn enhances the performance.
  • Use shortcut joins- Shortcut joins provides the shorter path between 2 tables and thus improves the query efficiency.
  • Set the proper value of array fetch size in universe connection- Array fetch size is the number of records fetched by a universe from database in each fetch. It should neither be too high and nor be too low. It depends on the network speed and database which you use. Sometimes its good to play with this number and verify the performance. 
  • All measure objects should use SQL aggregate function- Every Measure Objects should use SQL Aggregation function so that while querying there will be less number of dataset retuned in report. Without this user has to handle many rows in the report side.
  • Use Row and Time limit in Universe ParameterUse the universe parameter “Limit size of result set to” and “Limit execution time to” efficiently and according to your need, because this feature can increase or decrease the universe performance based on how you use it.
  • Use Universe Conditions instead of report filters- the reason is very obvious, as Universe conditions will restrict the data at database itself but if you use report filters data will fetched from database and then it will be restricted at report side which degrades the performance. 

   2. Report Level: 

  • Reduce the number of complex formulas/local report variables/complex filters
  • Try to use variables instead of formulas.
  • Breaks/Crosstab Reports/Charts will degrade the performance a bit in reports-Use it if it’s very much required but do not use it frequently.
  • Get benefits from prompts- specially the use date prompts if possible.
  • Use drills- It makes the report interactive for users and improve the performance as well.
  • Remove auto height/width if possible.
  • Use refresh on demand instead of refresh on open.
  • If you have a very large reports do not use refresh on demand in infoview-instead try to schedule the report, as refreshing will increase load on processing server while scheduling will be done on job server which is less busy than processing server in most of the cases. 



Labels in this area