1PAYMINEX034 - Control totals of bank nos. do not match. Calculated: &1, E record: &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 1PAYMINEX -

• Message number: 034

• Message text: Control totals of bank nos. do not match. Calculated: &1, E record: &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.

AnswerBot

• What is the cause and solution for SAP error message 1PAYMINEX034 - Control totals of bank nos. do not match. Calculated: &1, E record: &2 ?

  The SAP error message 1PAYMINEX034 indicates that there is a discrepancy between the control totals of bank numbers in a payment file. Specifically, the calculated total does not match the expected total as defined in the E record of the payment file. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Data Entry Errors: There may be mistakes in the bank details entered in the payment file, leading to incorrect totals.
  File Format Issues: The payment file may not be formatted correctly, causing misalignment of data.
  Incorrect Configuration: The configuration settings for payment processing in SAP may not be set up correctly, leading to mismatches in expected totals.
  Multiple Payment Runs: If multiple payment runs are processed without proper reconciliation, it can lead to discrepancies in totals.
  Changes in Bank Data: If bank account details have been changed or updated but not reflected in the payment file, it can cause mismatches.
  
  Solution:
  
  Verify Payment File: Check the payment file for any discrepancies in the bank numbers and amounts. Ensure that the totals match what is expected.
  Recalculate Totals: Manually recalculate the control totals to ensure they are accurate. Compare the calculated total with the E record total.
  Check Configuration: Review the configuration settings in SAP related to payment processing to ensure they are set up correctly.
  Correct Data Entry: If errors are found in the data entry, correct them and regenerate the payment file.
  Reprocess Payment: If necessary, reprocess the payment run after correcting any discrepancies.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling this error.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like FBZP (Payment Program Configuration) or F110 (Automatic Payment Transactions) to review and adjust settings.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches/updates.
  Testing: After making corrections, conduct a test run to ensure that the issue is resolved before processing live transactions.
  User Roles: Ensure that users have the appropriate roles and permissions to make changes to payment configurations and files.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the issue persists, consider reaching out to your SAP support team for further assistance.