Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member182675
Contributor

In this article I present the collection explanations to understand in a simple way the systems and the differences between them

Data can be transfer between two R/3 Systems reliably and safely via transactional RFC

The called function module is executed exactly once in the RFC server system

The remote system need not be available at the time when the RFC client program is executing a RFC

The tRFC component stores the called RFC function

together with the corresponding data in the R/3 database, including a unique transaction identifier (TID)

When you attempt to process the transaction, the system checks whether that TID has already been processed

If it has, the transaction is ignored

If call is sent and the receiving system is down the call stay in the local queue

until the receiving system will up When you use TRFC

you cannot guarantee the order in which the function calls will be processed in the system

For cases where you need order you can use queued RFC which is an extension of transactional RFC

you place each function call in a logical queue

A function call cannot be executed until all of its predecessors in the queue have been processed.

Queued RFC calls are processed asynchronously

Every RFC request used a dialog work process on the application server on which the RFC is executed.

The different between TRFC and QRFC

Transactional RFC

Transactional RFC guarantees the following attribute

The call is executed exactly once in the target system When you use TRFC

you cannot guarantee the order in Which the function calls will be processed in the system

Queued RFC qRFC with Outbound Queue

In order to guarantee order which the function calls will be processed in the system used the qRFC

the qRFC used queues, A LUW is only transferred if it has

no predecessor (in reference to the sequence defined in the applications) in the participating queues

After a qRFC transaction is executed, the system attempts

to start the next qRFC transaction in the sequence from the queue

Sap Note

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

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

http://scn.sap.com/thread/136963

http://help.sap.com/saphelp_nwpi711/helpdata/en/f0/02a63b9bb3e035e10000000a114084/content.htm

Best Regards

Naor Shalom

2 Comments
Labels in this area