How To Fix EPIC_BANK_COMM105 - RFC error occurred; system could not send request message

SAP Error Message - Details

• Message type: E = Error

• Message class: EPIC_BANK_COMM - Message Class for BACO PROG

• Message number: 105

• Message text: RFC error occurred; system could not send request message

What causes this issue?

You tried to send a query to a bank communication client. However, the
system has found that there is a problem with the Remote Function Call
(RFC) connection.

System Response

The system generates the request message but is unable to send the
message to the bank communication client.

How to fix this error?

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

Procedure for System Administrators

Check the RFC connection from the <LS>Electronic Payment Integration
(China)</> screen by choosing <LS>Administration</> -> <LS>Check Client
Status</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EPIC_BANK_COMM105 - RFC error occurred; system could not send request message ?

  The SAP error message "EPIC_BANK_COMM105 RFC error occurred; system could not send request message" typically indicates an issue with the Remote Function Call (RFC) communication between SAP systems or between an SAP system and an external system. This error can arise due to various reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  Network Issues: There may be network connectivity problems between the SAP system and the target system.
  Configuration Errors: Incorrect RFC destination configuration in the SAP system can lead to this error.
  Authorization Issues: The user credentials used for the RFC call may not have the necessary authorizations.
  System Downtime: The target system may be down or not reachable at the time of the request.
  Firewall Restrictions: Firewalls may be blocking the communication between the systems.
  SAP Gateway Issues: Problems with the SAP Gateway service can also lead to RFC errors.
  
  Solutions:
  
  
  Check Network Connectivity:
  
  Ensure that the network connection between the SAP system and the target system is stable and operational. You can use tools like ping or traceroute to diagnose connectivity issues.
  
  
  
  Verify RFC Destination:
  
  Go to transaction code SM59 in the SAP GUI and check the configuration of the RFC destination. Ensure that the connection parameters (like target host, system number, client, user, and password) are correct.
  
  
  
  Test RFC Connection:
  
  In transaction SM59, select the RFC destination and use the "Connection Test" option to verify if the connection can be established successfully.
  
  
  
  Check User Authorizations:
  
  Ensure that the user credentials used for the RFC call have the necessary authorizations to perform the requested operation.
  
  
  
  Check System Status:
  
  Verify if the target system is up and running. You can check the system logs or contact the system administrator for confirmation.
  
  
  
  Review Firewall Settings:
  
  If applicable, check the firewall settings to ensure that the required ports for RFC communication are open.
  
  
  
  Check SAP Gateway:
  
  Ensure that the SAP Gateway service is running properly. You can check the status of the gateway using transaction SMGW.
  
  
  
  Review Logs:
  
  Check the system logs (transaction SM21) and the developer trace files (transaction ST11) for any additional error messages that might provide more context about the issue.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to RFC errors.
  Documentation: Review the SAP documentation for RFC communication and troubleshooting guidelines.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.