App Implementation: Manage Bank AccountsThe app consists of the SAP Fiori launchpad configuration (such as the tiles and the navigation) and back-end components (such as the Web Dynpro application itself). The back-end and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori.
Back-End Components Delivered with (Product Version Stack) | SAP S/4HANA Finance 1605 SPS 7
|
|---|---|
Front-End Components Delivered with (Product Version Stack) | SAP Fiori for SAP S/4HANA Finance 1605 SPS 4
|
For the Manage Bank Accounts
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 for Cash Management Applications |
This app uses Web Dynpro technology.
You can refer to the required implementation tasks for Web Dynpro apps in the SAP Fiori for SAP S/4HANA Finance Implementation Information
under .
The following sections list tasks that have to be performed to implement the app. You can find the data required to perform these tasks in the SAP Fiori apps reference library under the following link (choose Implementation Information
and select the relevant delivery date):
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F1366![]()
The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been assigned by an administrator to the catalog designed for this user's role.
For more information, see SAP Help Portal at : Configuring the Launchpad
and Configuring Authorization Roles
.
For more information on catalogs and roles, see 2242596
.
Customizing Navigation Target
Before you can access this app, you must have specified an RFC destination that points to the SAP back end where the Web Dynpro is running. The predefined system alias for the RFC destination is SAP_ECC_Financials
(see transaction LPD_CUST
and access the app-specific configuration).
Use transaction SM59
to check whether the RFC destination SAP_ECC_Financials
is available.
If this RFC destination is not available, create it manually (connection type H
) and configure it according to your needs (SSL).
You can also refer to Customizing Navigation Targets
in the SAP Help Portal, http://help.sap.com
under .
Component | Technical Name |
|---|---|
Web Dynpro Application |
|
Use transaction sicf
and make sure that the ICF service for the Web Dynpro application is activated.
Component | Technical Name |
|---|---|
Back-End Role |
|
Carry out the following configuration tasks in the back-end system:
Copy the back-end role and enter authorization values according to your business process.
Assign this role to the user in the back-end system.
To be able to implement the app, you must perform the necessary configuration tasks for SAP S/4HANA Finance for cash management in the SAP ERP system:
Make sure that you have properly configured the required Customizing activities under .
Make sure that you have properly configured the workflows that you want to use with Bank Account Management.
For more information, see .
This app is suitable to be extended. For more information, see App Extensibility: Manage Bank Accounts.
For more information about the user management concept in an SAP Fiori environment, see SAP Help Portal at : Users in ABAP Front-End System
and Users in ABAP Back-End System
.