How To Fix RSJOB035 - No user provided

RSJOB035 - Overview

• Message type: E = Error

• Message class: RSJOB - Job scheduler related messages

• Message number: 035

• Message text: No user provided

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.

RSJOB035 - Details

• The SAP error message RSJOB035 ("No user provided") typically occurs when a background job is scheduled without specifying a user who is authorized to execute it. This can happen in various scenarios, such as when creating or scheduling a background job in transaction codes like SM36 or SM37.
  
  Cause:
  
  Missing User Specification: The job was created without specifying a user in the "User" field.
  Default User Not Set: The system may not have a default user set for background jobs.
  Authorization Issues: The user who is trying to schedule the job may not have the necessary authorizations to execute jobs in the background.
  
  
  Solution:
  
  
  Specify a User: When scheduling the job, ensure that you specify a valid user in the "User" field. This user should have the necessary authorizations to execute the job.
  
  
  Check Default User Settings: If applicable, check the default user settings in the system configuration. You can set a default user for background jobs