6.1 A Structured Approach to Fiori Implementation

A successful SAP Fiori implementation is not an ad-hoc activity but a systematic process that requires careful planning and execution. The lifecycle involves a series of structured phases, beginning with verifying prerequisites, followed by the installation of necessary front-end and back-end software components, and concluding with app-specific configuration. This process has been simplified over time through the integration of the Fiori apps library with the SAP Maintenance Planner, which helps organizations identify the required components and configuration steps for the apps they wish to deploy.

6.2 Phase 1: Installation and Prerequisite Verification

Before any installation begins, it is crucial to verify that the system landscape meets all prerequisites. This includes checking for the correct versions of key components like SAP NetWeaver and the Central UI Add-On, as well as confirming the presence of a SAP HANA 1.0 database if Fact Sheet or Analytical apps are planned.

Once prerequisites are confirmed, the necessary software components are downloaded from the SAP Software Download Center (SWDC). The installation process then involves deploying the Central UI Add-On and any product-specific UI Add-Ons (e.g., for ERP, SRM, SCM) onto the front-end server. A significant advantage of these add-ons is that they are non-modifying, meaning they do not alter the core back-end system and can be installed without requiring any downtime for the business suite.

6.3 Phase 2: Configuration of Fiori Applications

After the foundational components are installed, each Fiori application type requires specific configuration steps to become operational.

1. Configuring Transactional Apps

The configuration for Transactional Apps involves setting up the complete communication path from the user’s browser to the back-end business logic.

• First, the SAP Web Dispatcher is configured to handle routing and enforce security for incoming HTTPS requests.
• On the front-end server, the necessary OData services are activated (using SPRO), and the corresponding Internet Communication Framework (ICF) services are activated (using SICF).
• A trusted RFC connection must be established between the front-end server and the back-end system to allow for secure, seamless communication.
• Finally, on the back-end server, the relevant user roles are assigned using the Profile Generator (PFCG) to grant users the authorizations needed to execute the transactions.

2. Configuring Fact Sheets

Fact Sheets have unique requirements centered around their search functionality. The critical configuration step is setting up the embedded Enterprise Search.

• This process begins with activating the necessary UI services for the search cockpit.
• Next, the search functionality is connected to the SAP HANA database.
• Using the Enterprise Search Cockpit (ESH_COCKPIT), administrators create the necessary search connectors for the relevant business objects and then run an indexing job to make the data searchable.

3. Configuring Analytical Apps

Analytical Apps rely on a specific architecture within the SAP HANA database. Configuration focuses on enabling the real-time data processing capabilities of the HANA XS Engine.

• These apps use content from HANA Live and the Smart Business components. The core of this architecture is the Virtual Data Model (VDM), which consists of a hierarchy of views (Private, Reuse, and Query views) designed to efficiently process massive quantities of data for analytical consumption.
• A key tool in this process is the KPI Modeler, which allows business analysts to define, manage, and visualize Key Performance Indicators. These KPIs are then surfaced to end-users as interactive tiles on the Fiori Launchpad, providing at-a-glance insights into business performance.

With implementation complete, attention must turn to the ongoing concerns of customization, security, and daily operations.