RFC
RFC-based integration connects programs and systems to SAP by calling function modules remotely, the classic foundation for SAP-to-SAP and program-level integration, including from external languages via connectors.
Use RFC for SAP-to-SAP and program-level integration where you call specific functions/BAPIs, choosing tRFC/qRFC for reliability.
- RFC integration invokes SAP function modules/BAPIs remotely, synchronously or (via tRFC/qRFC) reliably and asynchronously.
- Sync/async/transactional/queued RFC types.
- Watch out: Wrong tool for the integration style.
What RFC integration does
RFC integration invokes SAP function modules/BAPIs remotely, synchronously or (via tRFC/qRFC) reliably and asynchronously. External systems use SAP connectors (JCo for Java, NCo for .NET) to call SAP over RFC. It is powerful and low-level, and underpins much classic integration.
Key aspects
- RFC destinations (SM59).
- Sync/async/transactional/queued RFC types.
- Connectors (JCo/NCo) for external callers.
- Security: least-privilege users, secured gateway.
When to use it
Use RFC for SAP-to-SAP and program-level integration where you call specific functions/BAPIs, choosing tRFC/qRFC for reliability. Cloud scenarios increasingly wrap this in APIs, but RFC remains vital in classic/hybrid landscapes.
Common pitfalls
- Wrong tool for the integration style.
- Ignoring monitoring/error handling.
- Point-to-point instead of governed integration.