How To Fix ARUN_MAIN099 - Lock error; purchase order &1 locked by user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ARUN_MAIN -

• Message number: 099

• Message text: Lock error; purchase order &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 ARUN_MAIN099 - Lock error; purchase order &1 locked by user &2 ?

  The SAP error message ARUN_MAIN099 indicates that a purchase order (PO) is currently locked by another user, preventing you from making changes or processing that particular PO. This is a common issue in SAP systems when multiple users are trying to access the same document simultaneously.
  Cause:
  
  Concurrent Access: Another user is currently editing or viewing the purchase order, which locks the document for other users.
  Session Timeout: A user may have left a session open, causing the lock to persist even if they are no longer actively working on it.
  System Errors: Occasionally, system errors or crashes can leave locks in place that do not get released properly.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for the other user to finish their work and release the lock may be the simplest solution.
  Identify the User: Use transaction code SM12 (Lock Entries) to check which user has locked the purchase order. You can search for the specific PO number and see the user who has it locked.
  Contact the User: If you identify the user who has the lock, you can reach out to them to see if they can release the lock or if they are done with their changes.
  Release the Lock: If necessary and if you have the appropriate permissions, you can manually delete the lock entry in transaction SM12. However, this should be done with caution and typically only if you are sure that the user is not actively working on the PO.
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check if any background processes are running that might be affecting the PO.
  System Restart: In rare cases, a system restart may be required to clear persistent locks, but this should be done by your system administrator.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM21: To check system logs for any related errors or issues.
  SE11: To view the data dictionary and understand the structure of the purchase order table.
  
  
  User Training: Ensure that users are trained on how to properly exit transactions to avoid leaving locks in place.
  System Configuration: Review system settings related to locking mechanisms to ensure they are configured optimally for your business processes.
  
  If the issue persists or if you encounter frequent locking issues, it may be beneficial to consult with your SAP Basis team or system administrator for further investigation and potential adjustments to system settings.