Versions Compared

Version Old Version 5 New Version 6
Changes made by

Ana Chua

Ana Chua

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Enter the Job Name , for example ONELIST_JOBS_SCHEDULER

  2. Enter the Job Class - B or C (Medium / Low priority)

  3. Press the Step button

  4. Enter the ABAP Program Name - /IQX/ONELIST_JOBS

  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:

      Authorisation Object: S_BTCH_NAM (BTCUNAME - Background User Name for Authorization Check)
      Values: * (All users)

  6. Press the Save button

  7. Press the Start conditions button

  8. Press the Date/Time button and enter the scheduled start date and time

  9. Press the Period Values button and choose Other period from the options

  10. Enter 1 in the Minute(s) field

    Image RemovedImage Added

Press the Save button to complete the setup

...

With the above in place, the background job defined in the first step will create a background job per integration task type, at the specified frequency. The 'SYNC*' methods (described above) will call the methods you have redefined in your custom Adapter class, thereby enabling the extraction of data from the SAP Workflow / SAP objects (which will be sent to OneList) and the return flow of the OneList Actions to the SAP Workflow / SAP Objects.

OneList Delegation Profiles

Delegation Profiles that should be synchronized to OneList can be configured in transaction /IQX/OL_CONFIG.

FAB Workflow integration with OneList (Optional)

...

...

Key

Value

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.

OneList Global Settings

OneList Global Settings can be configured in transaction /IQX/OL_CONFIG.

...

Key

Value

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 User Master

  • HR - Email is retrieved from HR

  • 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.

FAB Workflow integration with OneList (Optional)

Info

Not everyone will integrate FAB Workflows with OneList. If you are using only standard SAP Workflows, then skip this section.

...


Note that there is a sequence to be followed, as per the tree structure, shown below:

OneList Endpoint configuration (this may be complete already)
Add entries for each of the systems in your SAP landscape. When you save this information, SAP will prompt you for a transport request. This will enable you to transport the entries to your Quality Assurance and Productive systems, as well as importing into your Development Unit Testing Client. 

...