Procedure documentationCreating RFC Destinations in the Central System

 

Each Target System requires an RFC destination in the Central System. Follow this procedure to create and test the RFC destinations.

Prerequisites

Each Target System should have one system user, with the required authorization profile, who is designated for the purpose of PAL communication.

Procedure

Log on to the central system and select Start of the navigation path Administration Next navigation step System Administration Next navigation step Administration Next navigation step Network Next navigation step RFC Destinations End of the navigation path or enter transaction code SM59. Check first whether there are already RFC destinations for your Target Systems.

Note Note

RFC destinations which will be used for PAL must have connection type 3 (ABAP connection).

End of the note.

Create an RFC destination for each target system. The overall procedure is described in the Application Help: Entering Destination Parameters. For PAL, there are a few details to be taken into account:

Select Logon & Security. Go to section Logon.

  • Enter the system user created before in the Target System (see section Prerequisites below) for this RFC destination.

  • Do not use the Current User option.

  • We recommend that you leave the input field Language empty. The logon language of the user in the Central System to be used for the RFC communication with the Target System will be selected automatically then. If you specify a logon language in the RFC destination, this language will be used for all messages from the Target System later on in PAL.

  • Enter a password and save it.

Result

The RFC destinations to your Target Systems are created and saved. Before you go on, you should:

  • Perform a connection test for each RFC destination.

  • Perform a remote logon test for each RFC destination.

General information about remote destinations: Maintaining Remote Destinations