How To Fix FDT_EXPRESSIONS752 - Column &1 does not exist in table &2

FDT_EXPRESSIONS752 - Overview

• Message type: E = Error

• Message class: FDT_EXPRESSIONS - Formula & Derivation Tool: Expressions

• Message number: 752

• Message text: Column &1 does not exist in table &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_EXPRESSIONS752 - Column &1 does not exist in table &2 ?

  The SAP error message FDT_EXPRESSIONS752 indicates that there is an issue with a column reference in a table. Specifically, the error states that the column specified (denoted as &1) does not exist in the table specified (denoted as &2). This error typically occurs in the context of using the SAP Fiori or SAP S/4HANA applications, particularly when working with data expressions or field mappings.
  
  Cause:
  
  Incorrect Column Name: The column name specified in the expression or configuration does not match any of the columns in the specified table.
  Table Structure Changes: The underlying database table may have been modified (e.g., columns added, renamed, or deleted) after the expression was created.
  Typographical Errors: There may be a typo in the column name or table name.
  Data Source Issues: The data source being referenced may not be correctly configured or may not be available in the current context.
  
  
  Solution:
  
  Verify Column Name: Check the column name (&1) in the