How To Fix KX364 - Error saving newly created objects in TADIR:

SAP Error Message - Details

• Message type: E = Error

• Message class: KX - EC-EIS/EC-BP: Data basis, data collection

• Message number: 364

• Message text: Error saving newly created objects in TADIR:

What causes this issue?

Objects entry in the global object catalog was unsuccesssful.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Enter the objects in table TADIR using the table maintenance
transaction. Assign the following development classes for generation:
'KC ' = objects generated by SAP for the SAP-EIS application;
'KCG0' = objects generated by the user for the SAP-EIS application;
'KE ' = objects generated by SAP for the application CO-PA;
'KEG0' = objects generated by the user for the application CO-PA
Enter 'R3TR' as program ID here, as object type and object name in
the action log: R3TR TABL T2701 or R3TR DTEL RKCG_DIM01.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KX364 - Error saving newly created objects in TADIR: ?

  The SAP error message KX364 typically occurs when there is an issue related to saving newly created objects in the TADIR table, which is the repository for all development objects in SAP. This error can arise due to various reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to create or modify objects in the TADIR table.
  Database Lock: There may be a lock on the TADIR table or related tables, preventing the saving of new objects.
  Transport Directory Issues: Problems with the transport directory or transport requests can lead to this error.
  Inconsistent Data: There may be inconsistencies in the data being saved, such as missing required fields or invalid object types.
  System Configuration: Incorrect system configuration or settings related to the development environment can also lead to this error.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create and modify objects. This can be done by checking the user's roles and authorizations in transaction SU53 or SUIM.
  Release Locks: Use transaction SM12 to check for and release any locks on the TADIR table or related tables that may be causing the issue.
  Check Transport Directory: Verify that the transport directory is correctly configured and that there are no issues with transport requests. You can check this in transaction SE09 or SE10.
  Validate Object Data: Ensure that all required fields for the object being created are filled out correctly and that the object type is valid. Review the object creation process for any missing information.
  System Configuration: Review the system configuration settings related to the development environment. Ensure that all necessary components are correctly set up.
  Check for SAP Notes: Look for any relevant SAP Notes that may address this specific error. You can search for notes in the SAP Support Portal.
  
  Related Information:
  
  
  Transaction Codes: 
  
  SE80: Object Navigator, where you can create and manage development objects.
  SE09/SE10: Transport Organizer, for managing transport requests.
  SM12: To check and manage database locks.
  SU53: To analyze authorization issues.
  
  
  
  SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on your system configuration and the exact nature of the error.
  
  
  By following these steps, you should be able to diagnose and resolve the KX364 error in SAP.