How To Fix CX062 - Sales document &1 is currently being processed by &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CX - Nachrichten für Konfigurationsprozess

• Message number: 062

• Message text: Sales document &1 is currently being processed by &2

What causes this issue?

You want to process an order BOM, but the sales order for the order BOM
is being processed at the same time. This means that you cannot change
the order BOM right now.

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?

Try again later. You can process the BOM again once the changes to the
sales order have been saved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CX062 - Sales document &1 is currently being processed by &2 ?

  The SAP error message CX062 indicates that a sales document (like a sales order) is currently being processed by another user or session. This typically occurs in scenarios where multiple users are trying to access or modify the same sales document simultaneously, leading to a lock situation.
  Cause:
  
  Concurrent Access: Another user is currently editing or processing the sales document.
  Session Lock: The document is locked due to a previous transaction that has not been completed or has not been released properly.
  Long-running Transactions: If a transaction takes too long to complete, it can lead to locks on the document.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to finish processing the document and then try again.
  Check Lock Entries: Use transaction code SM12 to check for lock entries. You can see which user is currently holding the lock on the document. If necessary, you can ask that user to release the lock.
  Transaction Monitoring: If you have the necessary authorizations, you can monitor the transaction using SM21 (System Log) or SM37 (Job Monitoring) to identify any long-running jobs that might be holding the lock.
  Contact Administrator: If the lock persists and you cannot identify the user or the reason for the lock, contact your SAP system administrator for assistance. They may need to release the lock manually if it is stuck.
  Review Custom Code: If this error occurs frequently, review any custom code or enhancements that might be causing locks to persist longer than necessary.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM21: View system logs for errors and warnings.
  SM37: Monitor background jobs.
  
  
  User Communication: If you are in a collaborative environment, communicate with your team members to ensure that they are aware of the document being processed.
  Documentation: Refer to SAP Help documentation for more details on handling locks and error messages.
  
  By following these steps, you should be able to resolve the CX062 error and continue processing your sales document.