How To Fix FTR_GENERAL360 - Transaction changed, but no correspondence-relevant fields were affected

FTR_GENERAL360 - Overview

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 360

• Message text: Transaction changed, but no correspondence-relevant fields were affected

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_GENERAL360 - Transaction changed, but no correspondence-relevant fields were affected ?

  The SAP error message FTR_GENERAL360 indicates that a transaction has been modified, but none of the fields that are relevant for correspondence (such as letters, notifications, or other forms of communication) have been changed. This can occur in various contexts, particularly in financial transactions or asset management.
  
  Cause:
  
  No Correspondence-Relevant Changes: The transaction was altered, but the changes did not impact any fields that are designated as relevant for generating correspondence.
  
  Configuration Issues: The system may not be configured correctly to recognize which fields should trigger correspondence.
  User Actions: A user may have attempted to save changes that do not affect correspondence-relevant fields, leading to this error.
  
  
  Solution:
  
  Review Changes: Check the changes made to the transaction. Ensure that at least one correspondence-relevant field is modified if you intend to generate correspondence.
  Check Configuration: Verify the configuration settings in the SAP system to ensure that the correspondence-relevant fields are correctly defined. This may involve checking the settings