How To Fix MDG_DQR_GENERAL028 - No suitable edition for change request type &1 is found

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_DQR_GENERAL - Messages of package MDG_DQR_GENERAL

• Message number: 028

• Message text: No suitable edition for change request type &1 is found

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 MDG_DQR_GENERAL028 - No suitable edition for change request type &1 is found ?

  The SAP error message MDG_DQR_GENERAL028 indicates that there is no suitable edition for the specified change request type in the Master Data Governance (MDG) system. This error typically arises when you are trying to create or process a change request, but the system cannot find a valid edition that corresponds to the change request type you are using.
  Causes:
  
  Missing Edition Configuration: The edition for the specified change request type may not be configured in the system.
  Incorrect Change Request Type: The change request type being used may not be correctly set up or may not correspond to any existing editions.
  Inconsistent Data: There may be inconsistencies in the data or configuration that prevent the system from recognizing the edition.
  Authorization Issues: The user may not have the necessary authorizations to access the edition related to the change request type.
  
  Solutions:
  
  
  Check Edition Configuration:
  
  Go to the MDG configuration settings and verify that the edition for the specified change request type is correctly defined.
  Ensure that the edition is active and properly linked to the change request type.
  
  
  
  Review Change Request Type:
  
  Confirm that the change request type you are using is valid and correctly configured in the system.
  Check if the change request type is assigned to the correct edition.
  
  
  
  Maintain Editions:
  
  If the edition is missing, you may need to create a new edition or modify an existing one to include the required change request type.
  Use transaction code MDGIMG to access the configuration settings and maintain editions.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the edition and change request type.
  Review the user roles and profiles to confirm that they include the required permissions.
  
  
  
  Consult Documentation:
  
  Refer to the SAP Help documentation for MDG to understand the configuration and setup of editions and change request types.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the process to identify any underlying issues in the code or configuration that may be causing the error.
  
  
  
  Related Information:
  
  Transaction Codes: Use transaction codes like MDGIMG for configuration and MDG_CRM for managing change requests.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Community Forums: Engage with SAP community forums or support channels for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.