Resolve RFC Generation Errors in Solution Manager

Resolve errors

If RFC generation errors occur:

1. The message long texts contain details of the errors.

2. Resolve the errors, if possible. Click on the RFC connection in the Generate RFC Destinations dialog box, or double-click on the RFC connection in the Clients tab, to go to the detail view of the RFC connection in the Edit RFC Destinations transaction. You can test the RFC connection there, and make any changes.

3. You can repeat the generation by deleting the old RFC connection and generating again.

Sources of error/symptoms

The servers of a trusted RFC connection have changed

You want to generate an RFC connection of type Trusted. The following symptoms occur:

• The RFC log shows:

  • The RFC connection was generated outside the Trusted/Trusting RFC connection.

  • Error message: Function group SCCA not found.

  • The RFC generation return code in the RFC log is 1.

• You have satisfied and checked all prerequisites for the RFC connection to work:

  • You have tested the RFC connection in the transaction SM59, and the RFC connection works

  • You have authorization.

  • The authorization S_RFC contains the function group SCCA

Proceed as follows:

1. Delete the RFC destination with the Clean-Up RFC Destinations pushbutton, in the Solution Manager System Landscape transaction (SMSY), in the Solution Manager system.

2. Check the server data in the RFC connection in the component system. If the server data is not correct, delete the RFC destination with Extras Trusting Systems in the transaction SM59 in the component system.

3. Delete the RFC destination with Extras Trusted Systems in the transaction SM59 in the Solution Manager system.

For further information about defining trusted/trusting connections, see Trusted/Trusting between SAP Systems.

User already exists

The generation of the RFC connection can fail because the user specified in the Generate RFC Destinations dialog box already exists in the target system, and cannot be created again. To solve the problem:

• If this user is not otherwise used, you can delete it in the target system, and regenerate the RFC destination.

• Change the user to be created, in the Generate RFC Destinations dialog box, and regenerate the RFC destination.

• If you know the password, or can change it, delete the RFC destination, and regenerate it with the user option Use Existing User, Specify Password.

Insufficient Support Package status

The Support Package status in the component systems must be sufficient. The error log long text tells you the required Support Package status.

Missing authorization

The generated user may not have all necessary authorization in the target system. The generation log indicates this. Assign the required authorization to the generated user in the target system, manually.