App Implementation: Clear Incoming PaymentsBefore you can start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori and that this system landscape already includes the front-end components and back-end components for your app:
SAP Fiori System Landscape Options | . |
|---|---|
Configuration of Front-End Server | . |
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 |
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) |
|
For more information about the installation of SAP Fiori products, see SAP Help Portal at .
Note
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your front-end 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 section Virus Scanning in the SAP S/4HANA UI Technology guide.
To work correctly, this app requires the following libraries:
Reuse ClearPayments
Reuse CodingBlock
Central Financial Fiori Reuse Library
All activities that are necessary to install the libraries are described in the Required SAP Notes and Front-End Server: Activate UI5 Application sections of this document.
Before implementing the app, you must ensure that you have implemented the Manage Journal Entries
app correctly. This app is an integral part of the Clear Incoming Payments
app because it enables the simulation of the clearing.
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):
Component | Technical Name |
|---|---|
OData Service (Version Number) |
|
OData Service (Version Number) |
|
OData Service (Version Number) |
|
For more information about activating OData services, see SAP Help Portal at .
Component | Technical Name |
|---|---|
| SAP UI5 Application |
|
For more information, see SAP Help Portal at .
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
.
You must assign OData service authorizations for the app to your users. The assignments must be made on the back-end server and on the front-end server.
For information on the Fiori authorization and user management concept, see SAP Help Portal at .
Note
This app is not extensible.
To be able to search for matching open items based on payment reference information, such as invoice number or reason for payment, you must define rules for payment allocation. Note that this search is based on the search logic for electronic bank statements.
You define rules for payment allocation in Customizing for Financial Accounting
under .
Define posting parameters
Define entries for each company code. If you need rules on a more detailed level, you can also make settings for different house banks and account IDs.
In the Posting Mode
field, select Import and Post
.
In the Rule for Session Name
field, select Name Derived from House Bank ID and Account ID
.
Define number ranges
Define intervals for the document number or reference document number.
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
.