/FTI/CUST_ACCESS018 - TADIR entry creation failed, rolling back work and aborting creation

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/CUST_ACCESS -

• Message number: 018

• Message text: TADIR entry creation failed, rolling back work and aborting creation

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.

AnswerBot

• What is the cause and solution for SAP error message /FTI/CUST_ACCESS018 - TADIR entry creation failed, rolling back work and aborting creation ?

  The SAP error message /FTI/CUST_ACCESS018 TADIR entry creation failed, rolling back work and aborting creation typically indicates an issue related to the creation of a TADIR entry, which is a table in SAP that stores information about the objects in the system, such as programs, function modules, and other development objects.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to create entries in the TADIR table.
  Database Issues: There may be a problem with the database connection or the database itself, such as a lack of space or corruption.
  Transport Directory Issues: If the system is trying to create a transport request, there may be issues with the transport directory or configuration.
  Object Locking: The object being created may be locked by another user or process, preventing the creation of the TADIR entry.
  System Configuration: There may be configuration issues in the system that prevent the creation of TADIR entries.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create TADIR entries. This can be done by checking the user's roles and authorizations in transaction SU53 or SUIM.
  Database Check: Verify the database connection and check for any issues such as space limitations or corruption. You may need to consult with your database administrator.
  Transport Directory: Check the transport directory settings and ensure that they are correctly configured. You can do this in transaction STMS.
  Object Locking: Use transaction SM12 to check for any locks on the object being created. If there are locks, you may need to wait for them to be released or contact the user who has locked the object.
  System Logs: Check the system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  Reboot or Restart: In some cases, a simple restart of the application server or the entire system may resolve transient issues.
  
  Related Information:
  
  TADIR Table: The TADIR table is crucial for the transport system in SAP, as it keeps track of all development objects and their transport status.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE03 (Transport Organizer), and SE11 (Data Dictionary) for further investigation.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.