Test Script
SAP S/4HANA - 09-09-24
Cash Application Integration (1MV)
PUBLIC
Table of Contents
1 Purpose
2 Prerequisites
2.1 Model Availability
2.1.1 Historical Data
2.1.2 Training Data Extraction
2.1.3 Machine Learning Training Progress, Benchmark Report, and Model Activation
2.2 Additional Manual Configuration
2.3 System Access
2.4 Roles
2.5 Business Conditions
3 Overview Table
4 Test Procedures
4.1 Scheduling Accounts Receivable Jobs - Automatic Bank Statement Reprocessing – Receivables Clearing
4.2 Scheduling Accounts Receivable Jobs – Automatic Lockbox Processing (Optional)
4.3 Extracting Payment Advice Information
1 Purpose
Overview
The SAP Cash Application uses the past data in your system to propose invoice matching prediction results. It helps lower the manual effort in the time-con-
suming clearing process of open items.
With this scope item, remittance advice can also be created automatically by the system based on the advice file sent from your customers or payees.
To use this solution's functions, you must purchase the extra license on SAP BTP.
Note To use this solution's functions, you must purchase the extra license on SAP BTP.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each
process step, report, or item is covered in its own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the
process but are needed for testing are marked accordingly. Project-specific steps must be added.
Note Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a
different notation, enter values as appropriate.
Cash Application Integration (1MV)
Test Procedures PUBLIC 2
2 Prerequisites
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and busi-
ness conditions.
2.1 Model Availability
To test the scope item, you must activate the respective SAP Cash Application country model in SAP BTP.
The following steps are required to generate SAP Cash Application country model.
2.1.1 Historical Data
The SAP Cash Application is a machine-learning-based solution. The algorithm is derived solely from historical cleared bank statement items against the in-
voices in the system. The minimum historical data required for Cash Application is 10,000 cleared bank statement items.
For technical details of the data requirement, see the SAP Cash Application Prerequisites on the SAP Help Portal.
2.1.2 Training Data Extraction
Upon confirmation that the historical data met the prerequisite volume and clearing processes, such data need to be sent to Cash Application as training
data.
For more information on the training processes, see the Cash Application Training Process and Activities documentation on the SAP Help Portal.
2.1.3 Machine Learning Training Progress, Benchmark Report, and Model Activation
Upon completion of the training job in SAP S/4HANA, the machine learning training status can be monitored via the Model Manager UI. Once the overall train-
ing progress is completed successfully, you can view the benchmark result. The country model can then be activated.
For more information on the Model Manager UI Onboarding process and activities, see the Model Manager for SAP Cash Application documentation on SAP
Help Portal.
Cash Application Integration (1MV)
Test Procedures PUBLIC 3
2.2 Additional Manual Configuration
Before you can test this scope item, you must have completed the additional post-activation configuration steps that are described in the Set-Up Instructions
for this scope item. These configuration steps are specific for your implementation and include mandatory settings that are not delivered by SAP and must be
created by you.
For more information, refer to the Administration Guide to Implementation of SAP S/4HANA with SAP Best Practices. In the table, search for this scope item
and follow the link to the document.
2.3 System Access
System Details
System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.
2.4 Roles
Assign the following business roles to your individual test users. Alternatively, if available, you can create business roles using the following spaces with
pages and predefined apps for the SAP Fiori launchpad and assign the business roles to your individual test users.
Note These roles or spaces are examples provided by SAP. You can use them as templates to create your own roles or spaces.
For more information about business roles, refer to Assigning business roles to a user in the Administration Guide to Implementation of SAP S/4HANA with
SAP Best Practices.
Name (Role) ID (Role) Name (Launchpad Space) ID (Launchpad Space) Log On
Cash Management Specialist SAP_BR_CASH_SPECIALIST Cash Management SAP_SFIN_SP_CMS_OVR
Accounts Receivable Accountant SAP_BR_AR_ACCOUNTANT Accounts Receivable SAP_SFIN_SP_AR_ACC
2.5 Business Conditions
Before this scope item can be tested, the following business conditions must be met.
Cash Application Integration (1MV)
Test Procedures PUBLIC 4
Scope Item ID Business Condition
J59 - Accounts Receivable Must be in scope as prerequisite.
Cash Application Integration (1MV)
Test Procedures PUBLIC 5
3 Overview Table
Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for per-
forming the typical tasks of a business role.
You can find all other apps not included on the homepage using the search bar.
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.
Process Step Business Role App/Transaction Expected
Results
Scheduling Accounts Receivable Jobs - Automatic Bank Statement Reprocessing – Accounts Receivable Accountant Schedule Accounts Receivable
Receivables Clearing [page ] 7 Jobs (F2366)
Scheduling Accounts Receivable Jobs – Automatic Lockbox Processing (Optional) Refer to the Lockbox (1JT) test script. Refer to the Lockbox (1JT) test
[page ] 9 script
Note This step is only relevant for the
US and Canada.
Extracting Payment Advice Information [page ] 9 Accounts Receivable Accountant Manage Payment Advices
(F2550)
Cash Application Integration (1MV)
Test Procedures PUBLIC 6
4 Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
4.1 Scheduling Accounts Receivable Jobs - Automatic Bank Statement Reprocessing – Re-
ceivables Clearing
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Testing Date:
Tester Name: Duration:
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This background job automatically matches invoices to bank statements, thus supporting the accounts receivable accountant in clearing the items.
Prerequisites
Open bank statements exist in the system. If not, see the Bank Integration with File Interface (1EG) scope item to upload bank statement files, or the Basic
Cash Operations (BFB) scope item for manual bank statement creation.
Open invoices are sent to the Cash Application using the Cash Application: Open Item Upload job template.
The model for the Bank Statement Company Code's country is available and activated.
To maintain the reprocessing rules, see the Accounts Receivable (J59) test script, section Manage Bank Statement Reprocessing Rules (Optional).
Cash Application Integration (1MV)
Test Procedures PUBLIC 7
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /
Step Comment
#
1 Log On Log on to the SAP Fiori launchpad as an Accounts Receivable Accountant.
2 Access the SAP Open Schedule Accounts Receivable Jobs (F2366).
Fiori App
3 Create a New Choose Create. The New Jobs view is displayed.
Job
4 Enter Job Data Make the following entries and choose Schedule: The background job is scheduled and the
General Information section: page skips back to the Application Jobs
view.
● Job Template: Cash Application: Automatic Bank Statement Reprocessing
Scheduling Options section:
● Start Immediately: Selected
Parameter section:
● Statement Number: <the bank statement number to be processed>
● Company Code: <your company code>, for example, 1010
● Account Type for Clearing: D - Customers
● Automatic Clearing: <see note>
Note If you select this checkbox, the matched items are cleared automatically. If you
don't select the checkbox, the matched items are cleared manually per the following
steps.
● Open Items Proposal: <scheduled jobs to receive a list of machine learning
proposals for matching receivables to existing bank statement items>
● Account Proposal: <scheduled jobs to receive a list of Machine Learning pro-
posals for matching accounts to existing bank statement items>
5 Check the Logs Monitor the job status. The status is Finished once the job has been processed. Make a note of the bank statement num-
Access the log of proposals for bank statement items sent to the SAP Cash Application. bers and company code: __________
__________
Save the bank statement number and company code to process the subsequent steps.
6 Check the ex- Choose Details and choose the Log tab. You can see the machine learning logs,
planation (Op- such as match field and match range, in
tional) Log Details.
Cash Application Integration (1MV)
Test Procedures PUBLIC 8
4.2 Scheduling Accounts Receivable Jobs – Automatic Lockbox Processing (Optional)
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Testing Date:
Tester Name: Duration:
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
With automatic lockbox processing, you can collect and process incoming payments. A prerequisite is that the lockbox service is offered by your bank (US
and CA only).
Note This step is only relevant for the US and Canada.
Prerequisites
For more information about the prerequisites, see the Lockbox (1JT) scope item.
Procedure
Execute the test procedures in the Lockbox (1JT) test script.
4.3 Extracting Payment Advice Information
Test Administration
Customer project: Fill in the project-specific parts.
Cash Application Integration (1MV)
Test Procedures PUBLIC 9
Test Case ID <X.XX> Testing Date:
Tester Name: Duration:
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This function lets you automatically extract payment advice information for further processing.
Prerequisites
Open bank statements exist in the system. If not, see the Advanced Cash Operations (J78) scope item to enter bank statements.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /
Step Comment
#
1 Log On Log on to the SAP Fiori launchpad as an Accounts Receivable
Accountant.
2 Access the SAP Open Manage Payment Advices (F2550) .
Fiori App
3 Upload the Pay- Choose Import.
ment Advice File
4 Upload the Pay- Make the following entries: The file that contains payment advice details is uploaded for automatic
ment Advice File Company Code: <company code> processing.
To upload the payment advice file (for example, advice1.pdf)
from your local environment, choose +. Locate and upload
the file.
Choose Process.
Choose OK.
Cash Application Integration (1MV)
Test Procedures PUBLIC 10
Test Test Step Name Instruction Expected Result Pass / Fail /
Step Comment
#
5 Check the Pro- Choose the Confirmation Pending (xx) tab. The tab displays the new payment advice of type 12. if you open it, you
cessing Result find the relevant information extracted from the document with machine
learning.
6 Confirm and Pro- Choose Confirm and Next. The information is stored for further processing.
ceed
Succeeding Process
For information on processing payment advices, see the Accounts Receivable (J59) scope item.
Cash Application Integration (1MV)
Test Procedures PUBLIC 11
Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles, pushbut-
tons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions. www.sap.com/contactsap
EXAMPLE Technical names of system objects. These include report names, program names, transaction
codes, table names, and key concepts of a programming language when they are surrounded
by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names
of variables and parameters, source text, and names of installation, upgrade and database
tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with
appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . © 2024 SAP SE or an SAP affiliate company. All rights re-
served.
No part of this publication may be reproduced or transmitted
in any form or for any purpose without the express permis-
sion of SAP SE or an SAP affiliate company. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distribu-
tors contain proprietary software components of other soft-
ware vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate
company for informational purposes only, without representa-
tion or warranty of any kind, and SAP or its affiliated compa-
nies shall not be liable for errors or omissions with respect to
the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in
the express warranty statements accompanying such prod-
ucts and services, if any. Nothing herein should be construed
as constituting an additional warranty.
SAP and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Ger-
many and other countries. All other product and service
names mentioned are the trademarks of their respective
companies.
See www.sap.com/copyright for additional trade-
Cash Application Integration (1MV) mark information and notices.
Test Procedures PUBLIC 12
