How To Fix BT672 - Reorganization of the event history has been started

SAP Error Message - Details

• Message type: E = Error

• Message class: BT - Background processing messages

• Message number: 672

• Message text: Reorganization of the event history 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 BT672 - Reorganization of the event history has been started ?

  The SAP error message BT672 indicates that a reorganization of the event history has been initiated. This message typically arises in the context of SAP Business Workflow or Business Transaction Management, where event histories can grow large and need to be managed to maintain system performance.
  Cause:
  The error message BT672 is not necessarily an error in the traditional sense but rather an informational message indicating that a background job for reorganizing the event history has been started. This can occur due to:
  
  Large Volume of Event Data: The event history table has accumulated a significant amount of data, which can impact performance.
  Scheduled Maintenance: A scheduled job or manual trigger has initiated the reorganization process to clean up or archive old event data.
  System Configuration: The system may be configured to automatically start reorganization processes based on certain thresholds.
  
  Solution:
  
  Monitor the Job: Check the status of the reorganization job in transaction SM37 (Job Monitoring). Ensure that it completes successfully without errors.
  Review Job Logs: After the job has completed, review the job logs for any warnings or errors that may indicate issues during the reorganization process.
  Adjust Retention Settings: If the event history is growing too large, consider adjusting the retention settings for event data. This can be done in the relevant configuration settings for the workflow or event management.
  Manual Cleanup: If necessary, you can manually trigger a cleanup or reorganization process using transaction SWF_CLEANUP or similar tools, depending on your specific SAP version and configuration.
  Consult Documentation: Refer to SAP documentation or notes related to event history management for best practices and recommendations.
  
  Related Information:
  
  Transaction Codes: 
  
  SM37: Job Monitoring
  SWF_CLEANUP: Workflow Cleanup
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or updates related to this message.
  Performance Tuning: Regularly monitor and tune the performance of your SAP system to prevent excessive growth of event history data.
  System Administration: Ensure that your system administrators are aware of the reorganization processes and can assist in monitoring and managing them effectively.
  
  If the message persists or if you encounter issues during the reorganization process, it may be beneficial to consult with SAP support or your internal SAP Basis team for further assistance.