How To Fix USMD_HRY_GENERAL002 - Transport the Customizing change only if target system has no open CR

SAP Error Message - Details

• Message type: E = Error

• Message class: USMD_HRY_GENERAL - Message Class for MDG Hierarchies

• Message number: 002

• Message text: Transport the Customizing change only if target system has no open CR

What causes this issue?

You changed the scope for simultaneous requests to restructure a
hierarchy in Customizing. The system allowed this change because there
are no open change requests for the hierarchy. You must now ensure that
target systems to which you transport this setting also have no open
change requests.

System Response

Your change has been saved.

How to fix this error?

When transporting this Customizing change, ensure the target system has
no open change requests.

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_HRY_GENERAL002 - Transport the Customizing change only if target system has no open CR ?

  The SAP error message USMD_HRY_GENERAL002 indicates that a customizing change cannot be transported to the target system because there are open Change Requests (CRs) in that system. This is a safeguard to ensure that the changes being transported do not conflict with ongoing development or configuration work.
  Cause:
  The error occurs when:
  
  There are open Change Requests in the target system that have not been released.
  The system is configured to prevent the transport of new changes if there are pending changes that could potentially conflict with the new changes being transported.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check Open Change Requests:
  
  Go to the target system and check for any open Change Requests. You can do this using transaction code SE09 or SE10.
  Identify any open requests that might be causing the issue.
  
  
  
  Release or Close Open Change Requests:
  
  If the open Change Requests are no longer needed, you can release or close them. This can be done by selecting the request and choosing the option to release it.
  If the requests are still needed, coordinate with your team to ensure that they are either completed or that the changes in the requests do not conflict with the changes you are trying to transport.
  
  
  
  Transport Changes in a Different Order:
  
  If possible, consider transporting the changes in a different order or at a different time when the open Change Requests have been addressed.
  
  
  
  Consult with Basis Team:
  
  If you are unsure about the open Change Requests or how to proceed, consult with your SAP Basis team. They can provide insights into the current state of the system and help manage the transport process.
  
  
  
  Related Information:
  
  Transport Management System (TMS): Understanding how TMS works can help you manage transports more effectively. Familiarize yourself with the transport landscape and the role of Change Requests.
  Change Request Management: Learn about best practices for managing Change Requests in SAP to avoid conflicts and ensure smooth transports.
  SAP Notes: Check for any relevant SAP Notes that might provide additional guidance or solutions related to this error message.
  
  By following these steps, you should be able to resolve the error and successfully transport your customizing changes to the target system.