How To Fix G3655 - Function module &1 does not exist in RFC destination &2

SAP Error Message - Details

• Message type: E = Error

• Message class: G3 - Messages for SAP Consolidation: Integration

• Message number: 655

• Message text: Function module &1 does not exist in RFC destination &2

What causes this issue?

Program execution requires access to function module &V1& in RFC
destination &V2&. However this function module is not available there.

System Response

Program execution is terminated; a reconciliation run with summary data
from RFC destination &V2& cannot be executed.

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message G3655 - Function module &1 does not exist in RFC destination &2 ?

  The SAP error message G3655 indicates that a function module specified in an RFC (Remote Function Call) destination does not exist. This can occur in various scenarios, such as when trying to call a function module from a different SAP system or when there is a misconfiguration in the RFC destination settings.
  Cause:
  
  Non-existent Function Module: The function module specified in the RFC call does not exist in the target system.
  Incorrect RFC Destination: The RFC destination may be pointing to the wrong system or client where the function module is not available.
  Authorization Issues: The user may not have the necessary authorizations to access the function module in the target system.
  Transport Issues: The function module may not have been transported to the target system yet.
  Naming Issues: There could be a typo in the function module name or the RFC destination.
  
  Solution:
  
  Verify Function Module: Check if the function module exists in the target system. You can do this by using transaction SE37 (Function Builder) in the target system.
  Check RFC Destination: Ensure that the RFC destination is correctly configured. You can check this in transaction SM59 (RFC Destinations).
  
  Make sure the destination points to the correct system and client.
  Test the connection to ensure it is working properly.
  
  
  Authorization Check: Ensure that the user executing the RFC call has the necessary authorizations to access the function module in the target system.
  Transport Check: If the function module was recently created or modified, ensure that it has been transported to the target system.
  Correct Naming: Double-check the spelling of the function module name in the code that is making the RFC call.
  
  Related Information:
  
  Transaction Codes:
  
  SE37: Function Builder - to check the existence of the function module.
  SM59: RFC Destinations - to manage and test RFC connections.
  SU53: Authorization Check - to analyze authorization issues.
  
  
  Logs and Traces: Check the system logs (transaction SM21) and the RFC trace (transaction ST01) for more detailed error information.
  Documentation: Refer to SAP Help documentation for more details on RFC and function modules.
  
  By following these steps, you should be able to identify and resolve the issue causing the G3655 error message.