Summary
Most of the processing in SAP happens in term of background jobs. Some of these jobs are very critical and need to run within specified duration. In production support environment, many a times need arises to repair failure of these jobs. Sometimes our User ID lacks the authorization to run some of these jobs and hence results in missing SLAs or dependencies. The blog further will explain step by step solution how to trigger such jobs with background User ID which has most of the authorizations required.
Step by Step Solution
Identifying Background Job
Using TCode SM37, with filter set to respective User ID and job type as scheduled/released; identify the correct job that needs to be scheduled with Background User ID.
Goto Change Options
Select the appropriate job and then from menu options, select Job -> Change or use CTRL+F11. This will open up the job definition screen; here hit the ‘step’ button as shown.
Step List Overview
The Step button will lead to Step List Overview screen. Here, simply click on the job and hit the change button (CTRL+SHIFT+F7).
Changing User
In the next screen simply change the User from IDADMIN to ALEREMOTE and save the job.
Authentication
This approach is a safe approach as though we can change the user ID of any job but the user ID with which we created the job remains unchanged. This can be helpful in tracking any misuse of this functionality. Also it can help in audit purposes.
