Today we discuss SAP Fiori, the buzz word in SAP landscape. Here we will learn about what is SAP Fiori, types of Fiori apps, architecture and benefits.
Let’s start with brief intro on SAP Fiori
SAP user interface had more than 3 lakh screens with various functions in it. SAP checked the most frequently used apps and then decided to renew these applications. That’s how SAP Fiori was born.
The word Fiori literally means “Flower” in Italian (that’s the reason when you open a home page sap Fiori application, we will see a picture of flowers). SAP Fiori is a Leading design for all SAP software and applications. It comprises a set of applications like work approvals, calculation apps, financial apps, and self-service apps etc. It enables multiple device applications (A user can start a process on mobile/tablet and continue the same process on desktop/laptops) and also provides role-based applications (300+) like Human Resources, Finance, Sales, Manufacturing, Supply Chain, R&D, Engg, Asset Management, etc.
SAP Fiori is a new user experience (UX) developed by SAP based on User Interface UI5 and OData services. It enables employees to work with SAP simply, quickly, and easily by eliminating the complexities involved in the SAP Landscape. SAP Fiori apps make SAP available in multiple devices like Mobile, tablets, etc and that helps the organizations to build productivity easily. Using modern design principles, Fiori apps provides customized, responsive, straight forward client experience and also delivers a role-based, consumer-grade user experience across all lines of business, and tasks. Being SAP Fiori stateless applications except for database operations you can execute each and every functionality at client side browser. Fiori apps performance better than ABAP screens, because Fiori apps is a lightweight browser-based screen, had more than 150 screen elements and also consumes less memory during execution.
There are 5 design principles for SAP Fiori UI5
SAP Fiori apps are classified into 3 types
Each differentiated by their focus and infrastructure requirements
When installing SAP fiori apps, separate the front-end components with the user interface (UI) layer from the back-end components, which contains the business logic and the back-end data.
Make sure the access is sure, all SAP Fiori apps can be accessed over the intranet(inside the corporate network) and the internet (outside the corporate network),
*use sap web dispatcher as reverse proxy server for fact sheets and analytical apps.
These apps let you perform transactional tasks such as creating a leave request for an employee. They represent simplified views and interaction with existing business processes and solutions and also run best on an SAP HANA database, but can also be ported to other databases with acceptable performance.
These apps display contextual information and key facts about central objects used in your business operations. From a fact sheet area (tile), you can drill down into its details. You can navigate from one fact sheet to its related fact sheets.
you can navigate from a document to the related business partner or to the master data.
You cannot access SAP GUI or Web Dynpro transactions through the SAP fiori Launchpad from mobile/desktop.
Fact sheets run only on an SAP HANA database and require an ABAP stack. They cannot be ported to the SAP HANA live (2-tier) architect.
These apps let you get a role-based insight into real-time operations of your business by collecting and displaying key figures directly in your browser. Analytical apps combine the data and analytical power of SAP HANA with the integration and interface components of SAP Business Suite.
To do this, you can easily use the pre-delivered KPIs and insight-to-action scenarios or define your own ones based on the KPI modeling framework.
Analytical apps run on an SAP HANA database and use virtual data models (VDM).
Find the key components of SAP Fiori architecture
*It is the first point of contact in sap F
*It is an entry point for all https/http requests and defines if a system has to accept or reject the requests and the server where the request should go. It can reject or accept connection to SAP Fiori system.
Note :- Both Fact sheets & analytical apps runs only on SAP HANA database to run but, transactional apps can run on any database
It contains all the user interface (UI) components of Fiori system and NetWeaver gateway.
It is used to set up a connection between SAP business suite and target clients, platform and also offers development and generation tools to create OData services to different client development tools.
It is used to store the business logic and the back-end data. Both search model for fact sheets and sap business suite is stored in this server.
It is used to run all analytical apps in SAP Fiori and also contain Fiori apps content and virtual data-model reuse content, which is provided through SAP HANA live.
Two components of HANA XS Engine
SAP Fiori Architecture for SAP S/4HANA comprises only one archetype and also supports for all transactional, analytical and search in SAP Fiori apps.
Technology components of SAP Fiori:-
ABAP Infrastructure Components:-
CDS Views (ABAP managed)
*Apps assignment via role-specific business catalogs.
*Predefined groups for FLP home page.
*Add / remove apps from home page.
*(Re)arrange tiles and groups.
*Select custom themes.
* Across apps and business objects
*fast, easy and contextual navigation
* Adaptive design to run on multiple devices
* Configuration allows to start device specific apps
* via UI theme designer
SAP Fiori launchpad being a runtime container supports intent based navigation for SAPUI5 Components, Web Dynpro ABAP or SAP GUI apps, and External URLs. Fiori launchpad provides platform independent service APIs with adapters for different front-end servers (ABAP, SAP Enterprise Portal, SAP HANA Cloud Platform) and local consumption (Sandbox for testing in SAP Web IDE, mobile offline).