How To Fix TR_AUSL573 - Table contents (client-specific, delivery class &2): no import

TR_AUSL573 - Overview

• Message type: E = Error

• Message class: TR_AUSL - Software Delivery Composer Messages

• Message number: 573

• Message text: Table contents (client-specific, delivery class &2): no import

What causes this issue?

The current delivery request &V1& contains entries from client-specific
tables with the delivery class &V2& (temporary data). You cannot
transport table entries from tables with this delivery class, even in
delivery requests. This is why the corresponding table entries would not
be imported into the target system.

System Response

The system displays the relevant entries in the results overview in the
object list check.

How to fix this error?

Check whether the entries are delivery-relevant and remove any entries
that you do not want to deliver.
If you do want to deliver these entries, change the delivery class of
their table. For more information on the delivery classes of tables, see
<DS:DE.CONTFLAG>Delivery Class</>.
Also check whether you can use Business Configuration Sets (BC Sets) to
deliver the client-specific table entries. For more information on BC
Sets, call transaction SCPR3 and choose <LS>Help -> Application Help</>.
If you have any problems with BC Sets, create a customer message under
the component BC-CUS-TOL.

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

Error message extract from SAP system. Copyright SAP SE.

TR_AUSL573 - Details

• The SAP error message TR_AUSL573 typically indicates that there is an issue with the transport of table contents in the SAP system. This error can occur when trying to import a transport request that contains client-specific data, but the system is unable to find the necessary data for the specified delivery class.
  
  Cause:
  
  Missing Transport Request: The transport request that contains the necessary data for the table may not have been created or released properly.
  Client-Specific Data: The table in question is client-specific, meaning that its data is specific to a particular client in the SAP system. If the transport request does not include the necessary client-specific data, the import will fail.
  Delivery Class Issues: The delivery class of the table may not allow for the import of data in the current context, or the data may not be available in the transport request.
  Transport Directory Issues: There may be issues with the transport directory