How To Fix AD347 - Table &: Structure changed; generate the database table again

SAP Error Message - Details

• Message type: E = Error

• Message class: AD - Data Dictionary application messages

• Message number: 347

• Message text: Table &: Structure changed; generate the database table again

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 AD347 - Table &: Structure changed; generate the database table again ?

  The SAP error message AD347 indicates that there has been a change in the structure of a database table, and as a result, the database table needs to be regenerated. This typically occurs when there are modifications made to the underlying data dictionary objects, such as fields being added, removed, or modified in a table or structure.
  Cause:
  
  Change in Data Dictionary: The most common cause is that the structure of a table or a related structure has been altered in the ABAP Dictionary (SE11). This could involve adding new fields, changing field types, or modifying field lengths.
  Transport Requests: If changes were transported from one system to another (e.g., from development to quality assurance or production), and the transport did not include the necessary adjustments to the database table.
  Inconsistent State: The database table may be in an inconsistent state due to failed updates or other issues.
  
  Solution:
  To resolve the AD347 error, you need to regenerate the database table. Here are the steps to do this:
  
  
  Go to Transaction SE11:
  
  Enter the transaction code SE11 in the command field.
  
  
  
  Select the Table:
  
  Enter the name of the table that is causing the error and click on the "Display" button.
  
  
  
  Check the Structure:
  
  Review the structure of the table to ensure that it reflects the intended changes.
  
  
  
  Activate the Table:
  
  If there are any changes that need to be activated, click on the "Activate" button. This will regenerate the database table.
  
  
  
  Generate the Table:
  
  If the table is already activated but still shows the error, you may need to explicitly generate the database table. You can do this by selecting the "Utilities" menu, then "Database Object", and finally "Generate".
  
  
  
  Check for Transport Issues:
  
  If the changes were transported, ensure that the transport request was completed successfully and that all necessary objects were included.
  
  
  
  Database Consistency Check:
  
  You can also run a consistency check on the database using transaction SE14 (Database Utility) to ensure that everything is in order.
  
  
  
  Recheck the Application:
  
  After regenerating the table, recheck the application or transaction that was causing the error to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SE11: Data Dictionary (for viewing and modifying tables and structures).
  SE14: Database Utility (for checking and adjusting database objects).
  
  
  
  Documentation: Always refer to SAP documentation or notes related to the specific version of SAP you are using, as there may be version-specific considerations.
  
  
  Backup: Before making changes, ensure that you have a backup of your data and that you are following your organization's change management procedures.
  
  
  If the problem persists after following these steps, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.