How To Fix MDG_REF_DATA008 - RFC connection &1 from system &2 to &3 does not use trusted RFC

MDG_REF_DATA008 - Overview

• Message type: E = Error

• Message class: MDG_REF_DATA - Message Class for Reference Data messages

• Message number: 008

• Message text: RFC connection &1 from system &2 to &3 does not use trusted RFC

What causes this issue?

The remote function module has not been called through a trusted RFC.
The RFC connection &V1& is not a trusted RFC.

System Response

Error occured during replication.

How to fix this error?

Contact the system administrator to create a trusted RFC connection
between &V2& and &V3&. This RFC connection has to be maintained in the
replication model under <LS>Master Data Governance -> General Settings
-> Data Replication -> Define Custom Settings for Data Replication ->
Define Replication Models</>. In the activity, select <LS>Assign
Outbound Implementation -> Assign Target Systems for Repl. Model/Outb.
Impl.</>

Procedure for System Administrators

Set up a trusted RFC connection between the hub system &V2& and client
&V3& where the data is replicated.
Perform the following steps to maintain a trusted RFC Connection:
Open transaction SM59.
Under <LS>ABAP Connections</>, select the RFC connection &V1&.
Select the<LS> Logon & Security</> tab. Select the radio button
<LS>Yes</> for the <LS>Trust Relationship</> field.

Error message extract from SAP system. Copyright SAP SE.

MDG_REF_DATA008 - Details

• The SAP error message MDG_REF_DATA008 indicates that there is an issue with the RFC (Remote Function Call) connection between two SAP systems. Specifically, it states that the RFC connection from system &2 to system &3 does not use a trusted RFC. This can lead to authorization issues when trying to access data or perform operations across these systems.
  
  Cause:
  The primary cause of this error is that the RFC connection is not configured to use trusted RFC. Trusted RFC connections allow for seamless communication between systems without requiring additional authentication for each call. If the connection is not trusted, the system may not allow certain operations due to security restrictions.
  
  Solution:
  To resolve this issue, you need to configure the RFC connection to be a trusted RFC. Here are the steps to do this:
  
  
  Access the RFC Destination Configuration:
  
  Go to transaction code SM59 in the SAP GUI.
  Locate the RFC destination that is causing the issue.
  
  
  
  Edit