Fiori Configuration Process
Fiori Application Types
1. SAP GUI Apps – These are the T-code based apps and require t-code access on the backend.
2. Transactional (SAP UI5) – These are native Fiori apps and require access to O-data services on
the backend.
3. Analytical/Design-studio – These are basically reports and require access to either O-data or
BEX query on the backend. For analytical apps which have design studio as their application
type, we require to provide access to BW reports/CDS views on the backend.
4. Web-Dynpro Apps – These are Web Dynpro type apps which require Web Dynpro Application
access on the backend.
Fiori Launchpad uses the nwbc service to launch the Web Dynpro applications. Which means
although the Web Dynpro application is working fine on your backend server, if you want to
integrate it to Fiori Launchpad you need to activate the following ICF node: /sap/bc/ui2/nwbc
5. FactSheet Apps -- Fact Sheet apps are not tile based apps rather Fiori search based. Fact Sheets
are called by search results from Fiori Launchpad. As a pre-requisite, Enterprise Search need to
be activated in backend system and search requests from Fiori Launchpad hits the backend
system directly
Teams Involved
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.
**Note :- 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.
ii. Login to the Fiori Launchpad Designer
➢ Before starting the configuration, select the Transport Request to capture the required changes.
Go to the Settings icon on the top right corner of the screen and choose the suitable TR.
➢ Create one Z-catalog and Z-group as per the requirement. Click on Save.
➢ Start configuring the tiles into the Z catalog. Now, let’s say if we want to configure the “Foreign
Exchange Overview”, we first get the following details from the Fiori apps Library.
1. SAP Business Catalog
2. SICF Node
3. O-data Service/T-code/WDA/BEX Query depending on the App Type.
4. Target Mapping
For the app Foreign Exchange Overview, Business catalog is SAP_TRM_BC_FXR_OVP.
Search for the Business catalog in the Launchpad Designer. From this catalog, we need to reference
the tile to our Z catalog.
➢ Drag the tile to the top and add it to the Create Reference tab.
➢ Select the catalog into which you want to add the tile i.e the Z Catalog
➢ Now go to the Target Mapping option next to tiles option. Select the target mapping for the tile
“Foreign Exchange Overview” and again Create Reference for the same.
Next, add the tile from this catalog into your group. Go to the Groups section.
➢ Click on Add Tile
➢ Select the catalog.
➢ Activate your tile.
Now the Z-catalog and Z-group is ready and we can provide access to the users via roles.
Fiori Role Creation
Front-end Role :
On the Front-end Fiori Role, add the catalog ID and Group ID from the Menu Tab.
➢ Click on Save.
➢ Assign this Front-end role to the user alongwith the Default role.
Back-end Configuration :
Create one role on the backend (s4 system) and add the following depending on the fiori application
type.
Case 1 : Application Type : SAP GUI Based App
Case 2 : Application Type : Web Dynpro Application
Case 3 : Application Type : Transactional Apps
Case 4 : Application Type : Analytical Apps (Design Studio Apps with BEX Queries)
Case 5 : Application Type : Factsheets
Case 1 : Application Type : SAP GUI Based App
Create a PFCG role and add the transaction code in the Menu tab. Maintain the authorization data.
Case 2 : Application Type : Web Dynpro Application(add the webdynpro application)
Go to Menu -> Authorization Default -> Web Dynpro Application
Case 3 : Application Type : Transactional Apps (add the O-data services)
Go to Menu -> Authorization Default -> TADIR Service -> Obj type - IWSV
Case 4 : Application Type : Analytical Apps (Design Studio Apps with BEX Queries)
Menu -> Report ID (Enter the report name). Maintain the values for S_RS_COMP, S_RS_COMP1 and
S_RS_AUTH in the Authorization tab.
Case 5 : Application Type : Factsheets
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 same user id, both on the Front end and Back end server and assign Front end role on the Front
system and backend role on the Backend system to the user alongwith the Default role.
