How To Fix ACMDT_OBJSTATUS035 - DDL source '&1' not exists in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4)

SAP Error Message - Details

• Message type: E = Error

• Message class: ACMDT_OBJSTATUS - ACM: Messages for the Object-Status of Designtime-Objects

• Message number: 035

• Message text: DDL source '&1' not exists in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4)

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 ACMDT_OBJSTATUS035 - DDL source '&1' not exists in table TADIR (PGMID=&2; OBJ=&3; DEVCLASS=&4) ?

  The SAP error message ACMDT_OBJSTATUS035 indicates that a Data Definition Language (DDL) source specified in the error message does not exist in the TADIR table. The TADIR table is a directory table in SAP that contains information about various objects in the SAP system, including their program IDs (PGMID), object types (OBJ), and development classes (DEVCLASS).
  Cause:
  The error can occur due to several reasons:
  
  Missing Object: The specified DDL source does not exist in the TADIR table. This could happen if the object was deleted or never created.
  Incorrect Object Name: There might be a typo or incorrect naming in the DDL source reference.
  Transport Issues: If the object was supposed to be transported from one system to another, it may not have been included in the transport request.
  Authorization Issues: The user may not have the necessary authorizations to view or access the object in question.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check TADIR Table:
  
  Use transaction SE11 to view the TADIR table and check if the specified DDL source exists. You can filter by the PGMID, OBJ, and DEVCLASS provided in the error message.
  
  
  
  Verify Object Existence:
  
  If the object does not exist, you may need to recreate it or ensure that it is properly defined in the system.
  
  
  
  Correct Naming:
  
  Double-check the naming of the DDL source in your code or configuration to ensure there are no typos.
  
  
  
  Transport Request:
  
  If the object is supposed to be in the system but is missing, check the transport requests to ensure that the object was included and successfully imported into the target system.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the object. You can check this in transaction SU53 or by consulting with your security team.
  
  
  
  Recreate the Object:
  
  If the object is indeed missing and cannot be found in any transport, you may need to recreate it manually.
  
  
  
  Related Information:
  
  TADIR Table: This table contains metadata about various objects in the SAP system, including their type, development class, and other attributes.
  Transaction Codes:
  
  SE11: Data Dictionary to view and manage database tables.
  SE80: Object Navigator to manage various development objects.
  SE03: Transport Organizer to manage transport requests.
  SU53: Authorization check analysis tool.
  
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or development team for further investigation.