How To Fix FDT_CP_MSG236 - &1 is not supported as result in Orchestration in Decision table with &2

FDT_CP_MSG236 - Overview

• Message type: E = Error

• Message class: FDT_CP_MSG -

• Message number: 236

• Message text: &1 is not supported as result in Orchestration in Decision table with &2

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_MSG236 - &1 is not supported as result in Orchestration in Decision table with &2 ?

  The SAP error message FDT_CP_MSG236 typically indicates that there is an issue with the configuration of a decision table in the context of orchestration within the SAP system. This error message suggests that a specific result type is not supported for the given context or configuration.
  
  Cause:
  
  Unsupported Result Type: The error occurs when the result type specified in the decision table is not compatible with the orchestration framework or the specific context in which it is being used.
  
  Configuration Issues: There may be a misconfiguration in the decision table or the orchestration setup that leads to this incompatibility.
  Data Type Mismatch: The data type of the result being returned may not match the expected data type for the orchestration process.
  
  
  Solution:
  
  Check Result Type: Review the result type specified in the decision table. Ensure that it is a valid and supported type for the orchestration context you are working with.
  Modify Decision Table: If the result