Skip to content
IT Canvass
SAP administration · Lesson

RFC

Quick answer

RFC is powerful, so it is a security focus: destinations should use least-privileged service users (not dialog users with wide access), the gateway should be secured against unauthorised registered programs, and trusted-RFC relationships must be controlled.

Key takeaways

  • An RFC destination, maintained in SM59, defines how to reach another system: its type (ABAP connection, TCP/IP, HTTP), target host…
  • Create and test destinations in SM59 (there is a built-in connection test).
  • Manage the credentials/users destinations log on with (least privilege).
  • Watch out: Dialog/over-privileged users in RFC destinations.

RFC destinations (SM59)

An RFC destination, maintained in SM59, defines how to reach another system: its type (ABAP connection, TCP/IP, HTTP), target host, and logon credentials. Interfaces, BAPIs called remotely, ALE/IDoc distribution and many integrations all rely on correctly configured destinations.

Administering RFC

  • Create and test destinations in SM59 (there is a built-in connection test).
  • Manage the credentials/users destinations log on with (least privilege).
  • Maintain trusted-system relationships where used.
  • Adjust destinations after system copies (they inherit the source’s settings).

Security is paramount

RFC is powerful, so it is a security focus: destinations should use least-privileged service users (not dialog users with wide access), the gateway should be secured against unauthorised registered programs, and trusted-RFC relationships must be controlled. Insecure RFC is a well-known attack path.

Troubleshooting

RFC failures, connection refused, logon failed, authorization missing, are among the most common integration issues. SM59’s connection test and the target system’s logs usually reveal the cause quickly.

Common pitfalls

  • Dialog/over-privileged users in RFC destinations.
  • Insecure gateway allowing rogue registered programs.
  • Stale destinations after a system copy pointing at the wrong system.

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. The professional certification is an advanced, experience-based credential, validating deep expertise and the…
    • B. Interfaces, BAPIs called remotely, ALE/IDoc distribution and many integrations all rely on correctly…
    • C. ALV (the ABAP List Viewer, now SAP List Viewer) is the standard framework for displaying tabular data in ABAP…
    Show answer

    B. Interfaces, BAPIs called remotely, ALE/IDoc distribution and many integrations all rely on correctly…

    Covered in the “RFC destinations (SM59)” section of this lesson.

  2. Which of these also applies to RFC?

    • A. Learning screens, not the end-to-end process.
    • B. Insecure RFC is a well-known attack path.
    • C. Guessing instead of using the reference tools.
    Show answer

    B. Insecure RFC is a well-known attack path.

    Covered in the “Security is paramount” section of this lesson.

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

    • A. SAP Fiori
    • B. SAP modules hub
    • C. SAP administration
    Show answer

    C. SAP administration

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

Frequently asked questions

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

RFC administration manages the connections (RFC destinations) that let SAP communicate with other SAP and external systems, and secures them. Because RFC underpins most integration, healthy, secure RFC configuration is essential.

What is connected to RFC in an SAP landscape?

An RFC destination, maintained in SM59, defines how to reach another system: its type (ABAP connection, TCP/IP, HTTP), target host, and logon credentials.

What is the practical takeaway on RFC?

RFC is powerful, so it is a security focus: destinations should use least-privileged service users (not dialog users with wide access), the gateway should be secured against unauthorised registered programs, and trusted-RFC relationships must be controlled.

What tends to go wrong with RFC in SAP Basis administration?

Dialog/over-privileged users in RFC destinations. Insecure gateway allowing rogue registered programs. Stale destinations after a system copy pointing at the wrong system.
CallWhatsAppEnquire