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: 074
Message text: Delivery request &1: Rejected requests (used elsewhere)
Not all change requests that were selected to be included in delivery
request &V1& (for delivery component &V2&) have been flagged.
The change requests rejected by the user are already being used in other
deliveries, which means that these change requests are not supposed to
be delivered again.
Log message.
The rejected change requests are listed in the following lines of the
log.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL074
- Delivery request &1: Rejected requests (used elsewhere) ?The SAP error message TR_AUSL074 indicates that a delivery request has been rejected because it is being used elsewhere in the system. This typically occurs in the context of transport requests, where a transport request is locked or in use by another process, preventing it from being processed or released.
Cause:
- Transport Request Lock: The transport request is currently being used or locked by another user or process.
- Dependencies: The request may have dependencies on other requests that are not yet released or are in a different state.
- Incorrect Configuration: There may be configuration issues in the transport management system that are causing the request to be rejected.
Solution:
- Check Lock Status: Use transaction code
SE03
(Transport Organizer Tools) to check if the transport request is locked. You can view the lock entries and see if another user is currently using the request.- Release Dependencies: Ensure that all dependent transport requests are released. If there are requests that need to be released first, do so before attempting to process the current request.
- Consult with Team Members: If you find that another user is using the request, coordinate with them to either release the request or to wait until they are finished.
- Transport Management Configuration: Review the transport management configuration to ensure that everything is set up correctly. This may involve checking the transport routes and settings in transaction
STMS
.- Recreate the Request: If the request is not critical and can be recreated, consider creating a new transport request and moving the objects to that request.
Related Information:
SE03
: Transport Organizer ToolsSE09
: Workbench OrganizerSE10
: Customizing OrganizerSTMS
: Transport Management SystemIf the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL070
&2 rejected (for delivery request &1)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TR_AUSL069
Delivery request &1: Rejected requests (not released)
What causes this issue? Not all of the change requests selected for inclusion in delivery request &V1& have been flagged. The unreleased chan...
TR_AUSL075
Delivery request &1: Copy all requests already used
What causes this issue? The user has flagged all change requests in the current request selection that are already being used in other deliveries, fo...
TR_AUSL076
No other requests flagged for delivery request &1 (type &2)
What causes this issue? No other change requests have been flagged for delivery request &V1& (type <ZH>&V2&</>) of delive...
Click on this link to search all SAP messages.