Show TOC

Procedure documentationGenerate RFC Connections Locate this document in the navigation structure

 

RFC connections to the component systems are a prerequisite for the following Solution Manager functions:

  • Generate Project IMGs in the Project Administration

  • Go to the managed systems in the Configuration phase

  • Customizing Synchronization (Synchronization Group Editor, Customizing Scout, Customizing Distribution)

  • Read system data via the Service Data Control Center

  • Managing Business Function Sets and Business Functions in the Switch Framework Cockpit

  • Monitor change requests (Change Request Management)

You can only generate RFC connections for ABAP-based main instances.

Prerequisites

  • You are authorized to logon to the target system and create a user there. You are also authorized to create RFC connections of type Trusted System connection, in the local and target systems, if required.

  • The managed systems are reachable.

  • The message servers are reachable under the name and system number specified in the Header Data tab.

  • If you use routers, or you must specify the Distributed Name Service name (DNS name) to generate an RFC connection, in your network, the generation of RFC connections has the following prerequisites:

    • You have created the managed system message server as a server, in the Solution Manager System Landscape, and specified routing information for it.

    • You have specified this server as the message server when you created its system.

  • You are in the Solution Manager System Landscape transaction (SMSY), and have saved your last change.

  • The system for which you want to generate RFC destinations is not flagged as Planned.

Procedure

You can:

Result

The system shows the RFC connections generated, on the Clients tab.

Give the users which RFC connections to the managed systems want to use, the appropriate authorization in the managed systems and in the Solution Manager system. Recreate the authorization profile, if necessary. For further information about the authorization objects and profiles required, see: