Service RFC destination is not defined in central configuration

Message type: E = Error

Message class: SRT_ADMIN - Administration Messages for SOAP Runtime

Message number: 010

Message text: Service RFC destination is not defined in central configuration

The service RFC destination for system processes does not exist. To run
properly, Web service runtime requires an RFC destination of type 3
(ABAP connection). You must configure this destination manually before
starting production operation. If you want to use this RFC destination,
you must make a user setting under "Logon & Security". The user entered
here must have the type "Service" and be assigned a password. Both
parameters must be configured in the destination (transaction SM59).


What causes this issue?

The system configuration is missing or incorrect after the system
installation.


System Response

The error is included in the list of ABAP runtime errors (transaction
ST22). The runtime error is assigned to the user SAPSYS and has the
short text CALL_FUNCTION_REMOTE_ERROR.


How to fix this error?

Use the program SRT_ADMIN_CHECK to check whether the error was actually
caused by a missing RFC destination. If so, proceed as follows:
Use transaction SU01 to create a user <user> of the type "Service".
Create a password for this user.
Use the profile SAP_BC_WEBSERVICE_SERVICE_USER as a template for
granting the required profile values and authorizations.
Use transaction SM59 to create an RFC destination <dest>.
You can give the RFC destination <dest> a name of your choice (in
accordance with RFC naming conventions). When you choose a name,
however, make sure it does not conflict with other system services (for
example, business workflow requires one RFC destination for each active
client).
The connection type must be 3.
The user <user> (see above) and its password must be entered under
"Logon & Security"
Start the report SRT_ADMIN, select the "Create Local ABAP Connection"
checkbox, and enter the name of the destination <dest> in the "Name of
ABAP Connection" field. Then run the report.


Procedure for System Administrators

Check whether the report SAPMSSY6 includes the line "perform
submit_report using 'TASK_SYSTEM_START' 30 240". If not, the software
version is not up-to-date. Contact SAP Software Support.

Error message extract from SAP system. Copyright SAP SE.