Professional Documents
Culture Documents
1S0 S4hana1909 BPD en Us
1S0 S4hana1909 BPD en Us
Table of Contents
1 Purpose 3
2 Prerequisites 4
2.1 System Access 4
2.2 Roles 4
2.3 Master Data, Organizational Data, and Other Data 4
2.4 Business Conditions 5
2.5 Preliminary Steps 6
2.5.1 Import Invoices Manually 6
2.5.2 Display Open Invoices 7
2.5.3 Create a Manual Input Bank Statement 8
3 Overview Table 12
4 Test Procedures 14
4.1 Assign Payment Methods 14
4.1.1 Match Payments with Invoices (Alternative 1) 14
4.1.1.1 Display Customer Account 16
4.1.1.2 Clear Open Items Manually 17
4.1.2 Assign Credit Card Payment Method (Alternative 2) 18
4.1.2.1 Authorization Saved 21
4.1.2.2 Payment Run 21
4.1.2.2.1 Schedule Payment Proposals 21
4.1.2.2.2 Release Payment Proposal 23
4.2 Display My Accounts 25
4.3 Display My Account Statements 27
5 Appendix 29
5.1 Succeeding Processes 29
The customer payments scope item is a public cloud solution delivered in the SAP Cloud Platform for electronic bill presentment and payment.
The integration between SAP S/4HANA and the customer payments solution allows users to view open invoices and customer master data from SAP S/4HANA.
You can pay open invoices or assign one or more invoices to an existing payment.
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.
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and
business conditions.
Syste Details
m
Syste Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned
m to your role.
2.2 Roles
Use the following standard test users or assign roles to testers, respectively:
Note The following roles are provided as example roles from SAP. You can use these as templates to create your own roles.
Purpose
In this activity, you post customer invoices in accounting. Journal Entries are created.
Prerequisites
Purpose
Prerequisite
Procedure
Purpose
A customer invoice must be available to follow the test procedures. If no credit balance is available in the system, then create one using the following
procedure. The steps must be completed before assigning the payment method of matching payment to invoices.
Prerequisite
When creating an incoming payment item in a manual bank statement, enter the customer number and text in the memo line that is displayed in the Match
Payments app, with invoices (in our example, its manual transaction F001 with interpretation algorithm 001).
Procedure
The Customer Payments (1S0) test script consists of several process steps and reports provided in the table below.
This section describes test procedures for each process step that belongs to this scope item.
Purpose
There are multiple alternatives for the user to assign payments in the system.
Match payments with invoices allows the user to take existing credits in the system and apply to outstanding invoices.
Assign credit card as the payment method describes how the user applies a credit card for paying outstanding invoices.
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Prerequisite
There must be an existing customer credit balance and an open customer invoice before you can proceed with this procedure. If an existing customer credit
balance is not available, see the Create a Manual Input Bank Statement topic in the Preliminary Steps under Prerequisites. If an open customer invoice is not
available, see the Import Invoice Manually topic in the Preliminary Steps under Prerequisites.
Procedure
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
The Accounts Receivable Accountant follows the procedure to determine the customer number after receiving the new payment advice email.
Prerequisite
A new payment advice email is received after the customer has completed the previous procedure.
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
The Accounts Receivable Accountant follows the procedure to clear open invoices manually, according to the information received in a payment advice email
from the previous procedure.
Prerequisites
Procedure
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
In this activity, you select open bills or credit items to pay and make payments with a credit card.
Prerequisite
An open customer invoice is available. If an open customer invoice is not available, see the Import Invoice Manually topic in the Preliminary Steps under
Prerequisites.
Procedure
Context
Purpose
The Payment Run section describes how to post payment using the automatic payment program.
Invoices are posted and are open for payment.
Prerequisite
The Assign Credit Card Payment Method procedure steps must be completed before proceeding with these steps.
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
Procedure
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
Procedure
Succeeding Processes
Caution Digital Payments (1S2) provides additional procedures for automatic payments for credit card and must be completed after completing all the
procedures in this scope item.
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
Prerequisite
Accounts associated with a credit card or bank account must already exist in the system.
Procedure
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
Type Description
Style
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
www.sap.com/contactsap
Example Emphasized words or expressions.
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 © 2019 SAP SE or an SAP affiliate company. All rights
by body text, for example, SELECT and INCLUDE. reserved.
No part of this publication may be reproduced or transmitted
Example Output on the screen. This includes file and directory names and their paths, messages, names in any form or for any purpose without the express
permission of SAP SE or an SAP affiliate company.
of variables and parameters, source text, and names of installation, upgrade and database
The information contained herein may be changed without
tools. prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components
Example Exact user entry. These are words or characters that you enter in the system exactly as they of other software vendors. National product specifications
may vary.
appear in the documentation.
These materials are provided by SAP SE or an SAP affiliate
company for informational purposes only, without
<Exampl Variable user entry. Angle brackets indicate that you replace these words and characters with
representation or warranty of any kind, and SAP or its
e> appropriate entries to make entries in the system. affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP or
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . SAP affiliate company products and services are those that
are set forth in the express warranty statements
accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no
obligation to pursue any course of business outlined in this
document or any related presentation, or to develop or
release any functionality mentioned therein. This document,
or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments,
products, and/or platforms, directions, and functionality are
all subject to change and may be changed by SAP SE or its
affiliated companies at any time for any reason without
notice. The information in this document is not a
commitment, promise, or legal obligation to deliver any
material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that
could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue
reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered
Customer Payments (1S0_US) PUBLIC in
trademarks of SAP SE (or an SAP affiliate company)
Purpose Germany and other Error: Reference
countries. source
All other not found
product and service 30
names mentioned are the trademarks of their respective
companies.