Page Comparison

The ProProcess Fiori Integration consists of two parts, one for the back-end system and one for the front-end system. Import the corresponding component to the corresponding system. In case you use a one system landscape (same front-end and back-end system), both components must be imported into this system.
The following Steps must be processed in order to setup the Components in the front-end system (or the one system, in one system landscape setup).
Activation of the ODATA service
The ODATA / Gateway Services for the ProProcess can be activated using the Gateway Customizing or the transaction /IWFND/MAINT_SERVICE. For more detailed information on how to activate a Gateway Service, please refer to the corresponding SAP documentation. The following services must be activated to use the components:

...

For the ProProcess Dashboard and Process List:

• bpf_dashboard

• bpf_procdetails

  Image Modified

  These steps must be repeated in every system, in which the BPF Fiori Apps shall be used. SICF Service activations are not transported.

  Assigning of service authorizations
  In order to access the ProProcess ODATA service, the user needs appropriate authorizations. The required authorizations are described in the chapter Authorization. Corresponding authorization default values are provided in the ProProcess Fiori role.
  Fiori launchpad integration
  The following steps must be processed in order to publish the ProProcess Dashboard in the launchpad:

• Assign the fiori catalogue /PCH/BPF_FIORI to the corresponding authorization roles for the end users.

  Image Modified

  The user must add the application to its launch page manually, if no customer specific tile group is assigned.

  Fiori MyInbox integration - front-end system
  The ProProcess work list is integrated into the SAP Fiori My Inbox 2. Therefore the Fiori My Inbox 2 needs to be setup according to the official SAP setup guide for the Fiori My Inbox.

• Setup the Fiori My Inbox according to the SAP Documentation and connect it to the corresponding back-end system(s). Please refer to the corresponding SAP Help or Wiki Pages regarding the current setup instructions.
• Define a system alias in transaction SPRO for the Gateway connection to the back-end which will be used by the BPF services. In case of a one system landscape, the alias may define a local connection. Further Information on system aliases for SAP Gateway can be found in the corresponding SAP help. In case of multiple back-end systems, one system alias needs to be created for every back-end system.
• Assign the system alias(es) (defined in the step above) to the Gateway Services /PCH/BPF_INBOX_SRV and /PCH/BPF_TASKS_SRV.
• define the semantic object ProNoviaBPFWorkItem (ProNovia ProProcess Workitem) in transaction /UI2/SEMOBJ.

• Assign the Fiori Catalogue /PCH/BPF_FIORI to the business roles for the end users, which shall use the ProProcess.

  Image Modified

  Make sure, that for all system aliases, used with BPF (My Inbox integration, as well as BPF Gateway service) the values for target system and target client are set correctly. Make sure, that, if the system aliases are transported and used in another system, the correct target system and target client are adjusted to match the correct names.

  
  

  Image Modified

  Due to the multi origin design of the SAP My Inbox, it is required to create an appropriate system alias also in case of an one system landscape and assign the correct target system an target client. Integrated deployment is not available for the My Inbox integration.

  
  

  Image Modified

  Be sure to consult the current valid SAP NetWeaver / SAP Fiori security guidelines for a secure setup (e.g. encryption...).

  
  

  Image Modified

  In case a Web Dispatcher Service is active in the Fiori Landscape, the settings must be adjusted accordingly.

  
  

  Image Modified

  The Fiori Catalogue /PCH/BPF_FIORI contains the Fiori My Inbox integration, as well as the ProProcess Dashboard and ProProcess Process List.

  
  Fiori MyInbox integration - back-end system
  The following steps need to be executed in all corresponding back-end systems (or in the one system, in case of a one system landscape).

• In the transaction SWFVISU, setup the BPF standard task in the section Task Visualization as follows. The standard task ID can be obtained from the BPF basic settings.
  • Visualization type: intend based navigation
  • Visualization parameter:
    • SEMANTIC_OBJECT ProNoviaBPFWorkItem
    • ACTION: displayInlineSWFDetail
    • QUERY_PARAM00 workitemId={WORKITEM}
    • QUERY_PARAM01 sap-system=sid({SYSTEM}.{CLIENT})

Custom Object navigations can be defined in the transaction SWFVISU in the section Object Visualization. The Objects, which must be used to adjust the navigation are of type ABAP Class with the default pattern /PCH/CL_BPF_WF_*. Custom Object types may differ. Currently the following types are part of the default delivery:

The type of navigation and the navigation parameter differ depending on the navigation target. Further information can be obtained in the corresponding SAP Help or Wiki.