How To Fix USMD2070 - Chg.request type &1: 'Scenario', 'UI Config', 'Optional' are initialized

SAP Error Message - Details

• Message type: E = Error

• Message class: USMD2 - Master Data: UI Modeling

• Message number: 070

• Message text: Chg.request type &1: 'Scenario', 'UI Config', 'Optional' are initialized

What causes this issue?

In change request type &V1&, you have entered a <LS>Scenario</> (or a
<LS>UI Configuration</>) for at least one entity type, or you have set
the <DS:DE.USMD_KEY_OPTIONAL>Optional</> indicator for at least one
entity type. However, this is only allowed for change request types that
edit individual objects, and of these, only for the leading entity type.

System Response

If change request type &V1& is a change request type that edits
individual objects, the system has deleted the scenarios and UI
configurations and has removed the <LS>Optional</> indicator for all
entity types, with the exception of the leading entity type.
If change request type &V1& is a change request type that can contain
more than one object, the system has deleted the scenarios and UI
configurations and has removed the <LS>Optional</> indicator for all
entity types.

How to fix this error?

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

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 USMD2070 - Chg.request type &1: 'Scenario', 'UI Config', 'Optional' are initialized ?

  The SAP error message USMD2070 typically occurs in the context of SAP Master Data Governance (MDG) when there is an issue with the change request type configuration. This error indicates that certain elements of the change request type, such as 'Scenario', 'UI Config', and 'Optional', have been initialized but not properly configured or are missing necessary settings.
  Cause:
  
  Incomplete Configuration: The change request type may not be fully configured in the system. This can happen if the necessary scenarios, UI configurations, or optional settings have not been defined.
  Missing Customization: If the system is expecting certain configurations that have not been set up, this error can occur.
  Transport Issues: If the configuration was transported from another system and not all necessary components were included, this could lead to initialization issues.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the MDG customizing settings (transaction code SPRO).
  Navigate to the relevant area for change request types and ensure that all required fields (Scenario, UI Config, Optional) are properly defined.
  Make sure that the change request type is linked to the correct scenarios and UI configurations.
  
  
  
  Review Change Request Type:
  
  Use transaction MDGIMG to review the change request type settings.
  Ensure that the change request type is active and that all necessary components are assigned.
  
  
  
  Transport Management:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included in the transport request.
  If needed, re-transport the missing configurations.
  
  
  
  Testing:
  
  After making the necessary adjustments, test the change request type to ensure that the error no longer occurs.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific version of MDG you are using for any additional guidance or known issues.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Community Forums: SAP Community and other forums can be helpful for finding similar issues faced by other users and their solutions.
  SAP Support: If the issue persists after following the above steps, consider reaching out to SAP Support for further assistance.
  
  By following these steps, you should be able to resolve the USMD2070 error and ensure that your change request type is properly configured.