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: 794
Message text: Generated object (from CHDO &1, not to be delivered):
The object entry identifies an object that was generated automatically
when the change document object (R3TR CHDO &V1&) was created. This
object cannto be transported and delivered. It is generated
automatically when the change document object &V1& is imported into the
target system.
Output of the relevant objects in the results overview of the object
list check.
You remove the object entries from the delivery by selecting them and
choosing <LS>Correct Entries</>. If these entries are to be generated in
the target system, then ensure that the delivery request contains the
transport object R3TR CHDO &V1&
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_AUSL794
- Generated object (from CHDO &1, not to be delivered): ?The SAP error message TR_AUSL794 typically indicates that there is an issue with the transport of a generated object, specifically that the object from a Change Document Object (CHDO) is not set to be delivered. This can occur in various scenarios, particularly when dealing with transport requests and change management in SAP systems.
Cause:
- Object Not Marked for Transport: The object in question may not be marked for transport, meaning it is not included in the transport request.
- Transport Request Issues: There may be issues with the transport request itself, such as it being incomplete or not properly released.
- Configuration Issues: There could be configuration settings in the transport management system that prevent the object from being delivered.
- Authorization Issues: The user may not have the necessary authorizations to transport the object.
Solution:
- Check Transport Request: Verify that the transport request includes the object. If it is missing, you may need to add it manually.
- Release Transport Request: Ensure that the transport request is released. You can do this in the Transport Organizer (transaction SE09 or SE10).
- Review Object Settings: Check the settings for the object in question to ensure it is marked for transport. This can often be done in the development environment.
- Authorization Check: Ensure that the user has the necessary authorizations to perform transport operations.
- Consult Transport Logs: Review the transport logs for any additional error messages or warnings that may provide more context on the issue.
- Contact Basis Team: If the issue persists, it may be necessary to involve the Basis team to check for any underlying system issues or configuration problems.
Related Information:
If you continue to experience issues after following these steps, it may be beneficial to consult with SAP support or your internal SAP team for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL792
Time stamp of delivery request: &1 &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TR_AUSL791
Time stamp of last correction/check: &1 &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TR_AUSL795
Inconsistent package/development class information (&1)
What causes this issue? The package/software class of the displayed objects is assigned to the coftware component (TDEVC~DLVUNIT) '&V2&&...
TR_AUSL797
Table PUTTB is empty
What causes this issue? The table PUTTB does not contain any entries for the basis release of the system. This means that the check for used objects ...
Click on this link to search all SAP messages.