Show TOC

Integrating Your SAP Business Workflow SystemLocate this document in the navigation structure

To integrate an SAP Business Workflow (BWF) system for use with Task Gateway, you must verify that your system is set up appropriately (prerequisites are fulfilled). Note that the SAP Business Workflow system must be based on SAP NetWeaver 7.00 SPS18 or higher. You must install the component IW_BEP in your SAP Business Workflow system. If your system landscape is based on SAP NetWeaver 7.40 or higher, it contains the core SAP Gateway component SAP_GWFND as standard and, as such, you do not need to install IW_BEP in your SAP Business Workflow system.

SAP Notes

Depending on your SAP NetWeaver release and Support Package Stack level, see the following SAP Notes (as mentioned in collective note 2119455 Information published on SAP site and apply as applicable to your SAP Business Workflow system:

  • My Inbox: Inbox API - SAP Note 1774246 Information published on SAP site

  • Service Class for Generation of URLS - SAP Note 2009417 Information published on SAP site

  • Number of Attachments of a Work Item Is Not Correct - SAP Note 2014238 Information published on SAP site

  • Missing API for Determination of Action "Forward" - SAP Note 2038832 Information published on SAP site

  • New WAPI for Checking Inbox - SAP Note 2040139 Information published on SAP site

  • Enhancement Framework for New Tables - SAP Note 2046569 Information published on SAP site

  • URL Generation for UI5 Applications (BSP) - SAP Note 2056158 Information published on SAP site

  • Missing API for Determination of Step Texts - SAP Note 2058479 Information published on SAP site

  • New WAPI for Reading Properties of Attachments - SAP Note 2065766 Information published on SAP site

  • My Inbox: API for Reading Customer Attributes for Inbox - SAP Note 2068161 Information published on SAP site

  • API for Reading Tasks/Workflows of a System - SAP Note 2083503 Information published on SAP site

  • My Inbox: Substitution API - SAP Note 2087165 Information published on SAP site

  • SAP_WAPI_FORWARDING_INFO_GET: Returns Incorrect Information - SAP Note 2103377 Information published on SAP site

  • Replacing WF-BATCH as Work Item Initiator with User - SAP Note 2108489 Information published on SAP site

  • Missing API for Determining Information About Supported Execution URL - SAP Note 2121309 Information published on SAP site

  • My Inbox: Standardization of Output of Date and Time - SAP Note 2121433 Information published on SAP site

  • Performance of Method CL_WAPI_MOBILE_INBOX->GET_CURRENT_INBOX - SAP Note 2132220 Information published on SAP site

  • CL_WAPI_STEP_ATTRIBUTES->GET_STEP_DESCRIPTION Returns No Values - SAP Note 2132239 Information published on SAP site

  • My Inbox: Standardization of Work Item Actions - SAP Note 2145901 Information published on SAP site

  • (Optional) Inbox: Output of Attachments for Leading Object - SAP Note 2155000 Information published on SAP site

  • CL_WAPI_STEP_ATTRIBUTES->GET_STEP_DECISION_DESCRIPTION Returns Too Many Lines - SAP Note 2175678 Information published on SAP site

  • CL_WAPI_MOBILE_INBOX->GET_RESUBMISSIONS: No Result Returned for Work Item Filter - SAP Note 2176378 Information published on SAP site

  • URL Generation for Applications (My Inbox) - SAP Note 2178368 Information published on SAP site

  • Metadata for transactions SWFVISU and SWFVMD1 - SAP Note 2200084 Information published on SAP site

  • CL_WAPI_MOBILE_INBOX->GET_WORKITEM_COUNTS does not differentiate by workflow step - SAP Note 2212078 Information published on SAP site

  • My Inbox: Mass-enabled access to definition of user attributes - SAP Note 2245526 Information published on SAP site

  • Optimization of URL generation (mass capability) - SAP Note 2259532 Information published on SAP site

Note

The SAP Business Workflow system includes different task types, but not all of these might be relevant for Task Gateway. If you want to restrict the task types to be considered by Task Gateway, use the task filter function to specify which task types apply. If the task filter is deactivated, all task types are considered. To restrict the applicable task types, activate the task filter. To activate or deactivate the task filter, open the SAP Customizing Implementation Guide and choose Start of the navigation path SAP NetWeaver Next navigation step SAP Gateway Service Enablement Next navigation step Content Next navigation step Workflow Settings End of the navigation path and execute the Enable Task Filter activity. This activity enables you to activate or deactivate the task filter and therefore specify which task types are relevant for Task Gateway.

To register a new system alias for your SAP Business Workflow system in your SAP Gateway system, you must first have:

  1. Created a new system alias (see Creating a System Alias). Software version for SAP Business Workflow systems would be /IWPGW/BWF

  2. Activated your Task Gateway TASKPROCESSING service (see Activating Task Gateway Service).

After you have created a system alias for your SAP Busines Workflow system and activated your Task Gateway service, proceed as follows to register the system alias:

  1. In the SAP Gateway system, start transaction SPRO.

  2. Choose SAP Reference IMG.

  3. Select Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver Next navigation step SAP Gateway  Next navigation step OData Channel Next navigation step Administration Next navigation step General Settings End of the navigation path.

  4. Select the Activate and Maintain Services activity. The Activate and Maintain Services screen is displayed.

  5. In the Service Catalog table, search for the Task Gateway Service, TASKPROCESSING, in the External Service Name column and select the entire line.

  6. In the System Aliases section, choose Add System Alias. The Change View "Assign SAP System Aliases to OData Service": Overview screen is displayed.

  7. Select the SAP system alias for your SAP Business Workflow system and choose Copy.

  8. In the SAP System Alias field, use the input help (F4) and select the system alias you previously created.

  9. In the Default System field, the checkbox does not need to be selected. If the checkbox is selected, this SAP system will be called by default.

  10. Press Enter.

  11. Choose Save.

To transport an alias assignment from the Change View "Assign SAP System Aliases to OData Service": Overview screen, select the row and choose Start of the navigation path Table View Next navigation step Transport End of the navigation path. In some cases a warning message is displayed that explains important points you should consider before transporting individual alias assignments. The message outlines general considerations you should adhere to.