Fiori Standard Apps Configuration v1.1

Fiori Apps configuration

Version 1.1 7th Sep, 2016

Fiori Apps Configurations

Revision History: Date

Name

Version Comments

25-Aug-2016

Arunkumar Dharmalingam

1.0

7-Sep-2016

Arunkumar Dharmalingam

1.1

Additions: Section 4.2.3: Testing of BEx Queries in Backend. Section 4.2.4: Additional note implementation for Web dynpro apps. Section 4.5.1: DCL Roles activation for CDS Section 4.5.2: 0Analysis activation Section 6.4: Customization of Launchpad URL

Copyright © 2016 Accenture. All rights reserved.

2


Table of Contents 1. Introduction: ............................................................................................................................................ 4 1.1. System Landscape: ................................................................................................................................. 4 2. Prerequisites: ........................................................................................................................................... 4 3. Fiori/Gateway General Setup: ................................................................................................................. 5 3.1. Task Lists: ............................................................................................................................................... 5 3.2. Create System alias for Local app: ....................................................................................................... 16 4. App specific Configuration:.................................................................................................................... 17 4.1. Transactional Apps: .............................................................................................................................. 17 4.2. Web Dynpro Apps: ............................................................................................................................... 23 4.2.1. HTTP(s) connection to backend: ....................................................................................................... 23 4.2.2. Generic ICF services activation: ........................................................................................................ 28 4.2.3. BI Content Activation: ....................................................................................................................... 31 4.2.4. Web Dynpro App specific activation: ................................................................................................ 46 4.3. Fact Sheet Apps:................................................................................................................................... 48 4.3.1. Web Dispatcher Configuration: ........................................................................................................ 48 4.3.2. Enterprise Search Activation:............................................................................................................ 48 4.3.3. Fact Sheet specific app activation:.................................................................................................... 65 4.4. Additional tasks:................................................................................................................................... 69 4.4.1. DCL role activation for CDS objects: ................................................................................................. 69 4.4.2. 0ANALYSIS Configuration: ................................................................................................................. 71 4.4.3. External Alias for Logoff in backend: ................................................................................................ 83 5. Security: ................................................................................................................................................. 86 5.1. Cross-Application Roles: ...................................................................................................................... 86 5.2. App specific Roles: ............................................................................................................................... 89 6. Fiori Launchpad Customizations (Optional): ......................................................................................... 91 6.1. Custom Catalog and Groups: ............................................................................................................... 91 6.2. Theme Designer: ................................................................................................................................ 100 6.3. Login/Logout Page Customizations:................................................................................................... 106 6.4. Launchpad URL customization: .......................................................................................................... 110 7. Troubleshooting:.................................................................................................................................. 113 Appendix: Reference Links ........................................................................................................................ 115


3


1.

Introduction: This document explains about configuration of Fiori standard applications. There are different types of apps delivered by SAP. Different set of apps required different software components in frontend system and backend system and configurations. Fiori App library lists out all the standard apps delivered by SAP and provided implementation details on which software components required for the apps. 1.1. System Landscape: In this document, configuration steps done with Frontend system (Fiori/Gateway) as Central Hub system which is built on separate Netweaver system 7.5 SP3 with required additional Frontend UI software components and Backend system is S/4HANA 1511 SP1. Web dispatcher will receive all the HTTP(s) requests and direct to Fiori/Gateway system.

2.

Prerequisites:   

Check for all set of software components needs to be installed on Frontend Server depending on the apps that need to be configured. Check for all required Prerequisites notes to be implemented based on the frontend and backend system support pack level. Check for app specific documentation from Fiori App library.


4


3.

Fiori/Gateway General Setup: Initial configurations need to be performed for Frontend Fiori and Backend S/4HANA systems to establish the connection between them. Basic configurations are done through SAP provided Tasks lists. 3.1. Task Lists: SAP has provided certain Task lists to automate basic configurations steps like services activation, SSO, RFC creation etc. Following Tasks lists need to be executed in below sequence.    

SAP_GATEWAY_BASIC_CONFIG SAP_FIORI_LAUNCHPAD_INIT_SETUP SAP_SAP2GATEWAY_TRUSTED_CONFIG (Backend system) SAP_GATEWAY_ADD_SYSTEM

Frontend System Login to Fiori system and go to tcode STC01 Select the Task list SAP_GATEWAY_BASIC_CONFIG and click on

Keep all the tasks checked and click on execute . It can be executed in background as well. Icon shows tasks are automatic.


5


Refresh the screen to check on the status. Once all the tasks are executed, status will turn green. Bottom section displays the logs. Logs of one of the tasks shows that Gateway is active.

Now similarly execute the next task list. SAP_FIORI_LAUNCHPAD_INIT_ SETUP

System will list out all the tasks within the Task list. Click on the button Parameter column to add additional parameters for specific tasks. HTTPS Profile parameter tasks are already skipped by the system. You can run the step if need to configure HTTPs protocol.


6

Fiori Apps Configurations Update the TR description for 1st task Create/Select Customizing Request Task.

Update the frequency of Application Index job. Currently set at every 15 mins in the 9th task.

Select all required tasks and click on Execute. Status will turn green once all the tasks are successful.


7

Fiori Apps Configurations /UI5/APP_INDEX_CALCULATE scheduled to run every 15 mins. Backend System Login to Backend S/4HANA system. Go to Tcode STC01 and open the task list SAP_SAP2GATEWAY_TRUSTED _CONFIG Update the parameter for the first task to provide RFC destination name.

Provide required server and instance no. details for RFC destination from S/4HANA to Fiori system


8

Fiori Apps Configurations Go back to previous screen and execute it. Initially executed in background, so the 2nd task (Add SAP system as trusted System) failed as it cannot be executed in Background. Executed the step again in dialog.

System gives a pop-up to show that it will try to login into Target (Fiori) system.

Enter Fiori system user ID and password


9

Fiori Apps Configurations Then rest of the steps gets executed successfully.

Go to SM59 to check the RFC that got created. Go to STRUSTSSO2 to see that system maintained Fiori system entry in the ACL.


10


There will be an entry for Fiori as rusted system in SMT1 tcode

Frontend System Now login back into Fiori system and go to tcode STC01 Enter Task list SAP_GATEWAY_ADD_SYSTEM


11

Fiori Apps Configurations Open the task list and update the required parameters for CTS, RFC and Gateway Tasks.

Update the TR name for CTS task.


12

Fiori Apps Configurations Update RFC destination details for RFC task. This will be Trusted RFC. Update the right client of Backend system to which Fiori need to be connected. Being it is trusted RFC, user should have same user ID in backend system as well.

Update the System alias name for Gateway Task. This system alias will use the RFC destination to backend system.


13


Icon shows first task is manual task. Task documentation shows that user executing this task list requires SAP_S_RFCACL authorization.

Backend System Login to backend (S/4HANA) system. Go to PFCG tcode and mention role SAP_S_RFCACL. Click on copy under Z role.

and save it

Go to Authorization data and click on Change authorization data. Update the Authorization values. Here all the values are maintained as *. Save and generate the profile. Assign the role to user. Same way created a role in frontend system as well.


14


Frontend System Now login back into the Frontend Fiori system. Open the task list and double click on and mark the task as confirmed.

Now execute the remaining tasks. SSO task will fail with login error if SAP_S_RFCACL role is not assigned to user in the backend system.


15

Fiori Apps Configurations Once executed, all the tasks will turn green.

3.2. Create System alias for Local app: Additional system alias is required for local apps. Front end system Create additional system alias in Frontend system. ‘My Inbox’ app is a local app but connect to backend system with Business Workflow Provider functionality. Go to SPRO SAP NetWeaver SAP Gateway  OData Channel  Configuration  Connection Settings  SAP Gateway to SAP system  Manage SAP System Aliases.


16

Fiori Apps Configurations There is already an entry for FI_S4HANA system alias. Create a similar alias with name FI_S4HANA_L, click on checkbox for local app and software version as /IWPGW/BWF

4.

App specific Configuration: There are different types of Fiori apps available like Transactional, Web dynpro, Fact sheet and Analytical. Based on the app type, configuration steps will differ. 4.1. Transactional Apps: Implementation details for each of the app is available in Fiori App library. Each Transactional app will have an ICF and OData service need to be activated in Front end server. Check of required details in Fiori App library Display G/L Account Line Items Transactional app taken as an example.

Frontend system Login to the Fiori system and go to SICF tcode


17

Fiori Apps Configurations Activate the ICF service. Search for the service mentioned as SAPUI5 application in the app library Activate the service under /default_host/sap/bc/ui5_ui5/ sap SAPUI5: FIN_GLL_ITB


18


Activate the OData service. Go to tcode /IWFND/MAINT_SERVICES Click on


19

Fiori Apps Configurations Search for the OData service under FI_S4HANA system alias Select the service and click on

Mention the package for Transport. OData activation gets captured in a Workbench TR.


20



21

Fiori Apps Configurations Now go back to the tcode /IWFND/MAINT_SERVICES and Check the activated service by clicking on

.

This step need to be performed before testing the apps from Fiori Launchpad.


22

Fiori Apps Configurations Similar step performed for all other transactional apps

OData service for My Inbox App will be available in Local. So it will be searched with LOCAL system Alias. Once activated, LOCAL alias changed to ‘FI_S4HANA_L’ alias which was created earlier for local apps.

4.2. Web Dynpro Apps: Fiori provides webdynpro type apps which can help in connecting backend webdynpro applications and SAP GUI for HTML. There are additional pre-requisite steps involved for web dynpro apps. 4.2.1. HTTP(s) connection to backend: Follow instructions as per note 2269272 in frontend system. Frontend system Implement Note 2271978 in Fiori system through SNOTE.


23

Fiori Apps Configurations Create RFC connections for _RFC and _http RFC destinations in Frontend. Here we will use FI and CO apps, so the systemalias is S4FIN System alias which need to be used can be checked in LPD_CUST tcode

_RFC will be used to extract app catalog from backend system. Any system user used in logon information.


24


_http RFC used for data connection. It is set as trusted system connection. _https can be configured if SSL is configured.


25


Go to tcode /UI2/APPDESC_GET Mention SAP_*_BC_* Uncheck the test mode and click on execute. This tcode uses S4FIN_RFC to connect to the backend system.


26


Implement notes 2279202 2296550 2314599 2313296 These notes were to fix the issue with web dynpro apps not recognizing the HTTP destinations


27

Fiori Apps Configurations Run program /UI2/INVALIDATE_GLOBAL_CA CHES This program need to be executed every time there are some changes to the apps (services activation etc.)

4.2.2. Generic ICF services activation: Apart from the services activated by the task lists, there are additional services need to be activated in both frontend and backend systems. Frontend system &

Same steps need to be performed in both the systems.

Backend system


28

Fiori Apps Configurations Go to tcode SICF and search for the respective services and activate them. /default_host/sap/bc/webdy npro (All services) /default_host/sap/public/b c /default_host/sap/public/m yssocntl /sap/public/icman /default_host/sap/bc/wdvd/ /default_host/sap/public/i cman /default_host/sap/public/i cf_info /default_host/sap/public/i cf_info /default_host/sap/bc/echo /default_host/sap/bc/error /default_host/sap/bc/nwbc /default_host/sap/bc/ui2/n wbc /sap/bc/apc/sap/WEBGUI_SER VICES

Go to tcode SE38 and execute SIAC_PUBLISH_ALL_INTERNAL


29


Go to SE80 and Publish ITS SYSTEM service


30


4.2.3. BI Content Activation: Some of the Web Dynpro apps internally uses BEx queries for which the BI contents need to be activated in the backend S/4HANA system BI content can be activated by following the steps mentioned in the note 1972819 Backend System Login to backend S/4HANA system and client 100 Check the client maintained in table RSADMINA. There will be one entry as BW with the same client 100 If there is no entry as BW, then no action required. But if there is an entry as BW with different client number, then follow steps as mentioned in the note 1972819.


31


Check if logical system entry maintained in the BD54 tcode


32

Fiori Apps Configurations Check logical system is maintained in SCC4 and client is open. Client should allow cross client customizing.

Verify the /BIC/ and /BI0/ as modifiable in SE03. Administration -> Set System Change Option

Update parameter in the DDIC user via SU01. Add parameter RSWAD_SKIP_JAVA = X Activation jobs will run under user DDIC. This parameter required to avoid any Java related errors.

Activate BI technical content. Go to tcode RSA1. First time when it tcode initiated, system will trigger the Activation BI_TCO_ACTIVATION job automatically.


33


Job failed

Check the status in RSTCO_ADMIN tcode If the job finished, it would have been Green. It is in Yellow, Retried the job by clicking on , but again failed.

Error logs can be checked from same tcode RSTCO_ADMIN. Error log shows that some of the classes are not actively available.


34

Fiori Apps Configurations Implement note via SNOTE (2238757 - Error message "Master data read class &1 not actively available" (R7B355) although read class is active) Once Implemented, this note requires manual activity as well to run the program through SE38 RS_UDO_NOTE_2238757 This manual activity is transportable and captured in a TR.


35


Once manual activity completed, mark the note as implemented.

Re-executed the BI_TCO_ACTIVATION job and it is successful


36

Fiori Apps Configurations Check the error logs from RSTCO_ADMIN by specifying the date/time and clicking on


37

Fiori Apps Configurations One of the InfoObjects not activated, so had to manually activate through tcode RSD1. Go to RSD1 and enter the InfoObject name and click on to manually activate it.


38

Fiori Apps Configurations Now the RSTCO_ADMIN status is green.

Verify the required Business functions are active in tcode SFW5. FIN_CO_CCMGMT FIN_CO_CCPLAN Activate the required BI content through tcode BSANLY_BI_ACTIVATION Required BI content can be checked from App implementation and sap help documentations These are 2 BI contents need to be activated. FIN_REP_GL /ERP/SFIN_PLANNING


39

Fiori Apps Configurations Go to tcode BSANLY_BI_ACTIVATION Select Business Category 99. Choose FIN_REP_GL and click on Activate.


40

Fiori Apps Configurations Mention RFC destination as NONE Click on to set NONE for dialog and background activation. Source system as ‘No DataSource replication’. Select the Copy option in Treatment of already Active Content Objects Select the checkbox ‘Install all Collected Objects’


41

Fiori Apps Configurations First click on Activate Simulation run

Check the see all successful.

to


42

Fiori Apps Configurations If all successful, then click on activation

Activation may take long time, so run it on background.


43

Fiori Apps Configurations Similarly activate the other BI content /ERP/SFIN_PLANNING in category 03.


44


Once the BI content is activated we can directly test the BEx queries which is used by the Fiori Apps through RSRT tcode

Mention the query name. Mention the query display as HTML with Parmeter1 option selection and click on Execute Here using query for Profit Center- Actuals app. Query details available in the App library.


45

Fiori Apps Configurations Mention required selection criteria and click on Execute.

System will be display the result confirming the BEx Query working fine.

4.2.4. Web Dynpro App specific activation: Web dynpro apps won’t have any OData services. All these web dynpro apps are defined in LPD_CUST in Front end system with corresponding backend system services. All the required apps services need to be activated from backend system. Frontend system Login to Fiori frontend system


46

Fiori Apps Configurations Go to tcode LPD_CUST and check the app connection details. Fiori app library gives details on specific app LPD_CUST role and instance. Within the Launchpad instance, system shows the details on web dynpro service and system alias. Here web dynpro application service is FCOM_GROUP_COSTCENTER and systemalias is S4FIN. This is the same system alias with which RFC connections created earlier.

Backend System Login to S/4HANA system Activate the ICF service in backend system through SICF tcode.

Implement the note in backend as some of web dynpro apps not displaying same result as its BEx query. 2254766


47

Fiori Apps Configurations 4.3. Fact Sheet 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. 4.3.1. Web Dispatcher Configuration: Web Dispatcher helps in redirecting the Fiori search calls to the backend system where Enterprise search is enabled. wdisp/system_ parameter need to be updated so that http calls with enterprise search prefixes goes to Backend system. Frontend system Login to the Web dispatcher server Go to the Profile path

/usr/sap//SYS/profile

Update the profile by updating wdisp/system_ parameters.

wdisp/system_0 = SID=, MSHOST= MSPORT=, SRCSRV=*:*, SRCURL=/sap/opu/odata/

Also update the system conflict parameter with value as 1.

wdisp/system_1 = SID=, MSHOST= MSPORT=, SRCSRV=*:*, SRCURL=/sap/public/bc/;/sap/bc/;/sap/public/icmandir/

HTTPs port has been deactivated in Web dispatcher.

wdisp/system_2 = SID=, EXTSRV=:, SRCSRV=*:*, SRCURL=/sap/es/ina/;/ENTERPRISE_SEARCH/, CLIENT=100

It can be enabled when configuring SSL.

wdisp/system_conflict_resolution = 1

Restart the Web dispatcher In this document we are not covering HTTPs protocol. All the configurations with HTTP only

4.3.2. Enterprise Search Activation: Enterprise Search need to be activated in Backend system to enable search connectors. SAP provides Task list to activate Enterprise Search.  

SAP_ESH_INITIAL_SETUP_000_CLIENT SAP_ESH_INITIAL_SETUP_WRK_CLIENT

Backend system Login to S/4HANA backend system


48

Fiori Apps Configurations Check Business functions are activated through tcode SFW5 BSCBN_HANA_NAV BSESH_HANA_SEARCH Login to client 000 in S/4HANA

Task list SAP_ESH_INITIAL_SETUP_000_CLIENT need to be executed only in 000 client.

Assign SAP_ESH_LOCAL_ADMIN role to the user who is running the task list.

Go to Tcode STC01. Mention task list as SAP_ESH_INITIAL_SETUP_000_ CLIENT and click on execute

First task has to be manually marked complete once the user given required access. Click on the completed.

icon to mark it


49


Update the client number for the 2nd task by clicking on . This is the client which will be used for Enterprise search. Once required client mentioned, save and go back to previous screen. Client 100 is used here.

ESH tasks list run for long time, so execute it in background.

STCTM* job triggered but ended with error.


50


Implement notes 2225294 and 2225542 to ESH error. No Manual tasks involved. Once the notes implemented, execute the task list SAP_ESH_INITIAL_SETUP_000_ CLIENT again. Again Task list ended with error with respect to software component EAAPPLH.


51

Fiori Apps Configurations ESH Software component status can be checked through tcode ESH_MODELER. This opens a new web browser. Select component EAAPPLH Actions -> Import Log Import Logs shows error on that component.

Meantime, whenever the software component checked through tcode ESH_MODELLER, ESH_IEF_OM_UPDATE* job runs automatically.


52

Fiori Apps Configurations ESH_IEF_OM_UPDATE* job updates those specific software components. Now Import Log of EAAPPLH is green.

Implement note 2266478 to correct the error in the task list This note has Pre-implement and post-implement steps. Those manual steps are transportable and captured in a TR.


53

Fiori Apps Configurations Go to SNOTE and Implement the note 2266478 System lists out the prerequisite notes and other manual actions.

First Manual action is to add few messages in message class ESH_ADM_MSG though SE91 tcode


54


Once manual activity is completed, mark the manual activity as completed and proceed with implementing other notes.


55


There are some post steps as well for which we need to add additional tasks in task list mentioned by SAP in those notes.

Go to STC01 tcode. Mention task list SAP_ESH_CREATE_INDEX_SC as mentioned in the note and click on change

.

Click on to add a new task as mentioned the note. Sequence of the tasks should be same as mentioned in the note.


56


Similarly add that task to tasklist SAP_ESH_INITIAL_SETUP_WRK _CLIENT as mentioned in the note.

Once all manual steps are done, Mark the note completed.


57

Fiori Apps Configurations Note and other manual tasks are captured in the TRs.

Now execute the SAP_ESH_INITIAL_SETUP_000_ CLIENT task list again. Task List executed successfully after the Note implementation.

Before executing next task list, update HANA DB user authorizations. Add TREX authorizations to Default HANA DB user SAP through HANA studio. Open the HANA studio and connect to Backend S/4HANA DB (DE1). Open the user SAPDE1 system and assign object privileges TREXVIADBSL and TREXVIADBSLWITHPARAMETE R Assign Execute privileges for those objects.


58


Login to working client of S/4HANA (Client 100)


Task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT has to be executed in the client 100 which will be connected to Fiori.

59

Fiori Apps Configurations Assign SAP_ESH_LOCAL_ADMIN role to the user who is running the task list.

Go to tcode STC01 and execute task list SAP_ESH_INITIAL_SETUP_WRK _CLIENT

Once the required access assigned to the user, manually mark the first task as completed. Click on the completed.

icon to mark it


60

Fiori Apps Configurations Fourth task is to set the connection to HANA DB. Enterprise Search uses either TREX or HANA DB connection. As the Back end system (S/4HANA) already on top of HANA DB connection, use the DEFAULT option. Save and go back the task list.

Sixth task is to Select Models to Create Connectors. Each app requires different set of Search Models. In this configuration document, selecting models within EAAPLH software component.


61


Click on Multiple Input option and select all required search models. Save and go back to task list.


62


Tasks which are having status will not be executed. Leave them as it is.

Execute the task list in background as the job will run for long time.

Once job completed, validate if all the steps are successful.

This task list schedules indexing jobs to run daily.


63

Fiori Apps Configurations Go to tcode ESH_COCKPIT to check the list of search connectors activated.

If any of the search connectors not required, then it can be deactivated. Select the required connectors, go to action -> deactivate.

If there are any additional search connectors need to be created, then it can be done through Task list SAP_ESH_CREATE_INDEX_SC This task list is a subset of SAP_ESH_INITIAL_SETUP_WRK _CLIENT


64

Fiori Apps Configurations Go to tcode ESH_SEARCH and search some objects to check if Enterprise Search is working.

Currently no authorization checks on search Models. This means all users can do a search for all objects. If search model authorizations need to be activated, then it has to be done through ESH_IMG tcode. Search and Operational Analytics  Enterprise Search  Search Configuration  Set parameters for Federated Search

4.3.3. Fact Sheet specific app activation: Fact sheet apps also has ICF and OData services need to be activated in the Frontend system. Frontend System Login to Fiori system


65

Fiori Apps Configurations Go to tcode SICF and activate required ICF services BSCBN_ANF_SFIN and FIN_FS_ACTTYPE are services for Activity Type app.

Go to tcode /IWFND/MAINT_SERVICES Click on

Search for the OData service under FI_S4HANA system alias Select the service and click on


66

Fiori Apps Configurations Mention the package for Transport. OData activation gets captured in a Workbench TR.


67

Fiori Apps Configurations Go back to the /IWFND/MAINT_SERVICES tcode and search for that specific service.

Click on Call browser in the bottom section of the screen. This step need to be performed before testing the apps in Fiori Launchpad.

Similarly, activate other fact sheet apps.


68

Fiori Apps Configurations 4.4. Additional tasks: There are some additional activities need to be performed for specific apps. 4.4.1. DCL role activation for CDS objects: This step is required for the apps (e.g. Audit Journal, Trial Balance) which uses Core Data Services (CDS) views in the backend HANA DB. Every CDS view will have associated Data Control Language (DCL) roles which need to be generated to access those CDS views Backend System Login to S/4HANA system and go to tcode SACM Click on DCL-Documents (readonly mode)


69


Select the column Package and filter only required package. Here we are focusing on only FI related CDS views, so chose FIN*

Select all those filtered packages and click on generate ABAP artifacts.


70

Fiori Apps Configurations Once generated, refresh to see the status of those DCL sources.

These DCL items which were activated define the authorizations required for those specific CDS objects. Double click one of the object to view the authorization defined in it.

4.4.2. 0ANALYSIS Configuration: This step is required for the apps (e.g. Query Browser) which uses Design Studio (0Analysis) for the CDS views/Queries. Notes 2289865 and 2106016 has details on configuration steps. Some of the steps already done as part BI content activation. Copyright © 2016 Accenture. All rights reserved.

71

Fiori Apps Configurations Backend System Login to the backend S/4HANA system. Go to tcode SE38. Deactivate BW statistics via report SAP_RSADMIN_MAINTAIN adding object RSDDSTAT_GLOBAL_OFF with VALUE = X in INSERT mode

Generate packages for OData services Go to SE38 Report EQ_RS_AUTOSETUP execute without check mode


72


Go to SE37. Activate BI_ALL through function module RSEC_GENERATE_BI_ALL

Click on execute


73

Fiori Apps Configurations Go to RSD5 tcode. Select ‘All InfoObjects’ and click on to check all of them in green.


74

Fiori Apps Configurations Go to SICF tcode Activate these SICF services /sap/bw/ina /sap/bw/Mime

Create ICF Handler service for GetServerInfo within /sap/bw/ina

Right click on ina and click on New sub-Element

Go to default host sapbwina

Mention Service Element as ‘GetServerInfo’ and select the type as ‘Reference to Existing Service’.


75


Go to Target tab and double click on /sap/es/ina/GetServerInfo.

Save it. It can be saved as a local or transportable object.


76


Once saved, Activate it.


77

Fiori Apps Configurations Frontend System Login to fiori system and go to tcode /IWFND/MAINT_SERVICES Search for the service RSAO_ODATA_SRV. Click on add system alias and assign that service to local alias. Once Local alias assigned, click on call browser.

Go to tcode RSOR to install the 0ANALYSIS.


Select object types  More types  Analysis Application and double click on Select objects

78


Select objects and click on Transfer selection


79


Select the DF1 system.


80


Now 0ANALYSIS selected for installation.

Click install under Install button.


81


Table RSAOOBJ will have 0ANALYSIS with version ‘A’.

Add these URLs to the web dispatcher parameter to redirect to backend S/4HANA system

wdisp/system_2 = SID=DE1, EXTSRV=:, SRCSRV=*:*, SRCURL=/sap/es/ina/;/ENTERPRISE_SEARCH/;/sap/bw/ina/;/sap/bw/Mime/ DS/Content/, CLIENT=100

/sap/bw/ina/ /sap/bw/Mime/DS/Content/ Check these URLs to validate the 0Analysis. http://:/sap/bc/ui5 _ui5/ui2/ushell/resources/sap/ zen/dsh/rt/all-dbg.js http://:/sap/opu/o data/sap/RSAO_ODATA_SRV/B iApplicationSet('0ANALYSIS')/? $expand=Data,Texts&sapclient=100 If there are any errors, then configuration is not complete


82


4.4.3. External Alias for Logoff in backend: Backend System Login to S/4HANA system and go to tcode SICF. Click on External Aliases


83

Fiori Apps Configurations Select the default_host and click on New

Maintain external aliases as /enterprise_search/sap/public /bc/icf/logoff Go to Trg Element tab and double click on /sap/public/bc/icf/logoff


84

Fiori Apps Configurations Click on Save.


85


5.

Security: 5.1. Cross-Application Roles: Users and Administrators require additional roles to access and manage the Fiori Launchpad. SAP already provided two roles SAP_UI2_ADMIN_750 – For Administrators SAP_UI2_USER_700 – For Users Frontend System Login to Fiori system and go to tcode PFCG.

Copy the role from SAP_UI2_ADMIN_750 to ZSAP_UI2_ADMIN_750

Add these standard Fiori OData services.

Go to Menu tab Click on small downward arrow in Transaction

ZINTEROP_0001 ZPAGE_BUILDER_CONF_0001 ZPAGE_BUILDER_CUST_0001 ZPAGE_BUILDER_PERS_0001 ZTRANSPORT_0001 These were the services created initially as part of task list execution SAP_FIORI_LAUNCHPAD_INIT_ SETUP in section 3.1


Select Authorization Default option.

86


Select TADIR Service

Select Object Type as IWSG SAP Gateway: Service Groups Metadata

Add all those required OData services and click on OK


87

Fiori Apps Configurations Those OData services will be listed under Role Menu.

Go to Authorizations tab and click on Change Authorization Data. Save and Generate profile.

the


88

Fiori Apps Configurations Similarly copy the other user role SAP_UI2_USER_700 to ZSAP_UI2_USER_700

Add only these 2 OData Services in Menu tab. ZINTEROP_0001 ZPAGE_BUILDER_PERS_0001

Save and generate profile.

the

5.2. App specific Roles: SAP provides standard frontend and backend role for Fiori apps. Frontend role will have app specific OData service, catalogs and groups. Here one such Frontend role copied and app relevant OData service added to it. Frontend System Login to Fiori system and copy the standard Fiori app role to Z role.


89

Fiori Apps Configurations Go to Menu and add the app specific OData Service

Click on small downward arrow in Transaction . Choose Authorization Default option.

Select TADIR Service and Object type IWSG


90

Fiori Apps Configurations Include OData service into that list. OData service in the screenshot is of ‘Display G/L Account Line Items App’.

Similarly, add other app OData services which belongs to this role.

Save and generate profile.

6.

the

Fiori Launchpad Customizations (Optional): Fiori Launchpad: Fiori Launchpad is the entry point for all the Fiori apps. Depending the catalogs, groups and roles assigned, user will be able to see Fiori apps. URL: http(s)://:/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html 6.1. Custom Catalog and Groups: Catalog: Set of apps you want to make available for one role. Depending on the role and the catalog assigned to the role, the user can browse through the catalog, choose apps from this catalog, and add them to the entry page of the SAP Fiori Launchpad. Group: Subset of catalog that contains the apps visible on the SAP Fiori Launchpad entry page. Which tiles are displayed on a user’s entry page depends on the group assigned to the user’s role. In addition, the user can personalize the entry page by adding or removing apps to predelivered groups or self-defined groups.


91

Fiori Apps Configurations Roles (PFCG): Contains references to catalogs and groups and provides users with access to the apps in these groups and catalogs. Custom Catalogs and Groups created through Fiori Launchpad designer. URL: http(s)://:/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html Frontend System Login to Launchpad designer URL. You need SAP_UI2_ADMIN_750 role assigned. Left side Navigation lists out the Catalogs and groups

Before starting any customizations need to set a TR in the designer, so that all the changes gets captured to that TR. Create a Customizing TR in SE09 and update the number in Designer by clicking on settings button on top left corner next to client number. Click on Catalog.

It can be left as None if the changes are only local.

to create new


92

Fiori Apps Configurations Search for required Apps from standard SAP provided Catalogs. Select the required Tiles and click on to copy to the Custom Catalog.


93


Similarly Copy all required Tiles and corresponding Target Mappings to the Custom catalog.

Drag and drop the catalog inside ‘Catalog Collection’


94


If corresponding Tiles and Target Mappings matches, then status will show

.

Fact Sheets will have only Target Mappings, so it will show as

.

Any changes to original Tiles/Target Mappings will reflect to the items copied in custom catalog. If those tiles/target mappings edited in custom catalog, then they will lose its reference with Original.


95

Fiori Apps Configurations Go to Groups section and click on to create custom Group.

Click on to link the group to a catalog. Then click on Input help button to select required Catalog.


96


Click on to add the Tile to the group. Once added it will turn into

For users to access the custom catalog/groups, they need to be assigned to a PFCG role. Go to PFCG and open required role. Go to Menu tab and click on small downward arrow in Transaction . Select SAP Fiori Catalog and add required Catalog to the role.


97


Similarly add required group to the role.


98

Fiori Apps Configurations Based on role definition, required OData services need to be added which is explained in section 5.2

User with that particular custom role assigned will able to see the custom group in Fiori Launchpad home page.

Click on in the bottom corner to add any other tiles from available catalog.


99


6.2. Theme Designer: SAP provides a tool to design the Fiori Launchpad theme. It can be accessed through tcode /UI5/THEME_DESIGNER or URL. http://:/sap/bc/theming/theme-designer?sap-client= Frontend System Login to Fiori system Active the SICF services ui5_demokit and theming.


100

Fiori Apps Configurations Go to tcode /UI5/THEME_DESIGNER. Custom themes are created by copying the existing standard themes. Select one of the themes and click on Open.

Provide Fiori Launchpad URL in the Link to Application field and click on Add Themes can be added to specific target URL.

Tool will show the preview. In the right side of the tool, we can update the color combinations for background and font.

Click on the Company logo field in the right side section to update company logo.


101


Similarly, background image can also be changed.

Go to Theme  Save As to save the Theme.


102


There are more options in the right-side for expert level theme customizations.


103

Fiori Apps Configurations Once all customizations are done, go to Theme  Save & Build

If the theme need to be transported, then it can be done from GUI level. Go to tcode /UI5/THEME_TOOL. Custom themes will be seen. Double click on Transport to save it in a TR.

Similarly, double click on Info to get the Theme URL. Sap-theme parameter need to be appended to Fiori Launchpad URL to access it directly with custom theme.


URL: https://.:/sap/bc/ui5_ui5/ui2/ushell/shells/abap/Fior ilaunchpad.html?sap-client=&saptheme=@https://.:/sap/public/bc/the mes/~client-

104

Fiori Apps Configurations Theme can be changed from Fiori Launchpad through User Preferences and select the required theme.


105


In order to set custom theme as default theme for all users, then go to tcode /UI2/NWBC_CFG_SAP Update parameter SAP_FLP from original to custom theme.

6.3. Login/Logout Page Customizations: Based on the requirements, login and logout pages can be customized. Frontend System Generally, there won’t be any log out page configured for Fiori. We can configure to redirect to Login page.


106


Go to SICF and open /sap/public/bc/icf/logoff. Go to Error Pages tab  Log off page.


107


Click on edit Select ‘Redirect to URL’ option and update the Fiori Launchpad URL.


108

Fiori Apps Configurations Click on Save and while saving system prompts for user password. Update a system user and password in Logon Data tab.

Changes to logoff SICF service gets saved into a TR.


109

Fiori Apps Configurations Login page can be customized through a class and method provided by SAP.

Class /UI2/CL_SRA_LOGIN and method INIT_DEFAULT_PARAMETERS The background image for the login page is located in the mime repository under the path: “/sap/public/bc/ui2/logon/img/”

6.4. Launchpad URL customization: Generally, Launchpad URL is lengthy and to easily remember the Launchpad URL we can create external alias. Launchpad URL: http://:/sap/bc/ui5_ui5/ui2/ushell/shells/abap/Fiorilaunchpad.html Frontend system Login to Fiori system Go to tcode SICF and click on execute

Select the default_host and click on External Aliases


110


Click on to create new external Alias

Mention an External Alias name and description.


111

Fiori Apps Configurations Then select the trigger element /default_host/sap/bc/ui2/flp

Save the external alias. Now fiori Launchpad can open with this url http://:/fiori

*This customized URL need to be added to the wdisp/system_ parameter. So that Web dispatcher can redirect to fiori system.


112


7.

Troubleshooting: If any of the apps are not connecting, then we need to check if the issue is in the frontend system or backend system. Frontend system Login to Fiori system Go to tcode /IWFND/ERROR_LOG If the app not connecting, then check the error log. If there are any error mentioned ‘No service found for namespace’, then respective OData service is not activated. There are additional Odata services/ICF need to be activated apart from the ones mentioned in the App library as it will have inter dependency with other services. If the error is in backend system, error log will have check box marked for backend. Here error screenshot says authorization error in backend system.


113

Fiori Apps Configurations Here the screenshot says error is in backend system with specific data object. This was because those specific search connectors ‘Purchase Orders’ and ‘Fixed Asset’ were inactive in backend system.

Browser logs also helps in troubleshooting the error. If there is an error in Fiori Launchpad, Check the browser console logs by pressing F12 key

Here one of the SICF services fin_lib not activated. There are additional Odata services/ICF need to be activated apart from the ones mentioned in the App library as it will have inter dependency with other services. In Some case, there would be additional backend ICF services need to be activated. As SAP continuously upgrading their apps list with new versions and support packs, there could be app specific errors as well. In those cases, need to reach out to SAP.


114


Appendix: Reference Links Title

Links

Fiori Apps library

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/

SAP help link

http://help.sap.com/saphelp_fiori_implementation_nw75/helpdata/en/ 7d/1adb1bd5de41908931410f62dc0990/frameset.htm

App implementation

http://help.sap.com/saphelp_fiori_implementation_nw75/helpdata/en/ ab/d57adcf9f841c2b192afd5db74ee0e/frameset.htm

Quick guide

https://websmp109.sap-ag.de/~sapidb/012002523100011778012014D

Automatic Configuration task list

https://websmp206.sap-ag.de/~sapidb/012002523100008986102014E

SAP Fiori Search

http://help.sap.com/saphelp_fiori_implementation_nw75/helpdata/en/ 12/af5252b10d5a64e10000000a423f68/frameset.htm

Enterprise Search

http://help.sap.com/saphelp_nw75/helpdata/en/77/3d61cec12a4c1088 d78ac909b9abb4/content.htm?frameset=/en/c3/bcfaa6170f4252b3749 b3599b79ead/frameset.htm¤t_toc=/en/6d/ad05874f344592b42 abc729eeadd4c/plain.htm&node_id=3&show_children=false http://help.sap.com/saphelp_nw75/helpdata/en/57/7d77c891954c21a 19c242694e83177/content.htm

Web Dispatcher Configuration


http://sapassets.edgesuite.net/sapcom/docs/2015/07/4ebea71f-5a7c0010-82c7-eda71af511fa.pdf

115

Fiori Standard Apps Configuration v1.1

Recommend Documents