How To Fix FDT_CHANGE_INFO091 - Database table for fetch was changed from &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CHANGE_INFO - FDT: Changes info in object for different versions

• Message number: 091

• Message text: Database table for fetch was changed from &1 to &2

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 FDT_CHANGE_INFO091 - Database table for fetch was changed from &1 to &2 ?

  The SAP error message FDT_CHANGE_INFO091 indicates that there has been a change in the database table that is being used for fetching data in a specific context. The message specifies that the database table has changed from one table (&1) to another (&2). This typically occurs in the context of using the SAP Fiori Design Studio or when working with data models in SAP applications.
  Cause:
  
  Data Model Changes: The underlying data model or database table has been modified. This could be due to changes in the database schema, such as renaming tables, changing table structures, or altering relationships between tables.
  Configuration Changes: Changes in the configuration of the application or the data source that the application is trying to access.
  Transport Issues: If changes were transported from one system to another (e.g., from development to production), there might be inconsistencies in the data model.
  
  Solution:
  
  Check Data Model: Review the data model configuration to ensure that the correct tables are being referenced. Verify that the changes made to the database schema are reflected in the application.
  Update References: If the application is still referencing the old table, update the references to point to the new table.
  Rebuild Data Model: If necessary, rebuild the data model in the application to ensure it aligns with the current database schema.
  Check Transport Logs: If the issue arose after a transport, check the transport logs for any errors or warnings that might indicate issues with the changes made.
  Consult Documentation: Review any relevant SAP documentation or release notes that might provide insights into changes made to the database tables or data models.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Transaction Codes: Use transaction codes like SE11 (Data Dictionary) to inspect the database tables and their structures.
  Debugging: If the issue persists, consider debugging the application to trace where the error is being triggered and gather more context about the data fetch operation.
  
  If the problem continues after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.