You are on page 1of 3

What Does RFC Mean?

I have seen references to RFC-XXXX where XXXX is a number. What does RFC mean? This article has been archived and is no longer updated by Apple. RFC stands for "Request for Comment". This refers to a description of a standard for new or modified internet or networking protocols. When standards are proposed, they are made available for public comment so that they can be refined and agreed upon. The document which details the proposed standards is called a "request for comment" document, or RFC. When the standards are finalized, they keep the same "RFC" name. For example, the RFC which defines the HyperText Markup Language (HTML), the format that web pages are written in, is RFC-1866. See the following: Note: Many of these documents are highly technical and may be difficult to understand without existing knowledge of the subject matter. The most common reason to need to know about a specific RFC is to judge if two components (system software, application software, network hardware or computer hardware) are compatible and interoperable. Generally speaking, if two devices support the same RFCs, then they are most likely interoperable. In case of doubt, contact the manufactuer of the two components. There are many search engines on the Internet that can aid you in finding a particular RFC, such as: The following comes from the RFC Editor, which can be found at: "The Requests for Comments (RFCs) are a series of notes, started in 1969, about the Internet (originally the ARPANET). The notes discuss many aspects of computing and computer communication focusing in networking protocols, procedures, programs, and concepts, but also including meeting notes, opinion, and sometimes humor. The specification documents of the Internet protocol suite, as defined by the Internet Engineering Task Force (IETF) and its steering group (the IESG), are published as RFCs. The RFC Editor is the publisher of the RFCs and is responsible for the final editorial review of the documents."
Communication between applications in different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. RFC calls a function to be executed in a remote system.

Synchronous RFC
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, meaning that the systems involved must both be available at the time the call is made.

Transactional RFC (tRFC) Transactional RFC(tRFC, previously known as asynchronous RFC) is an asynchronous communication method that executes the called function module just once in the RFC server. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID). If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program can proceed without waiting to see whether the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch. tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are executed in the order in which they are called are executed in the same program context in the target system run as a single transaction: they are either committed or rolled back as a unit.

Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.

Disadvantages of tRFC

tRFC processes all LUWs independently of one another. Due to the amount of
activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.

In addition, the sequence of LUWs defined in the application cannot be kept.

It is therefore impossible to guarantee that the transactions will be executed in the sequence dictated by the application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later.
Queued RFC (qRFC) To guarantee that multiple LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).

qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (based on the sequence defined in different application programs) in the participating queues. Implementation of qRFC is recommended if you want to guarantee that several transactions are processed in a predefined order.
Data transfer All RFC types are transferred by means of CPI-C or TCP/IP. They represent a