(DI-2002) OData and Fiori Manual Setup

Owned by SNP
Last updated: Apr 23, 2020 by Marian Vidra
4 min read

In the case you prefer to set up the OData manually, you may do as follows:

Prerequisites

  • Central package needs to be installed on the system.
  • Check prerequisites from the previous chapter (DI-2002) Fiori Prerequisites.
  • Check and choose a system architecture, based on it continue with the setup of an oData service.
  • System where OData services are activated has to be open for development.

Following steps will be executed on the system which is used for Fiori visualization. Fiori can be installed on a central system or on a different SAP system (e.g. in the case that the central system doesn't meet the Fiori prerequisites and the other SAP system does). The Fiori application requires an already installed OData service.
In the case that Fiori is installed on a SAP system other that the central, it must be connected with the central system through a RFC connection defined with the role /dvd/mon_admin. The manual "Setup of OData service", which is below, is for both cases (with some small differences for the setup of Fiori on a SAP central system or on a different SAP system).

Setup of the OData service

  1. Activate the SAP NetWeaver Gateway:
    • Run the transaction code /n/IWFND/IWF_ACTIVATE.
    • Click on the Activate button.

  2. Create a system alias:
    • Run the transaction code SM30.
    • Insert /IWFND/V_DFSYAL into the Table/View field.
    • Click on the Maintain button.
    • Click on New Entries and choose a unique alias for your system (if Fiori is installed on a SAP system other than central system, fill in the RFC Destination to connect these two systems. RFC connection must be defined with the role /dvd/mon_admin).  

3. Assign an alias to the OData gateway service with the following steps:

    • Run the transaction code /n/IWFND/MAINT_SERVICE and click on Add service.
    • Enter the previously defined system alias. 
    • Click on Get services.
    • Select services that you want to add and click on Add Selected Services.
    • Always add the following OData services: RL_SETT_SRV, MON_DET_SRV, HS_BODATA_SRV, HS_ODATA_SRV, HS_KPI_SRV
    • Select prefix "Z" and package assignment "$TMP" for the selected services and confirm. 

4. Activate the OData service

    • Go back.
    • Click on the previously added services and for each of them follow these steps (IMPORTANT: please bear in mind that these services might be already activated. By default they are, this is just a way to double check that everything is activated):
      • In the bottom left side of the screen click on ICF Node and choose Configure (SICF).
      • In the context menu of the service choose Activate Service. (The other option is that you use the transaction SICF, enter it into the Service Path /sap/opu/odata/dvd and activate the whole node which includes all previously added services.) 

  • After a service is activated, click on Test Service. A browser window appears with the information about the OData service. 

After each service is activated, enter the transaction /n/IWFND/MAINT_SERVICE and click on Load Metadata.

How to setup Fiori application

Prerequisites

  • Insights OData services are up and running (see previous section).
  • Insights Fiori application transport is imported into the system.

Setup steps

  1. Enable ui5 web application:
    • Run the transaction code SICF
    • Enter the service path: /sap/public/bc/ui2. Execute (F8)

    • In the context menu of the node ui2 choose Activate Service 

    • Change the service path to: /sap/bc/ui2/start_up.
    • Click on Apply.
    • In the context menu of the 'node start_up' choose Activate Service
    • Change service path to: /sap/bc/ui5_ui5/dvd/. 
    • Click on Apply.
    • Expand the "dvd" node.
    • In the context menu of the following node (Fiori) choose Activate:
    • In the context menu of the node "Fiori" click on Test Service.

2. The web browser should display an url similar to "http://<host>:<port>/sap/bc/ui5_ui5/dvd/fiori/index.html".