How To Fix S_ARC_LCM_MES073 - RFC call to FM &1 resulted in error ( &2 )

SAP Error Message - Details

• Message type: E = Error

• Message class: S_ARC_LCM_MES - Message Class for Legal Case Management (Subcomponent)

• Message number: 073

• Message text: RFC call to FM &1 resulted in error ( &2 )

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 S_ARC_LCM_MES073 - RFC call to FM &1 resulted in error ( &2 ) ?

  The SAP error message S_ARC_LCM_MES073 indicates that there was an issue with a Remote Function Call (RFC) to a function module (FM) in the SAP system. The error message typically includes two placeholders: &1 for the name of the function module that was called, and &2 for the specific error message or code that was returned.
  Cause:
  
  Network Issues: There may be network connectivity problems between the systems involved in the RFC call.
  Authorization Issues: The user or system making the RFC call may not have the necessary authorizations to execute the function module.
  Function Module Errors: The function module itself may have issues, such as being incorrectly implemented, or it may be encountering data-related problems.
  Configuration Issues: There may be configuration problems in the RFC destination or in the function module settings.
  System Performance: If the system is under heavy load, it may not be able to process the RFC call in a timely manner.
  
  Solution:
  
  Check Network Connectivity: Ensure that there are no network issues between the systems. You can use tools like ping or traceroute to diagnose connectivity.
  Review Authorizations: Verify that the user or system making the RFC call has the necessary authorizations to execute the function module. You can check this in transaction SU53 or by reviewing the user roles.
  Analyze the Function Module: Check the function module for any known issues or bugs. You can do this by reviewing the code in transaction SE37 or SE80.
  Check RFC Destination: Ensure that the RFC destination is correctly configured. You can check this in transaction SM59. Test the connection to see if it is working properly.
  Review System Logs: Check the system logs (transaction SM21) and the application logs (transaction SLG1) for any additional error messages that may provide more context.
  Performance Monitoring: If the system is under heavy load, consider monitoring system performance and optimizing resource usage.
  
  Related Information:
  
  Transaction Codes: 
  
  SE37: Function Module Maintenance
  SM59: RFC Destinations
  SU53: Authorization Check
  SM21: System Log
  SLG1: Application Log
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address known issues with the specific function module or error message.
  Documentation: Review the documentation for the specific function module to understand its parameters and expected behavior.
  
  If the issue persists after following these steps, it may be necessary to engage SAP support for further assistance.