Data Interfaces

Table RFCDES
© SAP AG
Maintaining RFCDES with Transaction SM59
RFC destinations
R/2 connections
R/3 connections
Internal connections
Logical connections
CMC connections
SNA/CPI-C connections
TCP/IP connections
You edit the table RFCDES with transaction SM59.
+
+
+
+
+
+
+
+
Connections via ABAP/4 driver
The following connection types (partner system/program) are possible:
I Internal: Same SAP system; communication from application server to application server.
( => same database). You cannot maintain this type. When the system is started, the entries are set
automatically.
2 Partner system is an R/2 System.
3 Partner system is another R/3 System => other database.
S Partner is a program which can be accessed via the LU6.2 protocol. No RFC SDKs are yet
available
for these platforms. Such a partner program would have to use hard APPC calls.
L Logical partner:
Reference is to an existing destination. Existing values (e.g. user name and password) can be
overwritte and new values can be added.
M CMC (Common Messaging Call) connection. This destination is designed for an R/3-to-R/3
connection
which uses the standard programming interface CMC for mail systems.
T Partner is an external RFC program based on TCP/IP.
X The RFC data flow can be passed to a self-defined ABAP/4 program
(ABAP/4 CPI-C program).
Similarly, R/2 contains the table RFCD (which references the table XCOM).