How To Fix KR367 - The selected totals records are destroyed

KR367 - Overview

• Message type: E = Error

• Message class: KR - Archiving Reports and Utilities

• Message number: 367

• Message text: The selected totals records are destroyed

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 KR367 - The selected totals records are destroyed ?

  The SAP error message KR367, which states "The selected totals records are destroyed," typically occurs in the context of the Controlling (CO) module, particularly when dealing with cost center accounting or internal orders. This error indicates that the system has detected that the totals records for a particular cost object have been corrupted or are missing.
  Causes:
  
  Data Corruption: The totals records may have been corrupted due to system errors, database issues, or improper data handling.
  Inconsistent Data: If there are inconsistencies in the data, such as missing entries or discrepancies in the database, it can lead to this error.
  Incorrect Configuration: Misconfiguration in the controlling area or related settings can also lead to issues with totals records.
  System Upgrades or Changes: Changes in the system, such as upgrades or migrations, may inadvertently affect the integrity of totals records.
  
  Solutions:
  
  Check Data Consistency: Use transaction codes like CKR1 (for checking cost object data) or CKR2 (for checking