How To Fix FDT_CORE350 - Enqueue failed on &1, object locked by &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CORE - Formula & Derivation Tool: Core

• Message number: 350

• Message text: Enqueue failed on &1, object locked by &2

What causes this issue?

BRFplus prevents concurrent changes of objects in different sessions by
using the SAP ENQUEUE technology for transactional programming. The
object &v1& is already locked by user &v2& and therefore cannot be
locked by you.
Active enqueues can be shown in transaction SM12.

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?

Wait until the object is not locked anymore and perform the action
again.

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 FDT_CORE350 - Enqueue failed on &1, object locked by &2 ?

  The SAP error message FDT_CORE350 indicates that an enqueue operation has failed because the object you are trying to access is currently locked by another user or process. This typically occurs in scenarios where multiple users or processes are trying to access or modify the same data simultaneously.
  Cause:
  The error message can be caused by several factors, including:
  
  Concurrent Access: Another user or process is currently using the object you are trying to access, leading to a lock.
  Long-Running Transactions: A transaction that takes a long time to complete may hold a lock on the object longer than expected.
  Deadlocks: In some cases, a deadlock situation may arise where two or more processes are waiting for each other to release locks.
  System Configuration: Configuration settings related to locking mechanisms may also contribute to this issue.
  
  Solution:
  To resolve the FDT_CORE350 error, you can take the following steps:
  
  
  Identify the Lock:
  
  Use transaction code SM12 to view the list of locks in the system. You can filter by the object name or user to find out who is holding the lock.
  
  
  
  Release the Lock:
  
  If you identify a lock that is no longer needed (e.g., a user has left the session open), you can manually delete the lock entry from SM12. However, be cautious when doing this, as it may disrupt the work of the user holding the lock.
  
  
  
  Communicate with Users:
  
  If the lock is held by another user, communicate with them to determine if they can release the lock or if they are still actively working on the object.
  
  
  
  Review Long-Running Transactions:
  
  Check for any long-running transactions that may be holding locks for an extended period. If possible, optimize these transactions to complete more quickly.
  
  
  
  Check for Deadlocks:
  
  If you suspect a deadlock, you may need to analyze the situation further. SAP provides tools and logs to help diagnose deadlocks.
  
  
  
  System Configuration:
  
  Review the system configuration related to locking mechanisms. Ensure that it is set up correctly to minimize locking issues.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM21: Check system logs for any related errors or warnings.
  ST22: Analyze dumps that may provide additional context for the error.
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for relevant notes.
  
  
  Documentation: Review SAP documentation on enqueue mechanisms and locking behavior to better understand how locks are managed in your system.
  
  
  By following these steps, you should be able to diagnose and resolve the FDT_CORE350 error effectively.