saptutorials in Blog

Mastering Fiori Configuration: A Comprehensive Guide

Table of Contents

Toggle

Understanding Fiori Application Types and Configuration Process

Fiori SAP’s user interface and design language have revolutionized how users engage with its applications. To fully unlock its power, it is crucial to understand the setup process as well as all types of Fiori applications available to users. This article introduces users to different kinds of SAP Fiori apps along with how they are set up as well as which teams are responsible for making sure a smooth implementation experience is provided by SAP Fiori applications. SAP Fiori encompasses various application types, each with specific backend requirements and functionalities:

Fiori Configuration Process

applications are categorized into different types, each with specific backend requirements. Below is an overview of these Fiori application types and their configuration processes:

SAP GUI Apps are T-code-based applications that require transaction code access on the backend. These applications are traditional SAP GUI transactions adapted for use within the environment. To configure SAP GUI Apps, ensure that users have the appropriate T-code access in the backend system.

SAP GUI Apps

They are T-code applications that require access to T-codes on the system behind, typically traditional SAP GUI applications migrated into the environment. Their easy interface is tailored for longtime SAP users, while they integrate seamlessly with Fiori Launchpad.

(SAP UI5) Transactional applications built with SAP UI5 are native applications that are designed to perform CRUD (Create, Read, Update, and Delete) operations. They typically need access to OData services at the backend to access and alter data. The process of setting up transactional apps includes:

Transactional (SAP UI5)

These native applications rely on OData services at the backend to access transaction data. They are built with the SAP UI5 framework for responsive and user-friendly interactions across different devices.

Implementing OData services in the system behind
Ensuring that users have the proper authorization to use these services.
Configuring Launchpad to display app tiles

Analytical/Design Studio Apps

Apps that analyze data utilize reports with access to OData, as well as BEX queries in the backend. They use Design Studio to define their type of access through BW or CDS views and designate reports from these views as essential for real-time analysis and informed decision-making based on extensive analysis.

Analytical apps deliver insights by utilizing reports and data visualizations. They can utilize OData services or BEx queries from SAP’s Business Warehouse (BW) system. For applications analyzing the design studio, accessing BW data or Core Data Services views may also be required.

The configuration steps for analytical/design studio apps include:

Activating OData or BEx services is required for the app.
Configuring the necessary BW reports or CDS views.
Ensuring integration with the Fiori Launchpad for seamless access.

Web Dynpro Apps

Web Dynpro apps are applications developed using SAP’s Web Dynpro framework that require access to other Web Dynpro applications running in the background. For Web Dynpro apps to function with Fiori Launchpad, it is necessary to activate ICF (Internet Communication Framework). In particular,, the node at /sap/bc/ui2/nwbc must be active.

Follow these steps to configure the Web Dynpro applications properly:

Ensuring the Web Dynpro application is active and functioning on the backend server.
Activating the ICF node mentioned above.
Integrating the Web Dynpro application with the Fiori Launchpad.

Fact Sheet Apps

Fact Sheet apps are search-based Fiori applications accessible via results via Fiori Launchpad. Enterprise Search activation in the backend system is essential to these apps; searches from Fiori Launchpad can directly access information in backend systems and vice versa. Furthermore, these applications provide detailed insight into business processes and objects to assist users find what they need more easily.

Teams Involved in Fiori Configuration

Several teams play a crucial role in the configuration of native Fiori apps:
The Basis team is responsible for activating essential services required for Fiori app configuration. These services include OData services and SICF (SAP Internet Communication Framework). The Communication Framework nodes must be properly activated; otherwise, apps cannot function correctly.

Basis – For any native fiori app configuration, we require activation of certain services which is done by Basis team. These services include O-data services and the SICF nodes.
Security/Development – Once the activation of these services is accomplished, Security/Development team can start the configuration of the tiles.
Native Fiori apps will not work without the activation of these services.
Important T-codes
/n/ui2/flpd_cust – to invoke Fiori Launchpad Designer (for configuration of Fiori tiles)
/n/ui2/flp – to invoke Fiori Launhpad (for end user access)
/n/iwfnd/maint_service – To activate/maintain the O-data services
Front-End Configuration
Tile Creation Process
The front configuration process is the same for any Fiori app. Front end configuration in done in the Fiori Launchpad Designer. Fiori Launchpad Designer is invoked from the Gateway Fiori client.
i Login to FID-100 System. Execute the T-code /n/ui2/flpd_cust to invoke the Fiori Launchpad Designer.

Back-end Configuration :

Create one role on the backend (s4 system) and add the following depending on the fiori application type.

Application Type: SAP GUI-Based App
Application Type: Web Dynpro Application
Application Type: Transactional Apps
Application Type: Analytical Apps (Design Studio Apps with BEX Queries)
Application Type: Factsheets
Application Type: SAP GUI-Based App

Create a PFCG role and add the transaction code in the Menu tab. Maintain the authorization data.

Application Type : Web Dynpro Application (add the Web Dynpro application and go to Menu -> Authorization Default -> Web Dynpro Application)
Application Type: Transactional Apps (add the O-data services). Go to Menu -> Authorization Default -> TADIR Service -> Obj type – IWS Application Type: Analytical Apps (Design Studio Apps with BEX Queries)
Navigate to Menu and select Report ID, then enter the report name. Maintain the values for S_RS_COMP, S_RS_COMP1, and S_RS_AUTH in the Authorization tab.
Application Type: Fact Sheets. To access, go to Menu -> Authorization Default -> TADIR Service -> Maintain the app template in the object S_ESH_CONN in the authorization tab.
User Creation and Role Assignment: Create the same user ID on both the front-end and back-end servers, and assign the front-end role to the front-end system and the back-end role to the back-end system, along with the default role.

Conclusion

The ability to configure Fiori applications is vital to making the most of SAP’s platform for user experiences. Understanding the various kinds of Fiori apps as well as their specific requirements for backends is essential to a practical implementation. ByBy following the steps for configuration described in this guide and optimizing the content to be SEO-friendly, you can ensure that the Fiori configuration information is shared and accessible to a wider audience

You might also find the following articles interesting.

saptutorials: We are a group of SAP Consultants who want to teach and make studying tough SAP topics easier by providing comprehensive and easy-to-understand learning resources.