Kontakt

Ansicht
Dokumentation

ABENRFC_SM59 - RFC SM59

ABENRFC_SM59 - RFC SM59

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Defining Remote Destinations

RFC destinations are defined in the table RFCDES. This table contains the logical destinations for remote function calls (RFCs).

The table RFCDES cannot be maintained directly.

The logical destinations can be maintained in the following ways:

  • Transaction SM59 or the menu path
Tools → Administration, Administration → Network → RFC Destinations
  • Using the Implementation Guide (IMG):
Choose Tools → Business Engineering → Customizing, Implementation Projects → SAP Reference IMG
In the hierarchy structure of the IMG, choose
Cross-Application Components
Distribution (ALE)
Communications
Define RFC Destination

Each time a remote function is called, the remote system must be specified in the addition DESTINATION.

The following information is required:

  • Technical settings
  • Connection type (TCP, SNA, ...)

  • Remote system

  • Destination

  • Load distribution in a server group (optional)

  • Name of the SAP target system (if load balancing used)

  • Target host (if load balancing not used)

  • Instance number

  • Security options
Trusted system?
  • Description of the logical destination
  • Logon information for the user in question
  • User

  • Client

  • Password

  • System language

The names of the users who created and last changed the entry are displayed, along with a time stamp.
The remote system details must be specified for the system to create an entry in the table RFCDES.
In remote function call, the user, client, and password fields are read from the RFC destination information to log onto the remote system.
For RFC communication with different clients and users, a correct password must be entered for each separate user.
If the language, client, and user fields are not filled for the RFC destination, the entries from the system table are used as default values.

Notes

  • The logon fields do not need to be filled in the case of RFC communication within the same AS ABAP with the same client and user. In this case, no password needs to be specified either.
  • If RFC is in dialog mode (not in background mode) and the RFC logon fails, an RFC logon screen is displayed allowing logons to the remote system 'by hand'.
The RFC logon screen is not displayed if the first function module to be called belongs to the system-specific function pool SRFC. This function pool includes function modules such as RFC_PING, RFC_SYSTEM_INFO, and RFC_LOGIN.
If an RFC logon window is required anyway, RFC communication to the RFC destination in question must be closed after this call using the function module 'RFC_CONNECTION_CLOSE'.
No logon screen is displayed if trusted/trusting systems are used.





Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4762 Date: 20240419 Time: 164705     sap01-206 ( 55 ms )