In this blog post, we would look SAP Fiori System configuration and Installation. This blog post contains the configuration and installation of SAP Fiori. All these activities are supposed to be performed by the SAP Basis Team or the SAP Fiori Admin (usually a Basis person). it is always good to know the below steps to have a quick bird’s eye’s view of the system and tell the management if their SAP Landscape is ready for Fiori Installation or not.
System Configuration and Installation:
Necessary system landscape
|SAP ERP 6.0 SP15 or Higher|
|SAP Enhancement package 2 of SAP ERP 6.0 SPS 06 or higher|
|SAP Enhancement package 3 of SAP ERP 6.0 SPS 05 or higher|
|SAP Enhancement package 4 of SAP ERP 6.0 SPS 05 or higher|
|SAP Enhancement package 5 of SAP ERP 6.0 SPS 03 or higher|
|SAP Enhancement package 6 of SAP ERP 6.0 SPS 02 or higher|
|SAP Enhancement package 7 of SAP ERP 6.0 SPS 01 or higher|
|SAP Enhancement package 8 of SAP ERP 6.0 SPS 01 or higher|
- Components on ABAP Back-end server
IW_BEP (Latest available version )
IW_PGW ( (Latest available version )
- Components on ABAP Front-End Server
|If front-end server SAP Netweaver 7.4 or higher the below listed components are automatically installed with your SAP Netweaver installation.||If front-end server SAP Netweaver 7.31 the below listed components will have installed separately from SAP Netweaver installation.|
|SAP Gateway||The component for SAP Gateway Foundation is included in the SAP Netweaver 7.4 or Higher installation||SAP NetWeaver Gateway 2.0 SPS 10|
|Central UI components||The Component for SAP UI is included in the SAP Netweaver 7.4 or Higher Installation.||UI add-on 1.0 for SAP enhancement package 3 for NetWeaver 7.0, minimum SPS 12 or SAP EHP1 for SAP Netweaver 7.3|
|Components to be Installed||SAP_UI (will be default with NW 7.4) IW_PGW (Latest available version )||SAP_UI (will be available with UI add on) IW_PGW (Latest available version )|
- SSO:-SSO is must for SAP Fiori implementation. SAP recommends Central Hub deployment for ABAP front-end and back-end servers, webdispatcher for mobile security.
Installation Tool :-
SAP recommends that you use Software update manager in combination with maintenance optimizer to install the components.
Add-Ons: If your system is lower than SAP Netweaver 7.4, you need to have at least these three Add-ons: IW_BEP, GW_CORE and IW_FND.
For SAP Netweaver 7.4 and higher, the above three components GW_CORE, IW_FND and IW_BEP are replaced by a new software component for the SAP Netweaver Gateway foundation, SAP_GWFND. These three components are included by default in the SAP Netweaver installation. We do not need to check the Add-On as the software component SAP_GWFND is deployed as part of SAP Basis.
Profile Parameters: In t-code RZ11, check the below two profile parameters are maintained correctly.
login/accept_sso2_ticket = 1
login/create_sso2_ticket = 2
Configuration steps we can be done using task lists but in this blog post we will learn about manual process also.
T-Code STC01 >> SAP_GATEWAY_BASIC_CONFIG>>Execute
task list generated as below and then execute and complete all the tasks.
same follow for below mentioned task lists:-
T-Code STC01 >> SAP_GATEWAY_ADD_SYSTEM>> Execute
T-Code STC01 >> SAP_GATEWAY_ADD_SYSTEM_ALIAS>> Execute
T-Code STC01 >> SAP_FIORI_LAU NCHPAD_INIT_SETUP>> Execute
For more information on SAP Fiori configuration using Task Lists :
Activation of SAP Netweaver Gateway:
T – Code SPRO > SAP Netweaver > Gateway > OData Channel> Configuration > Connection Settings > Activate or Deactivate SAP Netweaver Gateway
Here we have to choose “Activate” on the pop up confirmation window.
Creation of Trusted RFC between Backend system and Gateway:
Front-end App would often need to connect to the back-end to fetch data or even start SAP GUI Transactions or Web Dynpro Transactions from the App. In order to allow the user to seamlessly perform the activity, we need to set up an RFC connection between the frontend (Launchpad) and the back end server.
In the case of Central Hub Deployment (different front-end and back-end system), create an RFC destination to the other system and make it trusting.
If we have a combined front-end and back-end system setup (Embedded Deployment), then only create one RFC connection to itself.
In the case of Central Hub Deployment, do not forget to provide the end users same role in both front-end and back-end.
Creation of the SAP System Alias for Applications:
SAP System Alias is the logical name for the system connection. It adds an additional layer to the RFC destination to allow for the decoupling of SAP Gateway service and the RFC Destination.
Depending on whether you have embedded system or Hub with development in backend or Hub with development in the front-end, your system alias setting would change.
T-Code – SPRO > SAP Netw eaver > Gateway > OData Channel > Configuration > Connection Settings > SAP Netweaver Gateway to SAP System > Manage SAP System Aliases
You can also go to t-code SM30 and maintain view /IWFND/V_DFSYAL (Manage SAP System Aliases). Please note, we need to maintain the alias in the front-end systems if you have Central Hub Deployment.
Aliases in Central Hub Deployment with development in backend (Front-end GW + Back-end separate)
SAP recommends maintaining two System Aliases. One for normal back-end applications and another for backend workflow apps.
Aliases in Embedded System (Front-end + Back-end together)
LOCAL system points to itself.
Activate OData and ICF Services
The following services needs to be added with system alias using t-code /IWFND/MAINT_SERVICES on the front-end server.
Note – Do not activate the /UI2/LAUNCHPAD service. This service is not relevant for SAP Fiori.
Go to t-code /IWFND/MAINT_SERVICE or go to SPRO, SAP NetWeaver > Gateway > OData Channel > Administration > General Settings > Activate and Maintain Services
Add the service
Do not forget to assign it to the package. Hit the green tick button and save the added service and Repeat the same steps for all the listed services.
Finally, navigate to SICF and check that the services are active under the branch sap/opu/odata/ui2. If not, activate them manually by right-clicking and hitting Activate or select the service and go to Menu >Service/Host >Activate.
Call each service once by selecting it in transaction Activate and maintain services (/IWFND/MAINT_SERVICE), then choosing Call Browser in the screen area ICF Nodes. Select the OData node, not the SDATA node.
You have called a service successfully when an XML document is displayed without any error messages.
FYI: Gateway errors can be show via transaction /IWFND/ERROR_LOG
Activate SICF Services for SAP Fiori Launchpad
In addition to the ICF services that correspond to the OData services you have to activate the following ICF services manually.
- /default host/sap/bc/ui2/nwbc/
Run transaction Maintain Services (SICF) on the front-end server.
In the menu under Service/host Activate, activate the services under the following subtrees.
In the Activation of ICF Services dialog box, choose Yes with the hierarchy icon to activate all child nodes under a service.
Of all the services above, the below two are to Activate HTTP Services for UI5
Assign Administrator Role for SAP Fiori Launchpad to Administrator User:
You have created an administrator user who needs extensive authorizations, such as S_SERVICE, S_DEVELOP, /UI2/CHIP, S_RFC_ACL, and S_CTS_SADM. If applicable, create the user with the ID the user already has in the back end.
You copy the administrator role for the SAP Fiori launchpad delivered by SAP and assign it to your administrator user. The administrator is then authorized to use the SAP Fiori launchpad designer.
Run transaction Role Maintenance (PFCG) to copy the role SAP_UI2_ADMIN to your customer namespace.
On the Menu tab, open the menu of the pushbutton for adding objects (+ button). Select the object type Authorization Default.
Choose TADIR Service from the menu for the Authorization Default. Specify the following values:
Program ID: R3TR
Object Type: IWSG
In the table, enter the names of your activated services in the form <technical name>_<four-digit version number with leading zeros>, for example ZINTEROP_0001 and ZPAGE_BUILDER_CONF_0001. For the list of the activated services.
On the Authorizations tab, choose Propose Profile Name next to the Profile Name field.
Choose Change Authorization Data and then Generate.
You have generated a role with five IWSG authorizations and five IWSV authorizations. The IWSV authorizations are included in the role delivered by SAP, so they are not in your customer namespace.
Assign the new role to your administrator user.
if you do not want to save the Fiori Launchpad link to your already crowded browser favorite list, then add the below t-code in your SAP favorite. This will also take you to the Fiori Launchpad. No need to remember the long URLs.
The transaction code for SAP Fiori Launchpad is /UI2/FLP. It would take you to the log in page of Fiori.
Please follow each steps carefully and kindly follow Fiori installation and configuration guide.
For more information on SAP Fiori