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: 027
Message text: &2 not contained in object list of change request &1
The change request contains an object list in which the objects to be
changed (master data) needs to be specified explicitly. The master data
is <ZH>not</> specified in the object list.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Adjust the object list of the change request or remove the master data
from the file to be uploaded.
Error message extract from SAP system. Copyright SAP SE.
USMD6027
- &2 not contained in object list of change request &1 ?The SAP error message USMD6027 typically indicates that a specific object (like a data model or a configuration object) is not included in the change request you are trying to work with. This error often arises in the context of SAP Master Data Governance (MDG) when you are attempting to transport or activate changes that are not properly included in the transport request.
Cause:
The error message USMD6027 occurs due to one of the following reasons:
- The object you are trying to modify or activate is not included in the specified change request.
- The change request may have been created incorrectly or may not have been released properly.
- There may be a mismatch between the object and the transport request, possibly due to manual changes or incorrect configuration.
Solution:
To resolve the error USMD6027, you can follow these steps:
Check the Change Request:
- Verify that the object you are trying to work with is indeed included in the specified change request (
&1
).- You can do this by going to the transaction code SE09 or SE10 to view the transport requests and their contents.
Include the Object:
- If the object is not included, you may need to add it to the change request manually. You can do this by using the appropriate transaction (like SE80 or SE11) to include the object in the transport request.
Release the Change Request:
- Ensure that the change request is released. If it is in a modifiable state, you may need to release it to make the changes effective.
Check for Transport Layer Issues:
- Ensure that the transport layer is correctly configured and that there are no issues with the transport routes.
Consult Documentation:
- Review the SAP documentation or notes related to the specific version of MDG you are using, as there may be version-specific considerations or patches available.
Contact SAP Support:
- If the issue persists after following the above steps, consider reaching out to SAP support for further assistance, especially if this is a production environment.
Related Information:
By following these steps, you should be able to resolve the error message USMD6027 and successfully manage your change requests in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
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...
USMD6025
Entity &1 is located in change request &2
What causes this issue? The entity belongs to a change request (a) to which you are not assigned as the processor or (b) that is in a state in which ...
USMD6028
Edition &1 does not exist (for data model &2)
What causes this issue? Either the edition does not exist or it was created on the basis of a different data model. The data model is determined in C...
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...
Click on this link to search all SAP messages.