How To Fix BORGR573 - Purchase order item &2 in purchase order &1 is locked

BORGR573 - Overview

• Message type: E = Error

• Message class: BORGR - Messages Multi-Level Goods Receipt

• Message number: 573

• Message text: Purchase order item &2 in purchase order &1 is 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 BORGR573 - Purchase order item &2 in purchase order &1 is locked ?

  The SAP error message BORGR573 indicates that a specific purchase order item is locked, which prevents any modifications or actions from being performed on that item. This locking mechanism is typically in place to ensure data integrity and prevent concurrent updates that could lead to inconsistencies.
  
  Cause:
  
  Concurrent Access: The purchase order item may be locked because another user or process is currently editing or processing it.
  Background Jobs: A background job might be running that is accessing the same purchase order item.
  Transaction in Progress: A transaction that involves the purchase order item may not have been completed, leaving it in a locked state.
  System Errors: Occasionally, system errors or crashes can leave records in a locked state.
  
  
  Solution:
  
  Wait and Retry: If the lock is due to another user, waiting for a short period and then retrying the action may resolve the issue.
  Check Lock Entries: Use transaction code SM12 to check for lock entries. You