17.08.2013 Views

Data Interfaces

Data Interfaces

Data Interfaces

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

External RFC Program: Client<br />

© SAP AG<br />

RfcOpen(...);<br />

...<br />

RfcCall(...);<br />

...<br />

RfcReceive(...);<br />

...<br />

RfcCall(...);<br />

...<br />

RfcReceive(...);<br />

...<br />

RfcClose(...);<br />

}RfcCallReceive (...);<br />

The above program is an RFC client program, i.e. it initiates a communication and connects to the RFC<br />

server program.<br />

RfcOpen sets up a connection to the partner system (INIT, ALLOCATE, LOGON). You are then<br />

logged on to the SAP system.<br />

RfcCall calls a function module (SAP system) or a function (external system) and transfers parameters<br />

and tables.<br />

RfcReceive allows you to receive replies after RfcCall has been called. RfcReceive waits until a reply<br />

has been received.<br />

Instead of RfcCall and RfcReceive, you can use a function called RfcCallReceive.<br />

RfcClose closes the conversation with the partner system.<br />

Between a CALL and a RECEIVE you can always use a RfcLists. This tells you whether a function has<br />

been processed or whether the connection is still open.<br />

You pass connection parameters via RfcOpen (at least the client, user name and password) or a side<br />

information file. From Release 3.0, you should use saprfc.ini as the side information file. You can also<br />

use the following features:<br />

--> Addressing R/3 via load balancing (specify the message server)<br />

--> An external server program can be registered at an SAP gateway<br />

(--> Demon). This saves the start time usually required (performance option).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!