How To Fix BS_SOA_COMMON064 - Postprocessing order is locked by automatic resubmission

SAP Error Message - Details

• Message type: E = Error

• Message class: BS_SOA_COMMON - Common/generic messages for business suite service enabling

• Message number: 064

• Message text: Postprocessing order is locked by automatic resubmission

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 BS_SOA_COMMON064 - Postprocessing order is locked by automatic resubmission ?

  The SAP error message BS_SOA_COMMON064 indicates that a postprocessing order is locked due to an automatic resubmission process. This typically occurs in scenarios where a background job or a process is trying to reprocess a message or order that is already being handled by another process. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause
  
  Concurrent Processing: The error usually arises when multiple processes attempt to access the same postprocessing order simultaneously. This can happen in systems with high transaction volumes or when multiple instances of a job are running.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If one process is already working on a postprocessing order, other processes will be blocked until the first one completes.
  Automatic Resubmission: The system may have attempted to automatically resubmit a message or order for processing, but it found that the order is still locked by the previous attempt.
  
  Solution
  
  Wait and Retry: Often, the simplest solution is to wait for the current process to complete. Once the lock is released, the automatic resubmission can proceed.
  Check for Long-Running Processes: Use transaction codes like SM50 (Process Overview) or SM66 (Global Process Overview) to identify any long-running processes that may be holding the lock. If necessary, you can terminate these processes, but do this with caution as it may lead to data inconsistencies.
  Review Job Scheduling: If this error occurs frequently, review the scheduling of background jobs to ensure they are not overlapping in a way that causes contention for the same resources.
  Increase Lock Timeout: In some cases, you may consider increasing the lock timeout settings in the system configuration, but this should be done with caution and typically requires consultation with your SAP Basis team.
  Check for Configuration Issues: Ensure that the configuration for the relevant processes (like SOA or message processing) is set up correctly and that there are no issues with the underlying data or settings.
  
  Related Information
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view and manage locks) and SM21 (to check system logs for errors).
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches or updates that could resolve underlying issues.
  Documentation: Review SAP documentation related to the specific module or process you are working with, as there may be additional troubleshooting steps or best practices outlined.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support or your internal SAP Basis team for further investigation.