...
Define a Scheduler background job via SM36 with the following values:
Note: Do this in the client where you are executing your development, testing (Dev Unit Test or QAS) and in the live / productive client at go-live.
Step 1 | Enter the Job Name , for example
|
Step 2 | Enter the Job Class - B or C (Medium / Low priority) |
Step 3 | Press the Step button |
Step 4 | Enter the ABAP Program Name -
|
Step 5 | Enter the User - e.g.
|
...
Authorisation Object: S_BTCH_NAM (BTCUNAME - Background User Name for Authorization Check)
Values: * (All users)
Press the Save button | |
Step 6 | Press the Start conditions button Press the Date/Time button and enter the scheduled start date and time Press the Period Values button and choose Other period from the options Enter 1 in the Minute(s) field |
...
Press the Save button to complete the setup |
Info |
---|
Background jobs are usually created by the Basis team and should be set up to use an existing service user account with sufficient privileges, similar to WF-BATCH. |
...
Once the OneList Scheduler background job has been created, it will automatically schedule the OneList Adapter jobs defined in the 'OneList Job configuration' entries, discussed below (or the |
Authorization Object | Fields | Value | Description |
---|---|---|---|
|
|
| Delete other users' background jobs. |
| Is not used | ||
| Copy or repeat other users' jobs. | ||
| Display job logs belonging to other users | ||
| Release jobs (including your own) | ||
| Display definitions of other users' jobs | ||
| Change other users' background jobs. see SAP Note 1623250. | ||
|
| Reserved, set to | |
|
|
| Authorized user when scheduling |
|
|
| User is batch administrator |
Standard SAP Workflow integration with OneList (Optional)
...