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

TR_AUSL222 - Overview

• 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.

TR_AUSL222 - Details

• 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