Skip to Content

Usage of BW cache with SAP BO Design Studio 1.6


Environment: SAP BO Design Studio 1.6, SAP BW 7.3 and Design Studio dashboards hosted on Netweaver Platform Enteprise Portal.

We have developed a dashboard with couple of Bex queries. The cache (cache mode 5: Query Aggregates) has been enabled for these queries in BW. In order to test caching, we followed below steps -

1. At the start of the day, refreshed the Bex queries using RSRT transaction to ensure cache is filled.

2. Refreshed the bex queries subsequently using RSRT transaction and monitored the execution through SM50 where in it was noticed that it is fetching results from cache.

3. Executed the dashboard that internally triggered execution of the same queries and monitored the execution through SM50 where in it was noticed that the queries ignored the cached and went for sequential read from tables.

This is confusing me as queries when executed through RSRT are fetching results from cache but post that when same queries are executed from Design Studio dashboard they ignore the cache and go for sequential read from table.

Please suggest.

Note: Bex queries do not have any variables and provide a snapshot of data.

Thanks & Regards,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 21, 2018 at 10:21 AM

    Hi Abhijit,

    Are you sure your Design Studio application use the queries in the same way as in the RSRT ? The application can ask for free characteristics.

    Is there any action between the warming of the cache and the execution of the DS application that could invalidate it ?

    I have no issues with the cache and DS 1.6.



    Add comment
    10|10000 characters needed characters exceeded

    • Hi Abhijit,

      Thanks for the feedback.

      It would have been interesting though to check the behavior of the query with the read mode setting at "A Query to read all data at once" (thus caching all data of the query, free chars included). This setting can be set in the query properties at the RSRT level.

      Also, check if your query use a virtual char (RSRT, technical information).