How To Fix IHC768 - Archived log cannot be read. Payment order: & / & / &

SAP Error Message - Details

• Message type: E = Error

• Message class: IHC - IHC Messages

• Message number: 768

• Message text: Archived log cannot be read. Payment order: & / & / &

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 IHC768 - Archived log cannot be read. Payment order: & / & / & ?

  The SAP error message IHC768, which states "Archived log cannot be read. Payment order: & / & / &," typically occurs in the context of the SAP Intercompany Financial Management (IHC) module. This error indicates that the system is unable to access or read the archived log for a specific payment order, which can hinder the processing of intercompany payments.
  Causes:
  
  Missing Archive Files: The archived log files may have been deleted or moved from their original location, making them inaccessible.
  Incorrect Archive Configuration: The configuration settings for archiving in the SAP system may not be set up correctly, leading to issues in accessing archived data.
  Authorization Issues: The user may not have the necessary permissions to access the archived logs.
  Database Issues: There could be underlying database issues that prevent the system from reading the archived logs.
  Corrupted Archive: The archive files themselves may be corrupted, which would prevent them from being read.
  
  Solutions:
  
  Check Archive Location: Verify that the archived log files are present in the expected directory. If they are missing, restore them from a backup if available.
  Review Archive Configuration: Ensure that the archiving configuration in the SAP system is correctly set up. This includes checking the settings in transaction SARA (Archive Administration).
  User Authorizations: Confirm that the user encountering the error has the necessary authorizations to access the archived logs. This can be checked in transaction SU53 or by consulting with your security team.
  Database Health Check: Perform a health check on the database to ensure that it is functioning correctly. Look for any errors or issues that may be affecting data access.
  Check for Corruption: If you suspect that the archive files are corrupted, you may need to run a consistency check or restore from a backup.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (for archiving), SARI (for reading archived data), and SLG1 (for application log).
  SAP Documentation: Review the official SAP documentation for the IHC module and archiving processes to understand best practices and troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found effective.
  
  If the problem persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.