How To Fix /SCMTMS/WBN079 - Unable to lock &1 stocks in client &2; execute the report again


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /SCMTMS/WBN -

  • Message number: 079

  • Message text: Unable to lock &1 stocks in client &2; execute the report again

  • 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 /SCMTMS/WBN079 - Unable to lock &1 stocks in client &2; execute the report again ?

    The SAP error message /SCMTMS/WBN079 Unable to lock &1 stocks in client &2; execute the report again typically occurs in the context of SAP Transportation Management (TM) when the system is unable to lock certain stock items for processing. This can happen for various reasons, and understanding the cause and potential solutions is essential for resolving the issue.

    Cause:

    1. Concurrent Access: The stock items may be locked by another user or process. SAP uses locks to prevent data inconsistencies when multiple users or processes try to access the same data simultaneously.
    2. Long-Running Transactions: If a transaction is taking too long to complete, it may hold locks on the stock items longer than expected.
    3. System Configuration: There may be configuration issues in the SAP system that affect how locks are managed.
    4. Database Issues: Sometimes, underlying database issues can lead to locking problems.

    Solution:

    1. Retry the Operation: The simplest solution is to wait for a few moments and then retry executing the report or transaction. This allows time for any existing locks to be released.
    2. Check for Active Sessions: Use transaction codes like SM12 (to view and manage locks) to check if there are any active sessions holding locks on the stock items. If you find any unnecessary locks, you can release them if you have the necessary authorizations.
    3. Review Long-Running Processes: Identify any long-running transactions that may be holding locks and address them. You can use transaction SM66 to monitor active processes in the system.
    4. System Configuration Review: Consult with your SAP Basis team to ensure that the system is configured correctly for handling locks and that there are no underlying issues.
    5. Database Health Check: If the problem persists, it may be worth checking the health of the database and ensuring that it is performing optimally.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (lock entries), SM21 (system log), and SM66 (global work process overview) to diagnose and troubleshoot locking issues.
    • SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
    • User Authorizations: Ensure that users have the necessary authorizations to perform the actions they are attempting, as insufficient permissions can sometimes lead to unexpected behavior.

    If the issue continues after trying the above solutions, it may be necessary to involve your SAP support team or consult SAP documentation 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