How To Fix >6813 - Number of table entries for incoming correspondence is inconsistent

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 813

• Message text: Number of table entries for incoming correspondence is inconsistent

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 >6813 - Number of table entries for incoming correspondence is inconsistent ?

  The SAP error message "6813 Number of table entries for incoming correspondence is inconsistent" typically indicates a discrepancy in the data related to incoming correspondence entries in the SAP system. This error can arise due to various reasons, such as data inconsistencies, issues during data migration, or problems with the configuration of the relevant modules.
  Causes:
  
  Data Inconsistency: There may be a mismatch between the expected number of entries in the database tables related to incoming correspondence and the actual number of entries.
  Incomplete Data Migration: If data was migrated from another system or during an upgrade, some entries may not have been transferred correctly.
  Configuration Issues: Incorrect configuration settings in the relevant SAP modules can lead to inconsistencies in how data is recorded or processed.
  Database Corruption: In rare cases, database corruption can lead to inconsistencies in the data.
  
  Solutions:
  
  Check Data Consistency: Use transaction codes like SE16 or SE11 to check the relevant database tables for incoming correspondence. Look for any discrepancies in the number of entries.
  Reconcile Data: If you find inconsistencies, you may need to reconcile the data manually or through a program that can correct the discrepancies.
  Review Migration Logs: If the issue arose after a data migration, review the migration logs to identify any errors or warnings that occurred during the process.
  Configuration Review: Check the configuration settings in the relevant modules (e.g., SAP CRM, SAP FI) to ensure they are set up correctly.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  Consult SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP Support for assistance. They can provide guidance based on the specific details of your system and configuration.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to incoming correspondence, such as SOST (for sending and monitoring emails) and others relevant to your specific SAP module.
  Documentation: Review SAP documentation related to the module you are working with to understand how incoming correspondence is managed and what tables are involved.
  Testing: After making any changes or corrections, conduct thorough testing to ensure that the issue is resolved and that there are no further inconsistencies.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.