Each SAP Fiori app consists of front-end components (such as the user interface) and back-end components (such as the OData service).
SAP Fiori for SAP S/4HANA Finance contains the front-end components for a bundle of SAP Fiori apps and has to be installed on your ABAP front-end server. To be able to implement and use the apps, you have to ensure that the corresponding back-end components of these apps are active on your ABAP back-end server.
For more information about the necessary system landscape components, see the “Administrator’s Guide for SAP S/4HANA Finance” on SAP Help Portal at .
The following activities involve configuration that is specific to SAP S/4HANA Finance. These steps have to be followed in addition to those explained in the general Fiori app implementation information, which is available on the SAP Help Portal at http://help.sap.com/fiori_implementation. These activities are relevant for implementation teams working on a new installation and an upgrade.
User Default Parameters
The SAP Fiori launchpad (FLP) contains a user default parameter service that calls application plug-ins. For the display and use of the apps delivered with SAP Fiori for SAP S/4HANA Finance, the fin.central.user.defaultparameter
application plug-in is needed.
Register the fin.central.user.defaultparameter
application plug-in for use by following these steps:
Activate the FIN_USER_DEFAULTPARAMETER
OData service on your ABAP front-end server.
Add this service using the /IWFND/MAINT_SERVICE transaction. Alternatively, you can activate the services in the SAP Customizing Implementation Guide
(SPRO transaction) under .
Note
If you have multiple ABAP back-end servers, you must activate the FIN_USER_DEFAULTPARAMETER_SRV
technical services on each ABAP back-end server by listing each system alias.
The activation on the ABAP front-end server automatically triggers the activation of the FIN_USER_DEFAULTPARAMETER_SRV
technical service on your ABAP front-end server. You can check this on your ABAP back-end server using the SICF transaction. Check under
Activate the FIN_ACC_USERPAR
ICF service on your ABAP front-end server. Use the SICF transaction and check under .
The fin.central.user.defaultparameter
application plug-in is called for determining the value for certain user default parameters (for example, company code) from the ABAP back end. The plug-in is called in two situations:
A Fiori app is started that requires a certain user default parameter.
The FLP maintenance UI for the user default parameter is opened.
The FLP has its own persistency on the ABAP front-end server for storing the user default parameters. By default, all parameters are read from this persistency. If a parameter is not yet stored in the FLP persistency, then the application plug-in calls the back end for determining the parameter value.
Reuse Library
Activate the following ICF service on your ABAP front-end server by using the SICF transaction:
Component | Technical Name | SAP Note |
---|---|---|
|
|
For a detailed explanation of the SICF activation procedure, see the “App Implementation Information for SAP Fiori” at http://help.sap.com/fiori_implementation. Use the version for SAP NetWeaver 7.5.
Apps accessed from the SAP Fiori launchpad can use UI technologies other than SAPUI5, for example, Web Dynpro and Design Studio. Apart from the activities specified above, the detailed implementation steps may differ depending on the UI technology used. For more information, see Apps with Other UI Types and the implementation document for the specific app.
Apps delivered withSAP Fiori for SAP S/4HANA Finance offer in-app help for the business users actually performing their work. For more information about the in-app help and how to configure the necessary settings, see User Assistance Settings.
For information about the installation of analytical SAP Smart Business apps, see the SAP Help Portal at
.