How To Fix KR349 - No totals records to be archived found

SAP Error Message - Details

• Message type: E = Error

• Message class: KR - Archiving Reports and Utilities

• Message number: 349

• Message text: No totals records to be archived found

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 KR349 - No totals records to be archived found ?

  The SAP error message KR349 ("No totals records to be archived found") typically occurs when you attempt to archive cost accounting (CO) data, but the system cannot find any totals records that meet the criteria for archiving. This can happen for several reasons, and understanding the cause and potential solutions can help you resolve the issue.
  Causes:
  
  No Eligible Records: There may simply be no totals records in the database that meet the archiving criteria specified in the archiving object.
  Archiving Object Configuration: The archiving object may not be properly configured, or the selection criteria may be too restrictive.
  Data Already Archived: The records you are trying to archive may have already been archived in a previous run.
  Incorrect Selection Criteria: The selection criteria used in the archiving process may not match any existing records.
  Authorization Issues: Lack of proper authorizations may prevent the system from accessing the records.
  
  Solutions:
  
  
  Check Archiving Object Configuration: Ensure that the archiving object for CO is correctly configured. You can do this in transaction code SARA, where you can review the settings for the archiving object.
  
  
  Review Selection Criteria: Verify the selection criteria you are using for archiving. Make sure they are not too restrictive and that they align with the records you expect to archive.
  
  
  Check for Existing Archives: Use transaction code SARA to check if the records you are trying to archive have already been archived. You can look at the archive file and see if the records exist there.
  
  
  Run a Test Archive: If possible, run a test archive with broader selection criteria to see if any records are found. This can help you identify if the issue is with the criteria or if there are genuinely no records to archive.
  
  
  Check Authorizations: Ensure that you have the necessary authorizations to access and archive the records. You may need to consult with your SAP security team if you suspect authorization issues.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  Review Logs: Look at the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about why no records were found.
  
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Archive Administration
  SLG1: Application Log
  
  
  Archiving Process: Understand the overall archiving process in SAP, including the steps involved in data selection, writing to archive files, and deleting data from the database.
  Documentation: Refer to SAP documentation for detailed information on archiving in the CO module and the specific archiving objects involved.
  
  By following these steps, you should be able to identify the cause of the KR349 error and take appropriate action to resolve it.