Via tRFC, data can be transferred safely and reliably between applications. The RFC client calls a specific function module on the RFC server. The called function module is executed exactly once on the server. The resulting data is then stored temporarily in the SAP database under a unique transaction ID (TID), that is, data creation and data transmission are two separate processes. The tRFC is used for example to send business documents from one SAP system to another SAP system, often by using the ALE/IDoc layer.

One or several functional module calls can be grouped into a single tRFC LUW (logical unit of work). Due to its asynchronous nature, the tRFC can handle situations where the called remote system is not available at the time of posting. In such a case a reprocessing is triggered by the tRFC framework.

The following technical prerequisites have to be met in order to use the tRFC monitoring:

• The managed system is ABAP based system with basis release ≥ 7.00 (RFC client)

On the managed system, use transaction SM58 to check whether there are tRFC entries present.

Available Monitoring Categories

The available monitoring categories are:

• tRFC: tRFC entries send from the ABAP system (Monitoring transaction SM58)

Available Filter Options

tRFC 

For tRFC Monitoring, you can collect all tRFC entries in the managed system. You can also use the following filter parameters, to restrict the data collection:

• RFC Destination: The name of the RFC destination the tRFC is sent over (see SM59)
• Function Module: The name on the called function module (see SM58)
• User: The user in the RFC destination (see SM58)

Available Metrics

For interfaces of type tRFC the following metrics are collected:

tRFC 

• Number of tRFC entries: Number of entries that fall in the selected status group
  Metric parameters:
  
  • STATE_GROUP = CRITICAL, INTERIM
• Age of oldest tRFC entry: Age of the oldest entry that falls in the selected status group
  Metric parameters:
  
  • STATE_GROUP = CRITICAL, INTERIM

The following status codes are taken into account for error and interim statuses:

The term “Critical” as used above indicates an immediate error state, with no automatic reprocessing, manual action is required. The term “Interim” indicates a temporary error or backlog situation only. Usually automatic reprocessing is in place.