How To Fix VL247 - Purchase order &1 is currently being processed by &2

SAP Error Message - Details

• Message type: E = Error

• Message class: VL -

• Message number: 247

• Message text: Purchase order &1 is currently being processed by &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 VL247 - Purchase order &1 is currently being processed by &2 ?

  The SAP error message VL247 indicates that a purchase order (PO) is currently being processed by another user or session. This typically occurs when multiple users attempt to access or modify the same purchase order simultaneously, leading to a lock situation in the database.
  Cause:
  
  Concurrent Access: Another user is currently processing the same purchase order, which causes a lock on the record.
  Long-running Transactions: A transaction that takes a long time to complete may hold the lock longer than expected.
  System Issues: Sometimes, system performance issues or bugs can lead to locks not being released properly.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for a few moments and then try to access the purchase order again. The lock will be released once the other user completes their transaction.
  Identify the Lock: If the issue persists, you can identify which user is holding the lock:
  
  Use transaction code SM12 to view the lock entries. You can filter by the purchase order number to see which user is currently processing it.
  
  
  Contact the User: If you identify the user holding the lock, you can contact them to see if they can complete their transaction or release the lock.
  Release the Lock: If necessary, and if you have the appropriate authorizations, you can manually delete the lock entry in SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still processing the order.
  Check for System Issues: If this error occurs frequently, it may indicate underlying system performance issues. In such cases, it may be necessary to consult with your SAP Basis team to investigate and resolve any potential problems.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM21: To check system logs for any related errors or warnings.
  ST22: To check for dumps that might indicate underlying issues.
  
  
  User Training: Ensure that users are trained on how to properly handle transactions to minimize the chances of concurrent access issues.
  System Performance: Regularly monitor system performance and optimize long-running transactions to reduce the likelihood of locks.
  
  By following these steps, you should be able to resolve the VL247 error and understand its implications in your SAP environment.