How To Fix LAW_MESSAGES335 - The selected RFC destinations were applied and saved

SAP Error Message - Details

• Message type: E = Error

• Message class: LAW_MESSAGES - License Administration Workbench

• Message number: 335

• Message text: The selected RFC destinations were applied and saved

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 LAW_MESSAGES335 - The selected RFC destinations were applied and saved ?

  The SAP error message LAW_MESSAGES335 typically indicates that there was an issue related to Remote Function Call (RFC) destinations during a process, such as a system landscape configuration or a transport operation. This message suggests that the selected RFC destinations were applied and saved, but it may also imply that there was a problem with the configuration or connectivity of those destinations.
  Cause:
  
  Incorrect RFC Configuration: The RFC destinations may not be configured correctly, leading to connectivity issues.
  Network Issues: There could be network problems preventing the SAP system from reaching the specified RFC destinations.
  Authorization Issues: The user executing the operation may not have the necessary authorizations to access the RFC destinations.
  System Configuration: The system landscape may not be set up correctly, leading to issues with the RFC destinations.
  
  Solution:
  
  
  Check RFC Configuration:
  
  Go to transaction SM59 to review the configuration of the RFC destinations.
  Ensure that the connection type (e.g., T, 3, etc.) is appropriate for your use case.
  Test the connection using the "Test Connection" button to verify that it is working correctly.
  
  
  
  Network Connectivity:
  
  Ensure that there are no network issues preventing communication between the systems.
  Check firewall settings and network routes to ensure that the systems can communicate.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access the RFC destinations.
  Check roles and profiles assigned to the user to ensure they include the necessary permissions.
  
  
  
  Review System Landscape:
  
  Ensure that the system landscape is correctly defined in the SAP system.
  Check for any inconsistencies in the configuration that might affect the RFC destinations.
  
  
  
  Logs and Traces:
  
  Check the system logs (transaction SM21) and RFC traces (transaction SM58) for any additional error messages or warnings that could provide more context about the issue.
  
  
  
  SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or related issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SM59: RFC Destinations
  SM21: System Log
  SM58: Asynchronous RFC Monitor
  
  
  Documentation: Refer to SAP Help documentation for more details on configuring RFC destinations and troubleshooting connectivity 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 following these steps, consider reaching out to your SAP Basis team or SAP support for further assistance.