Skip to content
IT Canvass
SAP APIs · Lesson

RFC

Quick answer

RFC is the go-to for SAP-to-SAP and program-level integration and remains vital, though cloud integration increasingly layers OData/APIs on top.

Key takeaways

  • RFC allows a function module in one system to be called from another (or from an external program via SDKs/connectors) as if local.
  • External systems use RFC through SAP connectors/SDKs (e.
  • Synchronous (sRFC): caller waits; both systems up.
  • Watch out: Wrong RFC type for reliability needs.

What RFC is

RFC allows a function module in one system to be called from another (or from an external program via SDKs/connectors) as if local. It underpins BAPIs, ALE/IDoc distribution, and countless interfaces. Destinations (SM59) define how to reach the target system.

RFC types

  • Synchronous (sRFC): caller waits; both systems up.
  • Asynchronous (aRFC): fire-and-forget.
  • Transactional (tRFC): guaranteed once, survives outages.
  • Queued (qRFC): ordered, guaranteed, for interfaces.

RFC in integration

External systems use RFC through SAP connectors/SDKs (e.g. the SAP JCo for Java, NCo for .NET) to call BAPIs/RFMs. Reliable interfaces use tRFC/qRFC so messages are not lost or reordered. RFC destinations and their security (least-privilege service users, secured gateway) are central.

When to use it

RFC is the go-to for SAP-to-SAP and program-level integration and remains vital, though cloud integration increasingly layers OData/APIs on top. Understanding RFC is essential for classic and hybrid landscapes.

Common pitfalls

  • Wrong RFC type for reliability needs.
  • Insecure destinations/gateway.
  • No error handling for unreachable systems.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. Which statement is true of RFC?

    • A. SAP can be deployed in several ways, on-premise, private cloud, public cloud, or hybrid, and the model you…
    • B. It underpins BAPIs, ALE/IDoc distribution, and countless interfaces.
    • C. An authorization profile is the generated set of authorizations that actually gets assigned to a user…
    Show answer

    B. It underpins BAPIs, ALE/IDoc distribution, and countless interfaces.

    Covered in the “What RFC is” section of this lesson.

  2. Which of these also applies to RFC?

    • A. Destinations (SM59) define how to reach the target system.
    • B. Over-fetching data without $filter/$top.
    • C. Row loops in SQLScript instead of set operations.
    Show answer

    A. Destinations (SM59) define how to reach the target system.

    Covered in the “What RFC is” section of this lesson.

  3. Which part of the Learn SAP curriculum covers RFC?

    • A. SAP installation
    • B. SAP APIs
    • C. SAP navigation
    Show answer

    B. SAP APIs

    This lesson sits in the SAP APIs section of the Learn SAP course.

Frequently asked questions

What does RFC stand for, and how is it used in SAP APIs?

RFC (Remote Function Call) is the protocol that lets programs call SAP function modules remotely, the foundation beneath BAPIs and much SAP integration, connecting SAP to SAP and to external systems.

What connects to RFC in SAP APIs?

RFC is the go-to for SAP-to-SAP and program-level integration and remains vital, though cloud integration increasingly layers OData/APIs on top.

What else is worth knowing about RFC?

RFC allows a function module in one system to be called from another (or from an external program via SDKs/connectors) as if local.

What tends to go wrong with RFC in SAP APIs?

Wrong RFC type for reliability needs. Insecure destinations/gateway. No error handling for unreachable systems.
CallWhatsAppEnquire