How To Fix MDG_OTC_CUST004 - BOR Object &1 is still assigned to Object Type Code &2

MDG_OTC_CUST004 - Overview

• Message type: E = Error

• Message class: MDG_OTC_CUST - MDG: Object Type Code Maintenance messages

• Message number: 004

• Message text: BOR Object &1 is still assigned to Object Type Code &2

What causes this issue?

You cannot assign the &V1& Business Object Repository (BOR) object to
the &V3& <DS:DE.MDG_OBJECT_TYPE_CODE_BS>BO Type</> because it is
already assigned to the &V2& BO Type.

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

System Response

The current assignment can not be stored.

How to fix this error?

Choose between the following options:
Delete the assignment of the &V1& BOR Object to the &V2& BO Type and
make the new assignment.
Assign another BOR Object to the &V3& Object Type.

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_OTC_CUST004 - BOR Object &1 is still assigned to Object Type Code &2 ?

  The SAP error message MDG_OTC_CUST004 indicates that a Business Object (BOR Object) is still assigned to a specific Object Type Code, which is preventing certain operations from being completed. This error typically arises in the context of Master Data Governance (MDG) when trying to delete or modify a business object that is still in use or linked to other objects.
  
  Cause:
  The error occurs because the system has detected that the specified BOR Object (represented by &1) is still associated with the Object Type Code (&2). This means that there are dependencies or references that need to be resolved before the object can be modified or deleted. Common causes include:
  
  The object is still being referenced in other configurations or transactions.
  There are active relationships or links to other business objects.
  The object is part of a workflow or process that is currently active.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Dependencies: Investigate where