How To Fix FDT_CORE802 - Message number &1 in message class &2 does not exist

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 802

• Message text: Message number &1 in message class &2 does not exist

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_CORE802 - Message number &1 in message class &2 does not exist ?

  The SAP error message FDT_CORE802 with the description "Message number &1 in message class &2 does not exist" typically indicates that the system is trying to reference a message that is not defined in the specified message class. This can occur in various scenarios, such as when using the SAP Fiori apps, SAP Forms, or other functionalities that rely on message classes for user feedback.
  Cause:
  
  Missing Message Definition: The message number specified in the error does not exist in the message class. This could be due to a missing translation or a configuration issue.
  Custom Development: If there are custom developments or enhancements, the message might not have been properly defined in the custom message class.
  Transport Issues: If the message class was transported from one system to another (e.g., from development to production), it might not have been included in the transport request.
  System Upgrade: After an upgrade, some message classes may not be fully updated or might have been deprecated.
  
  Solution:
  
  Check Message Class: Use transaction code SE91 to check the message class and see if the message number exists. If it does not, you may need to create it.
  Create Missing Message: If the message is indeed missing, you can create it in the message class using SE91. Ensure that you provide a meaningful description for the message.
  Review Custom Code: If the error is coming from custom code, review the code to ensure that it is referencing the correct message class and message number.
  Transport Requests: If the issue arose after a transport, check the transport logs to ensure that the message class was included and properly transported.
  System Configuration: Ensure that the system is properly configured and that all necessary components are installed and activated.
  
  Related Information:
  
  Transaction Codes:
  
  SE91: To manage message classes.
  SE80: To check for custom developments that might be causing the issue.
  
  
  SAP Notes: Check SAP Notes for any known issues related to the specific message class or error message.
  Documentation: Review SAP documentation for the specific application or module you are working with to understand how messages are handled.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.