How To Fix >6318 - Correspondence type &1 for &2: No items found in time interval

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 318

• Message text: Correspondence type &1 for &2: No items found in time interval

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 >6318 - Correspondence type &1 for &2: No items found in time interval ?

  The SAP error message 6318 indicates that there are no items found for a specified correspondence type within a given time interval. This error typically arises in the context of financial or logistics processes where correspondence (such as invoices, statements, or notifications) is generated based on certain criteria.
  Cause:
  
  No Correspondence Created: There may not be any correspondence items created for the specified type and time interval.
  Incorrect Time Interval: The time interval specified in the selection criteria may not match any existing records.
  Incorrect Correspondence Type: The correspondence type specified may not be valid or may not have been set up correctly in the system.
  Data Selection Issues: There may be issues with the data selection criteria, such as filters that exclude all relevant records.
  
  Solution:
  
  Check Correspondence Creation: Verify if any correspondence has been created for the specified type. You can do this by checking the relevant transaction or report that generates correspondence.
  Review Time Interval: Ensure that the time interval you are using in your selection criteria is correct and that it encompasses the dates for which you expect to find correspondence.
  Validate Correspondence Type: Confirm that the correspondence type you are using is valid and correctly configured in the system. You can check this in the configuration settings for correspondence types.
  Adjust Selection Criteria: Modify the selection criteria to broaden the search parameters. This may involve changing the date range or removing certain filters that may be too restrictive.
  Check Authorization: Ensure that you have the necessary authorizations to view the correspondence items. Lack of proper authorization can sometimes lead to the appearance of no items being found.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using specific transaction codes related to correspondence (e.g., F.27 for correspondence processing).
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  Documentation: Review the SAP documentation related to the specific module you are working with (e.g., FI, SD) for more details on correspondence processing.
  Support: If the issue persists after checking the above points, 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.