How To Fix /SCWM/EXT_SYS_LCK008 - &1 &2 is locked with a persistent lock by an other process


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /SCWM/EXT_SYS_LCK -

  • Message number: 008

  • Message text: &1 &2 is locked with a persistent lock by an other process

  • Show details Hide details


  • 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/EXT_SYS_LCK008 - &1 &2 is locked with a persistent lock by an other process ?

    The SAP error message /SCWM/EXT_SYS_LCK008 indicates that a specific object (like a warehouse task, handling unit, or another entity) is locked by another process in the Extended Warehouse Management (EWM) module. This typically occurs when multiple processes attempt to access or modify the same object simultaneously, leading to a conflict.

    Cause:

    1. Concurrent Access: Another transaction or process is currently using the object, which prevents your process from accessing it.
    2. Long-Running Transactions: If a transaction takes too long to complete, it can hold a lock on the object longer than expected.
    3. System Configuration: Certain configurations or custom developments may lead to unexpected locking behavior.
    4. Deadlocks: In some cases, a deadlock situation may arise where two processes are waiting for each other to release locks.

    Solution:

    1. Identify the Locking Process:

      • Use transaction code SM12 to view the list of locks in the system. You can filter by user or object type to find the specific lock.
      • Check the details of the locking process to understand what it is doing.
    2. Wait and Retry:

      • If the locking process is legitimate and expected to complete soon, you may need to wait for it to finish and then retry your operation.
    3. Terminate the Locking Process:

      • If the locking process is stuck or taking too long, you may need to terminate it. This can be done using transaction SM66 (global overview of processes) or SM50 (local overview of processes) to find and stop the process.
    4. Review Custom Code:

      • If the issue is recurring, review any custom code or enhancements that may be causing excessive locking.
    5. System Configuration:

      • Check the configuration settings related to locking behavior in EWM. Adjusting these settings may help reduce locking conflicts.
    6. Consult SAP Notes:

      • Look for relevant SAP Notes that may address this specific error or provide guidance on best practices for managing locks in EWM.

    Related Information:

    • Lock Management: Understanding how SAP handles locks is crucial. Locks are used to ensure data integrity and prevent conflicts during concurrent processing.
    • Performance Monitoring: Regularly monitor system performance and transaction durations to identify potential bottlenecks that could lead to locking issues.
    • User Training: Ensure that users are trained on how to properly manage transactions to minimize locking conflicts.

    If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant