How To Fix FDT_DSM021 - Application exits are not allowed in remote services

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_DSM - BRFplus: Decision Service Manager

• Message number: 021

• Message text: Application exits are not allowed in remote services

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_DSM021 - Application exits are not allowed in remote services ?

  The SAP error message FDT_DSM021 indicates that application exits are not allowed in remote services. This error typically occurs when there is an attempt to execute an application exit (a type of user exit or enhancement) in a context where it is not permitted, particularly in remote function calls (RFC) or web services.
  Cause:
  
  Remote Context: The error arises when a function module or method that is being called remotely tries to execute an application exit. Application exits are designed to be executed in a dialog context and are not supported in remote contexts.
  Configuration Issues: There may be misconfigurations in the way the remote service is set up, leading to attempts to invoke application exits.
  Code Logic: The code logic may inadvertently call an application exit when it should not, especially if the code is designed to work in both local and remote contexts.
  
  Solution:
  
  Review Code: Check the code that is being executed in the remote service. Ensure that it does not call any application exits. If it does, you will need to refactor the code to avoid this.
  Use Alternative Approaches: Instead of using application exits, consider using other enhancement techniques that are compatible with remote calls, such as BAdIs (Business Add-Ins) or explicit enhancement points.
  Error Handling: Implement error handling to gracefully manage situations where an application exit might be called inappropriately.
  Testing: After making changes, thoroughly test the remote service to ensure that it behaves as expected without invoking application exits.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific guidance or patches related to this error. SAP frequently updates its documentation and provides solutions for known issues.
  Documentation: Review the SAP documentation on user exits, BAdIs, and remote function calls to understand the limitations and best practices.
  Community Forums: Engage with the SAP community forums or support channels for additional insights or similar experiences from other users.
  
  By addressing the root cause of the error and ensuring that your code adheres to the constraints of remote services, you can resolve the FDT_DSM021 error effectively.