How To Fix WG368 - Purchase order &1 is blocked by user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: WG - Messages for store order and investment buy

• Message number: 368

• Message text: Purchase order &1 is blocked by user &2

What causes this issue?

The purchase order is currently being edited by another used and cannot
therefore be selected for manual load building.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Run load building without the locked purchase order. Start selection
again or make selections at a later date.
Choose "Refresh PO" to update the selection during processing. In doing
so, purchase orders that have been released are re-included in
processing.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WG368 - Purchase order &1 is blocked by user &2 ?

  Certainly! Here's a detailed explanation for the SAP error message WG368: Purchase order &1 is blocked by user &2:
  
  Error Message:
  WG368: Purchase order &1 is blocked by user &2
  
  &1 = Purchase Order number
  &2 = User ID who blocked the PO
  
  
  Cause:
  This message appears when you try to process or change a Purchase Order (PO) that is currently locked or blocked by another user in the system. SAP uses a lock mechanism to prevent simultaneous changes to the same document by multiple users, which could lead to data inconsistencies.
  
  The PO is currently locked because another user (&2) is editing or has locked the PO.
  The lock can be due to an ongoing transaction, incomplete processing, or a session that did not release the lock properly.
  
  
  Solution:
  
  
  Check who has locked the PO:
  
  Identify the user (&2) who has the lock.
  You can contact this user to ask them to finish their work and release the lock.
  
  
  
  Wait and retry:
  
  Sometimes locks are temporary and will be released once the user finishes their transaction or logs off.
  Wait a few minutes and try again.
  
  
  
  Use transaction SM12 to check and delete locks (if appropriate):
  
  Go to transaction SM12 (Lock Entries).
  Enter the PO number or relevant object to find the lock entry.
  Verify the user and reason for the lock.
  If the user is no longer working or the lock is stale (e.g., user session ended unexpectedly), you can delete the lock entry.
  Caution: Deleting locks can cause data inconsistencies if the user is still working on the PO. Only delete locks if you are sure the lock is stale.
  
  
  
  Check for background jobs or batch processes:
  
  Sometimes batch jobs or workflows might lock the PO.
  Check if any background jobs are running that might be processing the PO.
  
  
  
  System or network issues:
  
  If locks are not released due to system crashes or network issues, a system administrator might need to intervene.
  
  
  
  
  Related Information:
  
  Lock Mechanism in SAP: SAP uses enqueue locks to ensure data consistency during updates.
  Transaction SM12: Used to monitor and manage lock entries.
  Transaction ME22N / ME23N: Purchase order change/display transactions where this error might appear.
  User Communication: Coordination with the user holding the lock is often the quickest resolution.
  System Admin Role: Sometimes requires Basis team intervention to clear locks or investigate system issues.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  PO is locked by another user currently editing it.
  
  
  Solution
  Contact user to release lock, wait, or delete lock via SM12 if safe.
  
  
  Related Transactions
  SM12 (locks), ME22N/ME23N (PO processing)
  
  
  Notes
  Avoid deleting locks unless sure the lock is stale to prevent data issues.
  
  
  
  
  If you need help with the exact steps in SM12 or further troubleshooting, feel free to ask!