Do not use MNU_ETOOLS_EXPANDANDREFRESH if you do not need it!!
From my experience, more than 30% of BPC projects use this Macros in their BPC query or Input which is not necessary at all. Macro “EXPANDANDREFRESH” will cause an additional unnecessary refresh for this report. Please change it with MNU_EXPAND and this can save you at least 50% of runtime!
If you use Fiddle tool(www.fiddler2.com/) to trace the BPC reprots, you will find two same http sessions.
From my experience, more than 30% of BPC projects use this Macros in their BPC query or Input which is not necessary at all. Macro “EXPANDANDREFRESH” will cause an additional unnecessary refresh for this report. Please change it with MNU_EXPAND and this can save you at least 50% of runtime!
And if you want to make sure these if additional refresh command is no necessary in your scenario, Go to transaction SLG1-> Find the application logs of your queries, then you will find the detail MDX statement by clicking "problem class other". If two MDX statement is exactly the same, then you can remove this extra refresh
- SAP Managed Tags:
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
