Versions Compared

Version Old Version 6 New Version 7
Changes made by

ProNovia

Marvin Biesenbach

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 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 (blue star) sap (blue star) bc (blue star) ui5_ui5 (blue star) 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

...

  • 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

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

...

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

...