How To Fix MDG_BS_MAT_GOV_SCOPE004 - Settings for relationships EAN_MARA and EAN_MARM must be the same

MDG_BS_MAT_GOV_SCOPE004 - Overview

• Message type: E = Error

• Message class: MDG_BS_MAT_GOV_SCOPE - Message class for governance scope check BAdI

• Message number: 004

• Message text: Settings for relationships EAN_MARA and EAN_MARM must be the same

What causes this issue?

In data model &1, it is not possible to govern the referencing
relationship EAN_MARA without the referencing relationship EAN_MARM. It
is also not possible to govern the referencing relationship EAN_MARM
without the referencing relationship EAN_MARA.

System Response

These inconsistent settings cannot be saved.

How to fix this error?

Govern both relationships or ungovern both relationships.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDG_BS_MAT_GOV_SCOPE004 - Settings for relationships EAN_MARA and EAN_MARM must be the same ?

  The SAP error message MDG_BS_MAT_GOV_SCOPE004 indicates that there is a mismatch in the settings for the relationships between the EAN (European Article Number) in the MARA (General Material Data) and MARC (Plant Data) tables. This error typically arises in the context of Master Data Governance (MDG) for Material Management when there are inconsistencies in the configuration of these relationships.
  
  Cause:
  The error occurs when the settings for the EAN relationship in the MARA table do not match those in the MARC table. This can happen due to:
  
  Inconsistent Configuration: The configuration settings for the EAN relationship in the material master data are not aligned between the general data (MARA) and the plant-specific data (MARC).
  Data Entry Errors: Incorrect or incomplete data entries in either the MARA or MARC tables can lead to this inconsistency.
  Custom Development: If there are custom developments or enhancements that affect how EANs are handled, they may not be properly synchronized