How To Fix /PF1/MSG_CONV680 - Field 21 of MTn92 does neither match field 20 nor 21 of original message

/PF1/MSG_CONV680 - Overview

• Message type: E = Error

• Message class: /PF1/MSG_CONV -

• Message number: 680

• Message text: Field 21 of MTn92 does neither match field 20 nor 21 of original message

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 /PF1/MSG_CONV680 - Field 21 of MTn92 does neither match field 20 nor 21 of original message ?

  The SAP error message /PF1/MSG_CONV680 indicates a problem with the conversion of a financial message, specifically an MTn92 message, which is part of the SWIFT messaging standards used in financial transactions. This error suggests that there is a mismatch between the fields in the original message and the fields in the converted message.
  
  Cause:
  The error typically arises due to one of the following reasons:
  
  
  Field Mismatch: The content of field 21 in the MTn92 message does not match the expected values in field 20 or field 21 of the original message. This could be due to incorrect data entry or a failure in the mapping process during the conversion.
  
  
  Data Integrity Issues: There may be issues with the data integrity, such as missing or incorrectly formatted data in the original message.
  
  
  
  Configuration Issues: The configuration settings for the message conversion might not be set up correctly, leading to discrepancies in how fields are interpreted.
  
  
  Version