BPF Fiori Components Setup

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.

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.

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 Solution	BSP Service	Odata Service
Fiori My Inbox integration	bpf_f_ibox and bpf_taskhndl	/PCH/BPF_INBOX_SRV /PCH/BPF_TASKS_SRV
ProProcess Dashboard and Process List:	bpf_dashboard bpf_procdetails	/PCH/BPF_REPORTING_SRV
Fiori Process Analysis	bpf_ppa core_dashboard core_license	/PCH/BPF_PPA_SRV /PCH/CORE_LICENSE_SRV

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.

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.

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.

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:

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

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.