Database Tables and Predefined Views
The statistics data is spread over a number of different database tables.
It is therefore easiest to use two predefined views (RSDDSTAT_OLAP and RSDDSTAT_DM). You use Data Browser (transaction SM16) to do this.
Field | Description |
---|---|
SESSIONUID |
UID of the user session (a role area) |
STEPUID |
UID of the user step |
HANDLEID |
Counter for the runtime object |
HANDLETP |
Type of runtime object |
EVENTID |
ID (NUMC9) of the event from the RSDDSTATEVENTS table |
UNAME |
User name |
STEPTP |
Type of step (RSDDSTATSTEPTP table) |
STEPCNT |
Ascending count of steps |
UTIME |
Time (type TIMS) from STARTTIME field |
CALDAY |
Calendar day (type DATS) from STARTTIME field |
RUNTIME |
Duration of a step in seconds |
INFOPROV |
InfoProvider (if valid) |
OBJNAME |
Name of the runtime object (such as query or Web template) |
OBJPROP |
Properties of the object encoded as CHAR10
Example for queries:
|
STATLEVEL |
Statistics detail level (0, 1, 2) |
EVTIME |
(Net) Runtime of event |
EVCOUNT |
Counter for this event (not required for all events) |
EVENTIDCNT |
Number of calls for this event (for internal use only) |
STARTTIME |
Start time of step in yyyymmddhhmmss,mmmuuun format |
Field | Description |
---|---|
STEPUID |
UID of the user step |
HANDLEID |
Counter for the runtime object |
HANDLETP |
Type of runtime object |
DMUID |
UIP for data manager access |
ACCESSCNT |
Data access counter (database, BW accelerator, RFC and so on) during a data manager event |
UNAME |
User name |
UTIME |
Time (type TIMS) from STARTTIME field |
CALDAY |
Calendar day (type DATS) from STARTTIME field |
OBJNAME |
Name of the runtime object (such as query or Web template) |
INFOPROV |
InfoProvider |
PARTPROV |
If INPROV is a MultiProvider, PARTPROV specifies the InfoProvider contained in it |
AGGREGATE |
Technical name of the aggregate or BWA index (if applicable) |
TABLTP |
Type of fact table (F or E) if InfoCube or aggregate accessed |
TIMEDMPREP |
Preparation time of data access, for ACCESSCNT = 0 only, since not parallel |
TIMEDMPOST |
Postprocessing time for data, for ACCESSCNT = 0 only, since not parallel |
TIMEREAD |
Data read time (database, RFC for example) |
TIMESID |
Time for calculation/determination of new SIDs |
TIMENAVATTR |
Time for reading master data |
TIMEHIERARCHY |
Time for hierarchy handling. Contains the time to explode the hierarchy and the time needed to store the hierarchy on the database or SAP NetWeaver BW Accelerator for further processing. |
DBSEL |
Number of records read from the database |
DBTRANS |
Number of records transferred |
WP_ID |
ID of the work process where the (possibly parallel) data read access was made |
STARTTIME |
Start time of step in yyyymmddhhmmss,mmmuuun format |