How To Fix /SAPAPO/MSDP_OPTLOG120 - Optimization run &1 locked by user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/MSDP_OPTLOG -

• Message number: 120

• Message text: Optimization run &1 locked by user &2

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 /SAPAPO/MSDP_OPTLOG120 - Optimization run &1 locked by user &2 ?

  The SAP error message /SAPAPO/MSDP_OPTLOG120 Optimization run &1 locked by user &2 typically occurs in the context of SAP Advanced Planning and Optimization (APO) when a user attempts to start an optimization run that is already locked by another user. This locking mechanism is in place to prevent multiple users from modifying or running the same optimization process simultaneously, which could lead to data inconsistencies or conflicts.
  Cause:
  
  Concurrent Access: Another user is currently executing an optimization run, and the system has locked that run to prevent others from starting it until the first user completes their task.
  Session Timeout: Sometimes, if a user has an active session that has not been properly closed, it may still hold a lock on the optimization run.
  System Error: In rare cases, a system error or crash may leave a lock in place even after the user has exited.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait until the user who is currently running the optimization completes their task. You can check the status of the optimization run in the relevant transaction or monitoring tool.
  Identify the Lock: Use transaction SM12 to check for locks in the system. You can search for the specific optimization run ID and see which user is holding the lock.
  Release the Lock: If you determine that the lock is no longer needed (for example, if the user has logged out or the session has timed out), you can manually delete the lock entry in SM12. However, this should be done with caution and ideally with the consent of the user who holds the lock.
  Communicate with Users: If multiple users are working on the same optimization runs, it may be beneficial to establish a protocol for communication to avoid conflicts.
  Check for System Issues: If this error occurs frequently, it may be worth investigating if there are underlying system issues or if the locking mechanism is functioning as intended.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage locks), SM21 (to check system logs), and ST22 (to check for dumps).
  User Roles: Ensure that users have the appropriate roles and permissions to execute optimization runs without conflicts.
  Documentation: Refer to SAP documentation or support notes for any updates or patches that may address known issues related to locking mechanisms in APO.
  
  If the problem persists or if you are unsure about releasing locks, it may be advisable to consult with your SAP Basis team or SAP support for further assistance.