How To Fix MMPUR_ARCHIVE060 - Document &1 has been written to the archive (but not deleted)

SAP Error Message - Details

• Message type: E = Error

• Message class: MMPUR_ARCHIVE - Messages for Archiving in Purchasing

• Message number: 060

• Message text: Document &1 has been written to the archive (but not 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 MMPUR_ARCHIVE060 - Document &1 has been written to the archive (but not deleted) ?

  The SAP error message MMPUR_ARCHIVE060 indicates that a document has been successfully written to the archive but has not been deleted from the database. This message is typically related to the archiving process in SAP, particularly in the Materials Management (MM) module.
  Cause:
  
  Archiving Process: The archiving process is designed to move data from the database to an archive storage to improve performance and manage data volume. The message indicates that the document has been archived but not deleted from the database.
  Configuration Settings: There may be specific settings in the archiving configuration that prevent the deletion of the document after archiving.
  Authorization Issues: The user executing the archiving process may not have the necessary authorizations to delete the document after it has been archived.
  Errors During Deletion: There may have been an error during the deletion phase of the archiving process, which prevented the document from being removed from the database.
  
  Solution:
  
  Check Archiving Configuration: Review the archiving configuration settings in transaction SARA to ensure that the deletion of documents after archiving is enabled.
  Review Logs: Check the archiving logs for any errors or warnings that occurred during the archiving process. This can provide insights into why the deletion did not occur.
  Authorization Check: Ensure that the user has the necessary authorizations to perform both archiving and deletion. This may involve checking roles and permissions in transaction PFCG.
  Manual Deletion: If the document is still present in the database and you have confirmed that it should have been deleted, you may need to manually delete the document using the appropriate transaction (e.g., ME23N for purchase orders).
  Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error message or provide guidance on the archiving process for your version of SAP.
  
  Related Information:
  
  Archiving Process: Understand the overall archiving process in SAP, including the steps involved in writing to the archive and deleting from the database.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration), SARI (Archive Information System), and others related to archiving.
  SAP Documentation: Refer to SAP Help documentation for detailed information on archiving in the Materials Management module and best practices for managing archived data.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.