How To Fix TR_AUSL222 - Exclusion list not modifiable; request of type &1 already exists

SAP Error Message - Details

• Message type: E = Error

• Message class: TR_AUSL - Software Delivery Composer Messages

• Message number: 222

• Message text: Exclusion list not modifiable; request of type &1 already exists

What causes this issue?

Delivery requests of type <ZH>&V1&</> already exist for delivery
component &V3& (in delivery &V4&). The corresponding delivery request of
type <ZH>&V2&</> has already been released.
This means that you cannot create or make changes to the exclusion list,
since it no longer influences the objects included in the delivery
requests of type <ZH>&V2&</> or <ZH>&V1&</>.

System Response

The action terminates.

How to fix this error?

After you have created the contents of the delivery requests of type
<ZH>&V2&</> or <ZH>&V1&</> for the first time, you can no longer make
consistent changes to the exclusion list.
If you have to make changes to the exclusion list, you must first merge
the existing delivery requests of type <ZH>&V1&</> in the delivery
requests of type <ZH>&V2&</>. To do this, choose <LS>Utilities -> &V1&
-> Merge all in &V2&</>.
You must then reset the delivery component to re-create the delivery
requests. To do this, choose <LS>
Delivery Component -> Reset</>.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

You can then make changes to the exclusion list and use it to re-create
a consistent delivery request of type <ZH>&V2&</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR_AUSL222 - Exclusion list not modifiable; request of type &1 already exists ?

  The SAP error message TR_AUSL222, which states "Exclusion list not modifiable; request of type &1 already exists," typically occurs in the context of transport management within SAP systems. This error indicates that there is an attempt to modify an exclusion list for a transport request, but the request type specified already exists in the exclusion list, preventing further modifications.
  Cause:
  
  Duplicate Request Type: The error is primarily caused by trying to add a transport request of a type that is already present in the exclusion list. This can happen if you are trying to include a transport request that has already been excluded or if there is a misconfiguration in the transport management system.
  System Configuration: There may be issues with the configuration of the transport routes or the transport domain, leading to conflicts in the transport requests.
  User Permissions: The user may not have the necessary permissions to modify the exclusion list.
  
  Solution:
  
  Check the Exclusion List: Review the current exclusion list to see if the transport request type you are trying to add is already present. You can do this by navigating to the transport management system and checking the exclusion settings.
  Remove Existing Entry: If you find that the request type is already in the exclusion list and you want to modify it, you may need to remove the existing entry first before adding a new one.
  Correct Configuration: Ensure that the transport routes and domain configurations are set up correctly. You may need to consult with your SAP Basis team to verify that everything is configured properly.
  User Authorization: Check if the user has the necessary authorizations to modify the exclusion list. If not, you may need to request additional permissions from your SAP security team.
  Consult SAP Notes: Look for any relevant SAP Notes that might address this specific error. SAP frequently updates its knowledge base with solutions for common issues.
  
  Related Information:
  
  Transport Management System (TMS): Understanding how TMS works in SAP can help in troubleshooting transport-related issues. Familiarize yourself with the concepts of transport requests, transport routes, and the exclusion list.
  SAP Basis Documentation: Refer to the official SAP documentation for detailed information on transport management and error handling.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.