Message type: E = Error
Message class: TR_AUSL - Software Delivery Composer Messages
Message number: 521
Message text: Entry can be transported but is not usually delivered:
The object entry indicates an object that is transportable in principle,
but usually has no significance for delivery.
Example of this are:
Transporting no-existant function modules (using 'LIMU FUNC')
<ZH>Note</>: Consistent delivery of these entries is only guaranteed by
delivering the entire function group (using 'R3TR FUGR').
Transporting software components (using 'R3TR VERS ...')
<ZH>Note</>: Delivering the complete object 'software component' is not
allowed. Instead, changes to the software component are performed by the
import tools themselves (when importing a delivery for this software
component).
Comment lines and control lines for transports (such as 'CORR MERG
...').
The system displays the affected objects in the results overview of the
object list check.
Check whether the specified objects are delivery-relevant and remove the
objects that you do not want to deliver. To do this, select them and
choose <LS>Correct Selected Entries</>.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL521
- Entry can be transported but is not usually delivered: ?The SAP error message TR_AUSL521 indicates that an entry can be transported but is not usually delivered. This message typically arises in the context of transport management in SAP, particularly when dealing with transport requests and the transport of objects between different SAP systems (e.g., from development to quality assurance or production).
Cause: The error message TR_AUSL521 usually occurs due to the following reasons: Custom Development: The object you are trying to transport is a custom development or configuration that is not part of the standard delivery of SAP. This means that while it can be transported, it is not included in the standard SAP transport packages. Transport Layer Settings: The transport layer settings for the object may not be configured to allow for standard delivery. This can happen if the object is part of a specific development package that is not intended for delivery. Transport Request Configuration: The transport request may not be set
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL520
Invalid entry in object list (invalid object type/object name/ ...):
What causes this issue? The object entry is incorrect (or not permitted in the current release). This may be due to an invalid object type or an inva...
TR_AUSL519
&1: no delivery component defined for delivery request &2
What causes this issue? You can only check the object list of request &V2& for objects in other software components if the request is assigne...
TR_AUSL522
Check not possible: object directory entry does not exist:
What causes this issue? The object directory entry is missing for the object entry. This object directory entry is absolutely necessary to perform th...
TR_AUSL523
Check not possible; package/development class &1 does not exist:
What causes this issue? The object entry has not been assigned to a package/development class. The entry must, however, be assigned to a development ...
Click on this link to search all SAP messages.