How To Fix FARR_CONS_CHECK116 - Contract Check is not possible, Company code &1 locked by another run.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONS_CHECK - Message Class for Contract Consistency Check

• Message number: 116

• Message text: Contract Check is not possible, Company code &1 locked by another run.

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 FARR_CONS_CHECK116 - Contract Check is not possible, Company code &1 locked by another run. ?

  The SAP error message FARR_CONS_CHECK116 indicates that a contract check cannot be performed because the specified company code is currently locked by another process. This typically occurs in the context of contract management or financial transactions where multiple processes may attempt to access or modify the same data simultaneously.
  Cause:
  
  Concurrent Processing: Another user or background job is currently processing data for the same company code, which locks the records to prevent data inconsistencies.
  Long-Running Transactions: A transaction that takes a long time to complete may hold the lock longer than expected.
  System Configuration: Certain configurations or settings in the SAP system may lead to locks being held longer than necessary.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other process to complete. Once the lock is released, you can attempt the contract check again.
  Identify the Lock: Use transaction code SM12 to check for locks in the system. You can see which user or process is holding the lock on the company code.
  
  If you have the necessary authorizations, you can delete the lock entry if it is safe to do so (e.g., if the process holding the lock is no longer running).
  
  
  Check Background Jobs: Use transaction code SM37 to check for any background jobs that might be running and holding the lock. If a job is taking too long, you may need to investigate or terminate it if appropriate.
  Review System Performance: If locks are a frequent issue, consider reviewing system performance and optimizing long-running transactions or processes.
  Consult with Basis Team: If the issue persists, it may be beneficial to consult with your SAP Basis team to analyze the locking behavior and system performance.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM37: Monitor background jobs.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide guidance on handling locks.
  Documentation: Review SAP documentation related to contract management and locking mechanisms to understand how to manage locks effectively.
  
  By following these steps, you should be able to resolve the error and perform the necessary contract checks in SAP.