on 01-27-2005 8:44 PM
Hi,
I have a web template with the property "Read Mode for data" set to "Hybrid" mode.
I have not maintained precalculated data yet. but, in hybrid mode, the query should run and if there is no precalculated data, it should get the current data.
When I execute this, the query does return the (current) data but the "context menu" is disabled. i.e. I can not do any navigations or any drill downs.
I understand that for precalculated data context menu is disabled. But, why is the context menu disabled when I ran it in hybrid mod and when it fetched current data...
Any input is greatly appreciated and rewarded
Thanks
John
Hi John,
I hate to give away a million dollar answer, but here it is
We had a similiar situation where the users did not want a static report, but a report where navigation was possible. Ofcourse, performance was to be same as a pre-calculated report. The following was our solution -
1) Do not set the web template to "stored" mode. Leave it with the regular setting.
2) In RSRT set the "properties" of the base query with the options 3 and 2. Query read mode can be set to A as well. (read further comments on the query read mode in the notes below)
3) Schedule the reporting agent job.
4) When you execute the web template, it should then start reading the data from the cache rather than the application server.
5) The cache will be used for all other navigations and the context menu will be available as well.
This solution has its "cons" of course -
1)The background job will start the query in read mode "A". Depending on data volumes it could be a long running job.
2)If your users are willing to live with a longer run time for the "very first" "new" navigation that they execute, you can possibly set the query read mode to "H" as well. The very first run will take a long time after that, it will read data from cache.
2) If you have lot of templates that plan to make use of this feature, the cache size will fill up. There has to be a proactive cache management in place.
Hope that helps !
Cheers,
Anil.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One way to solve this is to add an icon or link to open the static query in a new window with the following code:
SAP_BW_URL_Get()+ "&CMD=RELEASE_DATA_PROVIDER&DATA_PROVIDER=DP1&TEMPLATE_ID=template_name&CHANGE_ITEM=X&ITEMID=TABLE_1"
This will use the cache from the pre-calculated template so it will run fast.
Thanks,
Jeff
John - just tested this on my prototype 3.5 system and I get the same issue. What version are you using?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.