How To Fix S1560 - Aggregation of statistical data has been started

SAP Error Message - Details

• Message type: E = Error

• Message class: S1 - Statistik / SAP-Monitor

• Message number: 560

• Message text: Aggregation of statistical data has been started

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 S1560 - Aggregation of statistical data has been started ?

  The SAP error message S1560, which states "Aggregation of statistical data has been started," typically indicates that a process related to the aggregation of statistical data is currently in progress. This message is not necessarily an error but rather an informational message that can occur in various contexts within SAP, particularly in modules that deal with statistical data, such as SAP Controlling (CO) or SAP Sales and Distribution (SD).
  Cause:
  
  Ongoing Process: The message usually means that a background job or a report that aggregates statistical data is currently running. This could be due to scheduled jobs or manual execution of reports.
  Locking Mechanism: SAP uses locking mechanisms to prevent data inconsistencies. If a job is running, it may lock certain tables or processes, leading to this message.
  Long-Running Jobs: If the aggregation process takes longer than expected, users may encounter this message when trying to access related data.
  
  Solution:
  
  Wait for Completion: If you encounter this message, the simplest solution is to wait for the ongoing aggregation process to complete. You can check the status of background jobs in transaction code SM37.
  Check Job Status: Use transaction SM37 to monitor the status of the job. Look for any jobs related to statistical data aggregation and see if they are still running or if they have completed successfully.
  Review Logs: If the job has failed or is taking too long, review the job logs for any errors or warnings that might indicate what went wrong.
  Restart Job: If the job has failed, you may need to restart it. Ensure that there are no other processes that could interfere with the aggregation.
  Consult Basis Team: If the issue persists or if you suspect that there is a problem with the system performance, consult your SAP Basis team for further investigation.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM37 (Job Monitoring), SM21 (System Log), and ST22 (Dump Analysis) for troubleshooting.
  Documentation: Refer to SAP Help documentation for specific modules to understand how statistical data aggregation works and any related configurations.
  Performance Tuning: If aggregation jobs frequently take too long, consider performance tuning of the database or reviewing the configuration of the aggregation process.
  
  If you continue to experience issues or if the message appears in a context that seems unusual, it may be beneficial to reach out to SAP support or your internal SAP support team for further assistance.