How To Fix MDG_OITC_CUST002 - Delimiter not allowed for key structure &1 of object ID type &2

MDG_OITC_CUST002 - Overview

• Message type: E = Error

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

• Message number: 002

• Message text: Delimiter not allowed for key structure &1 of object ID type &2

What causes this issue?

You have changed the <DS:DE.MDG_STRUCNAME_OBJECT_ID>key structure</>
forthe &V2& <DS:DE.MDG_IDS_TYPE_CODE_BS>Object ID type</>. The old key
structure supported a <DS:DE.MDG_CC_OBJECT_ID_DELIMITER>delimiter</>.
The new one, &V1&, does not support a delimiter.

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

System Response

How to fix this error?

Delete the defined delimiter. If key mapping exists for the
corresponding <DS:DE.MDG_OBJECT_TYPE_CODE_BS>business object type</>,
undo changes to key structures to avoid data inconsistencies.

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_CUST002 - Delimiter not allowed for key structure &1 of object ID type &2 ?

  The SAP error message MDG_OITC_CUST002 indicates that there is an issue with the key structure of an object ID type in the Master Data Governance (MDG) module. Specifically, the error states that a delimiter is not allowed for the key structure of the specified object ID type.
  
  Cause:
  This error typically occurs when:
  
  Invalid Characters: The key structure for the object ID type contains invalid characters or delimiters that are not permitted. In SAP, certain characters (like slashes, commas, etc.) may not be allowed in key fields.
  
  Configuration Issues: The configuration of the object ID type may not be set up correctly, leading to the inclusion of delimiters in the key structure.
  Data Entry Errors: During data entry or data import, delimiters may have been inadvertently included in the key fields.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Key Structure Configuration:
  
  Go to the configuration settings for the object ID type in the MDG