How To Fix >U036 - G/L adjustment program is currently being used/blocked by user &1

>U036 - Overview

• Message type: E = Error

• Message class: >U -

• Message number: 036

• Message text: G/L adjustment program is currently being used/blocked by user &1

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 >U036 - G/L adjustment program is currently being used/blocked by user &1 ?

  The SAP error message U036 indicates that the General Ledger (G/L) adjustment program is currently being used or blocked by another user. This typically occurs when multiple users attempt to access the same transaction or program simultaneously, leading to a lock situation.
  
  Cause:
  
  Concurrent Access: Another user is currently executing the G/L adjustment program, which locks the program for other users.
  Session Lock: The program may have been left open in another session or by another user, causing it to be locked.
  Long-running Transactions: If the program is taking a long time to execute, it may block other users from accessing it until it completes.
  
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to complete their transaction. After a short period, try accessing the program again.
  Check User Locks: If you have the necessary authorizations, you can check which user is currently using the program:
  Use transaction code SM12 to view and