Professional Documents
Culture Documents
Table of Contents
1 Purpose 2
2 Prerequisites 3
2.1 System Access 3
2.2 Roles 3
2.3 Master Data, Organizational Data, and Other Data 3
2.4 Business Conditions 4
3 Overview Table 6
4 Test Procedures 7
4.1 Upload Lockbox Files 7
4.2 Schedule Lockbox Jobs 10
4.3 Manage Lockbox Batches 14
4.4 Reprocess Incoming Checks 15
1 Purpose
With lockbox processes, customer can simply collect and process incoming payments if the lockbox service is offered by banks in the United States of
America.
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
Assign the following business roles to your individual test users.
Note The following roles are provided as example roles from SAP. You can use these as templates to create your own roles.
The Lockbox scope item consists of several process steps provided in the following table.
This section describes test procedures for each process step that belongs to 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
In this activity, you clear customer invoices and create bank journal entries. There are two options provided. The first option is the recommended option,
using the Manage Incoming Payment Files (F1680) SAP Fiori app. The second option is using the Upload Lockbox Files (FLB2) SAP Fiori app.
Prerequisites
A lockbox is created with the lockbox number, destination, origin, and valid customer invoices.
The file uses the date format of yymmdd.
The upload file requires a specific BAI2 format. If the BAI2 format received from the issuing bank does not match the SAP BAI2 format, the file cannot be
processed.
Lockbox (1JT_US) PUBLIC
Purpose Error: Reference source not found 7
For more information, see the Steps to Create the BAI2 File document, provided on the SAP Support Portal.
Note For the list of open invoices, by customer, to use for this test, run the Manage Customer Line Items (F0711) SAP Fiori app as aAccounts Receivable
Accountant role.
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
Note Automatic Lockbox Reprocessing is optional because it requires you have implemented SAP Cash Applications, which requires a separate, additional
license.
When implemented, automatic reprocessing is applied to certain business scenarios. Currently, Automatic Lockbox Reprocessing can only be used for
Unprocessed or Posted on acct business scenarios.
Restriction Processing for the Part. applied business scenario is currently not available.
In this activity, you schedule the background job processing. Unprocessed Lockbox statements can be matched to invoices, automatically, to clear open
items that didn’t get cleared during the previous Upload Lockbox Files procedure.
Prerequisite
Unprocessed or posted on account Lockbox files exist in the SAP S/4HANA system.
A connection to the machine learning (ML) server exists and all open invoices from the SAP S/4HANA system have been imported into the ML server.
The Cash Application Integration(1MV) scope item is implemented and the procedures completed.
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
This report provides the posting details for posted lockbox batches.
Prerequisite
Procedure
Test Administration
Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Purpose
Lockbox processing creates payment advices for any payment that cannot be applied fully. These payment advices are stored and post processing uses
these advices to correctly make payments to the customer. Use this process for Unprocessed, Posted on Acct, or Part. applied business scenarios.
Caution Do not use the Reprocess Incoming Checks - From Lockbox (FEBA_LOCKBOX) app, if the status is Applied when the Lockbox file was uploaded.
Prerequisite
Lockbox processing has been performed and lockbox data exists to be reprocessed. There are three scenarios requiring reprocessing of incoming checks:
● Scenario 1: Unprocessed - Neither the customer account nor the invoice could be found in the system. Create a new file with incorrect invoice number and
incorrect customer number (MICR number).
Procedure
5 Scenario 3 - Under Processing Status, since none of the invoices have been Not Assigned displays 0.00 and the
Lockbox (1JT_US) PUBLIC
Purpose Error: Reference source not found 17
Activate Item selected, the Assigned field displays a negative number and the document is ready to be cleared.
Not Assigned field displays the amount to be cleared. The Not Note In the selected Document Number row,
Assigned field must be 0.00 to post the document. red boxes display for CashDiscount and
From the details of all the customer document numbers available CDPer fields. Either enter a discount or skip,
for clearing, select the row of the document number to cleared. if no discount applies.
Choose the (Activate) Items button.
6 Scenario 3 - Choose Post and continue with the Final Step. The Lockbox: process checks view displays.
Post The Document XXXXXXXXXX was posted in
company code YYYY notification displays and
the status becomes a green square.
Final Display Item Expand the LOCKBOXDES LOCKBOXORI node and double-click the The 2 Document field displays the document
Step Details line with the green square icon. number from the previous step.
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
Lockbox (1JT_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 19
names mentioned are the trademarks of their respective
companies.