How To Fix >6120 - Reading the archive data for the correspondence history is not supported

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 120

• Message text: Reading the archive data for the correspondence history is not supported

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 >6120 - Reading the archive data for the correspondence history is not supported ?

  The SAP error message "6120 Reading the archive data for the correspondence history is not supported" typically indicates that there is an issue with accessing archived data related to correspondence history in the SAP system. This error can occur in various contexts, such as when trying to view or process correspondence documents that have been archived.
  Cause:
  
  Archiving Configuration: The system may not be configured to read archived data for correspondence history. This could be due to settings in the archiving object or the specific configuration of the correspondence functionality.
  Data Not Available: The specific correspondence data you are trying to access may not be archived or may have been deleted.
  Authorization Issues: The user may not have the necessary authorizations to access archived data.
  System Limitations: The version of SAP you are using may not support reading archived correspondence history.
  
  Solution:
  
  
  Check Archiving Configuration:
  
  Verify the archiving settings for the relevant object. Ensure that the archiving object is correctly configured to allow reading of archived data.
  Use transaction code SARA to check the archiving status and settings.
  
  
  
  Accessing Archived Data:
  
  If you need to access archived data, ensure that the appropriate archive files are available and that the system is set up to read them.
  You may need to restore the archived data if it is not accessible.
  
  
  
  User Authorizations:
  
  Check the user roles and authorizations to ensure that the user has the necessary permissions to access archived correspondence data.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific module you are working with to see if there are any known issues or additional configuration steps required.
  
  
  
  SAP Support:
  
  If the issue persists, consider reaching out to SAP support for assistance. They may provide specific notes or patches that address the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SARA (Archive Administration) and SARI (Archive Information System) for managing and viewing archived data.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  System Version: Ensure that you are aware of the version of SAP you are using, as features and support for archiving can vary between versions.
  
  By following these steps, you should be able to diagnose and potentially resolve the error related to reading archived correspondence history in SAP.