How To Fix CRM_MKTLIST_PACKAGE090 - Debugging mode is active

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_MKTLIST_PACKAGE - CRM Marketing: Messages External List Management

• Message number: 090

• Message text: Debugging mode is active

What causes this issue?

In the user settings of the user &V1& the parameter CRM_DEBUG_CODE is
set to the value MKTLIST.

System Response

If the parameter CRM_DEBUG_CODE is set to the value MKTLIST the system
doesn't start the workflow for the processing of the list. Instead of
the workflow the system tries to open a new SAPGUI window where the ABAP
debugger allows to debug the process steps.

How to fix this error?

If the processing of steps should be debugged the message can be
ignored. Otherwise the parameter CRM_DEBUG_CODE should be removed from
the user settings.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_MKTLIST_PACKAGE090 - Debugging mode is active ?

  The SAP error message "CRM_MKTLIST_PACKAGE090 Debugging mode is active" typically indicates that the system is currently in debugging mode, which can interfere with normal processing and lead to unexpected behavior or errors in the application.
  
  Cause:
  
  Debugging Mode Active: The error suggests that the debugging mode has been activated in the SAP system. This can happen if a developer or administrator has set breakpoints or activated debugging for a specific transaction or program.
  
  Configuration Issues: There may be issues with the configuration of the CRM Marketing List or related components that are being debugged.
  Custom Code: If there are custom enhancements or modifications in the CRM system, they might be causing the error when the debugging mode is active.
  
  
  Solution:
  
  
  Deactivate Debugging Mode:
  
  If you are not actively debugging, you should deactivate the debugging mode. You can do this by:
  Exiting the debugger if you are in a debugging session.
  Checking for any active breakpoints in the ABAP debugger