App Implementation: Schedule Payment Proposals 
System Landscape Requirements
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.
Required SAP Notes
For the Schedule Payment Proposals app, the following SAP Notes must be implemented:
Back-End/Front-End Server | SAP Note Number | Description |
|---|---|---|
Back-end server and front-end server | Release Information Note: Schedule Payment Proposals |
Implementation Tasks
The following sections list tasks that have to be performed to implement the Schedule Payment Proposals app. The tables contain the app-specific data required for these tasks:
Front-End Server: Activate OData Services
Component | Technical Name |
|---|---|
OData Service (Version Number) | FAP_SCHEDULE_PAYMENT_PROPOSAL (1) |
For more information about activating OData services, see Front-End Server: Activate OData Services.
Front-End Server: Activate SAP UI5/BSP Application
Component | Technical Name |
|---|---|
| SAP UI5/BSP Application | FIN_SCHPMTPRPSL |
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).
Front-End Server: Enable App for Access in SAP Fiori Launchpad
There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You require the listed data to perform these steps.
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 
https://www.sap.com/fiori-apps-library
.
Component | Technical Name |
|---|---|
Semantic Object | AccountingDocument |
Business Role | SAP_SFIN_BCR_PAYABLES_CLERK |
Business Catalog | SAP_SFIN_BC_PAY_CLERK |
Business Catalog Group | SAP_SFIN_BCG_PAY_CLERK |
Technical Role | SAP_SFIN_TCR_T |
Technical Catalog | SAP_SFIN_TC_T_FI |
Front-End Server and Back-End Server: Assign Roles with OData Service Authorization to Users
To grant specific users access to OData services, you have to assign roles (including OData service authorization for the app) to your users. You have to 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 adjust this role according to your needs.
On the front-end server, you can assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
OData Service (Version Number) | Back-End Server: Delivered Authorization Role (PFCG Role) | Front-End Server: Authorization Role |
|---|---|---|
| FAP_SCHEDULE_PAYMENT_PROPOSAL (1) | SAP_FIN_SCHPMTPRSL_APP | You can assign the OData service authorization to a business role, for example the delivered business role SAP_SFIN_BCR_PAYABLES_CLERK. |
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.
SAP Jam Integration
For information on how to configure SAP Jam, see http://help.sap.com/sapjam.
More Information
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.