SM59
Quick answer
SM59 maintains RFC destinations, the definitions of how SAP connects to other SAP and external systems for remote calls, and tests those connections.
Key takeaways
- Destination name and connection type (ABAP, TCP/IP, HTTP).
- Target host/system and connection parameters.
- Logon: service user and credentials (or trusted).
- Watch out: Using the wrong variant (create vs change vs display).
Purpose
It maintains RFC destinations, the definitions of how SAP connects to other SAP and external systems for remote calls, and tests those connections.
Key fields and screen
- Destination name and connection type (ABAP, TCP/IP, HTTP).
- Target host/system and connection parameters.
- Logon: service user and credentials (or trusted).
- Connection and authorization test buttons.
Tips
- Use least-privilege service users, not broad dialog users.
- Test the connection (and authorization) after any change.
- After a system copy, correct destinations that point at the source.
Common errors
- Connection failed (host/port/network).
- Logon failed (wrong credentials/user locked).
- Authorization missing in the target system.
Common pitfalls
- Using the wrong variant (create vs change vs display).
- Missing prerequisite master data or authorization.
- Not checking the resulting document/log.
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
Which statement is true of SM59?
- A. The delivery document in SD manages the outbound movement of goods to the customer, picking, packing and…
- B. File-based integration (often over SFTP) exchanges data as files, a simple, widely-supported, asynchronous…
- C. Connection and authorization test buttons.
Show answer
C. Connection and authorization test buttons.
Covered in the “Key fields and screen” section of this lesson.
Which part of the Learn SAP curriculum covers SM59?
- A. SAP release notes
- B. SAP TCodes
- C. SAP HANA
Show answer
B. SAP TCodes
This lesson sits in the SAP TCodes section of the Learn SAP course.
Frequently asked questions
What does SM59 stand for in SAP?
SM59 is the SAP transaction code for RFC Destinations (Basis/Integration). It maintains RFC destinations, the definitions of how SAP connects to other SAP and external systems for remote calls, and tests those connections.
What is worth remembering about SM59 in practice?
Destination name and connection type (ABAP, TCP/IP, HTTP). Target host/system and connection parameters. Logon: service user and credentials (or trusted).
What is another point to note about SM59?
Use least-privilege service users, not broad dialog users. Test the connection (and authorization) after any change. After a system copy, correct destinations that point at the source.
What tends to go wrong with SM59?
Using the wrong variant (create vs change vs display). Missing prerequisite master data or authorization. Not checking the resulting document/log.