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 |
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
For the Cash Position Details app, the following SAP Note must be implemented:
Back-End/Front-End Server | SAP Note Number | Description |
---|---|---|
Back-end server and front-end server | Release Information Note: Cash Position Details |
The following sections list tasks that have to be performed to implement the Cash Position Details app. The tables contain the app-specific data required for these tasks:
Component | Technical Name |
---|---|
CASH_DISPOSITION_SRV (1) | CASH_DISPOSITION_SRV |
Component | Technical Name |
---|---|
UI5 Application | FIN_ANALYZEPOSI |
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).
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
.Component | Technical Name |
---|---|
Semantic Object | BankAccount |
Business Role | SAP_SFIN_BCR_CASHMANAGER |
Business Catalog | SAP_SFIN_BC_CASHMANAGER |
Business Catalog Group | SAP_SFIN_BCG_CASHMANAGER |
Technical Role | SAP_SFIN_TCR_T |
Technical Catalog | SAP_SFIN_TC_T_FI |
LPD_CUST Role | UIAPFI70 |
LPD_CUST Instance | TRANSACTIONAL_CM |
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 |
---|---|---|
CASH_DISPOSITION_SRV (1) | SAP_FIN_ANALYZEPOSI_APP | You can assign the OData service authorization to a business role, for example the delivered business role SAP_SFIN_BCR_CASHMANAGER. |
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.
In the SAP Fiori launchpad designer, there are several parameters required for displaying data in this app. To specify the mandatory parameters, proceed as follows:
In the SAP Fiori launchpad designer, search for the Cash Manager catalog.
In the Cash Manager catalog, choose Target Mapping.
Select the entry with Semantic Object of BankAccount and Action of analyzeCash, and then choose the Configure button.
In the General section, specify the Default values for the following parameters:
Parameter | User Input |
---|---|
HierarchyID | The name of the liquidity item hierarchy that you want to use to view the cash position data |
RepCurrency | The currency that you want to use to view the cash position data |
ExRateType | The exchange rate type that you want to use to convert other currencies into the reporting currency |
To be able to implement the app, you must perform the following configuration tasks for SAP Cash Management powered by SAP HANA in the SAP ERP system under
:Configure planning levels to classify cash flows according to the source financial transactions
Configure planning groups to classify cash flows by customer and vendor groups
Configure flow types to classify cash flows with respect to their life cycle
Configure liquidity items, liquidity item hierarchies, and liquidity item derivation rules to categorize cash flows according to the source and use of the cash movements
Activate source applications of accounting and the Exposure Hub to include the transactions of the activated applications to cash position calculation
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.