Before you start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori. This also implies that the front-end components and back-end components for your app are already available in this system landscape:
SAP Fiori System Landscape Options | |
---|---|
Configuration of Front-End Server | |
Back-End Components Delivered with (Product Version Stack) | SAP Simple Finance add-on 1.0 SPS04 for SAP Business Suite powered by SAP HANA |
Front-End Components Delivered with (Product Version Stack) | SAP Fiori for the SAP Simple Finance add-on 1.0 SPS04 for SAP Business Suite powered by SAP HANA |
Ensure that the front-end component of the app is in place on your front-end server. It is automatically installed with the UI add-on.
Front-End Server: Front-End Component of App (Software Component) | UIAPFI70 100 |
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
Note
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content.
For more information on virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.
For the Clear Incoming Payments app, the following SAP Notes must be implemented:
Back-End/Front-End Server | SAP Note Number | Description |
---|---|---|
Back-End/Front-End Server | SAP Note for the Fiori app "Clear Incoming Payments" – collective SAP Note for implementing the Clear Incoming Payments app. To make sure that the app functions correctly, you must implement the corrections that are described in the SAP Notes listed in this collective note. | |
Back-End/Front-End Server | SAP Note regarding the usage of OData service FAC_FINANCIALS_POSTING. To make sure that the app functions correctly, you must take into consideration the instructions in this SAP Note. |
The following sections list tasks that have to be performed to implement the Clear Incoming Payments app. The tables contain the app-specific data required for these tasks:
Component | Technical Name |
---|---|
OData Service (Version Number) | FAR_MANUAL_CLEARING_SRV (1) |
OData Service (Version Number) | FAC_FINANCIALS_POSTING_SRV (1) |
OData Service (Version Number) | FAC_FINANCIAL_DOCUMENT_SRV_01 |
For more information about activating OData services, see Front-End Server: Activate OData Services.
Component | Technical Name |
---|---|
SAP UI5 Application | FIN_ARMANCLEAR |
For more information about how to activate the ICF service, see Front-End Server: Activate ICF Services of SAPUI5 Application (for transactional apps) or Activate ICF Service of BSP Application (fact sheets).
The SAP Fiori launchpad is the entry point to SAP Fiori apps. From a user perspective, it displays those SAP Fiori apps that have been assigned to the catalog designed for this user's role.
This presupposes that an administrator has made the necessary assignments in the launchpad designer to enable a user's access to the respective SAP Fiori apps in the SAP Fiori launchpad. For more information, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.
SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library at
.You must assign OData service authorizations for the app to your users.
Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
Make the assignment on the back-end server and on the front-end server:
On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs. For more information, see Back-End Server: Assign OData Service Authorization to Users.
On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs. For more information, see Front-End Server: Assign OData Service Authorization to Users.
For the OData service FAR_MANUAL_CLEARING_SRV (1) you need the following authorization roles:
Back-End Server: SAP_FIN_AR_MANUAL_CLEARING_APP
Front-End Server: SAP_SFIN_BCR_RECEIVABLES_CLERK
Note
To ensure that the G/L document can be simulated and displayed, you have to assign the PFCG role SAP_FIN_GLDOCMANAGE_APP to the selected user, in addition to the SAP_FIN_AR_MANUAL_CLEARING_APP role. You may also want to define instance based restrictions, for example, to limit the access to one company code only.
Before implementing the app, you must ensure that you have implemented the Manage G/L Documents app correctly. This app is an integral part of the Clear Incoming Payments app because it enables the simulation of the clearing.
For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.