How To Fix >6808 - Incoming correspondence already exists for period &2 in year &3

>6808 - Overview

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 808

• Message text: Incoming correspondence already exists for period &2 in year &3

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 >6808 - Incoming correspondence already exists for period &2 in year &3 ?

  The SAP error message "6808 Incoming correspondence already exists for period &2 in year &3" typically occurs in the context of financial accounting or accounts receivable when you are trying to post an incoming payment or correspondence for a period where a record already exists. This error is designed to prevent duplicate entries for the same period and year.
  
  Cause:
  
  Duplicate Entry: The most common cause is that there is already an incoming correspondence (like a payment or invoice) recorded for the specified period and year.
  Incorrect Posting Period: You may be trying to post to a period that is already closed or has restrictions.
  
  Configuration Issues: There may be configuration settings in the system that prevent posting to certain periods.
  
  
  Solution:
  
  
  Check Existing Records: 
  
  Go to the relevant transaction (e.g., F-28 for incoming payments) and check if there is already an entry for the specified period and year.
  Use transaction codes like FBL1N (Vendor Line Item