How To Fix USMD1060 - Data model &1, ent. type &2: Relationship of type "leading" inconsistent

USMD1060 - Overview

• Message type: E = Error

• Message class: USMD1 - Datenmodel

• Message number: 060

• Message text: Data model &1, ent. type &2: Relationship of type "leading" inconsistent

What causes this issue?

Entity types with <DS:DE.USMD_USAGE_TYPE>storage and use type</> <LS>4
</> must be used as to-entity types in one relationship with the
relationship type <LS>Leading</>. You can use the from-entity type to
process the attributes or assignment of additional entity types using
the relationship type <LS>Referencing</>.
There is either more than one relationship with <LS>Leading</> as the
relationship type, or none at all.

System Response

The data model cannot be saved or activated.

How to fix this error?

Make sure that there is exactly one relationship with the relationship
type <LS>Leading</>.

Procedure for System Administrators

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.

USMD1060 - Details

• The SAP error message USMD1060 indicates that there is an inconsistency in the data model related to a "leading" relationship between entities. This typically occurs in the context of SAP Master Data Governance (MDG) when there are issues with the relationships defined between different master data entities.
  
  Cause:
  The error can arise due to several reasons:
  
  Inconsistent Relationship Definition: The relationship defined as "leading" may not be properly set up in the data model. This could be due to missing or incorrect configuration in the relationship settings.
  Data Integrity Issues: There may be inconsistencies in the underlying data that violate the expected relationship rules.
  Model Configuration Errors: The data model itself may have been incorrectly configured, leading to conflicts in how entities relate to one another.
  Changes in Data Model: If there have been recent changes to the data model or relationships, it may not have been updated correctly across all relevant entities.
  
  
  Solution:
  To resolve the USMD1060