How To Fix USMD_GOV_API350 - Hierarchy &1 in &2 hierarchy assignment is locked by change request &3

SAP Error Message - Details

• Message type: E = Error

• Message class: USMD_GOV_API - Messages for Governance API

• Message number: 350

• Message text: Hierarchy &1 in &2 hierarchy assignment is locked by change request &3

What causes this issue?

Hierarchy &V1& with parent &V4& in &V2& hierarchy assignment is locked
by change request &V3&.

System Response

How to fix this error?

Change request &V3& needs to be released before you can change this
hierarchy.

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 USMD_GOV_API350 - Hierarchy &1 in &2 hierarchy assignment is locked by change request &3 ?

  The SAP error message USMD_GOV_API350 indicates that a hierarchy assignment is locked due to an active change request. This typically occurs in the context of SAP Master Data Governance (MDG) when you are trying to make changes to a hierarchy that is currently being modified or is under review in a change request.
  Cause:
  
  Active Change Request: The hierarchy you are trying to modify is locked because it is part of an active change request. This means that another user or process is currently working on that hierarchy, preventing you from making changes.
  Locking Mechanism: SAP uses a locking mechanism to ensure data integrity. When a change request is created, it locks the relevant objects to prevent concurrent modifications.
  
  Solution:
  
  
  Check Active Change Requests: 
  
  Use transaction code SWI1 (Work Item Selection) or SWI2_FREQ (Work Items) to check for active change requests that might be locking the hierarchy.
  Identify the change request that is locking the hierarchy and see if you can coordinate with the user who is working on it.
  
  
  
  Wait for Release: If the change request is being actively worked on, you may need to wait until it is completed and released.
  
  
  Unlocking the Hierarchy: If you have the necessary authorizations, you can unlock the hierarchy by:
  
  Completing or rejecting the change request that is locking it.
  If you believe the lock is no longer valid (e.g., the user has left the session), you may need to contact your SAP Basis team to manually release the lock.
  
  
  
  Review Change Request Status: Ensure that the change request is in a status that allows for the hierarchy to be modified. If it is in a status that does not permit changes, you will need to change its status accordingly.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SWI1, SWI2, and SE03 (Transport Organizer) for managing change requests and locks.
  Authorization: Ensure you have the necessary authorizations to view and manage change requests and locks.
  Documentation: Refer to SAP documentation or help resources for more detailed information on managing change requests and hierarchy assignments in MDG.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team for further assistance.