How To Fix >6559 - No correspondence request &2 found for correspondence type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 559

• Message text: No correspondence request &2 found for correspondence type &1

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 >6559 - No correspondence request &2 found for correspondence type &1 ?

  The SAP error message "6559 No correspondence request &2 found for correspondence type &1" typically occurs in the context of the SAP system when dealing with correspondence processing, such as invoices, statements, or other forms of communication generated by the system.
  Cause:
  This error message indicates that the system is unable to find a correspondence request that matches the specified correspondence type and request number. The reasons for this could include:
  
  Missing Correspondence Request: The correspondence request that you are trying to process does not exist in the system.
  Incorrect Parameters: The parameters (correspondence type and request number) provided may be incorrect or do not match any existing records.
  Data Deletion: The correspondence request may have been deleted or archived, making it unavailable for processing.
  Authorization Issues: The user may not have the necessary authorizations to view or process the correspondence request.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  Verify Parameters: Check the correspondence type and request number you are using. Ensure that they are correct and correspond to an existing request.
  Check Correspondence Requests: Use transaction codes like SOST (for sending correspondence) or SORE (for correspondence requests) to check if the request exists in the system.
  Review Deletion/Archiving: If the request was deleted or archived, you may need to restore it or create a new correspondence request.
  Check Authorizations: Ensure that you have the necessary authorizations to access the correspondence requests. You may need to contact your system administrator for assistance.
  Consult Logs: Check the application logs or system logs for any additional error messages or information that might provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SOST, SORE, or any specific transaction related to the correspondence type you are working with.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal. There may be specific patches or updates that address known issues.
  Documentation: Review the SAP documentation for the specific module you are working with (e.g., FI, SD) to understand how correspondence processing is handled.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.