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: 799
Message text: @AI@ Details for delivery of generated objects: see long text
Only specific generated objects can be delivered. The required attribute
is not currently maintained which is why it is not possible to produce a
list of generated objects due to VOFM.
The system always displays this message to inform you that you can
remove VOFM-generated objects from the error list by specifying an RFC
connection to the development system in table TRDELVCHKA.
To specify the RFC destination of the development system, proceed as
follows:
If the RFC destination does not yet exist, use the relevant transaction
to create the <DS:TRAN.SM59>RFC destination</> for the development
system.
In <DS:TRAN.SE16>transaction SE16</> call table TRDELVCHKA.
Enter the following values:
CHECK_NAME,,,,&V1&
DLV_NAME,,,,&V2&
ATTRIBUTE,,,,&V3&
POS,,,,<any>
VALUE,,,,<RFC destination>
Save your entries.
Run the check again.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL799
- @AI@ Details for delivery of generated objects: see long text ?The SAP error message TR_AUSL799 typically relates to issues with the transport of generated objects in the SAP system. This error can occur during the transport process when there are problems with the objects that are being transported, such as missing dependencies, incorrect configurations, or issues with the transport request itself.
Cause:
- Missing Dependencies: The objects you are trying to transport may depend on other objects that are not included in the transport request.
- Incorrect Configuration: There may be configuration issues in the transport settings or the objects themselves.
- Transport Request Issues: The transport request may be incomplete or not properly released.
- Authorization Issues: The user may not have the necessary authorizations to perform the transport.
- System Configuration: There may be inconsistencies in the system configuration that prevent the transport from being processed correctly.
Solution:
- Check Dependencies: Review the objects in the transport request and ensure that all dependencies are included. You can use transaction code SE01 or SE09 to analyze the transport request.
- Review Long Text: The error message often has a long text that provides more details. You can view this by clicking on the message or using transaction code SE91 to look up the message.
- Release Transport Request: Ensure that the transport request is properly released. You can do this in transaction SE09 or SE10.
- Check Authorizations: Verify that the user performing the transport has the necessary authorizations. You may need to consult with your security team.
- System Consistency: Check for any inconsistencies in the system that may affect the transport. This may involve checking the transport directory or the transport logs.
- Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. You can search for notes in the SAP Support Portal.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
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 ...
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_AUSL801
@AI@ Details for delivery of modifications: see long text
What causes this issue? If objects of other software components are contained in the delivery, the system displays these as errors as standard. If yo...
TR_AUSL_EXT259
Requests included in delivery request &1 contain entries in table &2
What causes this issue? While including the flagged change requests in delivery request &V1&, the system detected entries in database table &...
Click on this link to search all SAP messages.