How To Fix >6370 - Issue date of run &1 must be after last correspondence from &2

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 370

• Message text: Issue date of run &1 must be after last correspondence from &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 >6370 - Issue date of run &1 must be after last correspondence from &2 ?

  The SAP error message "6370 Issue date of run &1 must be after last correspondence from &2" typically occurs in the context of correspondence processing, such as when generating letters, invoices, or other documents in SAP. This error indicates that the issue date you are trying to set for a correspondence run is earlier than the last correspondence date for the specified entity (e.g., a customer or vendor).
  Cause:
  The error arises due to the following reasons:
  
  Date Validation: The system is enforcing a rule that the issue date of the new correspondence must be later than the last correspondence date recorded for the entity.
  Data Entry Error: The user may have mistakenly entered an incorrect issue date that precedes the last correspondence date.
  System Configuration: There may be specific configurations or business rules set up in the SAP system that enforce this validation.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Last Correspondence Date:
  
  Review the last correspondence date for the entity (e.g., customer or vendor) in question. This can usually be found in the correspondence history or logs.
  You can use transaction codes like S_O5_12000001 or S_O5_12000002 to view correspondence history.
  
  
  
  Adjust Issue Date:
  
  Ensure that the issue date you are trying to set for the new correspondence is later than the last correspondence date. If necessary, update the issue date accordingly.
  
  
  
  Review Configuration:
  
  If you believe the validation is incorrect or too strict, consult with your SAP administrator or functional consultant to review the configuration settings related to correspondence processing.
  
  
  
  Testing:
  
  After making the necessary adjustments, attempt to generate the correspondence again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for correspondence processing, such as FBL1N (Vendor Line Item Display) or FBL5N (Customer Line Item Display).
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message. You can search the SAP Support Portal for specific notes that may address this error.
  Documentation: Review SAP documentation or user manuals related to correspondence processing for additional context and best practices.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team for further assistance.