Data Interfaces

External RFC Program: Server
© SAP AG
main(...)
{ ...
RfcAccept(...)
...
RfcInstallFunction(...)
...
RfcDispatch(...)
...
RfcClose(...)
}
...
static RFC_RC rfcfunc(...)
...
Data processing
{ RfcGetData(...)
RfcSendData(...)
}
The above example demonstrates how an external RFC server program should be structured.
RfcInstallFunction installs all RFC-enabled functions in this program. You must explicitly declare all
program functions. This allows RfcDispatch to find them.
In addition, RfcInstallFunction automatically declares the following standard library functions:
RFC_SYSTEM_INFO: Returns system information to the calling system.
RFC_DOCU: Documents which RFC functions can be called in the program.
RFC_PING: Checks that the communication path to the program is correct.
RFC_START_GUI: Starts SAPGUI on the frontend.
ARFC_DEST_SHIP,
ARFC_DEST_CONFIRM: Used internally with transactional RFC.
You can call these in R/3 from the menu bar of Transaction SM59 when you display a RFC destination
(system information: target system, function list, test connection)
RfcDispatch waits for a function call for an internal program function and subsequently calls this
function.