How To Fix ESDMO012 - &1 of &2 selected IDocs have alreay been deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: ESDMO - Messages for EDI Monitor

• Message number: 012

• Message text: &1 of &2 selected IDocs have alreay been deleted

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 ESDMO012 - &1 of &2 selected IDocs have alreay been deleted ?

  The SAP error message ESDMO012 indicates that the IDocs (Intermediate Documents) you are trying to process have already been deleted. This error typically occurs in scenarios where you are attempting to reprocess or delete IDocs that are no longer available in the system.
  Cause:
  
  IDoc Deletion: The IDocs you are trying to access have been deleted from the database. This could happen due to a manual deletion process or an automated job that cleans up old IDocs.
  Incorrect IDoc Selection: The selection criteria used to retrieve the IDocs may have included IDocs that were already deleted.
  Data Consistency Issues: There may be inconsistencies in the database or issues with the IDoc processing logic that lead to attempts to access non-existent IDocs.
  
  Solution:
  
  Check IDoc Status: Use transaction code WE02 or WE05 to check the status of the IDocs you are trying to process. This will help you confirm whether they have indeed been deleted.
  Review Deletion Jobs: If IDocs are being deleted automatically, review the configuration of any background jobs or processes that may be responsible for this. Ensure that the retention settings are appropriate for your business needs.
  Adjust Selection Criteria: If you are using a program or transaction to select IDocs, ensure that the selection criteria are correct and do not include deleted IDocs.
  Error Handling: Implement error handling in your IDoc processing logic to gracefully handle cases where IDocs are not found.
  Reprocess Valid IDocs: If you have valid IDocs that need to be processed, ensure that you are selecting the correct ones and that they have not been deleted.
  
  Related Information:
  
  IDoc Management: Familiarize yourself with IDoc management in SAP, including how to monitor, process, and delete IDocs.
  Transaction Codes: Common transaction codes related to IDocs include:
  
  WE02 / WE05: Display IDocs
  WE19: Test tool for IDocs
  BD87: Reprocess IDocs
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to IDoc processing and deletion.
  
  If the problem persists after following these steps, consider reaching out to your SAP Basis or technical support team for further assistance.