How To Fix /EACC/LOCAL_INTEGRTY002 - System cannot be reached under RFC destination &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /EACC/LOCAL_INTEGRTY -

• Message number: 002

• Message text: System cannot be reached under RFC destination &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /EACC/LOCAL_INTEGRTY002 - System cannot be reached under RFC destination &1 ?

  The SAP error message /EACC/LOCAL_INTEGRTY002 System cannot be reached under RFC destination &1 typically indicates that the system is unable to connect to a specified RFC (Remote Function Call) destination. This can occur for various reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Network Issues: There may be network connectivity problems between the SAP system and the target system defined in the RFC destination.
  Incorrect RFC Destination Configuration: The RFC destination may be incorrectly configured, including wrong hostnames, IP addresses, or ports.
  Authorization Issues: The user credentials used for the RFC connection may not have the necessary authorizations to access the target system.
  Target System Down: The target system may be down or not available for some reason (maintenance, crashes, etc.).
  Firewall Restrictions: Firewalls may be blocking the connection to the target system.
  SAP Gateway Issues: The SAP Gateway service may not be running or may be misconfigured.
  
  Solutions:
  
  
  Check Network Connectivity:
  
  Use tools like ping or telnet to check if the target system is reachable from the SAP system.
  Ensure that there are no network outages or issues.
  
  
  
  Verify RFC Destination Configuration:
  
  Go to transaction SM59 in the SAP GUI.
  Check the configuration of the RFC destination (e.g., hostname, service, and connection type).
  Test the connection using the "Connection Test" button in the RFC destination configuration.
  
  
  
  Review User Credentials:
  
  Ensure that the user credentials used for the RFC connection are correct and have the necessary authorizations.
  Check if the user is locked or has expired credentials.
  
  
  
  Check Target System Status:
  
  Verify that the target system is up and running.
  If possible, check the logs of the target system for any errors.
  
  
  
  Firewall and Security Settings:
  
  Ensure that firewalls are configured to allow traffic between the SAP system and the target system.
  Check for any security policies that might be blocking the connection.
  
  
  
  SAP Gateway Configuration:
  
  Ensure that the SAP Gateway service is running on the SAP system.
  Check the gateway logs for any errors that might indicate issues with the connection.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: To manage RFC destinations.
  SMGW: To monitor the SAP Gateway.
  SICF: To check and manage HTTP services.
  
  
  
  Logs and Traces:
  
  Check the system logs (SM21) and developer traces (ST22) for any related error messages.
  Use transaction SLG1 to check application logs for more detailed error information.
  
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to RFC connections.
  
  
  By following these steps, you should be able to diagnose and resolve the issue related to the /EACC/LOCAL_INTEGRTY002 error message. If the problem persists, consider reaching out to your SAP Basis team or SAP support for further assistance.