How To Fix BCOM_R070 - Existence of scenario '&2' on server '&1' cannot be checked

SAP Error Message - Details

• Message type: E = Error

• Message class: BCOM_R - Business Communication: Messages for Rule-Based Routing

• Message number: 070

• Message text: Existence of scenario '&2' on server '&1' cannot be checked

What causes this issue?

Due to an RFC error, the system cannot check whether the scenario &V2&
exists on routing server &V1&.

System Response

If the user wants to delete the scenario from the database, it has to
be deleted from all routing servers first in order to guarantee data
consistency. Therefore, the server is included in the list of servers
that know the scenario, although this cannot be established due to the
RFC error. As a result, the scenario may not be able to be deleted from
the database because it cannot be deleted from this server. Additional
error messages may also be output during the download. The maintenance
of the scenario and the download to other servers that have an
established RFC connection is, however, not affected.

How to fix this error?

Check the RFC connection for server &V1&. If there is a temporary
problem, remove it. If the server is no longer included in the system
landscape permanently, either remove it from the list of servers in
<DS:TRAN.SBCA>SAP routing server administration</>, or delete the flag
'server in use'. The server is then no longer considered in any actions
and, consequently, not contained in the list of servers that know the
scenario.
Warning: If you set this flag for a server that is still actively
included in the system landscape and is to be provided with routing
data, this can lead to problems than cannot be removed from the SAP
System.

Procedure for System Administrators

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 BCOM_R070 - Existence of scenario '&2' on server '&1' cannot be checked ?

  The SAP error message BCOM_R070 indicates that the system is unable to check the existence of a specific scenario on a designated server. This error typically arises in the context of SAP Business Communication Management (BCM) or related components where scenarios are defined for communication processes.
  Cause:
  
  Server Connectivity Issues: The server specified in the error message may be down, unreachable, or there may be network issues preventing the connection.
  Configuration Issues: The scenario may not be properly configured in the system, or it may not exist on the specified server.
  Authorization Issues: The user may not have the necessary permissions to access the scenario on the server.
  System Errors: There could be underlying system errors or inconsistencies in the BCM configuration.
  
  Solution:
  
  Check Server Status: Ensure that the server specified in the error message is up and running. You can do this by pinging the server or checking its status in the SAP system.
  Verify Scenario Configuration: Go to the configuration settings in the BCM and verify that the scenario '&2' is correctly defined and exists on the server '&1'.
  Review Authorizations: Check the user authorizations to ensure that the user has the necessary permissions to access the scenario on the specified server.
  Check Logs: Review the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Restart Services: If the server is operational but the issue persists, consider restarting the relevant services or the server itself.
  Consult Documentation: Refer to SAP documentation or notes related to BCM for any specific troubleshooting steps or known issues related to this error message.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error. You can search for the error message or related keywords in the SAP Support Portal.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  System Monitoring: Implement monitoring tools to keep track of server health and connectivity to prevent future occurrences of this error.
  
  If the issue persists after trying the above solutions, it may be necessary to escalate the problem to your SAP Basis team or SAP support for further investigation.