How To Fix FDT_EXPRESSIONS801 - Function module &1 not found

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 801

• Message text: Function module &1 not found

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_EXPRESSIONS801 - Function module &1 not found ?

  The SAP error message "FDT_EXPRESSIONS801 Function module &1 not found" typically indicates that the system is trying to call a function module that does not exist or is not accessible in the current context. This error is often related to the use of the FDT (Form Data Tool) or other functionalities that rely on specific function modules.
  Causes:
  
  Missing Function Module: The function module specified in the error message is not available in the SAP system. This could be due to it not being created, deleted, or not transported correctly.
  Transport Issues: If the function module was recently transported from another system (like Development to Quality or Production), it may not have been included in the transport request.
  Authorization Issues: The user may not have the necessary authorizations to access the function module.
  Incorrect Configuration: The configuration settings in the FDT or related areas may be incorrect, leading to the system attempting to call a non-existent function module.
  System Version: The function module may exist in a different version of SAP or may have been deprecated in the current version.
  
  Solutions:
  
  
  Check Function Module Existence:
  
  Use transaction SE37 (Function Builder) to check if the function module exists in the system. If it does not exist, you may need to create it or transport it from another system.
  
  
  
  Transport Requests:
  
  If the function module is missing, check the transport requests to ensure that it was included and successfully transported. You may need to re-transport it if it was missed.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to execute the function module. You can check this using transaction SU53 after the error occurs.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the FDT or related areas to ensure that they are set up correctly. This may involve reviewing the settings in transaction FDT or related transactions.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific function module or the FDT to see if there are any known issues or updates.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. Provide them with the error message details and any relevant context.
  
  
  
  Related Information:
  
  Transaction Codes: SE37 (Function Builder), SE80 (Object Navigator), FDT (Form Data Tool).
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide guidance on function modules.
  System Logs: Check system logs (transaction SLG1) for additional error messages or context that may help diagnose the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.