How To Fix FDT_CORE808 - Message text of &1(&2) requires a second message variable

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 808

• Message text: Message text of &1(&2) requires a second message variable

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_CORE808 - Message text of &1(&2) requires a second message variable ?

  The SAP error message FDT_CORE808 indicates that a message text requires a second message variable. This typically occurs in the context of using message classes in SAP, where certain messages are defined to include placeholders for dynamic content. When a message is defined with multiple placeholders, the system expects the corresponding number of variables to be provided when the message is called.
  Cause:
  
  Missing Variable: The message text defined in the message class has more placeholders than the number of variables provided when the message is triggered.
  Incorrect Message Definition: The message might be incorrectly defined in the message class, expecting more variables than intended.
  Programming Error: There might be an error in the ABAP code where the message is being called, leading to an incorrect number of parameters being passed.
  
  Solution:
  
  
  Check Message Definition:
  
  Go to transaction SE91 (Message Class) and find the message class and message number associated with FDT_CORE808.
  Verify the message text and ensure that it is defined correctly with the appropriate number of placeholders (e.g., &1, &2).
  
  
  
  Update ABAP Code:
  
  Review the ABAP code where the message is being called. Ensure that the correct number of variables is being passed to the message.
  For example, if the message text is defined as Message text with &1 and &2, ensure that two variables are provided in the call, like this:
  MESSAGE 'Message text with &1 and &2' USING var1 var2.
  
  
  
  
  Testing:
  
  After making the necessary changes, test the functionality again to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Message Classes: In SAP, message classes are used to manage messages that can be displayed to users. Each message can have multiple variables that can be replaced with dynamic content.
  Placeholders: Placeholders in message texts are represented by &1, &2, etc. Each placeholder corresponds to a variable that will be substituted when the message is displayed.
  Debugging: If you are unsure where the message is being triggered, you can use the debugger to trace the execution and find the exact point where the message is called.
  
  If you continue to experience issues after checking the message definition and the ABAP code, consider reaching out to your SAP support team or consulting SAP documentation for further assistance.