How To Fix KR358 - Cost center master not archived because transaction data exists

SAP Error Message - Details

• Message type: E = Error

• Message class: KR - Archiving Reports and Utilities

• Message number: 358

• Message text: Cost center master not archived because transaction data exists

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 KR358 - Cost center master not archived because transaction data exists ?

  The SAP error message KR358 indicates that a cost center master record cannot be archived because there is existing transaction data associated with it. This is a common issue when trying to archive cost center data in SAP, as the system prevents the archiving of master data that is still linked to active transaction data.
  Cause:
  The primary cause of this error is that the cost center you are trying to archive has associated transaction data in various modules, such as:
  
  Controlling (CO)
  Financial Accounting (FI)
  Project System (PS)
  Other modules that may use cost centers
  
  The presence of this transaction data means that the cost center is still in use, and SAP requires that all related transaction data be cleared or archived before the master data can be archived.
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Identify Transaction Data: Use transaction codes like KSB1 (Cost Centers: Actual Line Items) or KOB1 (Order: Actual Line Items) to identify the transactions that are linked to the cost center. This will help you understand what data is preventing the archiving.
  
  
  Clear or Archive Transaction Data: Depending on your business requirements, you may need to:
  
  Clear the transaction data if it is no longer needed.
  Archive the transaction data if your organization has an archiving strategy in place. This typically involves using the archiving object for controlling (CO) to archive the relevant transaction data.
  
  
  
  Check for Open Items: Ensure there are no open items or pending transactions related to the cost center. This includes checking for any outstanding invoices, purchase orders, or other financial documents.
  
  
  Use the Archive Administration: If you have archived the necessary transaction data, you can use transaction code SARA to manage the archiving process for the cost center master data.
  
  
  Consult with Your SAP Basis Team: If you are unsure about how to proceed with archiving or if you need assistance in identifying the transaction data, consult with your SAP Basis or CO team for guidance.
  
  
  Related Information:
  
  Archiving Objects: Familiarize yourself with the relevant archiving objects in SAP, particularly those related to Controlling (CO) and Financial Accounting (FI).
  SAP Notes: Check for any SAP Notes related to archiving cost centers or the specific error message KR358 for additional guidance or updates.
  Documentation: Review SAP documentation on archiving processes to ensure compliance with your organization's data management policies.
  
  By following these steps, you should be able to resolve the KR358 error and successfully archive the cost center master data.