How To Fix MDG_ID_MATCH_API_BS014 - Object identifier types &1 and &2 belong to different object node types

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_ID_MATCH_API_BS - Messages belonging to Key Mapping

• Message number: 014

• Message text: Object identifier types &1 and &2 belong to different object node types

What causes this issue?

In a one of the methods of the Key Mapping API, the <LS>Object
Identifier Types</> passed to the API failed the validation of their
assigned <DS:DE.MDG_OBJECT_NODE_TYPE_CODE>Object Node Type</> .

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

<LS>Object Identifier Type</> &V1& is incorrect for <LS>Object Node
Type</>: &V3&
<LS>Object Identifier Type</> &V2& is incorrect for <LS>Object Node
Type</>: &V4&
The methods and the validation associated with them are described here:
<ZH>ADD_MATCHING</>
The <LS>Object Identifier Types</> of all IDs that belong to one
<LS>Object Type</> must belong to the same <LS>Object Node Type</>.
<ZH>ADD_OBJECT_DATA</>
<LS>Object Identifier Types</> that are added to existing objects must
belong to the same <LS>Object Node Type</>.
<LS>Object Identifier Types</> for new objects must belong to the same
<LS>Object Node Type</>.
<ZH>CHANGE_IDENTIFIER</>
The <LS>Object Identifier Types</> of the changed identifiers and the
existing identifiers of each of the objects that are passed to the
method must belong to the same <LS>Object Node Type</>.

System Response

The processing of the called method of the Key mapping API is stopped.

How to fix this error?

Fix the <LS>Object Identifier Types</> so they pass validation.
Reference the corrrect code values in the Customizing activity
<DS:SIMG.DRF_010>Define Object Identifiers</>.

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_ID_MATCH_API_BS014 - Object identifier types &1 and &2 belong to different object node types ?

  The SAP error message MDG_ID_MATCH_API_BS014 indicates that there is a mismatch between the object identifier types being used in a Master Data Governance (MDG) process. Specifically, it states that the two object identifier types (&1 and &2) belong to different object node types. This typically occurs when there is an attempt to match or compare two different types of master data objects that are not compatible with each other.
  Cause
  The error is usually caused by one of the following scenarios:
  
  Incorrect Object Type Usage: The system is trying to perform an operation (like matching or merging) on two different types of master data objects (e.g., trying to match a vendor with a material).
  Configuration Issues: There may be a misconfiguration in the MDG setup where the object types are not correctly defined or linked.
  Data Entry Errors: Users may have inadvertently selected or entered incorrect object types during data processing.
  
  Solution
  To resolve this error, you can take the following steps:
  
  
  Verify Object Types: Check the object types being used in the operation that triggered the error. Ensure that both identifiers belong to the same object node type.
  
  
  Review Configuration: 
  
  Go to the MDG configuration settings and verify the object node definitions.
  Ensure that the object types are correctly configured and that they are intended to be used together in the context of the operation you are performing.
  
  
  
  Correct Data Entry: If the error is due to incorrect data entry, ensure that users are selecting the correct object types when performing operations.
  
  
  Consult Documentation: Refer to the SAP MDG documentation for guidance on object types and their relationships. This can provide insights into how different object types should interact.
  
  
  Debugging: If you have access to the development environment, you can debug the process to see where the mismatch is occurring and gather more information about the specific identifiers involved.
  
  
  SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. Provide them with the error message details and the context in which it occurred.
  
  
  Related Information
  
  MDG Object Types: Familiarize yourself with the different object types in SAP MDG, such as Business Partner, Material, Customer, etc., and understand their relationships.
  Transaction Codes: Use transaction codes like MDGIMG to access the MDG configuration settings and review object node configurations.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to this error message.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.