How To Fix USMD6586 - Error due to background RFC Customizing for business object type &1

USMD6586 - Overview

• Message type: E = Error

• Message class: USMD6 - Messages for Data Transfer

• Message number: 586

• Message text: Error due to background RFC Customizing for business object type &1

What causes this issue?

There is no inbound destination defined with the prefix MDG_

System Response

The system cannot find an inbound destination with the prefix MDG_ for
the object &1. The messages cannot be sent queued. This may lead
to duplication of messages.

How to fix this error?

Contact your system administrator

Procedure for System Administrators

Define an inbound destination with the prefix MDG_ as follows:
Use transaction <DS:TRAN.SBGRFCCONF>SBGRFCCONF</>
Define a new inbound destination or choose an existing one
Add a new prefix MDG_
Create Scheduler settings for the new inbound destination

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message USMD6586 - Error due to background RFC Customizing for business object type &1 ?

  The SAP error message USMD6586 typically indicates an issue related to the background Remote Function Call (RFC) customizing for a specific business object type in the SAP system. This error can occur in the context of SAP Master Data Governance (MDG) or other modules that utilize business object types for data management.
  
  Cause:
  The error message USMD6586 is generally caused by one of the following issues:
  
  
  Missing or Incorrect Customizing: The background RFC settings for the specified business object type are either missing or incorrectly configured. This can happen if the necessary customizing steps were not completed during the setup of the business object.
  
  
  Authorization Issues: The user or system trying to execute the background RFC may not have the necessary authorizations to access or modify the business object type.
  
  
  Technical Issues: There may be technical issues with the RFC connection itself, such as network problems, incorrect destination settings, or issues with the target system.
  
  
  Inconsistent