How To Fix RSM2706 - Too many error records - update terminated

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM2 - Monitor assistant help texts

• Message number: 706

• Message text: Too many error records - update terminated

What causes this issue?

More than &V1& records have been flagged as incorrect. There is
probably a system error.

System Response

For performance reasons, the system terminates the update and
additional checks.

How to fix this error?

The errors that have occurred so far can be displayed in the PSA.
Analyze and correct the errors, and restart the update.
If you do not want the update process to terminate as soon as the
system registers &V1& errors, you can change the number of errors that
you want the system to tolerate. You do this in the scheduler on the
<LS>Update Parameters</> tabstrip under <PF>Error Handling</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM2706 - Too many error records - update terminated ?

  The SAP error message RSM2706 ("Too many error records - update terminated") typically occurs during the processing of a batch input session or during the execution of a background job that involves data updates. This error indicates that the system has encountered too many errors while processing the records, leading to the termination of the update process.
  Causes:
  
  Data Quality Issues: The records being processed may contain invalid or inconsistent data, leading to errors during the update.
  Configuration Errors: There may be issues with the configuration of the system or the specific transaction being executed.
  System Limitations: The system has a predefined limit for the number of error records it can handle before terminating the update process.
  Authorization Issues: The user executing the batch job may not have the necessary authorizations to perform the updates.
  Technical Errors: There could be underlying technical issues, such as database locks or connectivity problems.
  
  Solutions:
  
  Review Error Logs: Check the error logs for the batch input session or job to identify the specific records that caused the errors. You can use transaction codes like SM37 (for job monitoring) or SM21 (for system logs) to gather more information.
  Data Validation: Validate the data being processed to ensure it meets the required format and constraints. Correct any inconsistencies or invalid entries.
  Adjust Configuration: If the issue is related to configuration, review the settings for the transaction or process being executed and make necessary adjustments.
  Increase Error Limit: If appropriate, consider increasing the limit for error records in the system configuration. However, this should be done with caution and typically as a last resort.
  Re-run the Job: After addressing the identified issues, re-run the batch job or input session to see if the problem persists.
  Check Authorizations: Ensure that the user executing the job has the necessary authorizations to perform the updates.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM21 (System Log), and SLG1 (Application Log) to troubleshoot and analyze the issue.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Documentation: Review SAP documentation related to batch input processing and error handling for best practices and troubleshooting steps.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical support team for further assistance.