How To Fix /SMB/MD_AS_CUST073 - Job for Background could not be started: Processing in foreground

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/MD_AS_CUST -

• Message number: 073

• Message text: Job for Background could not be started: Processing in foreground

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 /SMB/MD_AS_CUST073 - Job for Background could not be started: Processing in foreground ?

  The SAP error message /SMB/MD_AS_CUST073 Job for Background could not be started: Processing in foreground typically indicates that a background job could not be initiated because the system is attempting to process it in the foreground instead. This can happen for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  System Configuration: The system may not be configured correctly to allow background processing for the specific job.
  Job Scheduling Issues: There may be issues with the job scheduling configuration or the job itself.
  User Authorizations: The user attempting to start the job may not have the necessary authorizations to execute background jobs.
  System Load: The system may be under heavy load, causing it to default to foreground processing.
  Job Parameters: Incorrect parameters or settings in the job definition can lead to this error.
  
  Solutions:
  
  
  Check Job Configuration:
  
  Review the job configuration in transaction SM37 (Job Monitoring) to ensure that it is set up correctly for background processing.
  Ensure that the job is defined to run in the background and not in the foreground.
  
  
  
  Review User Authorizations:
  
  Verify that the user has the necessary authorizations to execute background jobs. Check roles and profiles assigned to the user.
  
  
  
  System Performance:
  
  Monitor system performance and load. If the system is heavily loaded, consider scheduling jobs during off-peak hours.
  
  
  
  Job Parameters:
  
  Check the parameters and settings of the job. Ensure that all required parameters are correctly defined.
  
  
  
  Check for Errors in Job Logs:
  
  Look for any error messages or logs related to the job in transaction SM37. This can provide more context on why the job could not be started.
  
  
  
  Restart the Job:
  
  If the job was previously running and failed, try restarting it after addressing any identified issues.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide patches.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SM36: Define Background Job
  SM21: System Log
  ST22: Dump Analysis
  
  
  
  SAP Documentation: Refer to the official SAP documentation for more detailed information on background job processing and troubleshooting.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.