How To Fix S_ARC_LCM_MES072 - System failure at RFC call happen

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 072

• Message text: System failure at RFC call happen

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_MES072 - System failure at RFC call happen ?

  The SAP error message S_ARC_LCM_MES072, which indicates a "System failure at RFC call," typically arises during Remote Function Call (RFC) operations in SAP systems. This error can occur due to various reasons, and understanding the cause is essential for troubleshooting and resolving the issue.
  Possible Causes:
  
  Network Issues: Problems with the network connection between the SAP systems can lead to RFC call failures.
  Configuration Errors: Incorrect configuration of RFC destinations or settings in the SAP system can cause failures.
  Authorization Issues: The user executing the RFC call may not have the necessary authorizations to perform the operation.
  System Resource Limitations: Insufficient system resources (like memory or CPU) can lead to failures during RFC calls.
  System Bugs: There may be bugs in the SAP system or in the specific function module being called.
  Timeouts: If the RFC call takes too long to execute, it may time out and result in a failure.
  
  Solutions:
  
  Check Network Connectivity: Ensure that there are no network issues between the systems involved in the RFC call. You can use tools like ping or traceroute to diagnose connectivity.
  Review RFC Configuration: Verify the configuration of the RFC destination in transaction SM59. Ensure that the settings are correct and that the destination is reachable.
  Check Authorizations: Ensure that the user executing the RFC call has the necessary authorizations. You can check this in transaction SU53 after the error occurs.
  Monitor System Resources: Use transaction SM50 or SM66 to monitor system performance and check for any resource bottlenecks.
  Review System Logs: Check the system logs (transaction SM21) and the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context.
  Increase Timeout Settings: If timeouts are suspected, consider increasing the timeout settings for the RFC call in the RFC destination configuration.
  Update SAP System: If the issue persists, check for any available SAP Notes or patches that address known bugs related to the RFC call.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to the error message.
  Transaction Codes:
  
  SM59: To manage RFC destinations.
  SM21: To view system logs.
  SLG1: To view application logs.
  SU53: To analyze authorization issues.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve SAP support for further assistance.