How To Fix 0D805 - Correspondence creation: No items found for account: &1 partner: &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 0D - FS-CD General Messages

• Message number: 805

• Message text: Correspondence creation: No items found for account: &1 partner: &2

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 0D805 - Correspondence creation: No items found for account: &1 partner: &2 ?

  The SAP error message 0D805 ("Correspondence creation: No items found for account: &1 partner: &2") typically occurs when you are trying to generate correspondence (such as invoices, statements, or reminders) for a specific account and partner, but the system cannot find any relevant items to process.
  Causes:
  
  No Open Items: The account specified does not have any open items or transactions that require correspondence.
  Incorrect Account/Partner: The account number or partner number provided may be incorrect or does not exist in the system.
  Selection Criteria: The selection criteria used for generating correspondence may be too restrictive, leading to no items being selected.
  Data Issues: There may be data inconsistencies or missing entries in the database that prevent the system from finding the relevant items.
  Document Status: The documents related to the account may be in a status that does not allow for correspondence generation (e.g., already cleared or archived).
  
  Solutions:
  
  Check Open Items: Verify that there are open items for the specified account and partner. You can do this by checking the account balance or transaction history.
  Validate Account/Partner Information: Ensure that the account number and partner number are correct. You can cross-check these details in the master data.
  Review Selection Criteria: If you are using specific selection criteria for generating correspondence, consider broadening these criteria to include more items.
  Data Consistency Check: Run data consistency checks to identify any issues with the account or partner data. This may involve checking for missing entries or inconsistencies in the database.
  Document Status Review: Check the status of the documents related to the account. If they are cleared or archived, you may need to adjust your correspondence generation approach.
  Consult Documentation: Refer to SAP documentation or help resources for additional guidance on the specific transaction or report you are using to generate correspondence.
  
  Related Information:
  
  Transaction Codes: You may want to look into transaction codes related to correspondence generation, such as F.27 (Correspondence) or F.28 (Correspondence for Open Items).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to access the account and generate correspondence.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.