Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

A custom SAP Non-Workflow adapter can be used to facilitate the approval process in SAP that does not utilize an existing SAP Workflow.

This section will detail the steps you need to follow for setting up such a custom SAP Non-Workflow adapter that can connect to OneList V6. 

Prerequisites:

  • OneList v6 adapter is installed on your SAP Backend system 

Configuration steps:

Note

This example is based on a Purchase Order workflow

  1. Create a custom implementation class based on the IQX 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 and leave the implementation blank for now:
    1. EXECUTE_ACTION
    2. GET_ATTCHMENT_CONTENT
    3. GET_OBJECT_DETAILS
  3. Check, Save and Activate the implementation class.
  4. Maintain the following OneList configuration tables via SM30 (Note: Use the unit test client
    1. /IQX/OL_TASK_DEF - Task Definition
      1. Create a new entry with the following values: 
        • Job Type - The description of the type of task e.g. PO_APPROVAL
        • O.L.Task ID - The workflow task ID for the object you would like to retrieve the worklist items. e.g. TS20000166
        • Project Name - optional
        • Number - The number of workflow tasks that should be fetched ???? not sure
    2. /IQX/OL_JOB_DEF - Background Job Definition (more info on this - the entries in this table will be used to automatically create background jobs that will run to execute functionality)
      1. Create a new entry for each of the following values:
        • SYNC USER
          • Job Type - Use the job type defined in the previous step e.g. PO_APPROVAL
          • Class - Name of the implementation class created in step 1.c. e.g. ZCL_OL_PO_ADAPTER
          • Subcomponent - SYNC_USER_REQUEST
          • Short Description - Synchronize SAP users to OneList
          • Freq in mins - 5
        • SYNC ACTIONS
          • Job Type - Use the job type defined in the previous step e.g. PO_APPROVAL
          • Class - Name of the implementation class created in step 1.c. e.g. ZCL_OL_PO_ADAPTER
          • Subcomponent - SYNC_ACTIONS
          • Short Description - Synchronize adapter task actions to OneList
          • Freq in mins - 5
        • SYNC ATTACHMENTS
          • Job Type - Use the job type defined in the previous step e.g. PO_APPROVAL
          • Class - Name of the implementation class created in step 1.c. e.g. ZCL_OL_PO_ADAPTER
          • Subcomponent - SYNC_ATTACHMENTS
          • Short Description - Synchronize attachments to OneList
          • Freq in mins - 5
        • SYNC CHANGED TASK
          • Job Type - Use the job type defined in the previous step e.g. PO_APPROVAL
          • Class - Name of the implementation class created in step 1.c. e.g. ZCL_OL_PO_ADAPTER
          • Subcomponent - SYNC_CHANGED_TASK
          • Short Description - Synchronize the changed task list to OneList
          • Freq in mins - 10
        • SYNC DELTA TASK LIST
          • Job Type - Use the job type defined in the previous step e.g. PO_APPROVAL
          • Class - Name of the implementation class created in step 1.c. e.g. ZCL_OL_PO_ADAPTER
          • Subcomponent - SYNC_DELTA_TASK_LIST
          • Short Description - Synchronize detailed task list to OneList (delta tasks)
          • Freq in mins - 5
    3. /IQX/OL_ENDPOINT - OneList Service Endpoint
      1. Create a new entry with the following values: 
        • OneList URL - Specify the URL endpoint configured for OneList 
        • OneList Server App Path: /onelistserver/api/DataSync
        • SSL Client Identity: e.g. ANONYM
        • API Key: The unique API key used by the endpoint
        • Active: Checked
  • No labels