Components in Front-End System
Activation of the OData Services in the SAP Gateway Hub
The OData Services must be activated using the SAP Gateway Hub (target system for the OData service) or the transaction /IWFND/MAINT_SERVICE. For more detailed information on how to activate an OData Service, please refer to the corresponding SAP documentation.
Activation of Front-End Sources
The front-end source services for Fiori UI’s must be activated. Navigate to transaction SICF and there 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 any used ProNovia SAP Fiori solution.
Product | BSP Service (ICF Node) | OData Service(s) |
---|---|---|
UTI |
|
|
BPF |
|
|
BPF |
|
|
BPF |
|
|
DMC |
|
|
RQF |
|
|
RQF with Attachment Functionality * |
|
|
SCD |
|
|
Further prerequisites for the Attachment Functionality in the ProNovia Request (Create / Change / Display) Fiori App:
there must be a Storage Category activated for the Attachment Service. See: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/4c3d1c6b3d744f84aab4c273f979f430/9876d8dbc76445c58f87ef3d2f884052.html?locale=en-US#maintain-storage-category
the BAdI implementation: /PCH/ECR_ATTACHMENT_SRV must be activated and the method FINALIZE_OBJECT_KEYS() must exist (for some old versions the method is not yet available).
These steps must be repeated in every system, in which the ProNovia Fiori Apps shall be used. SICF Service activations are not transported.
Assigning of Service Authorizations
In order to access the OData Service, the user needs appropriate authorizations, which are described in the corresponing sections. Corresponding default values are provided in the ProNovia Fiori roles.
Fiori Launchpad Integration
Assign the required Fiori catalogs to the corresponding authorization roles for the end users:
Product | Fiori Application(s) | Technical Catalog |
---|---|---|
BPF | Process List, Process Overview, Process Analysis | /PCH/BPF_FIORI |
DMC | ProDocument Explorer | /PCH/DMC_FIORI |
RQF | Cockpit Request Creator, Request (Create / Change / Display) | /pch/ecr_tech_catalog |
SCD | ProSCMDashboard | /PCH/LDB_DASHBOARD |
The customer must add the Application to its Fiori Launchpad manually, if no customer specific tile group is assigned.
Adding Apps to the Launchpad
Please see following official SAP Documentation: https://help.sap.com/docs/ABAP_PLATFORM_NEW/a7b390faab1140c087b8926571e942b7/3de7bee2196f438a803564803b578dcc.html?version=201809.latest&locale=en-US .
SAP My Inbox 2.0 Integration (Front-End System)
Following ProNovia SAP Fiori Applications 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 required Gateway Services listed in the table below.
Define the semantic objects in transaction /UI2/SEMOBJ.
Assign the required Fiori Catalogues to the business roles for the end users.
Product | Fiori Application | OData Service(s) | Semantic Object | Technical Catalog |
---|---|---|---|---|
BPF | Process Work List | /PCH/BPF_INBOX_SRV | ProNoviaBPFWorkItem (ProNovia ProProcess Workitem) | /PCH/BPF_FIORI |
© ProNovia AG | Imprint | Data Protection