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: 583
Message text: Table contents (cross-client, delivery class &2): no import
The current delivery request &V1& contains entries from cross-client
tables of the delivery class &V2& ('temporary data'). You cannot
transport entries from tables in this delivery class. This is why the
entries would not be imported into the target system.
The system displays the entries that are affected in the result overview
of the object list check.
Check whether these entries are delivery-relevant and remove the
non-relevant entries.
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</>.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL583
- Table contents (cross-client, delivery class &2): no import ?The SAP error message TR_AUSL583 indicates that there is an issue with the transport of data related to a specific table in the SAP system. This message typically arises when you are trying to import a transport request that contains data for a cross-client table, but the system is unable to import the data due to certain conditions.
Cause:
- Cross-Client Table: The error specifically mentions that the table is a cross-client table. Cross-client tables are tables that store data that is not client-specific, meaning they are shared across all clients in the SAP system.
- Delivery Class: The delivery class of the table is likely set in such a way that it does not allow data to be imported. For example, if the delivery class is set to "C" (which means the table is client-dependent and should not be transported), the system will prevent the import of data.
- Transport Request Issues: The transport request may not be correctly configured or may not contain the necessary data for the import to proceed.
Solution:
- Check Delivery Class: Verify the delivery class of the table in question. You can do this by checking the table definition in the Data Dictionary (SE11). If the delivery class is not appropriate for the intended transport, you may need to adjust it or handle the data differently.
- Transport Request Configuration: Ensure that the transport request is correctly configured and includes all necessary objects. If the transport request is incomplete, you may need to recreate it or add the missing objects.
- Manual Data Transfer: If the data cannot be transported due to the delivery class restrictions, consider manually transferring the data using tools like LSMW (Legacy System Migration Workbench) or by creating custom programs to extract and load the data.
- Consult Documentation: Review SAP documentation or notes related to transport management and cross-client tables for additional guidance.
Related Information:
If the issue persists after following these steps, 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_AUSL582
Table contents (cross-client, delivery class &2): import possible
What causes this issue? The current delivery request &V1& contains entries from cross-client tables with the delivery class &V2&. The...
TR_AUSL581
Table contents (cross-client, delivery class &2): import (add) possible
What causes this issue? The current delivery request &V1& contains entries from cross-client tables with the delivery class &V2&. The...
TR_AUSL584
Table contents (cross-client, logical object type): check delivery class
What causes this issue? The current delivery request &V1& contains entries from cross-client tables of the (non-defined) delivery class &...
TR_AUSL585
Table contents (cross-client, general object type): check import behavior
What causes this issue? The current delivery request &V1& contains entries from cross-client tables as part of general transport objects.Syst...
Click on this link to search all SAP messages.