How To Fix /SCWM/MFS079 - Unable to delete some entries due to locks

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/MFS -

• Message number: 079

• Message text: Unable to delete some entries due to locks

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 /SCWM/MFS079 - Unable to delete some entries due to locks ?

  The SAP error message /SCWM/MFS079 Unable to delete some entries due to locks typically occurs in the context of the SAP Extended Warehouse Management (EWM) system, particularly when dealing with the Material Flow System (MFS). This error indicates that there are locks on certain entries that prevent their deletion. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  
  Locks on Entries: The most common cause of this error is that the entries you are trying to delete are currently locked by another process or transaction. This can happen if:
  
  Another user or process is currently accessing or modifying the same entries.
  There are open transactions that have not been completed or released.
  Background jobs or processes are running that are holding locks on the entries.
  
  
  
  Database Locks: Sometimes, database-level locks can also prevent deletion if the entries are being used in a transaction that has not yet been committed.
  
  
  Solution:
  
  
  Check for Active Sessions: Use transaction codes like SM12 (to view and manage locks) to check if there are any active locks on the entries you are trying to delete. If you find locks that are no longer needed, you can release them if you have the necessary authorizations.
  
  
  Identify the Locking Process: In SM12, you can identify which user or process is holding the lock. If it is a user session that can be safely terminated, you may choose to do so.
  
  
  Wait for Completion: If the locks are held by legitimate processes (like background jobs), you may need to wait for those processes to complete before attempting to delete the entries again.
  
  
  Check for Open Transactions: Ensure that there are no open transactions that are holding locks on the entries. You can check this in transaction SM21 (System Log) or ST22 (Dump Analysis) for any related issues.
  
  
  Review Custom Code: If you have custom developments or enhancements, review them to ensure they are not inadvertently causing locks.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: Display and manage locks.
  SM21: System log for monitoring.
  ST22: Dump analysis for error analysis.
  SE11: Data dictionary to check table definitions.
  
  
  
  SAP Documentation: Refer to the official SAP documentation for Extended Warehouse Management and Material Flow System for more detailed information on handling locks and transactions.
  
  
  Performance Monitoring: Regularly monitor system performance and transaction locks to prevent such issues from occurring frequently.
  
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.