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:
/PCH/BPF_INBOX_SRV and /PCH/BPF_TASKS_SRV for the Fiori MyInbox integration
/PCH/BPF_REPORTING_SRV for the ProProcess Dashboard and Process List
Activation of front-end sources
The front-end sources' services for the ProProcess Fiori UI must be activated. Navigate in transaction SICF to default_host 
sap bc ui5_ui5 pch and activate the following nodes via context menu activate the service:For .
BSP Services and Odata Services
The following tables shows the BSP Services and Odata services which needs to be activated for a specific fiori solution.
Fiori Solution | BSP Service | Odata Service |
|---|---|---|
Fiori My Inbox integration |
...
|
...
| ||
ProProcess Dashboard and Process List: |
|
|
Fiori Process Analysis |
|
|
| Note |
|---|
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:
...
| Note |
|---|
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.
...
| Info |
|---|
In case a Web Dispatcher Service is active in the Fiori Landscape, the settings must be adjusted accordingly. Further Informations are available in the SAP Note 2519744. |
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).
...
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:
ABAP Class | Name |
/PCH/CL_BPF_WF_AENR | ECM Change master |
/PCH/CL_BPF_WF_DRAW | Document |
/PCH/CL_BPF_WF_MARA | Material |
/PCH/CL_BPF_WF_MARC | Plant data for material |
...