Scribd
Upload
30 views5 pages

RFC - Remote Function Call

The document provides an overview of Remote Function Call (RFC) in SAP, detailing its types (sRFC, aRFC, tRFC, qRFC) and connection types (Type 3, Type I, Type T). It explains the purpose of RFC for communication between SAP systems and outlines the configuration process for establishing RFC connections using transaction SM59. Additionally, it discusses debugging RFC and the advantages of using RFC for data transfer and error handling.

Uploaded by

kaln g
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
30 views5 pages

RFC - Remote Function Call

The document provides an overview of Remote Function Call (RFC) in SAP, detailing its types (sRFC, aRFC, tRFC, qRFC) and connection types (Type 3, Type I, Type T). It explains the purpose of RFC for communication between SAP systems and outlines the configuration process for establishing RFC connections using transaction SM59. Additionally, it discusses debugging RFC and the advantages of using RFC for data transfer and error handling.

Uploaded by

kaln g
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Remote Function Call

In this topic, we described about the below sections -


 Remote Function Call
o RFC Types
 Synchronous RFC(sRFC)
 Asynchronous RFC(aRFC)
 Transactional RFC(tRFC)
 Queued RFC(qRFC)
o RFC Connection Types
 Type 3 connection
 Type I connection
 Type T connection
o Debugging RFC
For business applications, it is necessary to exchange the information with other
systems in the same or other systems group. To do this, a mechanism needed to
communicate between the SAP systems.
The systems communicate with function calls in the mechanism. The communication
between the systems using function calls is called as Remote Function Call (RFC). The
connection established using the Remote Function Call is called as RFC connection. In RFC,
the calling system and called system is different.
RFC takes care of communications between two independent SAP systems or client-
server communication between external client/server and SAP system. RFC consists of two
interfaces:
 ABAP Programs calling interface
 Non-SAP programs calling interface
Remote function call in the ABAP program can be place by using CALL
FUNCTION...DESTINATION statement.
Syntax: -
CALL FUNCTION 'remote-function'
DESTINATION <destination>
EXPORTING f1 =
IMPORTING f2 =
TABLES t1 =
EXCEPTIONS
The DESTINATION parameter describes the target SAP System where the function
runs in a system. Logical destinations are defined via transaction SM59 and stored in Table
RFCDES.
RFC Advantages:
 Convert the data format recognized by the target remote system.
 Calling necessary functions to establish communication between the systems.
 Handle errors in the communication process.
RFC Types -
There are four types of RFC.
 Synchronous RFC(sRFC)
 Asynchronous RFC(aRFC)
 Transactional RFC(tRFC)
 Queued RFC(qRFC)
Synchronous RFC (sRFC) -
Synchronous RFC is reliable and consistent process to transfer the data between the
systems. It requires both systems to be available to transfer the data.
The calling program in the source system waits until the requested process completed
at the remote system. The program is free once the process is completed at the remote
system. If the target system is not available, then the process goes to sleep mode and wait
until the system availability.
Asynchronous RFC (aRFC) -
Asynchronous RFC is not reliable process to transfer the data. Source system only
sends the data without verifying the target system status. Source system won't get any
acknowledgement from the target system about the data transfer.
The acknowledgements are not required in this RFC connection. The source system
has no information about the data transferred or not to the target system. The calling
program sends the request and releases immediately to work locally.
Transactional RFC (tRFC) -
The RFC connection is similar to asynchronous RFC. This RFC connection assigns
transaction id for each request and uses the transaction id for recognizing the request at the
remote system.
The remote system won’t process the request multiple times even though source
system requests multiple times. If the target system is not available, the data held in source
system until the target system available.
The report program "RSARFCSE" called in the background at regular intervals to place
the unsuccessful requests again and again identified by their transaction id.
Queued RFC (qRFC) -
Queued RFC is an extension/advanced version of transactional RFC. In this RFC,
requests are queued up and are processed in a sequence.
It guarantees that multiple Logical Unit of Work/Transaction are processed in the
order specified by the application. This RFC can be serialized using queues hence it is called as
Queued RFC.
RFC Connection Types -
There are three distinct types of trusted connections.
1. Type 3 connection
2. Type I connection
3. Type T connection
Type 3 connection -
The connection type is used to specify connection between ABAP systems. Source
system Host name/IP address, Logon information must specify in this connection type.
This is applicable for the RFCs between ABAP systems and external calls to ABAP systems.
Type I connection -
Used to specify ABAP systems connected to the same database as the current system.
The entries are pre-defined and can't modified.
Type T connection -
The connection type helps to connect destination system external programs that use
the RFC API to receive RFCs.
Start or registration is the activation type. Host name and program pathname to start
the connection.
Debugging RFC -
It is not possible to debug a remote function call to another system. For ABAP-to-
ABAP RFC calls, ABAP debugger can be used to monitor the execution of the RFC function in
the remote system.
For remote calls, the ABAP debugger with the debugging interface runs on the local
system to monitor the execution of the RFC function.

Configure RFC
In this topic, we described about the Configure RFC process in detail.
Step-1: Go to SM59 transaction code.

Step-2: It navigates to “Configuration to RFC Connections” Screen. Click on “new” icon to


create new connection.

Step-3: Enter RFC destination, connection type and description and click on “save button.
 RFC Destination – Destination/target system ID.
 Connection Type – Select one of the types of RFC connections as per requirement.
 Description – The descriptive information about the RFC connection.
Step-4: “Technical settings” tab opened for edit mode. Enter the target host and system
number and click on “Save” button.

Step-5: Click on “logon & Security” tab, Enter the logon details.
 Language – Specifies the target system's language.
 Client – Specifies the target system's logon client.
 User ID and Password – Specifies the userid and password to login on the target
system.
 Trust Relationship – Specifies the connection is trusted or not. If specified as trusted,
then opt it as “Yes”.
Step-6: Click on “Save” button. RFC connection is ready to use.
Step-7: Once the RFC established, we need to test the connection is established or not. Click
on “Utilities --> Test --> Authorization test”.

If status bar has no errors, Remote Function Call established successfully.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy