SM13 Update termination

Update was terminated

A user saves a document but receives an update termination; the asynchronous update request appears in SM13 with an error.

Likely root causes

  1. The update task raised an application error or ABAP exception after the dialog step completed.
  2. A database or system problem caused the update request to fail.
  3. Custom code in an update function module failed for production data.

What to inspect

  1. SM13 — open the failed update request and record the function/module details.
  2. ST22 for a short dump at the same user and timestamp.
  3. SM21 for system/database messages around the failure.
  4. Application logs or document data referenced by the failed update.

Resolution path

  1. Identify and correct the application, custom-code, data, or database cause before repeating the update.
  2. Determine whether the business document was partially created before retrying.
  3. Reprocess only using the supported application/update recovery path.
  4. Verify the document and downstream updates after recovery to avoid duplicate business postings.

ERPClimb is an independent platform and is not affiliated with SAP SE.