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: 590
Message text: Table contents belong to a table that cannot be transported directly
The current delivery request &V1& contains entries from tables that
cannot be transported directly. This could be because the contents of
these tables are transported using other transport objects.
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, correct them and then repeat
the object list check.
For more information on table contents that cannot be transported
directly, and their corresponding transport objects, see the message
<DS:NA.TR731>System objects cannot be transported directly</>.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL590
- Table contents belong to a table that cannot be transported directly ?The SAP error message TR_AUSL590 indicates that you are trying to transport table contents that belong to a table that cannot be transported directly. This typically occurs when you attempt to transport data from a table that is not designed to be included in transport requests, such as certain customizing tables or system tables.
Cause:
- Non-Transportable Tables: Some tables in SAP are designated as non-transportable due to their nature. These tables often contain configuration or customizing data that is specific to a particular client or system.
- Client-Specific Data: If the table is client-specific, it may not be allowed to be transported across different clients or systems.
- Transport Layer Restrictions: The transport layer settings may restrict certain tables from being included in transport requests.
Solution:
- Check Table Attributes: Use transaction SE11 (Data Dictionary) to check the attributes of the table in question. Look for the "Transport" settings to see if the table is marked as non-transportable.
- Manual Data Transfer: If the table cannot be transported, you may need to manually replicate the data in the target system. This can be done by exporting the data to a file and then importing it into the target system.
- Use Custom Transport Logic: If you have a specific requirement to transport data from this table, consider creating a custom transport solution or program that can handle the data transfer according to your needs.
- Consult Documentation: Review SAP documentation or consult with your SAP Basis team to understand the implications of transporting data from this table and to explore any potential workarounds.
Related Information:
If you continue to face issues or need further assistance, consider reaching out to your SAP support team or consulting with SAP experts who can provide tailored guidance based on your specific system configuration and requirements.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL589
Status of checks already performed for &1 invalidated (&2, &3, &4)
What causes this issue? The system has set the status of the completed object list checks for the delivery request &V1& to invalidated. This ...
TR_AUSL588
Assigned message variables: &1 &2 &3 &4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TR_AUSL591
Object from another namespace (&1 instead of &2):
What causes this issue? The delivery request &V3& contains objects from the namespace <ZH>&V1& </> but the delivery is as...
TR_AUSL592
Object from SAP or partner name range (&1 instead of namespace &2):
What causes this issue? The current delivery request &V3& contains objects from the name range <ZH>&V1&</>, however the n...
Click on this link to search all SAP messages.