How To Fix TR_AUSL130 - Exclusion list is not modifiable: request &1 (type &2) is already filled

SAP Error Message - Details

• Message type: E = Error

• Message class: TR_AUSL - Software Delivery Composer Messages

• Message number: 130

• Message text: Exclusion list is not modifiable: request &1 (type &2) is already filled

What causes this issue?

The delivery request &V1& of type <ZH>&V2&</> (for delivery component
&V3& in delivery &V4&) has already been filled.
This means that you cannot create or change the corresponding exclusion
list, since this list no longer has any influence on the objects already
included in the delivery request of type <ZH>&V2&</>.

System Response

The function terminates.

How to fix this error?

Once you have generated the contents of the delivery request of type
<ZH>&V2&</>, you can no longer make consistent changes to the
corresponding exclusion list.
If you do need to make changes to the exclusion list, you need to reset
the delivery component, so that you can re-create the delivery requests
(choose <LS>Delivery Component -> Reset</>).
You can then change the exclusion list and use it to re-create the
contents of the delivery request of type <ZH>&V2&</> consistently.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR_AUSL130 - Exclusion list is not modifiable: request &1 (type &2) is already filled ?

  The SAP error message TR_AUSL130 indicates that an exclusion list is not modifiable because a specific request (identified by &1) of a certain type (&2) is already filled. This typically occurs in the context of transport requests in SAP, particularly when dealing with transport management and the transport directory.
  Cause:
  
  Request Already Filled: The transport request you are trying to modify is already filled with objects. Once a transport request is filled, it cannot be modified to add or remove objects from the exclusion list.
  Incorrect Status: The transport request may be in a status that does not allow modifications, such as being released or already imported into the target system.
  System Lock: There may be a lock on the transport request due to ongoing processes or transactions that prevent modifications.
  
  Solution:
  
  Check Request Status: Verify the status of the transport request. If it is already released or imported, you will not be able to modify it. You may need to create a new transport request for any additional changes.
  Use a New Transport Request: If you need to exclude additional objects, create a new transport request and include the necessary objects in that request.
  Unlock the Request: If the request is locked, check if there are any ongoing processes that are using the request. You may need to wait for those processes to complete or consult with your SAP Basis team to unlock the request.
  Review Exclusion List: If you are trying to modify the exclusion list, ensure that you are doing so on a request that is still modifiable (i.e., not filled or released).
  
  Related Information:
  
  Transport Management System (TMS): Understanding how the TMS works in SAP can help you manage transport requests more effectively.
  Transport Request Types: Familiarize yourself with different types of transport requests (e.g., Customizing, Workbench) and their characteristics.
  SAP Notes: Check SAP Notes for any specific patches or updates related to transport management that might address known issues or bugs.
  Documentation: Refer to SAP Help documentation for detailed information on transport requests and their management.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team for further assistance.