How To Fix RSAR679 - RFC name for source system & (type &) not changed

RSAR679 - Overview

• Message type: E = Error

• Message class: RSAR - Data Transfer and Metadata Maintenance

• Message number: 679

• Message text: RFC name for source system & (type &) not changed

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 RSAR679 - RFC name for source system & (type &) not changed ?

  The SAP error message RSAR679 indicates that there is an issue with the RFC (Remote Function Call) connection for a source system in the context of SAP BW (Business Warehouse) or SAP Data Warehousing. This error typically arises when there is an attempt to change the RFC destination for a source system, but the system is unable to do so due to various reasons.
  
  Cause:
  
  Incorrect RFC Destination: The RFC destination for the source system may not be correctly defined or may not exist.
  Authorization Issues: The user may not have the necessary authorizations to change the RFC destination.
  System Configuration: There may be inconsistencies in the configuration of the source system or the BW system.
  Technical Issues: There could be underlying technical issues, such as network problems or system downtime.
  
  
  Solution:
  
  
  Check RFC Destination:
  
  Go to transaction SM59 in the SAP GUI.
  Verify that the RFC destination for the source system is correctly defined and is active.
  Test the