Do you have any question about this error?
Message type: E = Error
Message class: ESH_ENG_CDS_ABAP - ES-CDS/ABAP
Message number: 028
Message text: DDL artifact &1 already contained in transport request &2
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.
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.
ESH_ENG_CDS_ABAP028
- DDL artifact &1 already contained in transport request &2 ?The SAP error message ESH_ENG_CDS_ABAP028 indicates that there is a conflict with a Core Data Services (CDS) view or DDL artifact that is already included in a transport request. This typically occurs when you attempt to create or modify a CDS view that has already been included in a transport request that has not yet been released or imported into the target system.
Cause:
- Duplicate Inclusion: The DDL artifact (like a CDS view) you are trying to create or modify is already part of an existing transport request.
- Transport Request Not Released: The transport request containing the DDL artifact has not been released, which prevents further modifications or creations of the same artifact.
- Development Environment: This often happens in a development environment where multiple developers are working on similar objects.
Solution:
Check Existing Transport Requests:
- Use transaction code SE09 or SE10 to check the transport requests in your system.
- Look for the transport request that contains the DDL artifact mentioned in the error message.
Release the Transport Request:
- If the transport request is not yet released and you have the necessary authorizations, consider releasing it. This will allow you to create or modify the DDL artifact without conflicts.
Modify the Existing Artifact:
- If you need to make changes to the existing DDL artifact, you should do so in the transport request where it is already included. This way, you avoid duplication.
Create a New Transport Request:
- If you need to create a new DDL artifact, ensure that it does not conflict with existing ones. You may need to create it in a new transport request that does not include the conflicting artifact.
Consult with Team Members:
- If you are working in a team, communicate with your colleagues to ensure that no one else is working on the same DDL artifact simultaneously.
Related Information:
By following these steps, you should be able to resolve the error and continue your development work without further issues.
Get instant SAP help. Start your 7-day free trial now.
ESH_ENG_CDS_ABAP027
Transport request &2 cannot be used:
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_ENG_CDS_ABAP026
DDL artifact &1 added to transport request &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_ENG_CDS_ABAP029
Skip activation for domain &1: System not on HANA
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_ENG_CDS_ABAP030
Transport request &1 cannot be read
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.