How To Fix FDT_CORE035 - Expression type &1 cannot be used to create expressions, no class defined

FDT_CORE035 - Overview

• Message type: E = Error

• Message class: FDT_CORE - Formula & Derivation Tool: Core

• Message number: 035

• Message text: Expression type &1 cannot be used to create expressions, no class defined

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_CORE035 - Expression type &1 cannot be used to create expressions, no class defined ?

  The SAP error message FDT_CORE035 indicates that there is an issue with the expression type being used in a formula or expression within the SAP system. Specifically, the error states that the expression type cannot be used to create expressions because no class is defined for it. This typically occurs in the context of SAP's Flexible Data Import (FDI) or similar functionalities where expressions are defined for data processing.
  
  Cause:
  
  Undefined Expression Type: The expression type you are trying to use has not been defined in the system. This could be due to a missing configuration or a custom expression type that has not been properly set up.
  Incorrect Configuration: There may be a misconfiguration in the data model or the expression definitions that leads to the system not recognizing the expression type.
  Version Compatibility: If you are using a custom or third-party solution, it may not be compatible with the current version of