Skip to Content

Precalculate all characteristics combinations of a BW query...

Hi All,

We need precalculate all possible characteristics combinations (drill downs) of a query to fill the BW cache.

Looking on the Reporting Agent it´s possible precalculate a bw query using another query to control the filters, however using this feature it is not possible to pass all the possible navigations steps of the query to the variant.

Anyone can help me with this issue?


Add comment
10|10000 characters needed characters exceeded

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 03, 2006 at 07:45 AM

    Hi Enrique,

    Arun has comletely right.

    Only one more thing: you can also set in Tcode RSRT in Properties the Session A - Query must read all values.



    If it is all right please close the topic.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      The Query Read Mode set to: <b>A Query to Read All Data At Once</b> is the easiset way to handle this.

      If you review the SQL that is generated, you will see that all the Free Characteristics are selected in the query when this Read Mode is set.

      Keep in mind, that if this query has any input variables that users might change, those variables need to be set to Can be Changed During Navigation in order to have all their different executions of that query use the OLAP Cache.

      When you look at the query Prooperties, you may want to review the other related settings - Cache Mode and Persistence Mode.

  • Posted on Aug 03, 2006 at 05:21 AM


    Welcome to SDN...

    What you need to do for the same is :

    Have all the characteristiics in the rows areas and then run the query in the background using reporting agent , this will fill up the OLAP cache and you can use the same.

    All the data resides in the cache and you can use the original query later and it would fetch the records from the cache.

    To check the same , activate the cache first

    Then run the fully detailed query

    Now run any other version of the query through BeX and then check in SM04 to see if you are fetching the records directly from the cube/ods or from the cache ( indicated by RSRCACHE)


    Assign points if useful

    Add comment
    10|10000 characters needed characters exceeded