How To Fix FZ962 - You have exceeded the maximum number of locks

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 962

• Message text: You have exceeded the maximum number of locks

What causes this issue?

When assigning the bills of exchange to a house bank, a lock was set for
each bill of exchange. However, you selected more bills of exchange than
is possible to set locks.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check the size of the lock table (SAP Notes 552289 and 97760).
If it is not possible to increase the lock table, the lock logic can be
influenced by the settings you can make for the message as follows:
Message type E:
You can assign the maximum number of bills of exchange as there are
locks. If more bills of exchange are presented than possible locks, you
have to split the presentation of the bills.
Message type S:
All selected bills of exchange are assigned, but only the maximum number
of locks created. For each additional bill of exchange, the lock is
deleted again following a successful check.
<ZH><ZK>You need to make sure organizationally that no other user is
presenting bills of exchange from the same company code at the same tim
e. Otherwise there is a possibility that bills of exchange can be
presented twice.</></>
Message switched off (default):
For each bill of exchange assigned a lock is set.
INCLUDE CUSTOMIZED_MESSAGE_INFO OBJECT DOKU ID TX

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FZ962 - You have exceeded the maximum number of locks ?

  The SAP error message FZ962, "You have exceeded the maximum number of locks," typically occurs when a user or a process tries to acquire more locks than the system allows. This can happen in various scenarios, such as when a user is working with multiple transactions or when a program is trying to lock too many objects simultaneously.
  Cause:
  
  Exceeding Lock Limit: Each user session in SAP has a limit on the number of locks it can hold. This limit is defined in the system configuration. When a user or a program tries to exceed this limit, the error is triggered.
  Long-running Transactions: If a transaction takes a long time to complete and holds onto locks, it can prevent new locks from being acquired.
  Inefficient Lock Management: Poorly designed programs or transactions that do not release locks promptly can lead to this issue.
  High Concurrent Usage: In environments with many users or processes trying to access the same data, the lock limit can be reached quickly.
  
  Solution:
  
  Release Unused Locks: Check for any unnecessary locks held by the user or process. You can use transaction code SM12 to view and delete locks that are no longer needed.
  Optimize Transactions: Review the transactions or programs that are causing the issue. Ensure they are designed to acquire and release locks efficiently.
  Increase Lock Limit: If necessary, you can increase the maximum number of locks allowed per user. This can be done by adjusting the parameter enque/number_of_locks in the SAP profile parameters. However, this should be done with caution and typically requires consultation with your SAP Basis team.
  Monitor Lock Usage: Regularly monitor lock usage in your system to identify patterns or specific transactions that frequently cause lock contention.
  User Training: Educate users on best practices for using transactions that involve locking, such as completing transactions promptly and avoiding unnecessary concurrent sessions.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM21: To check system logs for any related issues.
  ST22: To check for dumps that might indicate underlying problems.
  
  
  SAP Notes: Check SAP Notes for any specific recommendations or patches related to lock management.
  Performance Tuning: Consider performance tuning of the database and application to reduce lock contention.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.