How To Fix MQ673 - &2 records were read, &3 changed, &4 added in table &1

SAP Error Message - Details

• Message type: E = Error

• Message class: MQ - Messages for Euro Changeover Package

• Message number: 673

• Message text: &2 records were read, &3 changed, &4 added 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 MQ673 - &2 records were read, &3 changed, &4 added in table &1 ?

  The SAP error message MQ673 typically indicates that there has been a change in the data of a specific table during a database operation, such as an update or a batch processing job. The message format usually includes placeholders for the number of records read, changed, and added, as well as the name of the table involved.
  Cause:
  
  Data Consistency Issues: The error may arise when there are inconsistencies in the data being processed, such as when the data in the table has been modified by another process while your transaction is running.
  Concurrency Issues: If multiple users or processes are trying to update the same records simultaneously, it can lead to conflicts.
  Batch Processing: If you are running a batch job that processes records in a table, the message indicates how many records were read, changed, or added during that job.
  
  Solution:
  
  Check for Concurrent Updates: Ensure that no other processes are modifying the same records at the same time. You may need to implement locking mechanisms or review the transaction isolation levels.
  Review Batch Jobs: If this error occurs during a batch job, review the job logs to identify any issues with the data being processed. Ensure that the data is in a consistent state before running the job.
  Data Validation: Validate the data being processed to ensure it meets the required criteria and does not violate any constraints.
  Error Handling: Implement error handling in your code to manage situations where records are changed or added unexpectedly. This may involve retrying the operation or logging the error for further investigation.
  Consult SAP Notes: Check the SAP Support Portal for any relevant notes or patches that may address this specific error message.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SE11 (Data Dictionary) to check the structure of the table mentioned in the error message.
  Logs and Traces: Use transaction codes like SLG1 (Application Log) to view logs related to the error for more context.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.