How to analy report in rsrt

Question

Hi, experts,
  I try to use Tcode: Rsrt to analysis the difference if report use aggregates or not.
  under the "Execute + Debug" button, I select the option "Display Statistics Data". but in output text interface, I can not found any information for query performance ( for example: run time, how much rows readed, how many transfer to OLAP processor, etc )
thanks in advance.

Answer 1

hi,
hope SAP Note Number: 130696 -Performance trace in BW-
helps 
Symptom
How can you monitor the performance of a query in BW?
Other terms
Performance, tracing, BW, query, report, time
Solution
1) Activate the saving of statistical data for each InfoCube
   -> BW Admin Workbench - Tools  -> BW Statistics for Infoproviders ->
   Select the "OLAP" field for the InfoCube.
3) Execute report/query
2) Analyze the RSDDSTAT table using Transaction SE16
   Access, for example, using the InfoCube name or the user name or the
   timestamp
1. Times that are saved:
QTIMEOLAPINIT
                     Time of the initialization of the query (for example, loading query in OLAP, compiling if required)
QTIMEOLAP
                     Time that the OLAP processor required
QTIMEDB
                     Time the database + network required to select the transaction data. The time is measured from when the SQL command is send to the database, and it is stopped when the requested data reaches the application server. This time therefore includes the transport on the network and the selection on the database.
QTIMEVARDP
                     Time the user required to enter the variables
QTIMEUSER
                     Time the user required between the navigation steps
QTIMECLIENT
                     Time of data formatting in the frontend
The time measurment starts when the OLAP processor has completed the data formatting. The data is then sent to the frontend (EXCEL). The time is stopped when the frontend (BW add-in in EXCEL) has inserted all data in the worksheets (writing the contents and formatting cell, if required). The time therefore includes the transport on the network with the RFC connection and the output in the frontend.
TIMECHAVLREAD
                     Time required to read master data
TIMEAUTHCHECK
                     Runtime of the authorization check.
TIMEREST
                     Time that could not be assigned in more detail (should be equal to 0; if this is not the case, something in the internal processing of the OLAP processor occured differently than expected.)
QRUNTIMECATEGORY
                     Time of a navigation step (QTIMEOLAPINIT + QTIMEOLAP + QTIMEDB + QTIMEEXCEL + QTIMECHAVLREAD) rounded to the next higher scaling (1,10,100,1000 ... seconds). As of 1.2B, this is rounded to 1,2,3, ... 10,20,30,...100,200,300,... seconds.
1. Data regarding the size of the query:
QDBSEL
                     Number of the records that had to be read on the database
QDBTRANS
Number of records that the database transferred to the server
QNUMCELLS
                     Number of cells that were transferred to the frontend
QNUMRANGES
                     Number of formattings that were transferred to the frontend
RECCHAVLREAD
                     Number of master data records to be read
1. In addition, the following is saved:
QAGGRUSED
                     Name of the aggregate used
QNACHLESEN
                     Indicator: Query reads during each navigation step
1. Administrative information
STATUID
                     Key of the table; link in view RSDDSTAT_V
QSESSION
                     All data for a call of the frontend (between start and end of the frontend) is compounded with this unique GUID.
QNAVSTEP
                     The navigation steps of a QSESSION are numbered in ascending order
QNUMOLAPREADS
                     Number of read operations OLAP processor for each navigation step
HANDLE
                     In the frontend, each embedded query has a separate, sequential number (handle)
If you want to analyze a certain query, start it and filter the values from the table afterwards: Selection options: infocube, user name, queryid (can be determined in the report monitor (Transaction RSRT)-> Technical information). The STARTTIME (UTC time) tells you whether you have found the correct session.
You can recognize a session because the QSESSION is always assigned the same ID. The sequence of the navigation steps is saved in QNAVSTEP. However, you can also determine it using the STARTTIME.