Page Comparison

...

• OneList v6 Adapter framework is installed on your SAP Backend system 
• SAP Workflow already completely built and and functional.

SAP Development tasks

1. Create a custom implementation class based on the IQX Adapter base class:
   1. Use the Class Builder in SAP (t-code SE24) to open the class /IQX/CL_SAP_WL_ADPT.
   2. From the menu bar, select Edit → Create Subclass.
   3. Enter the name of the subclass in the Class field.
      • e.g. ZCL_OL_PO_ADAPTER
   4. Enter a short description in the Description field.
      • e.g. Purchase Order adapter for OneList
   5. Choose Save.
   6. Enter the Package and choose Save again.
      
      
2. Redefine the following inherited methods (click on the method for the implementation example):
   1. EXECUTE_ACTION
   2. GET_ATTCHMENT_CONTENT
   3. GET_OBJECT_DETAILS
      
      
3. Create the new methods (called by GET_OBJECT_DETAILS) to retrieve the correct PO information, as well as set up the Action buttons in OneList:
   1. GET_PO_DETAIL
   2. GET_PO_ACTION
4. Check, Save and Activate the implementation class.

...

1. • Next, add an entry for the process you want to integrate between SAP and OneList.  If you are integrating OneList with an SAP Workflow, you will need to know the Standard Task ID (use the Workflow Builder (SWDD) or transaction PFTS to get this information) that contains the processing steps. Alternatively, if you are integrating a Fiori App Builder application with OneList, you will need to know the FAB Form name. For completeness, the screenshot below contains an example of both options - although we will only look at the Workflow integration below (the same steps will be followed for integration with a FAB App):
     
     
     
   • OneList Job Configuration
     Highlight the User integration entry (configured above, and remember this is only done once):
     
     Then double-click the 'OneList Job configuration' entry in the tree structure. Configuring this step allows the Adapter framework to communicate with the OneList instance, specifically for user integration. IQX has provided a standard user integration Adapter class (/IQX/CL_OL_SYNC_USERS), but in rare circumstances your organisation may need to alter the behaviour of this class. In that case, you will have to create a subclass of this class (see step 1 above, under SAP Development tasks) and override the relevant methods to suit your needs. in In that case, instead of /IQX/CL_OL_SYNC_USERS, use the name of your subclass in the below configuration steps. 
     
     You will need to define entries for the SYNC_USER_REQUEST and SYNC_USER_REQUEST_DELTA OneList User Integration APIs/Actions. For each entry, specify:
     • Adapter Class name: /IQX/CL_OL_SYNC_USERS,or your  or your user integration subclass
     • Frequency in minutes: how often the background job calling this OneList API should run. We recommend between 5 and 30 minutes.
     • Active - A flag to set whether this job should run. During specific scenarios (shutdown, data take-on, etc.) you may want to disable individual API calls. Normal value will be ticked.
     
     The end result should look something like this:
     
     
     Now highlight the process integration point for which you want to configure the background jobs ("SAP WF Process" in this example). Remember that there can be multiple processes integrated with OneList - these steps need to be repeated for every process:
     
     Then double-click the 'OneList Job configuration' entry in the tree structure. Configuring this step provides a link between your SAP Adapter class (for example ZCL_OL_PO_ADAPTER, created above) and the IQX OneList SAP Adapter framework.  For each entry defined here, the Adapter framework will create a background job at the specified frequency, thereby pushing / pulling data to and from OneList. You will need to define entries for the following 4 OneList Integration APIs/Actions:
     1. SYNC_ACTIONS
     2. SYNC_ATTACHMENTS
     3. SYNC_CHANGED_TASK_LIST
     4. SYNC_DELTA_TASK_LIST
        
        For each entry, specify:
        • Adapter Class name: your class created above, for example ZCL_OL_PO_ADAPTER
        • Frequency in minutes: how often the background job calling this OneList API should run. We recommend between 1 and 5 minutes at most.
        • Active - A flag to set whether this job should run. During specific scenarios (shutdown, data take-on, etc.) you may want to disable individual API calls. Normal value will be ticked.
          
          The end result should look something like this:
          
          
          
          

...

1. Define a Scheduler background job via SM36 with the following values:
   Note: Do this in the client where you are executing your testing (Dev Unit Test or QAS) and in the live / productive client at go-live.
   1. Enter the Job Name - ONELIST_SCHEDULER
   2. Enter the Job Class - B
   3. Press the Step button
   4. Enter the User - e.g. OL_ADMIN (Note: This should be a service user account created for background jobs)
   5. Enter the ABAP Program Name - /IQX/ONELIST_JOBS
   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

   11. Press the Save button to complete the setup

       Info
       title Note
       Background jobs are usually created by the Basis resource and should be set up to use the existing service user account

       Once the OneList Scheduler background job has been created, it will automatically schedule the OneList Adapter jobs defined in theOneList the 'OneList Job configuration' entries above (or the /IQX/OL_JOB_DEF maintenance table, below, for older versions).

Older version of the SAP Adapter
Note: Ignore this section if you used transaction /IQX/OL_CONFIG above.

...

Note: Make sure you return to the step above to complete the creation of the background job.

...