How To Fix /CFG/APPL_BCW_SRV706 - Job has been submitted and will start soon

SAP Error Message - Details

• Message type: E = Error

• Message class: /CFG/APPL_BCW_SRV -

• Message number: 706

• Message text: Job has been submitted and will start soon

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 /CFG/APPL_BCW_SRV706 - Job has been submitted and will start soon ?

  The SAP error message /CFG/APPL_BCW_SRV706 Job has been submitted and will start soon typically indicates that a background job has been successfully submitted in the SAP system, but it has not yet started executing. This message is not necessarily an error; rather, it is an informational message indicating the status of the job.
  Cause:
  
  Job Scheduling: The job has been scheduled but is waiting for system resources to become available. This can happen if there are other jobs currently running or if the system is busy.
  Job Priority: The job may have a lower priority compared to other jobs in the queue, causing it to wait until higher-priority jobs are completed.
  System Load: High system load or resource constraints can delay the execution of background jobs.
  Job Configuration: There may be specific configurations or dependencies that need to be met before the job can start.
  
  Solution:
  
  Monitor Job Status: Use transaction code SM37 to monitor the status of the job. You can check if the job is still in the queue or if it has started executing.
  Check System Load: Assess the current system load and resource availability. If the system is under heavy load, you may need to wait for resources to free up.
  Adjust Job Priority: If necessary, you can adjust the priority of the job to ensure it starts sooner. This can be done in the job scheduling settings.
  Review Job Configuration: Ensure that the job is configured correctly and that there are no dependencies or prerequisites that are preventing it from starting.
  Check for Errors: If the job does not start after a reasonable amount of time, check for any error messages or logs that may indicate why the job is not executing.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Monitor background jobs.
  SM36: Schedule background jobs.
  SM21: Check system logs for any related errors.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to job scheduling and execution.
  System Performance: Regularly monitor system performance and resource utilization to prevent delays in job execution.
  
  If the job remains in the "submitted" state for an extended period without starting, it may be necessary to investigate further or consult with your SAP Basis team for assistance.