RFC between 2 sap systems

[Former Member]

Hi,

can anyone tell me how to implement RFC between two

SAP systems?

[Former Member]

For setting up an RFC you should have a remote enabled Funtion module in the target system.You should be setting the RFC destination in the calling system through SM59,and your FM call should have an addition of value Destination followed by the RFC entity created in SM59.Hope this helps.

Regards,

Kiran

[Former Member]

hi

hope it will help you.

Reward if help.

RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;

and you will be passing an Import parameter DESTINATION to it.

Other code and usage will be similar to any fun module;

Have a look at any fun module in SE37 to understand better about the different components of Fun modules;

Refer this link:

http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm

check out the following link it might help you

http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf

[Former Member]

For setting up an RFC you should have a remote enabled Funtion module in the target system.You should be setting the RFC destination in the calling system through SM59,and your FM call should have an addition of value Destination followed by the RFC entity created in SM59.Hope this helps.

Regards,

Kiran

[Former Member]

u can use transaction sm59 ...enter the logon and the ip address of the connecting server ...

reward points if useful

[dhruv_shah3]

Hi,

We can cerate RFC connection within the system between the clients and between the systems and its client .

Go to sm59 click on create button, specify the RFC destination (which is target client logical system name),specify the connection type 3(r3 connection),specifie the discription,click on tecnichal settings tab define the target system GATEWAY HOST,GATE WAY SERVICE (SAP GW <SYSTEM NO>),

click on LOGON SECURTY tab specify target client no, user id, pw.(user type is communication user)SAVE .

Do the test connection if any errors occure solve it as per the log.

Same thing you have to perfom at target system.

In the place of communication user if you specify the dilogue user you can remotely log in to target system and you can work on it.

HTH

Regards,

Dhruv Shah

[Former Member]

Hi ,

RFC Purpose

Communication between applications of 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. The 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, which means that the systems involved must both be available at the time the call is made.

Transactional RFC (tRFC)

Transactional RFC (tRFC, also originally known as asynchronous RFC) is an asynchronous communication method that executes the called function module in the RFC server only once. 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 until a later time. The calling dialog program can proceed without waiting to see whether or not 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

· 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 guarantee that the transactional order of the calls is preserved.

Disadvantages of tRFC

· tRFC processes all LUWs independent 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. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee 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 (in reference to 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.

RFC: Data Transfer

All RFC types are transferred by means of CPI-C or TCP/IP. They constitute a form of gateway communication.

http://help.sap.com/saphelp_46c/helpdata/en/22/0424fe488911d189490000e829fbbd/frameset.htm

Regds

Eshwar

Please reward points if helpful...