How To Fix 25211 - Document is currently being edited in another recipient list

25211 - Overview

• Message type: E = Error

• Message class: 25 - DDS: document distribution (DMS)

• Message number: 211

• Message text: Document is currently being edited in another recipient list

What causes this issue?

You want to create a standard recipient list.
All the recipient lists in which documents in the standard recipient
list are used, are loched. This means that only one standrd recipient
list exists for a document.
A recipient list that is to be locked is currently being used by
another
user.

System Response

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

How to fix this error?

You can delete the document from the standard recipient list.
Please make sure you delete the entries in the document number and
document type fields.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 25211 - Document is currently being edited in another recipient list ?

  The SAP error message 25211, which states "Document is currently being edited in another recipient list," typically occurs when a document (such as a purchase order, sales order, or any other transactional document) is being accessed or edited by another user or session in the system. This can happen in scenarios where multiple users are trying to edit the same document simultaneously, leading to a conflict.
  
  Cause:
  
  Concurrent Access: Another user is currently editing the same document or has it open in their session.
  Session Issues: The document may be locked due to a previous session that did not close properly.
  System Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies, and if a document is locked by another user, you will receive this error.
  
  
  Solution:
  
  Check for Other Users: Verify if another user is currently editing the document. You can do this by checking the user sessions or asking your colleagues.
  Wait and Retry: