How To Fix /PRA/ACCOUNTING661 - You selected companies which are already locked or job is running

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/ACCOUNTING -

• Message number: 661

• Message text: You selected companies which are already locked or job is running

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 /PRA/ACCOUNTING661 - You selected companies which are already locked or job is running ?

  The SAP error message /PRA/ACCOUNTING661 indicates that you are trying to perform an operation on companies that are either locked or currently being processed by another job. This typically occurs in the context of financial or accounting operations where data integrity is crucial, and concurrent access to the same data is restricted.
  Causes:
  
  
  Company Lock: The company or companies you are trying to access may be locked for processing. This can happen if:
  
  A financial period is closed.
  A batch job is currently running that is processing data for those companies.
  A user has manually locked the company for maintenance or reporting purposes.
  
  
  
  Running Jobs: There may be background jobs or processes that are currently executing and have not yet completed. These jobs could be related to month-end closing, year-end closing, or other financial processes.
  
  
  Solutions:
  
  
  Check Locks:
  
  Use transaction code SM12 to check for any locks on the companies you are trying to access. You can see if there are any active locks and who has locked them.
  If you find locks that are no longer needed, you may need to contact the user who has the lock or, if appropriate, you can delete the lock entries (be cautious with this approach).
  
  
  
  Monitor Background Jobs:
  
  Use transaction code SM37 to check for any background jobs that are currently running. Look for jobs related to the companies in question.
  If you find a job that is taking too long or is stuck, you may need to investigate further or consult with your SAP Basis team to resolve the issue.
  
  
  
  Wait for Completion: If the companies are locked due to a running job, you may need to wait until the job completes before attempting your operation again.
  
  
  Consult Documentation: Review any relevant SAP documentation or notes related to the specific transaction or process you are trying to execute. There may be specific guidelines or best practices to follow.
  
  
  Contact Support: If the issue persists and you cannot identify the cause, consider reaching out to your SAP support team or consulting SAP Notes for further assistance.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM37: Monitor background jobs.
  SE38: Execute programs (if you need to run specific reports or jobs).
  
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  
  
  User Roles: Ensure that you have the necessary authorizations to perform the actions you are attempting, as insufficient permissions can also lead to similar error messages.
  
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.