How To Fix MDG_OITC_CUST003 - Leading key is already set for object identifier type &1

MDG_OITC_CUST003 - Overview

• Message type: E = Error

• Message class: MDG_OITC_CUST - MDG. Object Identifier Type Code messages

• Message number: 003

• Message text: Leading key is already set for object identifier type &1

What causes this issue?

You have selected the <LS>Leading Key</> checkbox for the <LS>Object
Identifier Type</> &V2&. This is not possible because <LS>Object
Identifier Type </>&V1& , which belongs to <LS>Object NodeType</> &V3&,
is still marked as leading key.

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?

Deselect the <LS>Leading Key</> checkbox<LS> </>for <LS>Object
Identifier Type</> &V2&.
Deselect the <LS>Leading Key</> checkbox for <LS>Object Identifier Type
</> &V1&.
Select the <LS>Leading Key</> checkbox for <LS>Object Identifier Type</>
&V2&

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDG_OITC_CUST003 - Leading key is already set for object identifier type &1 ?

  The SAP error message MDG_OITC_CUST003 indicates that there is an issue with the object identifier type in the Master Data Governance (MDG) system. Specifically, the error message states that the "leading key is already set for object identifier type &1." This typically occurs when there is an attempt to set or modify an object identifier type that already has a leading key defined.
  
  Cause:
  
  Duplicate Leading Key Assignment: The error usually arises when you try to assign a leading key to an object identifier type that already has one assigned. In MDG, each object identifier type can only have one leading key.
  
  Configuration Issues: There may be a misconfiguration in the MDG settings or in the object identifier type definitions.
  Data Consistency Issues: If there are inconsistencies in the data or if the system is trying to process an object that has already been defined with a leading key, this error can occur.
  
  
  Solution:
  
  
  Check Object