How To Fix SRET123 - Note that the SSR can have multiple RFC destinations

SRET123 - Overview

• Message type: E = Error

• Message class: SRET - SAP Retrieval : Administration - Indexing - Search

• Message number: 123

• Message text: Note that the SSR can have multiple RFC destinations

What causes this issue?

A Search Server Relation has at least 2 RFC destinations: one for the
search and one for indexing. Normally these are identical.

How to fix this error?

Technically it is possible to separate the search from the indexing. If
you do not want to separate them, both RFC destinations of the Search
Server Relation have to be changed.
The RFC destination for indexing is marked with an 'I' in the 'Action'
field.
The RFC destination for the search is marked with an 'S'.
You should only change the RFC destination if it is necessary for
technical reasons and the administrator is familiar with the system.
If you changed the RFC destination for the search, you should also
change the RFC destination for indexing. Both RFC destinations must
(should) be identical. This is also true if you changed an RFC
destination for indexing.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRET123 - Note that the SSR can have multiple RFC destinations ?

  The SAP error message SRET123 typically indicates an issue related to the System Landscape Directory (SLD) or the SAP Router configuration, particularly when dealing with Remote Function Calls (RFC) in a system landscape that involves multiple RFC destinations.
  
  Cause:
  
  RFC Destination Issues: The error may arise if the RFC destination is not correctly configured or if there are multiple RFC destinations that are not properly set up.
  Network Issues: There could be network connectivity problems between the SAP systems involved.
  Authorization Issues: The user or service account used for the RFC connection may not have the necessary authorizations.
  Configuration Errors: Incorrect settings in the SAP system or in the SLD can lead to this error.
  Multiple SSRs: If there are multiple System Service Requests (SSRs) configured, it may lead to confusion in routing the requests.
  
  
  Solution:
  
  
  Check RFC Destinations:
  
  Go to transaction SM59 and verify the configuration of the RFC destinations. Ensure that they are correctly set up and