How To Fix /PF1/MSG_CONV660 - Amount in field '32A' is not equal to sum of all fields '32B and 71G'

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_CONV -

• Message number: 660

• Message text: Amount in field '32A' is not equal to sum of all fields '32B and 71G'

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_CONV660 - Amount in field '32A' is not equal to sum of all fields '32B and 71G' ?

  The SAP error message /PF1/MSG_CONV660 indicates a discrepancy in financial data, specifically that the amount in field '32A' does not match the sum of the amounts in fields '32B' and '71G'. This error typically arises during the processing of financial documents, such as invoices or payment transactions, where the totals must reconcile.
  Cause:
  
  Data Entry Error: The most common cause is a manual data entry error where the amounts in fields '32B' and '71G' do not add up to the amount in field '32A'.
  Configuration Issues: There may be issues with the configuration of the financial document types or the mapping of fields in the system.
  Data Migration Issues: If data has been migrated from another system, there may be inconsistencies in the amounts due to incorrect mapping or transformation rules.
  System Bugs: Occasionally, there may be bugs in the SAP system or specific transactions that lead to incorrect calculations.
  
  Solution:
  
  Verify Data Entry: Check the values entered in fields '32A', '32B', and '71G'. Ensure that the sum of '32B' and '71G' equals '32A'.
  Recalculate Totals: If the amounts are derived from calculations, ensure that the calculations are correct and that there are no missing or incorrect entries.
  Review Configuration: If the issue persists, review the configuration settings related to the financial document types and ensure that they are set up correctly.
  Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as these may resolve known issues.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or known issues.
  Contact Support: If you are unable to resolve the issue, consider reaching out to SAP support or your internal IT team for further assistance.
  
  Related Information:
  
  
  Field Definitions:
  
  Field '32A': Typically represents a total amount or a key financial figure.
  Field '32B': Often represents a component of the total, such as a subtotal or a specific charge.
  Field '71G': May represent additional charges, taxes, or adjustments that contribute to the total.
  
  
  
  Transaction Codes: Depending on the context, you may need to use specific transaction codes (like FB60 for invoices, FBL1N for vendor line items, etc.) to investigate the entries related to this error.
  
  
  SAP Notes: Check SAP Notes for any specific notes related to this error message, as they may provide additional context or solutions.
  
  
  By following these steps, you should be able to identify and resolve the discrepancy causing the error message.