In short
RFC stands for Remote Function Call: calling a function remotely. In SAP, a lot of logic lives in function modules, small programs that do something like "give me the data for this customer" or "create an order". If such a function module is marked as remote-enabled, another system can call it via RFC: another SAP system, a .NET or Java application, or an integration platform. That makes it an RFC function module.
How does it work
- The calling side uses an SAP connector, such as NCo for .NET, JCo for Java or PyRFC for Python.
- The connection is recorded as an RFC destination, with server, system number and a user.
- The function module receives input, does its work in SAP and returns output and messages.
Types of RFC
- Synchronous (sRFC): the caller waits for the answer. The most widely used.
- Asynchronous (aRFC): the caller does not wait.
- Transactional (tRFC) and queued (qRFC): the call is executed exactly once, even if the connection drops briefly; qRFC also preserves the order.
When do you use RFC
- For direct, fast integrations with an SAP system in your own network.
- When a suitable function module or BAPI already exists.
- For custom functions that do exactly what your integration needs.
What to watch out for
- Give the technical user only the authorisations it needs.
- RFC is an SAP-specific protocol. For apps and web environments, OData is often the more obvious choice.
- In SAP's cloud editions, the options for RFC are limited; there you mainly work with released APIs.
Would you like advice on SAP RFC? Request a free advice conversation.
Updated on