topic TRFC and Asynchronous RFC in Application Development and Automation Discussions

TRFC and Asynchronous RFC

Former Member — Mon, 16 Jun 2008 06:31:54 GMT

Is there any diff between TRFC and ARFC ?

Is TRFC another name for ARFC?

Re: TRFC and Asynchronous RFC

Former Member — Mon, 16 Jun 2008 06:34:56 GMT

Hi,

Refer the help

http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm

https://forums.sdn.sap.com/click.jspa?searchID=12915179&messageID=4209768

Regards

Kiran Sure

Re: TRFC and Asynchronous RFC

prasanth_kasturi — Mon, 16 Jun 2008 06:36:06 GMT

Hi,

Transactional RFC (tRFC) they are previously known as ARFC

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.

regards

prasanth

Re: TRFC and Asynchronous RFC

Former Member — Mon, 16 Jun 2008 06:47:30 GMT

I checked all the previous threads bfore posting.. but still i didnt find difference between the two:

both have the following similarities:

1. the remote system may or may not b available at the time remote fn. is called

2. parallel processing

Re: TRFC and Asynchronous RFC

Former Member — Mon, 16 Jun 2008 06:49:23 GMT

Hi SRK,

Please check this link

http://help.sap.com/saphelp_nw2004s/helpdata/en/62/73241e03337442b1bc1932c2ff8196/content.htm

tRFC and qRFC

The transactional RFC and the qRFC use the resource check. The associated ABAP language elements for both RFC types is:

CALL FUNCTION Remote function IN BACKGROUND TASK DESTINATION destination

With a preceding additional function call (TRFC_SET_QIN_PROPERTIES or TRFC_SET_QUEUE_NAME) tRFC can be defined as qRFC.

This ABAP command flags the function module remote function for asynchronous processing. The module is not executed immediately. The data transferred with EXPORTING or TABLES is placed in a database table. A COMMIT WORK then triggers the function module. There are various cases:

● The data is updated. If tRFC/qRFC has been triggered within the update, these are executed in parallel after the V1 update (within the update). If the tRFC/qRFC call is registered in the scheduler, the scheduler is simply triggered within the update. The execution of tRFC/qRFC takes place outside the update through the scheduler.

● The data is not updated. The tRFC/qRFC function modules started within the application LUW are executed in parallel as far as possible. If local system resources are exhausted, the tRFC/qRFC is serialized so as not to further increase resource utilization. However, this is not the case if the tRFC/qRFC function modules are processed in batch. If the tRFC/qRFC have been started in batch, they are always processed in parallel as in the update process, regardless of the system resource utilization.

No resource checks are run with RFC calls from the update process or batch, since these must always be processed in parallel to avoid deadlocks.

Best regards,

raam