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.
The table below provides an overview of all statistical data (fields) for RFC and ICF and demonstrates the values that these fields can take.
Statistical Data for RFC and ICF
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 the system starting to read the query and finishing writing the reply, in ms |
|
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 |
Time that the call was executed on the server side |
|
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 (ICF) |
RFC logon procedure |
Possible values: o ' ': Unknown Authentication o ' 0 ': None Authentication o ' 1 ': HTTP Basic Authentication o ' 2 ': Authentication using Mysapsso2 Cookie o ' 3 ': SAP RFC Logon Procedure o ' 4 ': Service Logon Procedure o ' 5 ': Logon Using SAML o ' 6 ': Logon Using Form Fields o ' 7 ': Logon Using X.509 Certificate o ' 8 ': Recorder Authentication |
Logon method (RCF) |
ICF logon procedure |
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 |
Path |
ICF service path |
For example: /sap/bc/echo |
Port |
Name of port |
For example: 8080 |
Protocol |
Protocol ID |
Possible values: o unknown o HTTP o HTTPS o SMTP |
Received data |
Data received in bytes |
|
Remote execution time |
Time that the call was executed on the client side, in ms |
|
RFC type |
RFC type used |
Possible values: o S synchronous o a: asynchronous without reponse o A: asynchronous with reponse o t: transactional using asynchronous o T: transactional using synchronous |
Sent data |
Data sent in bytes |
|
Status Code |
Status code in accordance with HTTP specification |
For example: http 500 |
Status Phrase |
Description of the status code |
For example: 'Internal Server Error' |
Timestamp |
Time stamp of the call |
Format: 20050314 102205 CET |
Virtual Host |
Number of the virtual host |
For example: 0 |
To evaluate statistical data for RFC or ICF, proceed as follows:
Call transaction STAD.
In the selection screen, enter the criteria according to which you want to restrict your selection and choose OK.
Choose the required entry from the list by double-clicking it.
In Remote Function Calls or HTTP Records, click on the details for Connections and Calls.
A popup appears providing you with the relevant data.