How To Fix UJJ_EXCEPTION111 - Failed to get next number of range member ( &1 - &2 ). Object locked

SAP Error Message - Details

• Message type: E = Error

• Message class: UJJ_EXCEPTION - BPC: Message Class for UJJ Exception

• Message number: 111

• Message text: Failed to get next number of range member ( &1 - &2 ). Object locked

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 UJJ_EXCEPTION111 - Failed to get next number of range member ( &1 - &2 ). Object locked ?

  The SAP error message UJJ_EXCEPTION111 indicates that there is an issue with retrieving the next number in a range member due to the object being locked. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BPC (Business Planning and Consolidation) when trying to access or modify a planning object or data that is currently locked by another user or process.
  Cause:
  
  
  Object Locking: The most common cause of this error is that the object you are trying to access is locked by another user or process. This can happen if:
  
  Another user is currently editing the same planning object.
  A background job is running that is accessing the same data.
  There is a transaction that has not been completed, leaving the object in a locked state.
  
  
  
  Concurrency Issues: If multiple users or processes are trying to access the same object simultaneously, it can lead to locking issues.
  
  
  System Configuration: Sometimes, the configuration of the system or the way the planning functions are set up can lead to locking issues.
  
  
  Solution:
  
  
  Check Locks: Use transaction code SM12 to check for locks on the object. You can see which user or process is holding the lock and take appropriate action, such as waiting for the lock to be released or contacting the user who has the lock.
  
  
  Wait and Retry: If the lock is temporary (e.g., due to another user editing the object), you may simply need to wait for the other user to finish and then try again.
  
  
  Release Locks: If you have the necessary authorizations, you can manually release the lock from transaction SM12. However, be cautious with this approach, as it may disrupt other users.
  
  
  Check Background Jobs: If a background job is causing the lock, you may need to wait for it to complete or check if it can be canceled.
  
  
  Review Configuration: If this issue occurs frequently, review the configuration of your planning functions and locking mechanisms to ensure they are set up correctly.
  
  
  Consult Documentation: Refer to SAP documentation or support notes related to this error for any specific recommendations or patches that may address the issue.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To check the status of background jobs.
  SE11: To check the data dictionary for the object in question.
  
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may provide additional insights or solutions for this specific error.
  
  
  User Communication: If you are in a collaborative environment, communicate with your team members to ensure that everyone is aware of the locking situation and can coordinate their activities accordingly.
  
  
  By following these steps, you should be able to diagnose and resolve the issue related to the UJJ_EXCEPTION111 error message in SAP.