How To Fix /SOMO/JOBMON128 - No &1 was started by &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SOMO/JOBMON -

• Message number: 128

• Message text: No &1 was started by &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 /SOMO/JOBMON128 - No &1 was started by &2 ?

  The SAP error message /SOMO/JOBMON128 No &1 was started by &2 typically indicates that a job or process (represented by &1) was not started by the user or system identified by &2. This message is often related to job monitoring and scheduling within the SAP system, particularly in the context of background jobs.
  Cause:
  
  Job Ownership: The job may have been scheduled or started by a different user or system process, and the current user does not have the necessary permissions or ownership to view or manage it.
  Job Status: The job may not be in a state that allows it to be monitored or managed by the current user.
  Authorization Issues: The user may lack the required authorizations to view or interact with the job.
  Job Deletion or Completion: The job may have already completed or been deleted, leading to the inability to find it.
  
  Solution:
  
  Check Job Ownership: Verify who scheduled the job and ensure that you have the necessary permissions to view or manage it.
  Review Job Status: Use transaction codes like SM37 (Job Monitoring) to check the status of the job. Ensure that the job is still active or in a state that can be monitored.
  Authorization Check: Ensure that the user has the appropriate authorizations to view and manage background jobs. This may involve checking roles and profiles assigned to the user.
  Consult with Basis Team: If you are unable to resolve the issue, consult with your SAP Basis team or system administrator for further investigation. They can check system logs and job history for more details.
  Re-schedule the Job: If the job is no longer relevant or has been deleted, consider re-scheduling it if necessary.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM37: Job Monitoring
  SM36: Define Background Job
  SM21: System Log
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to job monitoring and scheduling.
  Documentation: Review SAP documentation for background job management to understand the processes and permissions involved.
  
  If the issue persists after following these steps, it may be beneficial to gather more specific details about the job in question and consult SAP support for further assistance.