Analyzing RFC Statistical Data 
You can use transaction STAD to call up various statistical data for RFC and ICF, in order to find the status of actions that you have performed. You can filter this data according to various criteria (such as user, time, server name) in the initial screen of the transaction.
Structure
The table below provides an overview of all statistical data (fields) for RFC and ICF and demonstrates the values that these fields can take.
Field name |
Meaning |
Values |
Authorization time |
Time required for authorization check, in ms |
|
Caller user name |
User name of caller |
|
Caller client number |
Client of the calling system |
For example: 400 |
Call Time Calling time |
Time between starting to write the query and finishing writing the reply in ms (from client view) |
|
Calls |
Number of calls |
|
Connection ID |
Connection ID (32 digit GUID) |
For example: 0A15535F31C142EDCCF10BCF00000000 |
Data send time |
Time required to send the data in ms |
|
Data receive time |
Time required to receive the data in ms |
|
Destination |
Name of the destination |
|
Execution time |
Execution time for call in ms (from server view, value is identical to Remote Execution Time) |
|
Host |
Host Name |
For example: ld0168.wdf.sap.corp |
Idle time |
Time between the system finishing writing the reply and beginning to read the 2nd query, in ms |
|
Instance |
Name of the calling instance |
For example: ld0168_BIN_53 |
IP address |
IP address of the calling system |
For example: 10.21.82.60 |
Logon method |
Possible values: o ' ': No authenti- cation o ' 1 ': User and password o ' 2 ': SSO Authentifi cation o ' 3 ': Logon ticket o ' 7 ': X.509 Certificate o ' 9 ': Exild Authentifi cation o 'A': SNC Authentifi- cation |
|
Logon time |
Time required to log on to partner system, in ms |
|
Method |
Call method used |
Possible values: o GET o SET |
Partner instance |
Instance name of the partner system |
ld02907_BCE_26 |
Partner IP address |
IP address of the partner system |
For example: 10.21.82.60 |
Partner release |
Release information for the partner system |
For example: 640 |
Port |
Name of port |
For example: 8080 |
Received data |
Data received in bytes |
|
Remote execution time |
Execution time for call in ms (from server view, value is identical to Execution Time) |
|
RFC type |
RFC type used |
Possible values: o S synchronous o a: Asynchronous without response o A: Asynchronous with response o t: transactional by asynchronous o T: transactional by synchronous |
Sent data |
Data sent in bytes |
|
Timestamp |
Time stamp of the call |
Format: 20050314 102205 CET |
More Information
You can find detailed information about using transaction STAD under: