How To Fix COM_DML_CUST035 - Entry & & & already exists (TADIR table)

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_DML_CUST - MDF Messages

• Message number: 035

• Message text: Entry & & & already exists (TADIR table)

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 COM_DML_CUST035 - Entry & & & already exists (TADIR table) ?

  The SAP error message COM_DML_CUST035 indicates that there is an attempt to create an entry in the TADIR table (which is used for storing object directory entries) that already exists. This error typically occurs during the transport of objects or when trying to create a new entry that conflicts with an existing one.
  Cause:
  
  
  Duplicate Entry: The most common cause is that the entry you are trying to create already exists in the TADIR table. This can happen if:
  
  The object has already been transported and exists in the target system.
  There is a manual attempt to create an object that has the same key as an existing one.
  There is a misconfiguration or inconsistency in the transport requests.
  
  
  
  Transport Issues: If you are working with transport requests, it may be that the transport request has not been properly imported, or there are inconsistencies between the source and target systems.
  
  
  Solution:
  
  
  Check Existing Entries: 
  
  Use transaction SE11 (Data Dictionary) or SE16 (Data Browser) to check the TADIR table for existing entries that match the one you are trying to create. 
  You can filter by the object type and name to see if the entry already exists.
  
  
  
  Remove or Modify the Duplicate:
  
  If you find that the entry already exists and is not needed, you may consider deleting it (if appropriate) or modifying your new entry to avoid the conflict.
  If the existing entry is valid, you may need to adjust your transport request or the object you are trying to create.
  
  
  
  Transport Management:
  
  Ensure that all transport requests are properly imported and that there are no inconsistencies between the systems.
  If you suspect a transport issue, you may need to re-import the transport request or check the transport logs for errors.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or notes related to the specific object type you are working with, as there may be specific guidelines or known issues.
  
  
  
  Contact SAP Support: 
  
  If the issue persists and you cannot resolve it, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  TADIR Table: This table contains the directory entries for all objects in the SAP system. It is crucial for the transport system and object management.
  Transport Requests: Understanding how transport requests work in SAP can help in diagnosing issues related to object creation and transport.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE01 (Transport Organizer), SE09 (Workbench Organizer), and SE10 (Customizing Organizer) for managing transport requests.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.