Show TOC

 RFC Settings


The Service Data Control Center uses RFC (Remote Function Call) destinations to communicate with other SAP systems. At least one RFC destination must be defined for the Service Data Control Center to work.


To change the RFC settings for the Service Data Control Center:

  1. Choose Start of the navigation path Goto Next navigation step Settings Next navigation step Task-specific End of the navigation path .

    A hierarchy of task-specific settings is displayed.

  2. Choose Start of the navigation path Task-specific settings Next navigation step Session Data Collection Next navigation step RFC Destinations Next navigation step Settings End of the navigation path .

  3. To display the RFC settings, click the Settings icon.

    A dialog box is displayed, with the tabs General and Destinations .

  4. To change the settings, choose Display <-> Change .

    The individual settings are described below.

  5. To save your changes, choose Continue .


Data can be sent as multiple packets or as a single packet.

It is recommended that you send the session data as multiple packets. If you have more than one server, each packet sent will contain the session data from one server.

If the session data is sent as a single packet, all the session data will be sent with one RFC call. This one packet will contain the session data from all the servers for which data was collected.

The block size is set by default to 320000, which should be appropriate for most situations.

You can define how long the system will wait in the event of a connection failure before attempting to reestablish the connection, and the number of attempts it will make before the connection is terminated.


Destination : The RFC destinations maintained in Service Data Control Center.

The Service Data Control Center uses the RFC destination SDCC_OSS to communicate with the SAPNet R/3 frontend. A task can communicate with the system it is running in through the RFC destination NONE; ; if this is the case, the system ID, and the installation number will be for the task's local system.

SID, Installation no. : The system ID (SID) and installation number are from the system that the RFC destination points to.

Master : The master SAP Solution Manager system is indicated in the ‘ Master ’ column.

The service definitions are taken from the master system. To ensure that the service definitions remain consistent, there can only be one master SAP Solution Manager system. If no master system is defined, the service definitions will be taken from the SAPNet R/3 frontend.

To SAP : The ' To SAP ' column indicates the active destinations to the SAP service system.

Only active destinations that are defined in transaction SM59 can be used for Service Data Control Center tasks.

To test a destination : Select a destination and choose ' Test RFC destination '.

This will send a small packet of data to the destination and wait for a reply. It will also check that the authorizations are sufficient.

To add or remove a destination from the list:

To remove a destination, select it and choose ‘ Remove RFC destination ’.

To add a new destination, choose ‘ Add RFC destination ’.

Note Note

The RFC destinations that point to SAP Solution Manager systems were generated automatically by the SAP Solution Manager Landscape (transaction SMSY). This procedure automatically makes the RFC destinations of SAP Solution Manager systems known to the Service Data Control Center.

If you are working with an older release of the SAP Solution Manager, you may need to create your own RFC destination. If you want the SAP Solution Manager to collect data from the system it is running in, you need to add the RFC destination NONE to this list.

End of the note.

Create Destination to SAPNet R/3 Frontend : Creates a new RFC destination by copying the existing SAPOSS destination to a new RFC destination, called SDCC_OSS. The new destination will point to SAP. A new user will be used, SDCC_NEW, with the password download .

The new RFC destination will be automatically displayed in the destinations overview.

Repairing RFC Destinations

If the existing SAPOSS destination does not point to SAP, it will not be possible to copy it. To resolve this issue, you must first repair the SAPOSS destination and then copy it to a new SDCC_OSS destination.

For more information, see SAP Note 812386 (RFC Connections to the SAPNet R/3 Frontend)

When the SAPOSS destination has been repaired, you can restart the copy procedure in the Service Data Control Center in the systems, in which copy failed.

See also:

SDCCN management in SAP Solution Manager

RFC Destinations

SAP Note 812386 (RFC Connections to the SAPNet R/3 Frontend)

If you are unable to work with transaction SMSY: SAP Note 824521 (SDCCN: Authorizations or RFC destinations are missing)

SAP Note 763561 (Service Data Control Center (SDCCN) - FAQ)