How To Fix FMCJ086 - Program was already started for company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCJ - IS-PS: Messages for Cash Desk Subsidiary Ledger

• Message number: 086

• Message text: Program was already started for company code &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 FMCJ086 - Program was already started for company code &1 ?

  The SAP error message FMCJ086, which states "Program was already started for company code &1," typically occurs in the context of financial transactions or processes that are being executed for a specific company code. This error indicates that a particular program or transaction is already running for the specified company code, which prevents a new instance of the program from being started.
  Cause:
  
  
  Concurrent Execution: The most common cause of this error is that the same program or transaction is already being executed for the specified company code. This can happen if:
  
  A user has initiated the program and has not completed it.
  Another user is running the same program simultaneously.
  A background job is already processing the same program for that company code.
  
  
  
  Lock Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If a program is already running, it locks the company code, and any subsequent attempts to start the same program will trigger this error.
  
  
  Solution:
  
  
  Check Running Instances: 
  
  Use transaction codes like SM37 (Job Monitoring) to check if there are any background jobs running for the same program and company code.
  If you find a job that is still running, you may need to wait for it to complete.
  
  
  
  Identify User Sessions:
  
  Use transaction SM04 (User Overview) or AL08 (Global User Overview) to see if another user is currently executing the program.
  If necessary, communicate with the user to determine if they can complete or cancel their session.
  
  
  
  Terminate Long-Running Processes:
  
  If a process is stuck or taking too long, you may need to terminate it. This should be done with caution and typically requires appropriate authorizations.
  
  
  
  Review Program Logic: 
  
  If this error occurs frequently, it may be worth reviewing the program logic to ensure that it handles concurrent executions appropriately.
  
  
  
  Consult with Basis Team: 
  
  If you are unable to resolve the issue, consult with your SAP Basis team. They can provide insights into system performance and any potential issues with locks or sessions.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM37, SM04, and AL08 for monitoring jobs and user sessions.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific program or transaction you are working with.
  Documentation: Review the documentation for the specific program to understand its expected behavior and any limitations regarding concurrent executions.
  
  By following these steps, you should be able to diagnose and resolve the FMCJ086 error effectively.