How To Fix >6804 - Inbound correspondence with key &1 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 804

• Message text: Inbound correspondence with key &1 not found

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 >6804 - Inbound correspondence with key &1 not found ?

  The SAP error message "6804 Inbound correspondence with key &1 not found" typically indicates that the system is unable to locate a specific inbound correspondence document based on the key provided. This error can occur in various contexts, such as when processing incoming documents or messages in SAP systems, particularly in modules related to document management or workflow.
  Cause:
  
  Missing Document: The document or correspondence with the specified key does not exist in the system. This could be due to it not being created, deleted, or archived.
  Incorrect Key: The key provided may be incorrect or malformed, leading the system to search for a non-existent document.
  Data Synchronization Issues: If the system is integrated with other systems, there may be synchronization issues that prevent the document from being available in the SAP system.
  Authorization Issues: The user may not have the necessary permissions to view the document, leading to the perception that it does not exist.
  
  Solution:
  
  Verify the Key: Check the key provided in the error message to ensure it is correct. Look for any typographical errors or formatting issues.
  Check Document Existence: Use transaction codes like SOST (for sending documents) or SBWP (for Business Workplace) to search for the document using the key. If it does not exist, you may need to create it or retrieve it from an archive.
  Review System Logs: Check system logs for any related errors or warnings that might provide additional context about why the document is not found.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the document. This may involve checking roles and permissions in the user profile.
  Consult with IT Support: If the issue persists, it may be necessary to consult with your IT support team or SAP Basis team to investigate further, especially if it involves integration with other systems.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that can help in troubleshooting, such as SOST, SBWP, or SE11 (for data dictionary).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP's support portal can provide updates or fixes.
  Documentation: Review SAP documentation related to inbound correspondence and document management for additional context and troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.