Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix TR_AUSL799 - @AI@ Details for delivery of generated objects: see long text


SAP Error Message - Details

  • 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

  • Show details Hide details
  • What causes this issue?

    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.

    System Response

    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.

    How to fix this error?

    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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message 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:

    1. Missing Dependencies: The objects you are trying to transport may depend on other objects that are not included in the transport request.
    2. Incorrect Configuration: There may be configuration issues in the transport settings or the objects themselves.
    3. Transport Request Issues: The transport request may be incomplete or not properly released.
    4. Authorization Issues: The user may not have the necessary authorizations to perform the transport.
    5. System Configuration: There may be inconsistencies in the system configuration that prevent the transport from being processed correctly.

    Solution:

    1. 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.
    2. 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.
    3. Release Transport Request: Ensure that the transport request is properly released. You can do this in transaction SE09 or SE10.
    4. Check Authorizations: Verify that the user performing the transport has the necessary authorizations. You may need to consult with your security team.
    5. 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.
    6. 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:

    • Transaction Codes: SE01 (Transport Organizer), SE09 (Workbench Organizer), SE10 (Customizing Organizer).
    • SAP Notes: Search for specific SAP Notes related to transport issues or the TR_AUSL799 error message.
    • Transport Logs: Review transport logs for additional error messages or warnings that may provide more context.
    • SAP Community: Consider checking the SAP Community forums for discussions related to this error, as other users may have encountered and resolved similar issues.

    If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant