Scribd
Upload
22 views1 page

RFC Connections

Remote Function Call (RFC) in SAP ABAP enables communication between SAP and external systems through various types, including Synchronous, Asynchronous, Transactional, and Queued RFCs. Synchronous RFC provides reliable two-way communication, while Asynchronous RFC lacks acknowledgment, making it less reliable. Transactional RFC ensures consistency with Transaction IDs, and Queued RFC maintains transaction order and reliability through FIFO processing.

Uploaded by

Ayoub Essadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
22 views1 page

RFC Connections

Remote Function Call (RFC) in SAP ABAP enables communication between SAP and external systems through various types, including Synchronous, Asynchronous, Transactional, and Queued RFCs. Synchronous RFC provides reliable two-way communication, while Asynchronous RFC lacks acknowledgment, making it less reliable. Transactional RFC ensures consistency with Transaction IDs, and Queued RFC maintains transaction order and reliability through FIFO processing.

Uploaded by

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

Remote Function Call (RFC) is a powerful feature in SAP ABAP, enabling communication between SAP

systems, as well as between SAP systems and external systems. RFCs facilitate remote function
execution in a seamless and efficient manner.

RFC is a type of function module used to communicate within sap system and outside of sap system
using the TCP/IP protocol , RFC's can be created under the transaction code SM59, There are few types
of RFC's that are available and they are

1. Synchronous RFC
2. Asynchronous RFC
3. Transactional RFC
4. Queued RFC

Asynchronous RFC:

The best example for Asynchronous RFC is one side love, We don't know whether our message received
or not, Like wise ASRFC's transmission are not reliable

Synchronous RFC:

Synchronous RFC is like a two way communication, Once the message reached system or program will
get an acknowledgement. If the target system is not reliable the communication will get into a sleep
mode and waits until the system is wakened , once the system is available it will starts to flow. This type
of RFC is bit costly when comparing to the other one

Transactional RFC:

This RFC is an advanced version of ARFC and SRFC, The request goes to receiving system if it is not
handled a Transaction ID is generated by the source system. A program RSARFCSE is scheduled in the
background to run for every 60seconds.

These transaction ID's are maintained under SM58 which documents the Transaction ID's and ensures
that reached the recipient system and confirms that the receiver system is consistent and reliable

Example : If a user is created in Main client it will distribute to the client dependent if any thing created
new

Queued RFC:

It is an advanced version of TRF and ensures that the transaction is committed based on FIFO/ Queue. It
ensures transaction consistency of LUW (Logical Units of Work) and reliability of data transmission.

SMQ1 - to monitor the outbound queues of a sending system refer SCOTT for FAX...

SMQ2 - Provides interface to monitor Inbound queues.

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