Reporting AGent problem need help immediately

Question

I have schedule a job everyday for reporting agent. Which includes 6 reports init with precalculated webtemplate. The reason to use this is that everyday morning the job will run before users use those reports and it will add that in cache so even if users run that reports first time it will be faster in performance.
Once the job is done i can see those entries in cache memory. But when I run the report its not using cache. it takes forever to execute for the first time. after running the report on web i checked the cache entries and i saw strange thing that when i run the report for the first time its replaces the previous entry of that report from cache with the current one. (eg. Reporting Agent job was finished at 4:00am in the morning - i could see the queries in cache memory with my id and time stamp 4:00am. But when i run the report at 7:00am it takes longer time and after running the report if i check cache entry for that perticular report i dont see 4:00am entry instead of that i see 7:00am entry)
Can some one tell me why its acting weird ??
FYI: When i created reporting agent setting  there are 4 options (checkbox) under calculate section:
1. Data
2. HTML for Web Browser
3. HTML for Pocket IE
4. Excel
in above options i just selected "Data" - will it might be the reason when i run the query on web its not using cache for the first time ??
Message was edited by:
        Keral Smith

Answer 1

Also check the SAP Note <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=0000751402&nlang=E">751402</a> and the SAP Note <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=962651&_NLANG=E">962651</a>.
<b>Symptom</b>
The reusability of the cache is poor when the "Not changeable during query navigation" variable setting is set. A preliminary calculation is not useful in this case.
<b>Other terms</b>
OLAP, cache, cache key, cache entries, reusability, reusage
preliminary calculation, variable not changeable during query navigation
<b>Reason and Prerequisites</b>
The various entries for each variable setting have different keys for "Not changeable during query navigation".
<b>Solution</b>
The key for queries in the OLAP cache comprises the following: "query", "variables not changeable during navigation" and "selection hierarchies".
To reuse cache entries, the cache always returns complete value sets that have already been precalculated and stored or subsets of these value sets. For reusage, the cache can only find subsets of value sets that have already been precalculated and stored if the key for the subset is a subset of the key for the value set that has already been calculated.
If the setting for query variables is set to "Not changeable during query navigation", a separate cache entry is created at the "Variables/hierarchies" cache level for each query selection. To enable this reusage, you must select exactly the same variable selection, since this results in the relevant key. In this case, a similarity check was performed in the cache for a query at variable level. In practice, a preliminary calculation is executed with the "*" variable selection. Usually, a user will choose another variable selection to be output. When you set the variables to "Not changeable during query navigation", you cannot reuse the precalculated value since the key does not correspond.
If the "Changeable during query navigation" variable setting is selected for a query, the variables are no longer part of the "Hierarchy/Variable" key, but rather the selection conditions (which are one cache hierarchy level lower). Therefore, the same "Hierarchy/variable" subtree for the query is selected for each variable selection (if the entry has already been calculated and stored) and checked to see whether the value set (or a subset) is considered to be a resulting set. If a value set with "*" was now selected with the preliminary calculation, this could be reused by selecting and returning the relevant value set for the subselection.
For increased reusability, the variable setting should be set to "Changeable during query navigation" and the preliminary calculation should take place with "*".
However, you should note that the preliminary calculation must have selected actual supersets. The OLAP processor only examines subset relationships in the cache. The system does not search and "merge" several different cache entries to determine the results of a query (therefore a multi-dimensional approach is not possible either).