{"id":145,"date":"2011-07-22T18:08:58","date_gmt":"2011-07-22T18:08:58","guid":{"rendered":"http:\/\/sapsecurityanalyst.com\/WP\/?page_id=145"},"modified":"2015-05-03T08:15:56","modified_gmt":"2015-05-03T08:15:56","slug":"remote-function-calls","status":"publish","type":"page","link":"https:\/\/sapsecurityanalyst.com\/WP\/general-disclaimer\/remote-function-calls\/","title":{"rendered":"RFC"},"content":{"rendered":"

<\/span><\/p>\n


\nCommunication between systems in an SAP environment can be between two SAP Systems or between an SAP system and a non-SAP system. Remote Function Call (RFC) is used for communication between two SAP Systems. \u00a0An RFC can also be used for communication within a system.\u00a0<\/span><\/p>\n

 <\/p>\n


\n RFC is an interface based on CPI-C (Common Programming Interface for Communication<\/strong>) protocol.<\/span>
\n<\/span><\/p>\n

<\/p>\n

 <\/p>\n

Describe the synchronous and asynchronous communication:<\/span><\/h3>\n


\n<\/strong>
\nCommunication Types:<\/span><\/span>
\n<\/strong>
\n(a) Synchronous Communication:<\/strong>\u00a0Synchronous Communication is implemented where there is a need for immediate return of data (response) from the receiving system to the sender system. The receiving system should be active at the time this communication is made so that it can process the function call at that very time.<\/span><\/span><\/p>\n


\nThis communication is very helpful when real-time response is required from the destination system.<\/span><\/p>\n

<\/p>\n

 <\/p>\n

(b) Asynchronous Communication: <\/strong>In Asynchronous Communication, the receiving system may or may not be available to receive the function call request made from the sender system. The function call can be processed at a later time when the receiving system gets available. Till that time the function call remains in an outbound queue of the sending system and the call is repeated at regular intervals until the receiving system gets available to process the request.<\/span><\/span><\/p>\n

 <\/p>\n


\n<\/span><\/p>\n

The advantage of this communication is that the receiving system need not be available all the time to process the request especially in cases where the receiving system is temporarily unavailable due to upgrade.\u00a0<\/span><\/p>\n

<\/p>\n

 <\/p>\n


\n<\/strong>Types of RFCs:<\/span><\/span><\/h3>\n


\n
\nBased on Types of Communication:<\/span><\/span>
\n<\/strong>
\n(a) Synchronous RFC<\/span>:<\/span><\/strong> This RFC is based on Synchronous Communication which means both the source system and destination system involved must be available at the time function call is made.<\/span><\/span><\/p>\n


\n<\/span><\/p>\n


\n(b) Transactional RFC (tRFC):<\/span><\/strong> This RFC is also known as Asynchronous RFC and is based on Asynchronous Communication Method. The remote system need not be available at the time tRFC is executed.<\/span><\/span><\/p>\n


\n<\/span><\/p>\n


\n
\nNext \u00a0RFC Authorization Concepts<\/span><\/a><\/em><\/span><\/span><\/span><\/h3>\n

 <\/p>\n


\n