Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: USMD6 - Messages for Data Transfer
Message number: 028
Message text: Edition &1 does not exist (for data model &2)
Either the edition does not exist or it was created on the basis of a
different data model. The data model is determined in Customizing of the
edition type.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Select a suitable edition using input help.
Error message extract from SAP system. Copyright SAP SE.
USMD6028
- Edition &1 does not exist (for data model &2) ?The SAP error message USMD6028 indicates that a specific edition for a data model does not exist in the system. This error typically occurs in the context of SAP Master Data Governance (MDG) when trying to access or manipulate data related to a specific edition of a data model.
Cause:
The error can be caused by several factors:
- Non-existent Edition: The edition specified in the error message does not exist in the system. This could be due to a typo or an incorrect reference.
- Data Model Configuration: The data model may not be properly configured, or the edition may not have been created or activated.
- Authorization Issues: The user may not have the necessary authorizations to access the specified edition or data model.
- Transport Issues: If the data model or edition was recently transported from another system, it may not have been properly imported.
Solution:
To resolve the error, you can take the following steps:
Check Edition Existence:
- Go to the relevant transaction (e.g., MDGIMG) and navigate to the configuration of the data model.
- Verify that the edition specified in the error message exists.
Create or Activate Edition:
- If the edition does not exist, you may need to create it. This can typically be done in the configuration settings for the data model.
- If it exists but is inactive, activate it.
Review Configuration:
- Ensure that the data model is correctly configured and that all necessary editions are defined.
Check Authorizations:
- Ensure that the user has the necessary authorizations to access the data model and its editions.
Transport Check:
- If the issue arose after a transport, check the transport logs to ensure that all objects were transported correctly.
Consult Documentation:
- Refer to SAP documentation or notes related to the specific data model and edition for additional guidance.
Related Information:
MDGIMG
for configuration and MDG_MDS
for master data services.By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
USMD6027
&2 not contained in object list of change request &1
What causes this issue? The change request contains an object list in which the objects to be changed (master data) needs to be specified explicitly....
USMD6026
Change request is missing
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
USMD6029
Entity type &2 not contained in edition type &1
What causes this issue? The entity cannot be processed because the assigned entity type is not contained in the edition type of the specified edition...
USMD6030
Error while writing to application Log
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.