How To Fix USMD6573 - Change request &1 does not contain objects to be replicated

USMD6573 - Overview

• Message type: E = Error

• Message class: USMD6 - Messages for Data Transfer

• Message number: 573

• Message text: Change request &1 does not contain objects to be replicated

What causes this issue?

The change request either does not have any objects in the object list
or no business object types could be found.

System Response

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

How to fix this error?

If the change request contains objects, contact the system
administrator.

Procedure for System Administrators

In Customizing for <LS>Master Data Governance </>under <LS>General
Settings </>-> <LS>Data Modeling </>-> <LS>Edit Data Model</>, check if
business object types have been assigned to the entity types in the
change request. If not, make the assignment and activate the data model.
In Customizing for <LS>Master Data Governance </>under <LS>General
Settings </>-> <LS>Data Replication </>, check if all the necessary
settings have been made.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message USMD6573 - Change request &1 does not contain objects to be replicated ?

  The SAP error message USMD6573 indicates that a change request does not contain any objects that are eligible for replication. This typically occurs in the context of SAP Master Data Governance (MDG) when you are trying to replicate data but the change request you are working with is empty or does not include any relevant objects.
  Causes:
  
  Empty Change Request: The change request was created but no objects were added to it.
  Incorrect Object Selection: The objects that were intended to be included in the change request were not selected or were excluded during the change request creation.
  Replication Settings: The replication settings may not be configured correctly, leading to no objects being marked for replication.
  Authorization Issues: There may be authorization issues preventing the objects from being included in the change request.
  Technical Issues: There could be technical issues or bugs in the system that prevent the objects from being recognized.
  
  Solutions:
  
  Check Change Request Contents: Open