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: TR_AUSL - Software Delivery Composer Messages
Message number: 187
Message text: Request &1 not yet used as a supplement component piece list
None of the deliveries that were created in the current SAP System use
request &V1& as a supplement component piece list.
However, you must use the supplement component piece list of the
previous delivery for the current delivery component &V2& (in delivery
&V3&).
This is just a warning. You can make a new entry.
Check and, if necessary, correct the value &V1&. Make sure that the
supplement component piece list of the predecessor of the current
delivery component &V2& (in delivery &V3&) has been entered.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL187
- Request &1 not yet used as a supplement component piece list ?The SAP error message TR_AUSL187 indicates that a transport request (denoted by
&1
) has not yet been used as a supplement component piece list. This error typically arises in the context of transport management within SAP, particularly when dealing with transport requests that are meant to carry changes or enhancements across different SAP systems.Cause:
- Transport Request Status: The transport request may not have been released or is still in a status that does not allow it to be used as a supplement.
- Missing Dependencies: The transport request may depend on other requests that have not been released or imported yet.
- Configuration Issues: There may be configuration issues in the transport management system that prevent the request from being recognized as a valid supplement component.
Solution:
Check Transport Request Status:
- Go to the Transport Organizer (transaction code SE09 or SE10) and check the status of the transport request. Ensure that it is released and ready for import.
Release the Transport Request:
- If the request is not released, you can release it by selecting the request and choosing the "Release" option. Make sure to follow the necessary steps to ensure that all objects are included.
Check Dependencies:
- Verify if there are any other transport requests that need to be imported first. If there are dependencies, ensure that those requests are imported into the target system.
Review Transport Routes:
- Ensure that the transport routes are correctly configured in the Transport Management System (TMS). Check if the target system is correctly set up to receive the transport request.
Consult Transport Logs:
- Review the transport logs for any additional error messages or warnings that might provide more context on why the request is not being recognized.
Contact Basis Team:
- If the issue persists, it may be necessary to involve your SAP Basis team or administrator to investigate further. They can check for any underlying issues in the transport management configuration.
Related Information:
By following these steps, you should be able to resolve the TR_AUSL187 error and successfully use the transport request as intended.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL186
&1 is not a supplement component piece list (contains subobject &2 &3)
What causes this issue? Request &V1& is not a supplement component piece list created using the Software Delivery Composer (SDC). Supplement ...
TR_AUSL185
Supplement component piece list &1 is empty; create contents
What causes this issue? The supplement component piece list &V1& is empty. The action that you want to perform requires that the supplement c...
TR_AUSL188
Supplement component piece list &1 not assigned to delivery component &2
What causes this issue? Request &V1& is used as a supplement component piece list in the current SAP System in delivery &V4&. However...
TR_AUSL189
Supplement change piece list &1 not released; you can still add to it
What causes this issue? If you have not released the supplement change piece list &V1&, you cannot create a delivery request of type <ZH&g...
Click on this link to search all SAP messages.