Step 1

Enter the Job Name , for example ONELIST_JOBS_SCHEDULER

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:

• IQX Component version <= 3.2.2 : /IQX/ONELIST_JOBS

• IQX Component version >= 3.2.3: /IQX/ONELIST_SCHEDULER with variant WITH_OPS_JOB
  

  Image Modified

Step 5

Enter the User - e.g. OL_ADMIN 

1. A service user account must be created to run these background jobs, similar to WF-BATCH. This user can be allocated any name (like OL_ADMIN above) to fit in with your organisation's policies / standards. 

2. We recommend that this user should be classified as a 'System' user in SU01 (not 'Dialog'):

3. We recommend that, like WF-BATCH, the service account must have broad authorisations (to be able to start background jobs, call programs, execute the methods in the Adapter framework, etc.). We therefore recommend SAP_ALL be allocated to this user. If that is not possible, then the user must be given at least the following roles in the table below, see Roles and Authorizations for Background Processing.

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

Image Added

Press the Save button to complete the setup

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 /IQX/OL_JOB_DEF maintenance table further down, for older versions).

S_BTCH_NAM

BTCUNAME

*

Authorized user when scheduling

S_BTCH_ADM

BTCADMIN

Y

User is batch administrator

The value "Y" of BTCADMIN enables all operations for any jobs across clients.

SYNC_DELTA

Sync Delta user by SAP ID mapping

SYNC_DELTA_EMAIL

Sync Delta user by Email mapping

SYNC_DELTA_V2

Sync Delta user using new OL API /GetUserSync with mapping is configured via /IQX/OL_CONFIG transaction in OneList Global Settings section

SYNC_CHANGE

Sync Change user

SYNC_ALL_DELEGATIONS

Sync delegation from OneList to SAP and vice versa.

Workflow Type

WF - Workflow

Substitution Profile

Defines the Substitution Profile maintained in SPRO that will be used by OneList.

Active

Flag that sets the Delegation Profile as active when ticked or inactive when unticked.

EMAIL_APPR_ENABLED

Flag that sets the email approval enabled if the value “X” or disabled if left blank.

EMAIL_MAX_AGE_DAYS

Defines the maximum age of the email.

EMAIL_MAX_FILESIZE

Defines the maximum size of the email.

EMAIL_SOURCE

Possible values:

• UM - Email is retrieved from SAP User Master

• HR - Email is retrieved from SAP HR record Infotype 0105.

• UM-HR - Default option if no setting is defined. Email is initially retrieved from the User Master. If the User Master is empty, the email is retrieved from HR.

• HR-UM - Email is initially retrieved from the HR. If the HR is empty, the email is retrieved from User Master.

ONELIST_USER_ID - is only available since IQX Version 3.3 along with OneList version 8.0.

Possible values:

• EMAIL: OneList ID is mapped to e-mail address

• SAPID: OneList ID is mapped to SAP ID

• PERNR: OneList ID is mapped to SAP HR Personal Number

SYNC_DELTA

Sync Delta user by SAP ID mapping

SYNC_DELTA_EMAIL

Sync Delta user by Email mapping

SYNC_DELTA_V2

Sync Delta user using new OL API /GetUserSync with mapping is configured via /IQX/OL_CONFIG transaction in OneList Global Settings section

SYNC_CHANGE

Sync Change user

SYNC_ALL_DELEGATIONS

Sync delegation from OneList to SAP and vice versa.

SYNC_ACTIONS

Every 2 minutes

SYNC_ATTACHMENTS

Every 2 minutes

SYNC_DELTA_TASK_LIST

Every 2 minutes

SYNC_CHANGED_TASK_LIST

Every 2 minutes

SYNC_USER

Every 5 minutes