How To Fix FTR_GENERAL361 - Correspondence object was added to BADI_TCOR_CREATE

FTR_GENERAL361 - Overview

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 361

• Message text: Correspondence object was added to BADI_TCOR_CREATE

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_GENERAL361 - Correspondence object was added to BADI_TCOR_CREATE ?

  The SAP error message FTR_GENERAL361 indicates that there is an issue related to the correspondence object being added to the BADI (Business Add-In) BADI_TCOR_CREATE. This error typically arises in the context of financial transactions, particularly in the area of treasury and risk management.
  
  Cause:
  The error can occur due to several reasons, including:
  
  
  Configuration Issues: The BADI implementation may not be correctly configured, or the necessary settings for the correspondence object may be missing.
  Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing or incorrect entries in the relevant tables.
  Custom Code Issues: If there is custom code implemented in the BADI, it may not be handling the correspondence object correctly.
  Authorization Issues: The user may not have the necessary authorizations to perform the action related to the correspondence object.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check BADI Implementation:
  
  Go to transaction SE18 to check the implementation of BADI_TCOR_CREATE.
  Ensure that