...

Your company may use both options, or only one - either way, you will have to do some common configuration / setup for the processes to work. For example, the background job that needs to run to manage the communication between SAP and OneList will have to be set up in the system / client where the workflows are running.

Image RemovedImage Added

Background job - setup (Mandatory)

...

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

   (Note: This should be a

    

   Info
   title User information
   A service user account must be created

   for

   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.  We recommend that this user should be classified a 'System' user in SU01 (not 'Dialog'): Image Added 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
    

...