How To Fix FTR_GENERAL036 - No correspondences exist for company code &1, deal number &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 036

• Message text: No correspondences exist for company code &1, deal number &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 FTR_GENERAL036 - No correspondences exist for company code &1, deal number &2 ?

  The SAP error message FTR_GENERAL036 indicates that there are no correspondences found for a specific company code and deal number in the financial transaction management module. This error typically arises in the context of financial instruments, such as derivatives or other financial contracts, when trying to process or display information related to a specific deal.
  Cause:
  
  Missing Correspondences: The primary cause of this error is that there are no existing correspondences (e.g., postings, transactions) for the specified deal number in the specified company code.
  Incorrect Deal Number or Company Code: The deal number or company code entered may be incorrect or does not exist in the system.
  Data Not Yet Processed: The transactions related to the deal may not have been processed or posted yet.
  Configuration Issues: There may be configuration issues in the financial transaction management settings that prevent the system from recognizing the correspondences.
  
  Solution:
  
  Verify Deal Number and Company Code: Double-check the deal number and company code you are using to ensure they are correct and exist in the system.
  Check for Correspondences: Use transaction codes like FTR_EDIT or FTR_DISPLAY to check if there are any existing correspondences for the deal number in question.
  Post Missing Transactions: If the transactions related to the deal have not been posted, ensure that they are processed correctly.
  Review Configuration: Check the configuration settings in the financial transaction management module to ensure that everything is set up correctly for the company code and deal type.
  Consult Documentation: Refer to SAP documentation or help resources for specific details on how to manage financial transactions and correspondences.
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FTR_EDIT, FTR_DISPLAY, and FTR_CREATE for managing financial transactions.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to view or manage the financial transactions related to the deal.
  System Logs: Review system logs for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.