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

FSH_ARUN_MSG021 - Overview

• Message type: E = Error

• Message class: FSH_ARUN_MSG - ARUN Message Class

• Message number: 021

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

  The SAP error message FSH_ARUN_MSG021 indicates a lock error related to a purchase order (PO). Specifically, it means that the purchase order identified by &1 is currently locked by another user identified by &2. This typically occurs when multiple users are trying to access or modify the same purchase order simultaneously.
  
  Cause:
  
  Concurrent Access: Another user is currently editing or processing the purchase order, which prevents other users from making changes until the lock is released.
  Long-running Transactions: A user may have left a transaction open for an extended period, causing the lock to persist.
  System Configuration: Certain configurations in the SAP system may lead to more frequent locking scenarios, especially in high-transaction environments.
  
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to finish their transaction and then try again. Locks are typically released once the user exits the transaction or saves their changes.
  Identify the Lock: Use transaction code SM12