Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Purpose © 2017 SAP SE or an SAP affiliate company. All rights reserved. 1

Test Script CUSTOMER
SAP S/4HANA - 09-08-17

Bank Integration with SAP Financial Services Network

(16R_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 Create pain.002.001.03_I071234_01.xml 6
2.5.2 Create camt.053.001.02_I071234_01.xml 8

3 Overview Table 12

4 Test Procedures 13
4.1 Outgoing Integration 13
4.1.1 Create Payment Medium 13
4.1.2 Send Payment Instruction to FSN 14
4.1.3 Pull Status Message from FSN 16
4.2 Incoming Integration 19
4.2.1 Pull Bank Statement from FSN 19
4.2.1.1 ISO CAMT.053 Format 19
 4.2.1.2 BAI2 Format 22
4.2.2 Import Electronic Bank Statement 26

5 Appendix 28
5.1 Process Integration 28
5.2 Preceding Processes 28
5.3 Succeeding Processes 29

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Purpose © 2017 SAP SE or an SAP affiliate company. All rights reserved. 2
1 Purpose

With SAP Financial Services Network, you can automatically connect to your banks to send payment instructions, receive status notifications, and receive bank statements. In monitoring, you
can supervise the status of the payment instructions and see which bank statements have come and which expected bank statements are still missing.
This document provides a detailed procedure for testing the scope item after solution deployment, reflecting the predefined scope of the solution. Each process step is covered in its own section,
providing the system interactions (that is, test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly (see the Test Step column).
Customer-project-specific steps must be added.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Purpose © 2017 SAP SE or an SAP affiliate company. All rights reserved. 3
2 Prerequisites

This section summarizes all prerequisites needed to conduct the test in terms of system, users, master data, organizational data, and other test data and business conditions.

2.1 System Access

The test should be conducted with the following system:

System Details

System Accessible via the SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.

2.2 Roles
Assign the following business roles to your individual test users.
The following roles are provided as example roles from SAP. You can use these as templates for your own roles.

Business Role Business Role ID Log On

Cash Management Special- SAP_BR_CASH_SPECIAL- Suggested sample user CASH_SPECIALIST in SAP S/4HANA Cloud representing the business role Cash Management Special-
ist IST ist.

For more information about business roles, refer to Assigning business roles to a user in the Administration Guide for the Implementation of SAP S/4HANA.

2.3 Master Data, Organizational Data, and Other Data

The organizational structure and master data of your company has been created in your system during activation. The organizational structure reflects the structure of your company. The
master data represents materials, customers, and vendors, for example, depending on the operational focus of your company.
Use your own master data to go through the test procedure. If you have installed an SAP Best Practices baseline package, you can use the following baseline package sample data:

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 4
 Data Sample Value Details Comments
Bank 011000390 820800001

House Bank USBK1 USBK2

House Bank Account ID USAC1

Bank Account Number 33333

25800611

Country US

Company Code 1710

SWIFT/BIC BOFAUS3M
CITIUS33MIA

Currency USD

2.4 Business Conditions

Before this scope item can be tested, the following business conditions must be met.

Scope Item Business Condition

J60 - Accounts Payable and/or If the Full (Extended) Cash Management is implemented, before the test step Outgoing Integration ensure that either:
J78 - Advanced Cash Operations and ● The payment run has been executed and the paying house bank uses the payment medium format for FSN connectivity in test
BFB - Basic Cash Operations script Accounts Payable (J60), and the BCM batch has been approved the step Approval and Bank Integration in test scrip Basic
Cash Operations (BFB).
● A bank transfer is made and the paying house bank uses the payment medium format for FSN connectivity in test script Advanced
Cash Operations (J78), and the BCM batch has been approved in the step Approval and Bank Integration in test script Basic Cash
Operations (BFB).

J60 - Accounts Payable and If the Basic (Core) Cash Management is implemented, before the test step Outgoing Integration ensure that: The payment run has
BFB - Basic Cash Operations been executed and the paying house bank uses the payment medium format for FSN connectivity in test script Accounts Payable (J60),
the process is linked to current test script Bank Integration with SAP Financial Services Network (16R) via a process interface men-
tioned in in the step Accounts Payable Bank Integration in test script Basic Cash Operations (BFB), because no approval is needed (no
BCM approval function is provided) when using Basic (Core) Cash Management.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 5
 Scope Item Business Condition
BD9 - Sell from Stock (for SAP S/4HANA Enter- Before the test step Incoming Integration ensure that either:
prise Management or SAP S/4HANA Enterprise ● Another tester has created a billing document, and its customer item is open (uncleared). You can find open customer items in the
Management Cloud) or app Manage Customer Line Items; in order to run this app, add accounts receivable related roles to your user, you may find these
J14 - Sales Order Processing - Project-Based Ser- roles in the test script Accounts Receivable (J59).
vices (for SAP S/4HANA Enterprise Management ● If you cannot find an existing open customer item, create a billing document by yourself. You can use test script BD9 or J14 to cre-
Cloud or SAP S/4HANA Professional Services ate a billing document.
Cloud)
Make a note of the amount and reference (XBLNR in the header) of the FI document of billing document. This information is needed to
or any other scope items creating customer invoice simulate the incoming payment (credit) item in an electronic bank statement. In the bank statement, a credit item can be reconciled
with customer invoice.

2.5 Preliminary Steps

2.5.1 Create pain.002.001.03_I071234_01.xml

Purpose

This file is required for a later process step.

The xml file name must contain the string ‘pain.002.001.03’ (for example, pain.002.001.03_I071234_01.xml). Because FSN does not accept files with the same name, and more than one tester is
testing this scenario, always use a different file name each time you test this step, and replace I071234 with a different ID you specified.

Procedure

1. In a text editor, paste the following code:

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.03">
<CstmrPmtStsRpt>
<GrpHdr>
<MsgId>BBBB/100928-PSR/00120141222054500</MsgId>
<CreDtTm>2014-12-22T05:45:00</CreDtTm>
Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER
Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 6
 <InitgPty>
<Nm>Tools Inc. America</Nm>
<PstlAdr>
<StrtNm>Times Square</StrtNm>
<BldgNb>7</BldgNb>
<PstCd>NY 10036</PstCd>
<TwnNm>New York</TwnNm>
<Ctry>US</Ctry>
</PstlAdr>
</InitgPty>
<DbtrAgt>
<FinInstnId>
<BIC>BOFAUS3M</BIC>
</FinInstnId>
</DbtrAgt>
</GrpHdr>
<OrgnlGrpInfAndSts>
<OrgnlMsgId>1000004611</OrgnlMsgId>
<OrgnlMsgNmId>pain.001.001.03</OrgnlMsgNmId>
<OrgnlCreDtTm>2014-12-21T20:38:42</OrgnlCreDtTm>
<OrgnlNbOfTxs>1</OrgnlNbOfTxs>
<OrgnlCtrlSum>1191.72</OrgnlCtrlSum>
</OrgnlGrpInfAndSts>
<OrgnlPmtInfAndSts>
<OrgnlPmtInfId>1000004611</OrgnlPmtInfId>
<OrgnlNbOfTxs>000000001</OrgnlNbOfTxs>
<OrgnlCtrlSum>1191.72</OrgnlCtrlSum>
<PmtInfSts>ACSP</PmtInfSts>
<TxInfAndSts>
<OrgnlEndToEndId>17102000000125</OrgnlEndToEndId>
<TxSts>ACSP</TxSts>
<OrgnlTxRef>
<Amt>
<InstdAmt Ccy="USD">1191.72</InstdAmt>
</Amt>
<ReqdExctnDt>2014-12-23</ReqdExctnDt>
<PmtMtd>TRF</PmtMtd>
<RmtInf>
<Ustrd>PREF:TEST FOR PAIN.002</Ustrd>
</RmtInf>
<Cdtr>
<Nm>TEST SE</Nm>
Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER
Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 7
 </Cdtr>
</OrgnlTxRef>
</TxInfAndSts>
</OrgnlPmtInfAndSts>
</CstmrPmtStsRpt>
</Document>

1. Save the file to a folder on your PC as pain.002.001.03_I071234_01.xml.

2.5.2 Create camt.053.001.02_I071234_01.xml

Context

This file is required for a later process step.

The xml file name must contain the string ‘camt.053.001.02’ (for example, camt.053.001.02_I071234_01.xml). Because FSN does not accept files with the same name, and more than one tester is
testing this scenario, always use a different file name each time you test this step, and replace I071234 with a different ID you specified.

Procedure

1. In a text editor, paste the following code:

<?xml version="1.0" encoding="utf-8"?>
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:camt.053.001.02">
<BkToCstmrStmt>
<GrpHdr>
<MsgId>20141222102146</MsgId>
<CreDtTm>2014-12-22T00:00:00</CreDtTm>
<MsgPgntn>
<PgNb>00001</PgNb>
<LastPgInd>false</LastPgInd>
</MsgPgntn>
</GrpHdr>
<Stmt>
<Id>CAMSLINK01000249</Id>
<ElctrncSeqNb>00006</ElctrncSeqNb>
Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER
Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 8
 <CreDtTm>2014-12-22T00:00:00</CreDtTm>
<Acct>
<Id>
<Othr>
<Id>33333</Id>
</Othr>
</Id>
<Svcr>
<FinInstnId>
<BIC>BOFAUS3M</BIC>
</FinInstnId>
</Svcr>
</Acct>
<Bal>
<Tp>
<CdOrPrtry>
<Cd>PRCD</Cd>
</CdOrPrtry>
</Tp>
<Amt Ccy="USD">5002.30</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Dt>
<Dt>2014-12-22</Dt>
</Dt>
</Bal>
<Bal>
<Tp>
<CdOrPrtry>
<Cd>CLBD</Cd>
</CdOrPrtry>
</Tp>
<Amt Ccy="USD">4018.83</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Dt>
<Dt>2014-12-22</Dt>
</Dt>
</Bal>
<Ntry>
<Amt Ccy="USD">208.25</Amt>
<CdtDbtInd>CRDT</CdtDbtInd>
<Sts>BOOK</Sts>
<BookgDt>
Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER
Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 9
 <Dt>2014-12-22</Dt>
</BookgDt>
<ValDt>
<Dt>2014-12-22</Dt>
</ValDt>
<AcctSvcrRef>FSN TEST AcctSvcrRef Item 1</AcctSvcrRef>
<BkTxCd>
<Prtry>
<Cd>PMNTRCDTDMCT</Cd>
</Prtry>
</BkTxCd>
<NtryDtls>
<TxDtls>
<Refs>
<ChqNb>MMTEST</ChqNb>
</Refs>
<AddtlTxInf>4711</AddtlTxInf>
</TxDtls>
</NtryDtls>
<AddtlNtryInf>4711</AddtlNtryInf>
</Ntry>
<Ntry>
<Amt Ccy="USD">1191.72</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<Sts>BOOK</Sts>
<BookgDt>
<Dt>2014-12-22</Dt>
</BookgDt>
<ValDt>
<Dt>2014-12-22</Dt>
</ValDt>
<AcctSvcrRef>FSN TEST AcctSvcrRef Item 1</AcctSvcrRef>
<BkTxCd>
<Prtry>
<Cd>PMNTICDTDMCT</Cd>
</Prtry>
</BkTxCd>
<NtryDtls>
<TxDtls>
<Refs>
<ChqNb>1000004611</ChqNb>
</Refs>
Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER
Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 10
 <AddtlTxInf>4712</AddtlTxInf>
</TxDtls>
</NtryDtls>
<AddtlNtryInf>4712</AddtlNtryInf>
</Ntry>
<AddtlStmtInf>FSN Test AddtlSmtInf</AddtlStmtInf>
</Stmt>
</BkToCstmrStmt>
</Document>

2. Save the file to a folder on your PC as camt.053.001.02_I071234_01.xml.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Prerequisites © 2017 SAP SE or an SAP affiliate company. All rights reserved. 11
3 Overview Table

Adjust the following process overview table to suit your scope item by listing all process step, report, or items described in this document (see example below).

Process Step, Report or Business Role Transac- Expected Results

Item tion/App
Create Payment Me- Cash Management
dium Specialist

Send Payment Instruc- Cash Management The payment medium file is sent to FSN and shows up in the correct folder of SFTP server.
tion to FSN Specialist

Pull Status Message Cash Management Bank sends the payment status message to FSN to acknowledge that payment medium file has been accepted by bank. And
from FSN Specialist S/4HANA system pulls the payment status message from FSN.

Pull Bank Statement Cash Management FSN maps the local bank statement format to ISO CAMT.053 format, and S/4HANA system pulls the ISO CAMT.053 bank
from FSN Specialist statement from FSN.

Import Electronic Bank Cash Management After the CAMT.053 bank statement is pulled from FSN, the electronic bank statement is imported automatically, and the
Statement Specialist postings in bank accounting and subledger accounting should be carried out.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Overview Table © 2017 SAP SE or an SAP affiliate company. All rights reserved. 12
4 Test Procedures

This section describes test procedures for each process step that belongs to this scope item.

4.1 Outgoing Integration

4.1.1 Create Payment Medium

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Purpose

In this process step, the payment medium file (DME file) for payment medium format of FSN connectivity is created automatically. Some steps need to be done in advance, see section Prerequi-
site.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 13
Prerequisite

If the Full (Extended) Cash Management has been implemented together with BCM (Bank Communication Management), after the outgoing payment is executed (whether through the payment
run for vendor in Accounts Payable (J60) test script, or making bank transfer in Advanced Cash Operations (J78) test script), and the BCM batch of this outgoing payment is approved (described
in step Approval and Bank Integration in Basic Cash Operations (BFB) test script), the payment medium file will be created automatically.
If the Basic (Core) Cash Management has been implemented, after the payment run is executed (described in Accounts Payable (J60) test script), the payment medium file will be created auto-
matically if the payment method is using PMW format.
Because Basic and Full Cash Management cannot be tested in the same client at the same time, please contact test organizer to make sure which verison of Cash Management should be tested
in current testing client.
Test scripts relevant to Basic Cash Operations (part of Basic Cash Management) are:
● BFB: sections only valid to Basic Cash, and sections valid to Basic Cash and Full Cash
Test scripts relevant to Full Cash Operations (part of Full Cash Management) are:
● BFB: sections only valid to Full Cash, and sections valid to Basic Cash and Full Cash
● J78: all sections
If in customizing, the PMW (payment medium workbench) medium format for FSN connectivity is assigned to the payment method as the default format. The payment medium file will be sent
to FSN automatically when S/4HANA system is connected to FSN, which will be described in next step.

Procedure

This step is done automatically.

4.1.2 Send Payment Instruction to FSN

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 14
Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Context

If the S/4HANA system is integrated with FSN, and a payment medium with PMW format for FSN connectivity is created, the payment medium file is sent to FSN automatically via FSN con-
nector, and this payment medium file will show up in the SFTP folder if this file has no error.
In this step, you check if the payment medium file reaches the SFTP server successfully.

Procedure

Test Test Step Instruction Expected Result Pass /

Step Name Fail /
# Comment
1 Access Access the SFTP folder.
Folder For example : /home/S4HTESTHCI/simbank/inbox/s4hana/v0115/BankConnectivity/Bank_Mod-
elS/QE4212/PAIN.001.001.03/BOFAUS3M
The path of the SFTP server folder depends on testing system, tenant, payment medium format, SWIFT/BIC of
house bank.
Please note the path provided in this test script is only an example, to get the specific path in SFTP folder for your
specific testing system&client and get the information about how to access the SFTP folder, please contact test
organizer for help.
In the example, this path stores the payment files with format ISO PAIN001 Credit Transfer (format depends
which payment method and paying house bank you used) which are sent out from system QE4 client 212 to FSN
tenant v0115, and the paying house bank’s SWIFT/BIC is BOFAUS3M (the SWIFT/BIC of house bank USBK1).

2 Check File Check if payment medium file is in the SFTP server folder. You should see a new file (such The payment medium file exists.
Existence asDTA150925051453_0279.xml) in the folder. The payment medium file was
sent to FSN successfully after
batch approval.

3 Open and Open and review the xml file to determine if the information (such as amount, bank’s information) is consistent
Review File with the outgoing payment from a house bank account you approved.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 15
 Test Test Step Instruction Expected Result Pass /
Step Name Fail /
# Comment
4 Note Down Make a note of the values of the following fields in the xml file:
Message ● <MsgId>Message ID</MsgId>. For example, 1000004611
Number
● <PmtInfId>Payment Information ID</PmtInfId> for example, 1000004611
● <CtrlSum>Amount</CtrlSum> for example, 1191.72
● <EndToEndId>Payment Document Number</EndToEndId> for example: 17102000000125
For example:
• Message ID: 1000004611
• Payment information ID: 1000004611
• Amount: 1191.72
• Payment document number: 17102000000125
Note An XML file may contain several payment documents. In this example, there is only one payment
document in the XML file.
Caution For the non-pain.001 payment medium formats (neither CGI credit transfer nor SEPA credit transfer), it is
possible that the information listed previously (, , etc.) cannot be found. For these payment media, skip the cur-
rent test step and next step Pull Satus Message from FSN.

4.1.3 Pull Status Message from FSN

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 16
Purpose

The bank sends the payment status file to FSN to acknowledge that payment medium file has been accepted. The system pulls the payment status file from FSN automatically.
When testing in SAP S/4HANA system with Basic Cash Management, skip this step. Bank Communication Management (BCM) is not in scope. The Status Message that is pulled from FSN cannot
update the BCM status.

Prerequisite

In the preliminary steps of Prerequisite section, you created the file pain.002.001.03_I071234_01.xml.
Procedure

Test Test Step Instruction Expected Result Pass /

Step Name Fail /
# Com-
ment
1 Retrieve the In the prerequisite steps, you created an XML file using provided text and added to a folder of your system.
XML file The XML file name must contain the string pain.002.001.03, for example,
from your lo- pain.002.001.03_I071234_01.xml.
cal drive
Retrieve the file for this procedure.
Because FSN does not accept files with the same name, and more than one tester is testing this scenario,
always use a different file name each time you test this step, and replaceI071234_01 with a different ID
you specified.

2 Open the Use a plain text editor to open the xml file.
XML file

3 Edit XML Replace the values of the following fields in file pain.002.001.03_I071234_01.xml by the values you noted
file down in the Send Payment Instruction to FSNstep, and save file pain.002.001.03_I071234_01.xml in your PC.
The values in the note below are example values. Use the values from step Send Payment Instruction to
FSN.
Note XML Values:
● <MsgId>Message ID</MsgId>, for example <MsgId> BBBB/100928-PSR/00120141222054500</MsgId>
(00120141222054500 is the real system data and time 001YYYYMMDDHHMMSS)
● <BIC>BIC</BIC>, for example, <BIC>BOFAUS3M</BIC> You can find the BIC of house bank USBK1 in app
Manage Banks

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 17
 Test Test Step Instruction Expected Result Pass /
Step Name Fail /
# Com-
ment
● <OrgnlMsgId>Original Message ID</OrgnlMsgId>, for example, <OrgnlMsgId>1000004611</OrgnlMs-
gId>
● <OrgnlCtrlSum>Amount</OrgnlCtrlSum> in <OrgnlGrpInfAndSts></OrgnlGrpInfAndSts>, for example,
<OrgnlCtrlSum>1191.72</OrgnlCtrlSum>
● <OrgnlPmtInfId>Original Payment Information ID</OrgnlPmtInfId>, for example, <OrgnlPmtIn-
fId>1000004611</OrgnlPmtInfId>
● <OrgnlCtrlSum>Amount</OrgnlCtrlSum> in <OrgnlPmtInfAndSts>< /OrgnlPmtInfAndSts>, for exam-
ple, <OrgnlCtrlSum> 1191.72</OrgnlCtrlSum>
● <OrgnlEndToEndId>Payment Document Number</OrgnlEndToEndId>, for example, <OrgnlEndToEn-
dId>17102000000125</OrgnlEndToEndId>
● <InstdAmt Ccy="USD">Amount</InstdAmt>, for example, <InstdAmt Ccy="USD">1191.72</InstdAmt>

4 Upload XML Upload the XML file you edited to the SFTP server folder. The xml file disappears from the SFTP
file to the For example, upload to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE4212/US BANK 1 server folder. A background job is
SFTP server scheduled to pull the payment status
from FSN to the S/4HANA system every
10 minutes.

5 Path of SFTP Note The path of SFTP server folder for payment status messages depends on testing system, country and
Server Folder house bank. If you want to get sufficient information on how to access the FSN bank tenants or SFTP server,
please contact test organizer for help. In this example, a PAIN002 file for house bank/account ID
USBK1/USAC1 in country US is pulled from FSN.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 18
4.2 Incoming Integration

4.2.1 Pull Bank Statement from FSN

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Purpose

For banks with FSN connection for example, USBK1 Bank statements are handled by FSN. FSN maps the local bank statement format to an ISO CAMT.053 format, and the SAP S/4HANA system
pulls the ISO CAMT.053 bank statement from FSN and then importing it automatically.

4.2.1.1 ISO CAMT.053 Format

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 19
Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

camt.053.001.002_I0.71234_01 XML File

In the Preliminary Steps in Prerequisites section, you created an xml file and saved it to a folder of your PC.
The xml file name must contain the string camt.053.001.02, for example, camt.053.001.02_I071234_01.xml.
Because FSN does not accept files with the same name, and more than one tester is testing this scenario, use a different file name every time when you test this step, and replace I071234 by a
different ID you specified.
Access that XML file and using a text editor, edit file for these XML Values:
● <MsgId>Message ID</MsgId>, for example, <MsgId>20141222102146</MsgId> (20141222102146 is the real system data and time YYYYMMDDHHMMSS)
● <ElctrncSeqNb>Bank Statement Number</ElctrncSeqNb>, for example, <ElctrncSeqNb>00006</ElctrncSeqNb> which should be the next bank statement number
● <Id>Account Number</Id> in <Othr></Othr>, for example, <Id>33333</Id> which is the account number of house bank/account ID USBK1/USAC1
● <BIC>BIC</BIC>, for example, <BIC>BOFAUS3M</BIC>
You can find the BIC of house bank USBK1 in the Manage Banks app.
● <Amt Ccy="USD">Opening Balance</Amt> in the first <Bal></Bal>, for example, <Amt Ccy="USD">5002.30</Amt> Opening balance = closing balance of latest imported bank statement.
● <Dt>Opening Balance Date</Dt> in the first <Bal></Bal>, for example, <Dt>2014-12-22</Dt>
● <Amt Ccy="USD">Closing Balance</Amt> in the second <Bal></Bal>, for example, <Amt Ccy="USD">4018.83</Amt> Closing balance = opening balance – debit amount + credit amount; For
example, 4018.83=5002.30+208.25-1191.72
● <Dt>Closing Balance Date</Dt> in the second <Bal></Bal>, for example, <Dt>2014-12-22</Dt>
● <Amt Ccy="USD">Item Amount</Amt> in the first <Ntry></ Ntry>, for example, <Amt Ccy="USD">208.25</Amt> which represents the amount of customer invoice
● <BookgDt><Dt>Booking Date</Dt></BookgDt> in the first <Ntry></ Ntry>, for example, <BookgDt><Dt>2014-12-22</Dt></BookgDt>
● <ValDt><Dt>Value date</Dt></ValDt> in the first <Ntry></ Ntry>, for example, <ValDt><Dt>2014-12-22</Dt></ValDt>
● <ChqNb>Reference</ChqNb> in the first <Ntry></ Ntry>, for example, <ChqNb>MMTEST</ChqNb> which is the reference of customer invoice.
● <Amt Ccy="USD">Item Amount</Amt> in the second <Ntry></ Ntry>, for example, <Amt Ccy="USD">1191.72</Amt> which is the payment amount in step Send Payment Instruction to FSN.
● <BookgDt><Dt>Booking Date</Dt></BookgDt> in the second <Ntry></ Ntry>, for example, <BookgDt><Dt>2014-12-22</Dt></BookgDt>
● <ValDt><Dt>Value date</Dt></ValDt> in the second <Ntry></ Ntry>, for example, <ValDt><Dt>2014-12-22</Dt></ValDt>
● <ChqNb>Reference</ChqNb> in the second <Ntry></ Ntry>, for example, <ChqNb>1000004611</ChqNb> which is the Payment information ID in step Send Payment Instruction to FSN.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 20
Prerequisite

As already described in the Business Conditions section, find a customer invoice created by another tester (the customer item must be uncleared), or perform step Enter Invoice without Sales
Order in Accounts Receivable (J59), or Sell from Stock (BD9), Sales Order Processing - Project-Based Services (J14) to create a customer invoice. Make a note of amount and reference (XBLNR in
the header) of the customer invoice document. You need this information when simulating an electronic bank statement.

Procedure

Perform the following steps to simulate an ISO CAMT.053 bank statement for house bank/account ID USBK1 /USAC1 directly FSN will get it form SFTP server, an dthe S/4HANA system will pull
the ISO CAMT.053 bank statements from FSN.
In this example, the simulated bank statement contains two line items:
● First item: a credit item which should be reconciled with an existing customer invoice, the customer invoice should have been already created (see the Prerequisites).
● Second item: a debit item that should be reconciled with the payment document created in section Send Payment Instruction to FSN.

Test Test Step Name Instruction Expected Result Pass /

Step Fail /
# Com-
ment
1 Log on Log onto the SAP Fiori Launchpad as a Cash Management Specialist. The SAP Fiori Launchpad displays.

2 Access the SAP Fiori Open Manage Bank Statements. The screen Manage Bank Statements displays.
app

3 Get Latest Bank State- To get the latest imported bank statement number, choose Show Filter Bar if search The latest bank statement number of the specified
ment Number criteria are hidden, and make the following entries: bank account displays on the screen Manage Bank
Company Code: 1710 Statements.

House Bank: USBK1 The next bank statement number is one greater than
the latest bank statement number. For example, if the
House Bank Account: USAC1
latest bank statement number is 00005, the next num-
Latest Statement: Latest only ber is 00006. If no latest bank statement was found,
and choose Go. the next number should be 00001.

4 Get Closing Balance of Make a note of the closing balance of the specified bank account. It can be found on The closing balance of the latest bank statement
Latest Bank Statement the screen Manage Bank Statements. should be the opening balance of the next bank state-
ment.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 21
 Test Test Step Name Instruction Expected Result Pass /
Step Fail /
# Com-
ment
If no latest bank statement was found, the opening
balance of the next bank statement should be zero.

5 Access the Open the camt.053 xml file with a text editor, for example,
camt.053.001.02 XML camt.053.001.02_I071234_01.xml. Because FSN does not accept files with the same
file previously created name, and more than one tester is testing this scenario, use a different file name
every time when you test this step, and replace I071234 by a different ID you speci-
fied.

6 Edit xml file Modify the XML file as shown in the previous Prerequisites.
In the ISO CAMT.053 bank statement file, always use ‘.’ as decimal point (don't use
‘,’). And the date format should be YYYY-MM-DD.

7 Upload XML file to the Upload the xml file you edited to the SFTP server folder. The xml file is removed from the SFTP server folder in
SFTP server For example, copy to the folder /home/S4HTESTHCI/simbank/out- several seconds. A background job is scheduled to pull
box/s4hana/v0115/QE421 2/US/BANK1 the bank statement from FSN to the S/4HANA system
every 10 minutes.

The path of the SFTP server folder for bank statements depends on testing system,
tenant, country, and house bank.
If you want to get sufficient information on how to access the FSN bank tenants or
SFTP server, please contact test organizer for help.
In this example, a CAMT.053 file for house bank/account ID USBK1/USAC1 in coun-
try US is pulled from FSN.

4.2.1.2 BAI2 Format

Test Administration

Customer project: Fill in the project-specific parts.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 22
Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Prerequisite

As already described in section Business Condition, find a customer invoice created by another tester (the customer item must be uncleared), or perform step Enter Invoice without Sales Order in
Accounts Receivable (J59), or Sell from Stock (BD9), Sales Order Processing - Project-Based Services (J14) to create a customer invoice. Make a note of the amount and reference (XBLNR in the
header) of the customer invoice document. You need this information when simulating an electronic bank statement.
Perform step Bank Transfer Actions in test script J78 and step Approval and Bank Integration in test script BFB again : make a bank transfer from bank account 33333 of bank 011000390 to
bank account 25800611 of bank 820800001 , amount USD 1191,72, use payment method ISO PAIN001: Credit Transfer, please note down the information described in step Pull Status Mes-
sage from FSN.
Create a new text file and name it BAI2_US_USBK1_00006.txt. Enter the following text into it and save it locally on your PC:
01,Test FSN ,Test Receiver,151116,0235,1,99,99,2/
02,Test Receiver, 011000390,1,151116,0235,USD/
03,33333,USD,010,500230,,,015,401883,,,045,13600000,,,/
16,195,20825,0,0,20825,0,TestPayref1,0815,Test Text Item 1/
88,0090000008/
16,455,119172,0,TestPayref2,1000004612,Test Text Item 2/
49,1500320062,99/
98,1500320062,1,99/
99,1500320062,1,99/

Procedure

Perform the following steps to simulate a BAI2 bank statement for house bank/account ID USBK1/USAC1, FSN will map the BAI2 statement format to an ISO CAMT.053 format automatically,
and the S/4HANA system will pull the ISO CAMT.053 bank statement from FSN.
In this example, the simulated bank statement contains two line items:
● First item: a credit item which should be reconciled with an existing customer invoice, the customer invoice should have been already created (see the Prerequisites).
● Second item: a debit item that should be reconciled with the payment document created in Send Payment Instruction to FSN.
Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER
Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 23
 Test Test Step Instruction Expected Result Pass /
Step Name Fail /
# Com-
ment
1 Log on Log onto the SAP Fiori Launchpad as a Cash Management Specialist. The SAP Fiori Launchpad displays.

2 Access the Open Manage Bank Statements. The screen Manage Bank Statements
SAP Fiori displays.
app

3 Get Latest To get the latest imported bank statement number, choose Show Filter Bar if search criteria are hidden, and make The latest bank statement number of
Bank the following entries: the specified bank account displays on
Statement the screen Manage Bank Statements.
Company Code: 1710
Number
House Bank: USBK1 The next bank statement number is
one greater than the latest bank state-
House Bank Account: USAC1
ment number. For example, if the latest
Latest Statement: Latest only bank statement number is 00005, the
and choose Go. next number is 00006. If no latest bank
statement was found, the next number
should be 00001.

4 Get Clos- Make a note of the closing balance of the specified bank account. It can be found on the screen Manage Bank The closing balance of the latest bank
ing Bal- Statements. statement should be the opening bal-
ance of ance of the next bank statement.
Latest
If no latest bank statement was found,
Bank
the opening balance of the next bank
Statement
statement should be zero.

5 Save txt Refer the to the text file BAI2_US_USBK1_00006.txt you previously created in the Prerequisite section. The txt
file in file name must contain the string BAI2, for example, BAI2_US_USBK1_00006.txt. Because FSN does not accept
your PC files with the same name, and more than one tester is testing this scenario, use a different file name every time
when you test this step.

6 Open txt Use a text editor to open this txt file.

file in
your PC

7 Edit txt Modify the txt file as shown in the note row below.
file Edit these Values in BAI2 file:

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 24
 Test Test Step Instruction Expected Result Pass /
Step Name Fail /
# Com-
ment
● Tag 01 (File Header): in this example: 01,Test FSN ,Test Receiver,151116,0235,1,99,99,2/. Replace 151116,0235
by the current time (format YYMMDD,HHMM); the value 1 in the following field is file identification number,
as it is unique value to distinguish files sent on the same date.
● Tag 02 (Group Header): in this example: 02,Test Receiver,011000390,1,151116,0235,USD/. 011000390 is
the bank key of USBK1, replace 011000390
if you are using another bank for testing; replace 151116,0235 by the current timem (format
YYMMDD,HHMM).
● Tag 03 (Account identifier & Summary status): in this example:
03,33333,USD,010,500230,,,015,401883,,,045,13600000,,,/.33333 is the account number, replace it if you
are using another account number for testing;
010 is the indicator of opening balance, 500230 is the opening balance (format without a decimal, means
5002.30 USD), replace 500230 by the closing balance of latest imported bank statement, or use 000 for the
first bank statement.
015 is the indicator of closing balance, 401883 is the closing balance (format without a decimal, means 4018.83
USD), replace 401883 by the calculated closing balance, for example, closing balance = 500230 + 20825 –
119172 = 401883.
● Fist tag 16 (Transaction Detail): in this example: 16,195,20825,0,0,20825,0,TestPayref1,0815,Test Text Item 1/.
20825 is the amount of the incoming payment from customer, it should be equal to the receivables of cus-
tomer invoice mentioned in Prerequisites.
● Tag 88 (Continuation Record): in this example: 88,0090000008/. 0090000008 is the reference of customer in-
voice (XBLNR), replace it by the reference of the customer invoice mentioned in Prerequisites.
● Second tag 16 (Transaction Detail): in this example: 16,455,119172,0,TestPayref2,1000004612,Test Text Item
2/. 119172 is the amount of an outgoing payment transaction, it should be equal to the amount of the payment
document of bank transfer which is described in Prerequisites; 1000004612 is the reference number, replace it
by the Payment information ID you noted down as described in Send Payment Instruction to FSN.
In the BAI2 bank statement file, an amount does not contain decimal point, for example 500230 means 5002.30.
And the date format should be YYMMDD.

8 Upload txt ● Upload the txt file you edited to the SFTP server folder. The txt file vanishes from the SFTP
file to the For example, upload to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE4212/US USBK1 server folder in several seconds. A
SFTP background job is scheduled to pull the
server

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 25
 Test Test Step Instruction Expected Result Pass /
Step Name Fail /
# Com-
ment
The path of SFTP server folder for bank statements depends on testing system, tenant, country, and house bank. bank statement from FSN to the
If you want to get sufficient information on how to access the FSN bank tenants or SFTP server, open a BCP mes- S/4HANA system every 10 minutes.
sage under the component LOD-FSN-INT.
In this example, a BAI2 bank statement file for house bank/account ID USBK1/USAC1 in country US is pulled from
SFTP by FSN, FSN will map it to an ISO CAMT.053 format file.

4.2.2 Import Electronic Bank Statement

Purpose
After the CAMT.053 bank statement is pulled from FSN, the S/4HANA system imports the electronic bank statement automatically, and the postings in bank accounting and Subledger account-
ing should be performed.
Since FSN maps the local bank statement formats to a CAMT.053 format, there is only one set of posting rules for the electronic bank statement.
The following posting rules are available for bank statement processing:

Transactions Text
F001 Cash receipt via interim account

F002 Checks In

F003 Checks Out

F004 Transfer Domestic/SEPA/Foreign

F005 Other Disbursements

F006 Other Receipts

F007 Cash Payment

F008 Cash Receipt

F009 Direct Debit / Collection

F010 Vendor Direct Debit

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 26
 Transactions Text
F011 Bank Fee

F012 Interest Received

F013 Interest Paid

F014 Returns Collection / Direct debit

F015 Returns vendor direct debit

F016 Unallocated Credit

F017 Unallocated Debit

FCD1 Direct Check Deposit

FCD2 Check Deposit via interim Account

Procedure
After the background job pulls the bank statement from FSN, the S/4HANA system imports the bank statement automatically.
If the Cash Management Full (Extended) version is implemented in the system, then you should review the relevant payment document using the Check Cash Flow Items app, to Check Status.
The status of the batch item should now be Stmt. Received.
Note The Check Cash Flow Items app is not available in the Cash Management Basic (Core) version.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Test Procedures © 2017 SAP SE or an SAP affiliate company. All rights reserved. 27
5 Appendix

5.1 Process Integration

The process to be tested in this test script is part of a chain of integrated processes.

5.2 Preceding Processes

You may first have completed the following processes and conditions before you start with the test steps:

Process Business Condition

Accounts Payable (J60) If the Full (Extended) Cash Management is implemented, before the test step Outgoing Integration ensure that either:
and/or ● The payment run has been executed and the paying house bank uses the payment medium format for FSN connectivity
Advanced Cash Operations (J78) in test script Accounts Payable (J60), and the BCM batch has been approved in step Approval and Bank Integration of
test script Basic Cash Operations (BFB).
and
● A bank transfer is made the the paying house bank uses payment medium format for FSN connectivity in test script Ad-
Basic Cash Operations (BFB)
vanced Cash Operations (J78), and the BCM batch has been approved in step Approval and Bank Integration of test script
Basic Cash Operations (BFB)

Sell from Stock (BD9) (for SAP S/4HANA Enterprise Manage- Before the test step Incoming Integration ensure that either:
ment or SAP S/4HANA Enterprise Management Cloud) ● Another tester has created a billing document, and its customer item is open (uncleared). You can find open customer
or items in the app Manage Customer Line Items; in order to run this app, add accounts receivable related roles to your
Sales Order Processing - Project-Based Services (J14) (for user, you may find these roles in the test script Accounts Receivable (J59).
SAP S/4HANA Enterprise Management Cloud or SAP ● If you cannot find an existing open customer item, create a billing document by yourself. You can run the test script BD9
S/4HANA Professional Services Cloud) or J16 to create a billing document.
or any other test scripts creating customer invoice, Make a note of the amount and reference (XBLNR in the header) of the FI document of billing document. This information is
needed to simulate the incoming payment (credit) item in an electronic bank statement. In the bank statement, a credit
item can be reconciled with customer invoice.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Appendix © 2017 SAP SE or an SAP affiliate company. All rights reserved. 28
5.3 Succeeding Processes
After completing the activities in this test script, you can continue testing the following business processes:

Process Business Condition

Basic Cash Operations (BFB) If the Full (Extended) Cash Management is implemented:
and After the payment status message is pulled from FSN, check the status change in app Check Cash Flow Items and app Monitor Payments.
Advanced Cash Operations (J78) After the bank statement is imported via FSN, check the status in app Bank Statement Monitor.

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Appendix © 2017 SAP SE or an SAP affiliate company. All rights reserved. 29
Typographic Conventions

Type Style Description

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.

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 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 .

Bank Integration with SAP Financial Services Network (16R_US) CUSTOMER

Appendix © 2017 SAP SE or an SAP affiliate company. All rights reserved. 30
www.sap.com/contactsap

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affili-
ate company.
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 Germany and other countries. Please see
http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for in-
formational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or omis-
sions with respect to the materials. The only warranties for SAP SE or SAP
affiliate company products and
services are those that are set forth in the express warranty statements ac-
companying 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 presenta-
tion, or to develop or release any functionality mentioned therein. This doc-
ument, or any related presentation, and SAP SE’s or its affiliated compa-
nies’ strategy and possible future developments, products, and/or platform
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 no-
tice. The information in this document is not a commitment, promise, or le-
gal 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 cau-
tioned not to place undue reliance on these forward-looking statements,
which speak only as of their dates, and they should not be relied upon in
making purchasing decisions.