How To Fix >6122 - Correspondence &1 of correspondence type &2 not found in database

>6122 - Overview

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 122

• Message text: Correspondence &1 of correspondence type &2 not found in database

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 >6122 - Correspondence &1 of correspondence type &2 not found in database ?

  The SAP error message 6122 indicates that a specific correspondence (document or message) of a certain type could not be found in the database. This error typically arises in the context of SAP modules that deal with correspondence management, such as SAP Financials, SAP Customer Relationship Management (CRM), or SAP Sales and Distribution (SD).
  
  Cause:
  
  Missing Correspondence: The correspondence document you are trying to access does not exist in the database. This could be due to it not being created, deleted, or archived.
  Incorrect Parameters: The parameters you are using to search for the correspondence (like the correspondence type or ID) may be incorrect or not matching any existing records.
  Authorization Issues: The user may not have the necessary authorizations to view the correspondence.
  Database Issues: There could be issues with the database connection or integrity that prevent the retrieval of the correspondence.
  
  
  Solution:
  
  Verify Correspondence Type and ID: Check the parameters you are using to ensure