How To Fix 60068 - Entries to be deleted are currently being processed

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 068

• Message text: Entries to be deleted are currently being processed

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 60068 - Entries to be deleted are currently being processed ?

  The SAP error message "60068 Entries to be deleted are currently being processed" typically occurs when there is an attempt to delete entries from a database table that are currently being accessed or processed by another transaction or user. This can happen in various scenarios, such as during data archiving, deletion of records, or when trying to clear certain logs.
  Cause:
  
  Concurrent Processing: Another user or process is currently accessing or modifying the entries you are trying to delete.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If a record is locked by another transaction, you will receive this error when trying to delete it.
  Long-running Transactions: If a transaction is taking a long time to complete, it may hold locks on the entries you want to delete.
  
  Solution:
  
  Check for Locks: Use transaction code SM12 to check for any locks on the entries you are trying to delete. If you find locks that are no longer needed, you can release them (be cautious with this step, as it may affect other users).
  Wait and Retry: If the entries are being processed by another transaction, you may need to wait until that transaction completes before attempting to delete the entries again.
  Identify Long-running Transactions: Use transaction code SM66 to monitor active processes and identify any long-running transactions that may be holding locks.
  Review Batch Jobs: If the deletion is part of a batch job, check the status of that job to ensure it is not currently running or stuck.
  Consult Logs: Check the application logs (transaction SLG1) for any additional information related to the error.
  System Restart: In some cases, if the issue persists and is affecting multiple users, a system restart may be necessary to clear any lingering locks.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage locks.
  SM66: Global work process overview.
  SLG1: Application log display.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for best practices on data deletion and archiving to avoid such issues in the future.
  
  If the problem persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.