Get Example source ABAP code based on a different SAP table
Warning: Undefined variable $prev in /customers/b/9/9/trailsap.com/httpd.www/sap-help/index.php on line 54
SECRET ARTICLE
Defining Remote Destinations You maintain remote destinations in table RFCDES. This table contains the logical destinations for remote function calls (RFCs). You cannot maintain table RFCDES directly. You can maintain the logical destination in the following ways:
Using the Implementation Guide (IMG): Choose Tools -> Business Engineering -> Customizing, Implement. projects -> SAP reference IMG In the hierarchy structure of the IMG, choose Cross-application components Distribution (ALE) Communication Define RFC destination Each time you call a remote function, you must specify the remote system in the DESTINATION addition. 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 sytsem (if you specified load distribution) - Target host (if you are not using load distribution) - Instance number
Security options Trusted System?
Description of the logical destination
Logon information for the user - User - Client - Password - Logon language The system displays the name of the users who created and last changed the entry, along with a timestamp. You must enter the remote system details in order for the system to create an entry in table RFCDES. In a 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 you must enter a correct password for each separate user. If you have not filled out the language, client, and user fields for the RFC destination, the sytsem uses the entries from the system table as default values.
Notes
You do not need to fill out the user details or password for RFC communication between application servers in the same ABAP system and client with the same user.
If you are running the RFC in dialog mode (but not in background mode) and the RFC logon fails, the system displays an RFC logon screen, allowing you to log onto 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 group SRFC. This function group includes function modules such as RFC_PING, RFC_SYSTEM_INFO, and RFC_LOGIN.
If you still want an RFC logon screen to be displayed, you must use the function module 'RFC_CONNECTION_CLOSE' to end the RFC communication with the relevant RFC destination.
No logon screen is displayed when you use trusted and trusting systems.
