/ACCGO/LOAD_OUT035 - Match locked by another user.

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/LOAD_OUT -

• Message number: 035

• Message text: Match locked by another user.

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.

AnswerBot

• What is the cause and solution for SAP error message /ACCGO/LOAD_OUT035 - Match locked by another user. ?

  The SAP error message /ACCGO/LOAD_OUT035 Match locked by another user typically occurs in the context of the SAP General Ledger or during the reconciliation process in the SAP system. This error indicates that a specific document or match is currently locked by another user, preventing you from making changes or processing it.
  Cause:
  
  Concurrent Access: Another user is currently accessing or processing the same document or match, which leads to a lock being placed on it.
  Long-running Transactions: If a user is taking a long time to complete their transaction, it can lead to locks that prevent others from accessing the same data.
  System Configuration: Certain configurations in the SAP system may lead to more aggressive locking mechanisms.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to complete their transaction. After some time, you can try to access the document again.
  Identify the Lock: If you have the necessary authorizations, you can check which user has locked the document. You can use transaction codes like SM12 (to view and manage locks) to identify the user and the locked object.
  Contact the User: If you identify the user who has the lock, you can reach out to them to see if they can complete their transaction or release the lock.
  Release the Lock: If the user is no longer active (e.g., they have logged out or their session has crashed), you may need to manually release the lock using transaction SM12. However, this should be done with caution and typically requires appropriate authorizations.
  Check for Background Jobs: Sometimes, background jobs may hold locks. Check if there are any running jobs that might be causing the lock.
  System Configuration Review: If this issue occurs frequently, it may be worth reviewing the system configuration and locking mechanisms to see if adjustments can be made to reduce locking conflicts.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (lock entries), SM21 (system log), and ST22 (dump analysis) for troubleshooting.
  User Training: Ensure that users are trained on how to properly complete transactions to minimize the time locks are held.
  Performance Monitoring: Regularly monitor system performance and user activity to identify patterns that may lead to locking issues.
  
  If the problem persists or if you are unsure about how to proceed, it may be beneficial to consult with your SAP Basis team or technical support for further assistance.