How To Fix FGL_SFIN_NGLM022 - Company code &2 is locked by user &1: Document transfer in process

SAP Error Message - Details

• Message type: E = Error

• Message class: FGL_SFIN_NGLM - SAP AC on HANA : New G/L Migration

• Message number: 022

• Message text: Company code &2 is locked by user &1: Document transfer in process

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 FGL_SFIN_NGLM022 - Company code &2 is locked by user &1: Document transfer in process ?

  The SAP error message FGL_SFIN_NGLM022 indicates that a company code is locked by a specific user because a document transfer process is currently in progress. This typically occurs in the context of financial document processing, such as during the transfer of documents between different ledgers or during the posting of financial documents.
  Cause:
  
  Document Transfer in Progress: The primary cause of this error is that a document transfer process is ongoing for the specified company code. This could be due to a user actively processing financial documents or a batch job that is running.
  User Lock: The user identified in the error message has initiated a process that locks the company code to prevent other users from making changes or posting documents simultaneously, which could lead to data inconsistencies.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait until the document transfer process is completed. Once the process is finished, the lock will be released automatically.
  Identify the User: If the process seems to be taking too long, you can identify the user who has locked the company code. This can be done using transaction SM12 (Display and Delete Locks). Look for the user ID mentioned in the error message and check if they are still active.
  Contact the User: If you find the user, you can contact them to understand if they are still working on the document transfer or if they can complete it.
  Release the Lock: If the user is no longer active or if the process has stalled, you may need to release the lock manually. This can be done in transaction SM12 by selecting the lock entry and deleting it. However, this should be done with caution, as it may lead to data inconsistencies if the document transfer is still in progress.
  Check for Background Jobs: Sometimes, background jobs may be running that could be causing the lock. You can check for any scheduled jobs in transaction SM37 (Job Monitoring) to see if there are any jobs related to document transfers that are still running.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM37: To monitor background jobs.
  FB03: To display financial documents.
  
  
  Documentation: Refer to SAP Help documentation for more details on document transfers and locking mechanisms in financial accounting.
  System Logs: Check system logs for any additional error messages or warnings that may provide more context about the issue.
  
  Best Practices:
  
  Ensure that users are aware of the locking mechanism and the importance of completing their processes in a timely manner.
  Regularly monitor and manage background jobs to prevent long-running processes that could lead to locks.
  Implement proper training for users on how to handle document transfers and the implications of locking company codes. 
  
  By following these steps, you should be able to resolve the error and understand the underlying issues related to document transfers in SAP.