How To Fix USMD_GOV_API072 - Derived data of &1 with key &2 is interlocked in change request &3

SAP Error Message - Details

• Message type: E = Error

• Message class: USMD_GOV_API - Messages for Governance API

• Message number: 072

• Message text: Derived data of &1 with key &2 is interlocked in change request &3

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message USMD_GOV_API072 - Derived data of &1 with key &2 is interlocked in change request &3 ?

  The SAP error message USMD_GOV_API072 indicates that there is an issue with derived data being interlocked in a change request. This typically occurs in the context of SAP Master Data Governance (MDG) when you are trying to process or change data that is currently locked due to an ongoing change request.
  Cause:
  The error message is triggered when:
  
  Interlocked Data: The derived data you are trying to modify is currently locked by another change request. This means that the data is being processed or has been modified in a way that prevents concurrent changes.
  Change Request Status: The change request that is locking the data may be in a status that does not allow for further modifications or is still being processed.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Change Requests: Identify the change request that is locking the derived data. You can do this by checking the change request number mentioned in the error message (&3).
  
  
  Review Lock Status: Look at the status of the change request. If it is still in process or not yet approved, you may need to wait until it is completed or approved.
  
  
  Release Locks: If you have the necessary permissions, you can release the lock on the data. This may involve:
  
  Completing or rejecting the change request that is currently locking the data.
  If you have access, you can use transaction codes like SM12 to check for and delete locks, but be cautious as this can affect other users.
  
  
  
  Consult with Colleagues: If you are unsure about the status of the change request or how to proceed, consult with your colleagues or the team responsible for data governance in your organization.
  
  
  Retry the Operation: Once the locking issue is resolved, you can retry the operation that triggered the error.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MDGIMG for configuration, SM12 for lock entries, and SE11 for data dictionary objects.
  Documentation: Refer to SAP documentation for Master Data Governance for more details on handling change requests and derived data.
  Support: If the issue persists, consider reaching out to SAP support or your internal IT support team for further assistance.
  
  By following these steps, you should be able to resolve the interlock issue and proceed with your data changes in SAP MDG.