How To Fix MQ672 - &2 records were read and &3 records changed in table &1

SAP Error Message - Details

• Message type: E = Error

• Message class: MQ - Messages for Euro Changeover Package

• Message number: 672

• Message text: &2 records were read and &3 records changed in table &1

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 MQ672 - &2 records were read and &3 records changed in table &1 ?

  The SAP error message MQ672 indicates that there is a discrepancy between the number of records read and the number of records changed in a specific database table during a data processing operation. This message typically arises in the context of data updates or batch processing where the system is trying to modify records in a database table.
  Cause:
  
  Data Inconsistency: The records being processed may not match the expected criteria for updates, leading to a situation where some records are read but not changed.
  Locking Issues: If records are locked by another process, they may be read but not updated.
  Business Logic Errors: The logic applied during the update process may not be correctly identifying which records should be changed.
  Database Constraints: Constraints such as foreign key or unique constraints may prevent certain records from being updated.
  Batch Processing Issues: If the operation is part of a batch job, it may be that some records were processed in a previous run, leading to fewer changes than expected.
  
  Solution:
  
  Check the Selection Criteria: Review the selection criteria used to read records. Ensure that it accurately reflects the records you intend to update.
  Review Business Logic: Examine the logic that determines which records are updated. Ensure it aligns with the intended business rules.
  Check for Locks: Use transaction codes like SM12 to check for locks on the records in question. If records are locked, you may need to wait for the locks to be released or resolve the locking issue.
  Examine Database Constraints: Check for any database constraints that might be preventing updates. This can include foreign key constraints or unique constraints.
  Log Analysis: Look at the logs generated during the operation for any additional error messages or warnings that could provide more context.
  Test in a Development Environment: If possible, replicate the issue in a development or test environment to better understand the cause without affecting production data.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE38 (ABAP Editor), and SM37 (Job Monitoring) to analyze the issue further.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Documentation: Review the documentation for the specific program or transaction that generated the error to understand its expected behavior and any prerequisites.
  
  By following these steps, you should be able to identify the root cause of the MQ672 error and implement a solution to resolve it.