How To Fix CMX_DA119 - Session active, logging not switched on

SAP Error Message - Details

• Message type: E = Error

• Message class: CMX_DA - Manufacturing Data Access: Messages

• Message number: 119

• Message text: Session active, logging not switched on

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 CMX_DA119 - Session active, logging not switched on ?

  The SAP error message CMX_DA119: Session active, logging not switched on typically occurs in the context of SAP's Data Aging (DA) functionality. This error indicates that there is an active session for data aging, but the logging feature is not enabled, which is necessary for the operation to proceed.
  Cause:
  
  Active Session: There is an ongoing session that is trying to perform data aging operations.
  Logging Not Enabled: The logging feature for data aging is not activated in the system settings, which is required for tracking changes and ensuring data integrity during the aging process.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Active Sessions:
  
  Use transaction code SM50 or SM66 to check for any active work processes or sessions that might be related to data aging.
  If you find any active sessions that are not needed, you can terminate them.
  
  
  
  Enable Logging:
  
  Ensure that logging is enabled for data aging. This can typically be done in the configuration settings of the Data Aging framework.
  You may need to consult your SAP Basis or system administrator to enable logging if you do not have the necessary permissions.
  
  
  
  Review Configuration:
  
  Check the configuration settings for Data Aging in transaction SIMG or SPRO. Look for settings related to data aging and ensure that logging is properly configured.
  
  
  
  Restart the Process:
  
  After ensuring that there are no active sessions and logging is enabled, try to restart the data aging process.
  
  
  
  Consult Documentation:
  
  Refer to the official SAP documentation or notes related to Data Aging for any specific configurations or prerequisites that may be required.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SM50: Monitor active processes.
  SM66: Monitor global processes.
  SIMG or SPRO: Access configuration settings.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that might provide additional insights or patches related to this error.
  
  
  Data Aging: Understand the concept of data aging in SAP, which is used to manage large volumes of data by moving older data to less expensive storage solutions while keeping the system performance optimal.
  
  
  If the issue persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.