Communication Table

Definition

The communication table contains all the RFC connections to the server on which the cursor is positioned (see the documentation SAP Gateway).

The connections are displayed where the local dispatcher of the client is located and those connections where the server is located. This means, the connections to the server that were made externally.

Use

The communication table helps you keep track of the RFC connections when monitoring the system or analyzing problems.

Structure

RFC Destination

Conv.ID

User

Terminal ID / Session

Type

Connection
Status

Request

Wp

Time

GTADIR_SERVER   

61004034

KUNZ     

T00059M00

CLIENT

ALLOCATED

.          

 1

09:16:44

.                

60788713

RFC_CORR_REQ

T00035M03

SERVER

ALLOCATED

CMRCV     

 0

09:18:22

EU_SCRP_WN32    

60230342

KUNZ     

T00059M02

CLIENT

ALLOCATED

.           

 1

09:05:18

.                 

02602553

HINZ      

T00035M04

SERVER

ALLOCATED

.          

 0

09:51:07

.                 

88959741

SCHMITT      

T00040M00

SERVER

ALLOCATED

CMSEND(SAP)

 1

17:51:27

.                 

86810585

MAIER 

T00035M02

SERVER

ALLOCATED

CMSEND(SAP)

 0

12:41:09

The entries in the table have the following meaning:

Field

Description

Destination

Communication partner

If the computer where you are currently logged on is the server of an RFC connection (see Type column), the destination column will be empty. If the local host is the RFC client, the remote destination - the server for this connection - is displayed in this field.  You can display and maintain RFC destinations using transaction SM59 or by clicking display and maintain Destination (see RFC Programming in ABAP).

Conv.Id

Conversation ID

User

User

Terminal ID / Session

The terminal ID is the number of the terminal in the list of all the clients logged on to the dispatcher. The session number is the current external session.

This information is used to determine RFC dependencies in the analysis of RFC connections.

The combination TID/session defines the context belonging to a conversation ID either as a client or as a server. The TID/session is used to determine which RFCs are still coming from this context (client). The TID / session information on the server side is used to check whether this also appears again as a client, and hence is part of an RFC chain that is accessible iteratively.

Type

Client  that requested a service and therefore the connection, or Server that fulfills the client’s request.

Connection
Status

Current connection status; the following entries are possible:

INITIALIZED

Connection is being made

ALLOCATED

Connection is made

DEAL NOW

Connection is being terminated

DEALLOCATED

Connection has been terminated

CLEAR SNC

When using SNC: Encrypted data is still being supplied before the connection can be terminated.

Request

Last call or request (at RFC level)

Wp

Last work process, used for processing

Time

Time of the last request that dealt with the connection