How To Fix FTR_GENERAL173 - Error during parallel processing; no correspondences were fetched

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 173

• Message text: Error during parallel processing; no correspondences were fetched

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_GENERAL173 - Error during parallel processing; no correspondences were fetched ?

  The SAP error message FTR_GENERAL173 indicates that there was an issue during parallel processing, specifically that no correspondences were fetched. This error typically occurs in the context of financial transactions, particularly in the area of treasury and risk management, where parallel processing is used to improve performance.
  Cause:
  
  Data Availability: The error may occur if there are no relevant data records available for processing. This could be due to filters applied in the selection criteria that do not match any records.
  Configuration Issues: There may be configuration issues in the treasury module that prevent the system from fetching the necessary correspondences.
  Parallel Processing Limitations: The system may have limitations or restrictions on the number of parallel processes that can be executed, leading to this error if those limits are exceeded.
  System Performance: If the system is under heavy load or if there are performance issues, it may not be able to fetch the required data in parallel processing mode.
  
  Solution:
  
  Check Data Selection Criteria: Review the selection criteria used for the transaction to ensure that they are correct and that there are indeed records that match the criteria.
  Review Configuration: Check the configuration settings in the treasury module to ensure that everything is set up correctly for parallel processing.
  Monitor System Performance: Use transaction codes like ST22 (Dump Analysis) or SM21 (System Log) to check for any performance issues or errors that may be affecting the system.
  Adjust Parallel Processing Settings: If applicable, consider adjusting the settings for parallel processing in the system to allow for more processes or to troubleshoot any limitations.
  Run in Single Processing Mode: As a temporary workaround, you can try running the transaction in single processing mode to see if it completes successfully without parallel processing.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FTR_EDIT, FTR_CREATE, or FTR_DISPLAY, which are used in the treasury module.
  SAP Documentation: Review the official SAP documentation for treasury and risk management for more insights into configuration and processing.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical team for further investigation, or to reach out to SAP support for assistance.