How To Fix FTR_GENERAL006 - No correspondence objects exist for the selection criteria

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 006

• Message text: No correspondence objects exist for the selection criteria

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 FTR_GENERAL006 - No correspondence objects exist for the selection criteria ?

  The SAP error message FTR_GENERAL006 ("No correspondence objects exist for the selection criteria") typically occurs in the context of financial transactions, particularly when dealing with financial instruments or treasury management. This error indicates that the system could not find any correspondence objects (such as documents, transactions, or records) that match the criteria specified in your selection.
  Causes:
  
  Incorrect Selection Criteria: The criteria you have entered (such as date range, document type, or other filters) may not match any existing records in the system.
  Data Not Yet Processed: The data you are looking for may not have been processed or posted yet, leading to no available correspondence objects.
  Authorization Issues: You may not have the necessary authorizations to view certain records, which could lead to the appearance that no records exist.
  Configuration Issues: There may be configuration settings in the system that are preventing the display of correspondence objects.
  Data Deletion: Correspondence objects may have been deleted or archived, making them unavailable for the current selection criteria.
  
  Solutions:
  
  Review Selection Criteria: Double-check the selection criteria you are using. Ensure that the date range, document types, and other filters are correct and relevant.
  Check Data Availability: Verify that the data you are looking for has been entered and processed in the system. You may need to check with your finance or treasury team.
  Authorization Check: Ensure that you have the necessary permissions to access the data. If not, contact your system administrator to review your authorizations.
  Consult Configuration: If you suspect a configuration issue, consult with your SAP Basis or functional consultant to ensure that the system is set up correctly to display the required correspondence objects.
  Data Recovery: If you suspect that data has been deleted or archived, check with your data management team to see if it can be restored or if there are alternative ways to access the information.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help you navigate to the correct data or reports (e.g., FTR_EDIT, FTR_DISPLAY).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Review SAP documentation related to financial instruments and treasury management for additional context on how correspondence objects are managed.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support or your internal IT team for further assistance.