How To Fix UG090 - LOCTEST: TADIR object & & & with development class & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: UG - Messages for Repository Switch

• Message number: 090

• Message text: LOCTEST: TADIR object & & & with development class & does not exist

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 UG090 - LOCTEST: TADIR object & & & with development class & does not exist ?

  The SAP error message UG090 indicates that there is an issue related to the TADIR object, which is a table that stores information about development objects in the SAP system. The error message specifically states that the TADIR object does not exist for the specified development class.
  Cause:
  
  Non-existent Development Class: The development class specified in the error message does not exist in the system.
  Transport Directory Issues: The object may not have been transported correctly, or the transport directory may not be updated.
  Authorization Issues: The user may not have the necessary authorizations to access the development class or the objects within it.
  Object Deletion: The object might have been deleted or not created properly in the system.
  Incorrect Object Type: The object type being referenced may not match the expected type for the development class.
  
  Solution:
  
  
  Check Development Class: Verify that the development class specified in the error message exists in the system. You can do this by using transaction SE80 (Object Navigator) or SE11 (Data Dictionary) to look for the development class.
  
  
  Check TADIR Entries: Use transaction SE03 (Transport Organizer Tools) to check the TADIR entries. You can look for the specific object and development class to see if it exists.
  
  
  Transport Request: If the object is part of a transport request, ensure that the transport request has been released and imported into the target system.
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to access the development class and the objects within it. You can check this using transaction SU53 (Authorization Check).
  
  
  Recreate Object: If the object is missing, you may need to recreate it in the development class.
  
  
  Check Object Type: Ensure that the object type you are trying to access is correct and matches the expected type for the development class.
  
  
  Related Information:
  
  TADIR Table: The TADIR table contains metadata about development objects, including their type, name, and associated development class.
  Transport Management System (TMS): Understanding how the transport management system works can help in troubleshooting issues related to object transport.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to the UG090 error message or TADIR objects.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.