DT035 - Table type changed from &->& (Table is deleted from DB)

SAP Error Message - Details

• Message type: E = Error

• Message class: DT - Table activation (incl. indexes)

• Message number: 035

• Message text: Table type changed from &->& (Table is deleted from DB)

What causes this issue?

The table type has changed. Changes in the database objects have
therefore become necessary. An existing database table must be deleted.

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?

This action might be carried out automatically by the system. Otherwise
you must delete the table from the database yourself using the database
utility (SE14).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DT035 - Table type changed from &->& (Table is deleted from DB) ?

  The SAP error message DT035 indicates that a table type has changed, specifically that a table has been deleted from the database. This error typically arises in the context of ABAP development, particularly when working with data dictionary objects or when there are inconsistencies between the data dictionary and the underlying database.
  Cause:
  
  Table Deletion: The most straightforward cause is that a database table that was previously defined in the ABAP Dictionary has been deleted from the database. This could happen due to a manual deletion or as part of a transport request that removed the table.
  Transport Issues: If a transport request was moved from one system to another (e.g., from development to production) and the table was deleted in the target system, this error can occur.
  Inconsistent Data Dictionary: If there are inconsistencies between the ABAP Dictionary and the actual database schema, such as changes made directly in the database without corresponding updates in the ABAP Dictionary.
  
  Solution:
  
  Check Database: Verify if the table in question has indeed been deleted from the database. You can do this by checking the database directly or using transaction codes like SE11 (Data Dictionary) or SE14 (Database Utility).
  Recreate the Table: If the table is missing and it is required, you may need to recreate it in the database. This can be done by using the Data Dictionary (SE11) to define the table again and then activating it.
  Adjust Transport Requests: If the issue arose due to a transport request, ensure that the transport is correctly configured and that all necessary objects are included. You may need to re-import the transport or adjust it to include the missing table.
  Synchronize Data Dictionary: If there are inconsistencies, you can use transaction SE14 to synchronize the database and the ABAP Dictionary. This can help resolve discrepancies between the two.
  Check for Dependencies: If other objects depend on the deleted table, you may need to update or remove those dependencies to avoid further errors.
  
  Related Information:
  
  
  Transaction Codes:
  
  SE11: Data Dictionary - to view and manage database tables and types.
  SE14: Database Utility - to check and adjust the database structure.
  SE80: Object Navigator - to view all objects related to a specific development object.
  
  
  
  Documentation: Refer to SAP Help documentation for more details on data dictionary management and error handling.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide specific guidance or solutions based on the version of SAP you are using.
  
  
  Development Guidelines: Ensure that any changes to the database schema are properly documented and communicated to all relevant team members to avoid inconsistencies in the future.
  
  
  By following these steps, you should be able to diagnose and resolve the DT035 error effectively.