How To Fix /STMC/CR_MSG699 - Error while recording statistics; current_mode=&1, required_mode=&2

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_MSG -

• Message number: 699

• Message text: Error while recording statistics; current_mode=&1, required_mode=&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 /STMC/CR_MSG699 - Error while recording statistics; current_mode=&1, required_mode=&2 ?

  The SAP error message /STMC/CR_MSG699 indicates that there is an issue with recording statistics in the system. The message specifies that there is a mismatch between the current mode and the required mode for recording statistics. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause
  The error occurs when the system is trying to record statistics, but the current mode of operation does not match the required mode. This can happen due to several reasons, including:
  
  Configuration Issues: The system may not be configured correctly for the required mode of operation.
  System State: The system might be in a state that does not allow for statistics recording (e.g., during a maintenance window or in a specific operational mode).
  Authorization Issues: The user or process attempting to record statistics may not have the necessary authorizations.
  Technical Issues: There could be underlying technical issues or bugs in the SAP system that are causing the error.
  
  Solution
  To resolve the error, you can take the following steps:
  
  
  Check Configuration: Verify the configuration settings related to statistics recording. Ensure that the system is set up to operate in the required mode.
  
  
  Review System State: Check if the system is in a maintenance mode or any other state that might prevent statistics recording. If so, wait until the system is back to normal operation.
  
  
  User Authorizations: Ensure that the user or process has the necessary authorizations to record statistics. You may need to consult with your SAP security team to verify this.
  
  
  Consult SAP Notes: Look for any relevant SAP Notes or patches that might address this specific error. SAP frequently releases updates that fix known issues.
  
  
  Check Logs: Review system logs (transaction SM21) for any additional error messages or warnings that could provide more context about the issue.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. Provide them with the error message details and any relevant logs.
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ST03N (Workload Analysis) and ST04 (Database Performance Analysis) for monitoring performance and statistics.
  SAP Documentation: Review SAP documentation related to performance monitoring and statistics recording for more detailed guidance.
  Community Forums: Check SAP Community forums for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.