How To Fix TG358 - Finding generated objects

SAP Error Message - Details

• Message type: E = Error

• Message class: TG - Messages for Upgrade Repository Switch

• Message number: 358

• Message text: Finding generated objects

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 TG358 - Finding generated objects ?

  The SAP error message TG358 typically relates to issues with generated objects in the context of ABAP development or when working with SAP's transport management system. This error can occur when the system is unable to find or access generated objects that are required for a particular operation, such as activating a program, report, or other development objects.
  Cause:
  
  Missing Generated Objects: The objects that are supposed to be generated (like function modules, classes, or interfaces) may not have been generated properly or are missing.
  Transport Issues: If the objects were transported from one system to another, there may have been issues during the transport process that caused the objects not to be available in the target system.
  Development Environment Issues: Sometimes, issues in the development environment, such as inconsistencies in the database or problems with the ABAP workbench, can lead to this error.
  Authorization Issues: Lack of proper authorizations can prevent the system from accessing the generated objects.
  
  Solution:
  
  Re-generate Objects: If the objects are missing, try to re-generate them. This can often be done by going to the relevant transaction (like SE80 for Object Navigator) and manually triggering the generation process.
  Check Transport Logs: If the issue is related to transport, check the transport logs for any errors or warnings that might indicate what went wrong during the transport process.
  Activate Objects: Ensure that all related objects are activated. Sometimes, activating the parent object can resolve issues with child objects.
  Check Authorizations: Ensure that the user has the necessary authorizations to access and manipulate the objects in question.
  System Consistency Check: Run consistency checks in the system to identify any inconsistencies that might be causing the issue. This can be done using transaction codes like SE11 (Data Dictionary) or SE14 (Database Utility).
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE11 (Data Dictionary), SE37 (Function Module), and SE24 (Class Builder) for managing and troubleshooting ABAP objects.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  Documentation: Review SAP documentation related to ABAP development and transport management for best practices and troubleshooting tips.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or consult SAP support for further assistance.