When reporting with BOBJ Clients on BW data users might request too detailed information pushing BW system over its limit and causing performance / system stability issues. There is a safety belt functionality which allows to set a maximum number of cells retrieved from BW. In my blog I will explain to set safety belt for different BOBJ Clients. If you do not authorization or system to play with you can create trial BW / BOBJ landscape in Cloud like exaplined here
Setting BW Safety Belt for Analysis OLAP
It is set in Central Management Console updating Properties of Adaptive Processing Server
Here are setting and default values
| Setting | Default Value |
|---|---|
Maximum Client Sessions | 15 |
| Maximum number of cells returned by a query | 100,000 |
| Maximum number of members returned when filtering | 100,000 |
To demonstrate how Safety Belt is working lets change Maximum number of cells returned by a query to something small, for example, 5.
and restart the Server
Now if we run Analysis for OLAP without drill down, then no error occurs
But if we drill down by Product or Sold-to number of cells will exceed the limit.
Setting BW Safety Belt for Web Intelligence and Crystall Report
It is set maintaining BICS_DA_RESULT_SET_LIMIT_DEF and BICS_DA_RESULT_SET_LIMIT_MAX paremeters in RSADMIN table. To demonstrate how safety belt works lets set the limits to some small value, for example, 5 running SAP_RSADMIN_MAINTAIN program.
Now if we run Web Intelligence report without drill down, then no error occurs
But if we drill down by Product or Sold-to number of cells will exceed the limit.
Safety Belt for Crystal Reports works the same way as for Web Intelligence