How To Fix FDT_DSM123 - Exit class &1 not called in Decision Manager system due to non-existence

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_DSM - BRFplus: Decision Service Manager

• Message number: 123

• Message text: Exit class &1 not called in Decision Manager system due to non-existence

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_DSM123 - Exit class &1 not called in Decision Manager system due to non-existence ?

  The SAP error message FDT_DSM123 indicates that a specific exit class is not being called in the Decision Manager system because it does not exist. This error typically arises in the context of SAP's Decision Service Management (DSM) when there is an attempt to execute a decision service that references an exit class that has not been defined or is not available in the system.
  Cause:
  
  Missing Exit Class: The exit class specified in the decision service configuration does not exist in the system.
  Incorrect Configuration: The decision service may be incorrectly configured, pointing to a non-existent or incorrectly named exit class.
  Transport Issues: If the exit class was recently transported from another system, it may not have been transported correctly or may not exist in the target system.
  Authorization Issues: The user executing the decision service may not have the necessary authorizations to access the exit class.
  
  Solution:
  
  
  Verify Exit Class: Check the configuration of the decision service to ensure that the exit class name is correct and that it exists in the system.
  
  Use transaction SE80 or SE24 to search for the exit class.
  
  
  
  Create or Transport Exit Class: If the exit class does not exist, you may need to create it or ensure that it is properly transported from the development environment to the production environment.
  
  If it is a custom class, ensure that the implementation is complete and activated.
  
  
  
  Check Configuration: Review the configuration settings in the Decision Manager to ensure that all references to exit classes are correct and that there are no typos or misconfigurations.
  
  
  Authorization Check: Ensure that the user executing the decision service has the necessary authorizations to access the exit class. You may need to check the roles and authorizations assigned to the user.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to Decision Service Management for any specific guidelines or troubleshooting steps related to exit classes.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Debugging: If you have access to the development environment, consider debugging the decision service to trace where the error occurs and gather more context about the missing exit class.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.