Now that the Fiori apps are included within the SAP software, I wanted to know (as a SAP technical basis consultant) what the steps and the effort would be to get one app up-and-running.
Although there is a lot of Fiori documentation available, I had trouble to get an overview of the technical steps to get one Fiori app working.
I realize that the below steps only apply to the system I installed (with the specific release and patch level) and the app I choose (because each app has specific after care), but it will gave me an idea what technical steps are needed and where I found the documentation and software.
The app I configured was: MyContacts.
As I said, this is for me only a way to get hands-on experience with Fiori.
To keep the costs low I choose a system setup with 1 combined frontend and backend system.
So just to be clear: normally you choose a system setup with a separate frontend server (with Gateway) and backend system (with SAP ERP for example).
I have installed SAP ECC 6.0 Ehp7 and I used the integrated Gateway which comes already out of the box when you install this system.
Just for your information I installed this SAP ECC system on AWS on a m3.large server.
The installation came automatically with the following patch level:
And the installation of SAP ECC 6.0 Ehp7 came with kernel version 741
Patches and add-ons
To get the basis of the system up-to-date I installed the following patches via SPAM:
- SAP_GWFND patch 6
- SAP_UI patch 7 and 8
And I installed the FIORI ERP APPLICATIONS X2 1.0 as add-ons via transaction SAINT.
The software you can download from http://service.sap.com/support > Software download > Installation and upgrades > A-Z index > F > SAP Fiori > SAP Fiori for Suite > FIORI ERP APPLICATIONS X2
When you go there you will see 5 downloadable objects:
But out of these 5, I only had to install the 2 UI add-ons via SAINT.
The 3 GBX are not needed as they are already in the system (included in the EA-APPL).
When you try to install these GBX you get the message:
So now we have the basic installation and patching done
The patch level in SPAM looks like:
We can start with the configuration part.
Activate the following services (under default_host>sap) via transaction SICF:
opu > utils > initial_logon
opu > odata > ui2
public > bc > ui5_ui5
public > bc > ui2
public > opu > resources
bc > ui2 > start_up
bc > ui5_ui5 > ui2 > launchpage
bc > ui5_ui5 > ui2 > tilechips
bc > ui5_ui5 > ui2 > ushell
bc > ui5_ui5 > sap > arsrvc_lpd_c
bc > ui5_ui5 > sap > arsrvc_sm
bc > ui5_ui5 > sap > arsrvc_spb_admn
bc > ui5_ui5 > sap > arsrvc_suite_pb
bc > ui5_ui5 > sap > arsrvc_upb_admn
bc > ui5_ui5 > sap > ar_srvc_launch
bc > ui5_ui5 > sap > ar_srvc_news
Create a trusted RFC between Gateway and Backend system.
As I said, to keep the costs low I have a combined frontend and backend system setup.
So I only created in transaction SM59 an RFC connection to itself.
It should have the nameconvention: <SID>CLNT<CLIENT>.
And in the Logon & Security tab it should use the current user.
In case you use a separate frontend and backend system, you have to create a trusted RFC connection.
So on each system create an RFC destination to the other system and make it trusting via transaction SMT1.
Creating the SAP System Alias for Applications
SAP Transaction SPRO > SAP NetWeaver > Gateway > Odata Channel > Configuration > Connection Settings > SAP NetWeaver Gateway to SAP System > Manage SAP System Aliases
Here we have to create a new entry.
I created the entry with the name ERP. Use the RFC destination that was created in the previous step.
Activation of SAP NetWeaver Gateway
SAP Transaction SPRO > SAP NetWeaver > Gateway > Odata Channel > Configuration > Connection Settings > Activate or Deactivate SAP NetWeaver Gateway
Here we have to choose “Activate”.
Add Gateway and UI5 Services
SAP transaction /IWFND/MAINT_SERVICE
Choose Add Service.
Maintain local in System Alias field and choose Enter.
A list of services now appear who are not yet activated:
Now we select the services that need to be activated.
In this case we will do: LAUNCHPAD
Enter the Package the object shall be assigned to. In case the objects are not transported select Local Object (this is what I did).
Confirm the information message that the metadata was loaded successfully.
Perform the same steps that you just did for LAUNCHPAD, but now for:
Configuration Fiori app specific
The app I configured was MyContact.
The configuration for the specific configuration can be found in the SAP Help.
First I activated the related service in transaction SICF.
I searched for *mycontact* and activated it:
Second I activated the specific app with transaction /IWFND/MAINT_SERVICE
We see that MyContact has no system alias assigned yet:
Add a system alias.
Only fill in the Service Doc Identifier: in this case search for “SD_MYCONTACTS”
And use the created alias “ERP” (which is an RFC to this system itself, because the Gateway and backend system are one and the same)
We can already test this service to see of we get an error by clicking on the “Call Browser”-button in the left corner window.
I got the message “This XML file does not appear to have any style information associated with it. The document tree is shown below.”
So no error is shown.
FYI: Gateway errors can be show via transaction /IWFND/ERROR_LOG
I created a user TESTFIORI.
End users must have authorization object S_RFCACL assigned to them before they can use a trusted connection.
In transaction PFCG I filled in the following roles:
For both roles I did the following:
- Go into change mode (we need the “Authorizations”-tab and “Users”-tab to be green)
- Goto “Authorizations”-tab and Change autorisation data. Save and Generate the authorizations (normally a functional authorization colleague will perform this action for you)
- Goto “Users”-tab and add your TESTFIORI user to the list of users. After this perform a User Comparison > Complete comparison
Both tabs should be green now.
We also need to add some basic Fiori authorizations.
I decided to add them to the SAP_SD_MYCONT_APP as this user already has this role (not so nice maybe, but this is just used as a demo).
So on in transaction PFCG authorization tab of SAP_SD_MYCONT_APP go to Change Authorization Data under the Maintain Authorization Data and Generate Profiles section.
Select Edit > “Insert authorization(s) > From template…”
I choose the following two (one by one):
After this again Save and Generate.
First I want in the Launchpad designer to create a specific group for this app.
Start the Fiori Launchpad Designer via:
First time we start we see not much:
Create a new catalog by clicking on the + sign in the left corner.
And create also a new Group by going to the Group tab and click on the + sign.
Now add an app in this newly created group:
Click on the + sign and add MyContacts:
Now we have to go back to SAP transaction PFCG and add this newly created group to the user TESTFIORI.
We edit the role SAP_SD_MYCONT_APP which this user TESTFIORI already has.
Goto “Menu”-tab and in the button-bar change the “Transaction”-button so that it becomes the “Group”-button.
Choose the group we created in the Designer:
Now start the Fiori Launchpad
and logon with the newly created user.
There are more apps shown but this is because they came along also with the patches I installed.
When I click on the MyContacts app:
There is no data in the system as I newly installed it, but for me this was what I wanted to see: an app in the Fiori Launchpad 🙂 .
And it also works form my smart phone:
During the installation and configuration I ran into a number of issues.
They can be prevented when you perform the steps in the above order.
To prevent some basic mistakes, remember that there is a need for:
- Patching Gateway and SAP_UI
- General configuration & authorization for basic Fiori
- App specific configuration & authorization
- Opening the ICM server port of the SAP system in firewall (if you want to access it via public Internet via your mobile device)
- SU53 to see what autorization you miss
- /IWFND/ERROR_LOG to see the application logs
- dev_icm to see the errors in the ICM trace
Summary of the effort
My technical effort was:
- Setup AWS system + download software = 1 day
- Installation ECC system + patching = 2 days
- Configuration general + Fiori app specific = 2 day
- Testing and documentation = 1 day
Of course this was just a simple test with a combined frontend / backend system and only one app.
But also with this limited setup for myself I got a feeling for the steps that a technical basis consultant needs to perform.
It is also possible to deploy a complete preconfigured Fiori solution on AWS via the CAL (Cloud Appliance Library).
The steps for this are described in my next blog.
-  Create Semantic Object in SAP Fiori Server (Front-end) server.
-  Create Launchpad Role in SAP Fiori Server (Front-end) server.
-  Create Business Catalog.
-  Create Business Group.
-  Create App's PFCG Role in SAP Fiori Server (Front-end) server.
To display SAP CoPilot in the SAP Fiori Launchpad, the following configuration steps are required: Create a catalog to assign SAP CoPilot to an SAP Fiori launchpad catalog. SAP Fiori target mapping on the catalog for the SAP CoPilot plugin.
There are three types of apps in SAP Fiori: transactional apps, analytical apps, and factsheet apps.
- Add your app to the Portal site. From the side navigation panel in your Supplier Portal site, click Content Management and select Apps to open the Manage App Configuration editor. ...
- Assign your app to a catalog. Click the Catalogs tab. ...
- Add the app to a group. ...
- Preview your app on the launchpad page.
Introduction: 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
All these activities are supposed to be performed by the SAP Basis Team or the SAP Fiori Admin (usually a Basis person).. SAP ERP 6.0 SP15 or HigherSAP Enhancement package 2 of SAP ERP 6.0 SPS 06 or higherSAP Enhancement package 3 of SAP ERP 6.0 SPS 05 or higherSAP Enhancement package 4 of SAP ERP 6.0 SPS 05 or higherSAP Enhancement package 5 of SAP ERP 6.0 SPS 03 or higherSAP Enhancement package 6 of SAP ERP 6.0 SPS 02 or higherSAP Enhancement package 7 of SAP ERP 6.0 SPS 01 or higherSAP Enhancement package 8 of SAP ERP 6.0 SPS 01 or higher Components on ABAP Back-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 installationSAP 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.. 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 .. T – Code SPRO > SAP Netweaver > Gateway > OData Channel> Configuration > Connection Settings > Activate or Deactivate SAP Netweaver Gateway. T-Code – SPRO > SAP Netw eaver > Gateway > OData Channel > Configuration > Connection Settings > SAP Netweaver Gateway to SAP System > Manage SAP System Aliases. 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. 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 .. 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.. In the Activation of ICF Services dialog box, choose Yes with the hierarchy icon to activate all child nodes under a service.. Assign Administrator Role for SAP Fiori Launchpad to Administrator User:. You copy the administrator role for the SAP Fiori launchpad delivered by SAP and assign it to your administrator user.
Overview Once SAP UI5 app has been deployed in SAP Fiori (Front-End) server, we need to do some configurations for accessibility of this app in SAP Fiori Launchpad. SAP Fiori launchpad is a shell that hosts
Once SAP UI5 app has been deployed in SAP Fiori (Front-End) server, we need to do some configurations for accessibility of this app in SAP Fiori Launchpad.. In this blog, we will com to know about steps to configure any custom UI5 for SAP Fiori launchpad access.. SAP Fiori Server (Front-end) SAP Fiori Launchpad Url: http://
Info This guide will focus on the installation of a ‘Create Sales Orders’ Transactional Fiori App in an ABAP environment on ERP 6.0 EHP 7 running embedded Gateway using transaction SAINT. There are
This guide will focus on the installation of a ‘Create Sales Orders’ Transactional Fiori App in an ABAP environment on ERP 6.0 EHP 7 running embedded Gateway using transaction SAINT.. It describes the app features, installation information, configuration as well as extension points which tell you what features of the standard app can be enhanced.. If the above says ‘HANA’ then we either need SAP Business Suite on HANA or S/4 Hana in order to install and run the app.. From the FIORI catalogue identify the front ends components to be installed (Implementation Information/Installation/Front-End Components):. Identify name of the app from the Fiori apps library (Implementation Information/Configuration/SAPUI5 Application). From the FIORI apps catalogue identify the front ends components to be installed (Implementation Information/Installation/Back-End Components):. Identify the name of the OData Service from the Fiori apps catalogue (Implementation Information/Configuration/OData Services). Run transaction /IWFND/MAINT_SERVICE and click ‘Add Service’:. Select the displayed Backend Service and click on ‘Add Selected Services’:. SAP provides you with role templates once you install the relevant app components.. a) Create PFCG role with Launchpad Start Authorization Copy role SAP_UI2_USER_700 under the Z namespace e.g. Z_UI_USER. Go to tab ‘Authorizations’ click on ‘Change Authorization Data’. Assign the authorization role to the user in the ‘User’ tab and click on ‘User Comparison’. Find the business role template in the FIORI apps library documentation for our SD app.. The natural environment as an entry point for FIORI apps is the FIORI Launchpad which is a container for all your FIORI apps and it should be used in the production environment.
As a first step of SAP Fiori installation, let me guide you on how to install both frontend and backend components. SAP Fiori Configuration
Easy and simple approach for SAP Fiori installation and configuration using SAP Maintenance Planner Tool Learn through simple steps on how to download and upload components to server with SAP Marketplace Understand tools and techniques on how to configure SAP Fiori Launchpad Learn how to integrate SAP Gateway and SAP Business Suite. The next step in SAP Fiori installation is backend component installations, this mainly comprises of SAP Business Suite Products and SAP NetWeaver Components SAP Business Suite Products: SAP Fiori Products are installed on the backend server as add-ons to specific SAP Business Suite Products SAP NetWeaver Components: SAP NetWeaver Components relatively differ based on the database you use. 1.. Below are the detailed out steps for “SAP Fiori Configuration Guide”. Activate SAP Fiori Launchpad and SAP Fiori Launchpad Designer Services. For end users to access SAP Fiori, you will need to activate some of the OData services to configure the SAP Fiori Launchpad.. Activation StepsStep 1: Go to transaction /IWFND/MAINT_SERVICE in the SAP GUI Step 2: Click on “Add Service” button and select “Local” for the system alias (In case of Embedded Deployment) Step 3: Enter “page_builder*” for the “External Service Name” field Step 4: Click on “Get Services” and select all the services, i.e., ui2/page_builder_conf,/ui2/page_builder_cust,/ui2/page_builder_pers Step 5: Click on “Add Selected Services”, you will now see that these services being activated Step 6: Repeat steps 1-4 to activate the remaining two services. This will display all the activated services on your customer namespace (Refer Screenshot below) Activate Internet Communication Framework Services As a next step to SAP Fiori Configuration Guide, you will need to activate some of the ICF nodes onto your SAP Fiori Launchpad, steps of which are given below for your understanding Step 1: Run the transaction SICF Step 2: In the service path field, enter “/sap/bc/ui5_ui5/sap and click on the execute button Step 3: Right click on the service and click on “Activate Services” for the below mentioned services /default_host/sap/bc/ui5_ui5/sap/ar_srvc_launch /default_host/sap/bc/ui5_ui5/sap/ar_srvc_news /default_host/sap/bc/ui5_ui5/sap/arsrvc_upb_admn /default_host/sap/bc/ui5_ui5/ui2/ushell /default_host/sap/bc/ui2/nwbc /default_host/sap/bc/ui2/start_up /default_host/sap/public/bc/icf/logoff` /default_host/sap/public/bc/ui2 /default_host/sap/public/bc/ui5_ui5 Step 4: Click “Yes” with the hierarchy to activate all the child nodes. ZINTEROP_0001. ZPAGE_BUILDER_PERS_0001 Configure the SAP Fiori Launchpad Login screenStep 1: Run transaction SICF Step 2: In the “Service path” field, enter “/sap/bc/ui5_ui5/ui2/ushell” and click on “Execute” icon Step 3: Double-click the “ushell” service and click on “Error pages” tab Step 4: Select the “System Logon” radio button and click “Configuration” Step 5: Choose “Custom Implementation” radio button and enter “/UI2/CL_SRA_LOGIN” in the ABAP class. field Step 6: Click “Confirm” icon and Click on “Save” button on the Create/Change a service screen Step 7: Repeat the same steps for “/sap/bc/ui5_ui5/sap/arsrvc_upb_admn” to configure the logon for. Launchpad designer tool Step 8: Login to your Launchpad and Launchpad designer tool to check if it’s working Activate and integrate SAP Gateway and SAP Business Suite As the last step in the SAP Fiori Configuration Guide, you will need to activate SAP Gateway to provide a connection between SAP Front end and Back end.. This integration is done to set up the trusted remote function call (RFC) Step 1: Run transaction SM59 Step 2: Click on “Create” icon Step 3: Input the following details. RFC Destination: Enter RFC destination name. Connection Type: “3”. Description 1: “SAP ERP”. Load Balancing: “NO”. Target Host: Enter the SAP Business Suite server name. Instance Number: “00” Step 4: Click on “Logon and Security” tab. Language: “EN”. Client: “120”. User: “Select the current user checkbox”. Trust Relationship: “Yes” Step 5: Repeat the same steps on your ABAP Backend server with the target host as your ABAP Frontend server. After setting the RFC Destination, you will need to run the “Creating Trusting Relationships wizard” (refer screenshots below).
InfoThis guide will focus on the installation of a ‘Create Sales Orders’ Transactional Fiori App in an ABAP environment on ERP 6.0 EHP 7 running embedded Gateway using transaction SAINT. There are also other ways to install the apps with SAP Maintena
Run transaction /IWFND/MAINT_SERVICE and click ‘Add Service’:. Assign a package (I am using a local object for test purposes – in real scenario create a package). SAP provides you with role templates once you install the relevant app components.. c) Create PFCG role to access oData services. To get the Component name run the following link: https:// :/sap/bc/ui5_ui5/sap/sd_so_cre/Component.js