How To Fix SCRM900 - RFC destination & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: SCRM - Check Results Management

• Message number: 900

• Message text: RFC destination & does not exist

What causes this issue?

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

System Response

How to fix this error?

This message was issued by the CHECKMAN since no corresponding RFC
destination exists.
You must create an RFC destination adhering to the following
nomenclature: XXX_CHECKMAN.
The first three characters represent the target system - for example,
BCO.
The other 8 characters always represent '_CHECKMAN'
These make up the complete RFC name - for example, BCO_CHECKMAN.
Whether the RFC destination is trusted or trusting can be adapted to
your work rhythm.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCRM900 - RFC destination & does not exist ?

  The SAP error message "SCRM900 RFC destination & does not exist" typically indicates that the system is trying to access a Remote Function Call (RFC) destination that has not been defined in the SAP system. This can occur in various scenarios, such as when trying to connect to another SAP system or an external system.
  Cause:
  
  Missing RFC Destination: The specified RFC destination is not created in the SAP system.
  Incorrect RFC Name: The name of the RFC destination may be misspelled or incorrectly referenced in the code or configuration.
  Authorization Issues: The user may not have the necessary authorizations to access the RFC destination.
  System Configuration: The system may not be properly configured to recognize the RFC destination.
  
  Solution:
  
  
  Create the RFC Destination:
  
  Go to transaction code SM59 (RFC Destinations).
  Check if the RFC destination exists. If it does not, create a new one by clicking on "Create" and filling in the necessary details (e.g., target host, system number, client, user, password, etc.).
  Test the connection to ensure it is working correctly.
  
  
  
  Verify the RFC Name:
  
  Double-check the name of the RFC destination in the code or configuration where it is being called. Ensure that it matches exactly with the name defined in SM59.
  
  
  
  Check Authorizations:
  
  Ensure that the user or the application trying to access the RFC destination has the necessary authorizations. You can check this in transaction SU01 (User Maintenance) and ensure the user has the appropriate roles assigned.
  
  
  
  Review System Configuration:
  
  If the RFC destination is supposed to connect to another SAP system, ensure that the target system is correctly configured and accessible from the source system.
  
  
  
  Check for Network Issues:
  
  If the RFC destination points to an external system, ensure that there are no network issues preventing the connection.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: Manage RFC Destinations
  SU01: User Maintenance
  ST22: Dump Analysis (to check for any runtime errors)
  SM21: System Log (to check for any related logs)
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on configuring RFC destinations and troubleshooting connectivity issues.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address specific issues related to RFC destinations.
  
  
  By following these steps, you should be able to resolve the "SCRM900 RFC destination & does not exist" error in your SAP system.