RFC
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.
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.
- 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.