How To Fix KG874 - Log was deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: KG - CO-PA Planning

• Message number: 874

• Message text: Log was deleted

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 KG874 - Log was deleted ?

  The SAP error message KG874 ("Log was deleted") typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with the actual activity allocation or when trying to analyze logs related to cost center accounting or internal orders. This error indicates that the log file that the system is trying to access has been deleted or is no longer available.
  Cause:
  
  Log Deletion: The log file may have been deleted manually or automatically by the system due to retention policies or cleanup jobs.
  System Configuration: The system may be configured to delete logs after a certain period, which can lead to this error if you try to access a log that has already been purged.
  Data Archiving: If data archiving processes are in place, logs may be archived and subsequently deleted from the active database.
  User Permissions: In some cases, the user may not have the necessary permissions to access the log, leading to confusion about the log's availability.
  
  Solution:
  
  Check Log Availability: Verify if the log file is indeed deleted. You can check the relevant transaction codes (like KOB1 for order-related logs) to see if the logs are available.
  Review System Settings: Check the system settings for log retention and deletion policies. You may need to adjust these settings if logs are being deleted too quickly.
  Re-run the Process: If the log was deleted due to a previous process, try re-running the allocation or activity process to generate a new log.
  Consult with Basis Team: If you suspect that the logs are being deleted due to system jobs or archiving processes, consult with your SAP Basis team to understand the configuration and make necessary adjustments.
  Check User Permissions: Ensure that the user has the appropriate permissions to access the logs. If not, request the necessary access rights.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KOB1 (for displaying order logs), KSB1 (for cost center reports), and KSU5 (for actual activity allocation).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional context or solutions.
  Documentation: Review SAP documentation related to Controlling and logs to understand how logs are managed and what best practices are recommended for log retention.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.