on 07-29-2014 3:40 AM
Dear experts,
I'm running a webi report connected to backend BW via universe. Any idea on how to separate the webi executing duration into BO side part, BW side part?
Thanks,
Hi Hong ,
*The overall runtime can be split into 5 different parts (Database, OLAP, MDX, RFC and
WebIntelligence) .
*We have to gather the statistics in the SAP BW system. Use transaction SE16 (Data Browser)
and go to table RSDDSTAT_OLAP
*Enter User name and UTIME and calendar date object name (Bex query)
*Press the execute button and you will get the table with all the statistics in SAP BW. Now, you
have to separate the backend runtimes into database, OLAP and MDX runtime.
*Gathering the Database Runtime
Click on the header of the column “EVENTID” to mark the whole column. Set a filter by pressing
and select the between range from 9000 to 9011.
*Gathering the OLAP Runtime
Click on the header of the column “EVENTID” to mark the whole column. Set a filter by pressing
and select the between range from 2500 to 4999.
*Gathering MDX runtime
Click on the header of the column “EVENTID” to mark the whole column. Set a filter by pressing
and select the between range from 40000 to 40036.
*Gathering the Single Statistical Records STAD
To get the memory consumption, Remote Function Calls (RFC) and the details about all the BAPIs
called during report execution, we need to enter transaction STAD in SAP BW.
When starting STAD, set a filter on the connection user for the Universe and select the appropriate
start time and the length of the interval to be investigated (according to the total runtime of the report).
This will return a set of RFC calls to the backend. Normally, the major runtime influencing part can be
easily determined by the column “Response time (ms).
Subtract all this times from Webi report refresh time , we get time taken at BO end.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We can distinguish both RFC and DB times with STAD ,
this will return a set of RFC calls to the backend. Normally, the major runtime influencing part can be easily determined by the column “Response time (ms).
Double-click that line to get to the details .
Double click on RFC to get to the RFC statistics
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.