App Implementation: Process Collections Worklist 
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) | UIFSCM70 100 |
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
Required SAP Notes
For the Process Collections Worklist app, the following SAP Note must be available:
Back-End/Front-End Server | SAP Note Number | Description |
|---|---|---|
This SAP Note applies to both the back and the front end. | Release Information Note for the SAP Fiori app Process Collections Worklist |
Implementation Tasks
The following sections list tasks that have to be performed to implement the Process Collections Worklist 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) | FAR_DUNNING_PROPOSAL_SRV (1) |
| OData Service (Version Number) | UDMO_COLLECTION_WORKLIST (1) |
OData service UDMO_COLLECTION_WORKLIST includes OData service FAR_DUNNING_PROPOSAL_SRV.
For more information about activating OData services, see Front-End Server: Activate OData Services.
Front-End Server: Activate UI5 Application
Component | Technical Name |
|---|---|
| UI5 Application | FSCM_COLLWORKL |
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 data listed below for this.
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 | CustomerCollections |
Business Role | SAP_SFIN_BCR_FSCM_COLL_SPECIAL |
Business Catalog | SAP_SFIN_BC_FSCM_COLL_SPECIALIST |
Business Catalog Group | SAP_SFIN_BCG_FSCM_COLL_SPECIALIST |
Technical Role | SAP_FSCM_TCR_T |
Technical Catalog | SAP_FSCM_TC_T |
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 copy this role and adjust it to meet your specific requirements.
On the front-end server, you can assign the OData service authorization to a new or existing role, such as a user role that has been adjusted according to your requirements.
OData Service (Version Number) | Back-End Server: Delivered Authorization Role (PFCG Role) | Front-End Server: Authorization Role |
|---|---|---|
| UDMO_COLLECTION_WORKLIST (1) | SAP_FSCM_COLLWORKL_APP | You can assign the OData service authorization to a business role, for example, to the business role SAP_SFIN_BCR_FSCM_COLL_SPECIAL delivered. |
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.
Configuration
Within SAP Accounting powered by SAP HANA, you have configured and are using application component SAP Collections Management (FIN-FSCM-COL).
So that you can branch to the details, you must also have implemented the Process Receivables app.
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.
Note
This app runs on desktops only.