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

Close

How To Fix TG129 - -> & objects marked as generated and not delivered


SAP Error Message - Details

  • Message type: E = Error

  • Message class: TG - Messages for Upgrade Repository Switch

  • Message number: 129

  • Message text: -> & objects marked as generated and not delivered

  • Show details Hide details


  • Self-Explanatory Message

    Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

    To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

    Unfortunately, there isn't any extra information in this error notice.



    What else can you do?

    First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

    Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

    You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.


Smart SAP Assistant

  • What is the cause and solution for SAP error message TG129 - -> & objects marked as generated and not delivered ?

    The SAP error message TG129 indicates that certain objects in the system are marked as "generated" and are not delivered. This typically occurs in the context of transport requests and can affect the transport of objects between different SAP systems (e.g., from development to quality assurance or production).

    Cause:

    1. Generated Objects: The objects in question are usually generated artifacts, such as database views, function modules, or other objects that are created dynamically based on the underlying definitions. These objects are not physically stored in the transport request but are generated at runtime.

    2. Transport Configuration: The transport configuration may not be set up to include generated objects, or the objects may not have been properly included in the transport request.

    3. Development Environment: The objects may have been created or modified in a way that they are not recognized as transportable, often due to missing dependencies or incorrect settings.

    Solution:

    1. Check Object Status: Verify the status of the objects in question. You can do this by using transaction codes like SE80 (Object Navigator) or SE11 (Data Dictionary) to check if the objects are indeed marked as generated.

    2. Include in Transport Request: If the objects need to be transported, ensure that they are included in the transport request. You may need to manually add them to the transport request if they were not automatically included.

    3. Re-generate Objects: If the objects are not being recognized correctly, you may need to regenerate them. This can often be done by reactivating the relevant development objects.

    4. Check Transport Layer: Ensure that the transport layer is correctly configured and that the objects are in the correct transport directory.

    5. Consult Documentation: Review SAP documentation or notes related to the specific objects you are working with, as there may be specific instructions or known issues related to those objects.

    6. SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if this is affecting critical business processes.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SE09 (Transport Organizer), SE10 (Transport Organizer Tools), and SE01 (Transport Organizer) for managing transport requests.
    • SAP Notes: Search for SAP Notes related to TG129 or the specific objects you are dealing with, as there may be patches or updates that address this issue.
    • Transport Management System (TMS): Understanding how TMS works can help in managing transports effectively and avoiding issues with generated objects.

    By following these steps, you should be able to address the TG129 error and ensure that your objects are properly managed within the SAP transport system.

    • 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