RFC
Administration
Purpose
Remote Function Call (RFC) is the central SAP technology for exchanging data between SAP systems. It comprises the RFC interface and the RFC protocol.
Various RFC types can be used, depending on the type of data transfer required. These RFC types all have different quality of service properties:
● sRFC (synchronous RFC)
● aRFC (asynchronous RFC)
● tRFC (transactional RFC)
● qRFC (queued RFC)
● bgRFC (background RFC)
Prerequisites
To use RFC for data transfer between systems, the following settings need to be made:
● RFC destination maintenance (transaction SM59)
To ensure that the sending system can reach the respective target system for the data transfer, this target system must be defined as RFC destination in the sending system. The RFC destination contains various parameters that serve to define the target and the form of the RFC communication.
● Configuration of system resources for RFC
To guarantee the optional functionality in RFC, the various system parameters need to be defined, for example to set the maximum number of work processes that can be occupied by RFC.
Tools
● The central tool for RFC destination administration is transaction SM59. To call this transaction in the SAP menu, choose Administration → System Administration → Administration → Network →Maintain Remote Destinations.
● You can use a monitoring transaction to monitor the RFC communication. The transaction to use depends on the RFC type:
○ tRFC: SM58
○ qRFC: SMQ1 and SMQ2
○ bgRFC: SBGRFCMON
● You can also use various other transactions to perform other administration tasks:
○
Definition of
trusted system
relationships
(simplified logon procedure for RFC communication)
Periodic Tasks
● Monitoring:
○ tRFC
○
qRFC
○
bgRFC
Event-Driven Tasks
● Error Handling:
○ tRFC
○
qRFC
○ bgRFC
Other Tasks
●
Maintaining Remote
Destinations
●
Configuring System
Resources for RFC