How To Fix FARR_ACCR_DB035 - User &1 is running a revenue posting job for company code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_ACCR_DB - Revenue Accounting - Accrual Management DB Access

• Message number: 035

• Message text: User &1 is running a revenue posting job for company code &2

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_ACCR_DB035 - User &1 is running a revenue posting job for company code &2 ?

  The SAP error message FARR_ACCR_DB035 indicates that a user is currently running a revenue posting job for a specific company code. This message typically arises in the context of the SAP Revenue Accounting and Reporting (RAR) module, where concurrent processing of revenue postings can lead to conflicts.
  Cause:
  The error occurs when:
  
  A user is executing a revenue posting job (such as posting accruals) for a specific company code.
  Another user or process attempts to initiate a similar job for the same company code at the same time.
  
  This is a concurrency control mechanism to prevent data inconsistencies and ensure that revenue postings are processed in a controlled manner.
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Wait for Completion: If you are not in a hurry, simply wait for the current job to complete. You can check the status of the job in the job monitoring transaction (e.g., SM37) to see if it is still running.
  
  
  Identify the User/Job: Use transaction SM37 to identify the user and the job that is currently running. You can filter by the company code and check the job status.
  
  
  Communicate with the User: If you identify the user running the job, you may want to communicate with them to understand the expected completion time or to coordinate the execution of your job.
  
  
  Job Scheduling: If you frequently encounter this issue, consider scheduling jobs during off-peak hours or implementing a job scheduling strategy to avoid conflicts.
  
  
  Check for Locks: If the job seems to be stuck or taking too long, you may need to investigate if there are any locks or issues causing the delay. You can use transaction SM12 to check for locks related to the company code.
  
  
  System Configuration: If this is a recurring issue, you may want to review the system configuration and job scheduling settings to optimize the processing of revenue postings.
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SM37: Job Monitoring
  SM12: Display and Delete Locks
  SE38: Execute Program (to run specific jobs)
  
  
  
  Documentation: Refer to SAP Help documentation for Revenue Accounting and Reporting for more details on job processing and best practices.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide patches related to this error message.
  
  
  By following these steps, you should be able to resolve the FARR_ACCR_DB035 error and manage revenue posting jobs more effectively in your SAP environment.