How To Fix FDT_CP_MSG426 - No rows entered in Decision Table : '&1'

FDT_CP_MSG426 - Overview

• Message type: E = Error

• Message class: FDT_CP_MSG -

• Message number: 426

• Message text: No rows entered in Decision Table : '&1'

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_CP_MSG426 - No rows entered in Decision Table : '&1' ?

  The SAP error message FDT_CP_MSG426 indicates that no rows were entered in a decision table, which is part of the Business Rules Framework (BRF+) in SAP. This error typically occurs when a decision table is expected to have data for processing, but it is empty or not properly configured.
  
  Cause:
  
  Empty Decision Table: The decision table may not have any entries, which means there are no rules defined for the conditions being evaluated.
  Incorrect Configuration: The decision table might not be correctly linked to the relevant business logic or might not be activated.
  Data Retrieval Issues: There could be issues with how data is being retrieved or passed to the decision table, leading to it being empty at runtime.
  Authorization Issues: The user executing the process may not have the necessary authorizations to view or access the entries in the decision table.
  
  
  Solution:
  
  
  Check Decision Table Entries:
  
  Navigate to the decision table in the BRF+ workbench and verify