16R S4CLD2302 BPD en Us

Test Script
SAP S/4HANA Cloud - 26-12-22

1.1.1
Bank Integration with SAP Multi-Bank Connectiv-

ity (16R_US)
PUBLIC
Table of Contents
1 Purpose
2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
2.4 Business Conditions
2.5 Preliminary Steps
2.5.1 Create pain.002.001.03_I071234_01.xml
2.5.2 Create pain.002.001.03_I071234_02.xml
2.5.3 Create camt.053.001.02_I071234_01.xml
2.5.4 Create camt.054.001.02_I071234_01.xml
2.5.5 Create camt.053.001.02_I071234_02.xml
2.5.6 Check Alternative Format Type
2.5.7 Adapt Payment Medium File Structure for Supplier Financing (Optional)
2.5.8 Enable Situation Framework
2.5.8.1 Manage Teams and Responsibilities
2.5.8.2 Create Situation Type
3 Overview Table
4 Test Procedures
4.1 Outgoing Integration
4.1.1 Create Payment Medium
4.1.2 Send Payment Instruction to MBC (Optional)
4.1.3 Monitor Situations
4.1.4 Check Notification
4.1.5 Pull Status Message from MBC (Optional)
4.2 Incoming Integration
4.2.1 Pull Bank Statement from MBC
4.2.1.1 ISO CAMT.054 Format
4.2.1.3 BAI2 Lockbox Message Format
4.2.2 Import Electronic Bank Statement
4.2.3 Pull Bank Services Billing Files from MBC
4.2.4 Route Payment Files and Payment Transaction Messages
4.2.4.1 Route Payment Transaction Messages Initiated by SAP Systems
4.2.4.2 Route Payment Files Initiated by non-SAP Systems
4.3 MBC Message Monitor
5 Appendix
5.1 Process Integration
5.2 Succeeding Processes
Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Test Procedures PUBLIC 2
2 Purpose
With SAP Multi-Bank Connectivity (MBC), SAP establishes connections with your banks to automatically send payment instructions, receive status notifications, receive bank statements, and re-
ceive lockbox messages. Leveraging the monitoring capabilities, you can supervise the status of all payment instructions and see which bank statements are received and which expected bank state -
ments are still missing. The monitoring is only available in combination with Advanced Cash Operations (J78).
This test script describes an example of the end-to-end process using manual steps to test the setup without needing to connect to an actual real bank. In an actual productive implementation, this
process is fully automated.
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 appropri -
ate.

3 Prerequisites
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.
3.1 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.
3.2 Roles
Create business roles using the following business role templates delivered by SAP and assign them to your individual test users.
Alternatively, if available, you can use the following spaces delivered by SAP. You create a space with pages containing predefined essential apps and assign it to the business role. You then assign
this business role to your individual users.
For more information, refer to How to Create a Business Role for the Administrator in the product assistance for SAP S/4HANA Cloud.
Name (Role ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
Template) On
Cash Manage- SAP_BR_CASH_SPECIAL- Cash Management Specialist SAP_BR_CASH_SPECIALIST

ment Specialist IST
Business Inte- SAP_BR_BANK_INT_SPE- Business Integration Specialist - Bank Integration SAP_BR_BANK_INT_SPECIALIST

gration Spe- CIALIST
cialist - Bank
Integration
Configuration SAP_BR_BPC_EXPERT Configuration Expert - Business Process Configuration / Business Configura- SAP_BR_BPC_EXPERT / SAP_CA_SPT_BPC_FM_PC /
Expert - Busi- tion - Feature Management / BPC Expert Workflow Space / Business Process SAP_CA_SPT_BPC_WORKFLOW_PC /
ness Process Configuration – Manage your Solution / Business Process Configuration - Ex- SAP_CA_SPT_IC_LND_BASE_PC / SAP_EI_SPT_BPC_EXT_PC /
Configuration tensibility Explorer / Business Process Configuration – Finance / Materials SAP_FIN_SPT_BPC_EXPERT_PC / SAP_MM_SPT_BIZ_PROC_CON-
Management - Business Process Configuration FIGN_PC

3.3 Master Data, Organizational Data, and Other Data
The organizational structure and master data of your company have 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.
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
3.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 MBC connectivity in test script Accounts Payable (J60), and the
BFB - Basic Cash Operations BCM batch has been approved the step Approval and Bank Integration in the Advanced Cash Operations (J78) test script.
● A bank transfer is made and the paying house bank uses the payment medium format for MBC connectivity and the BCM batch has been approved in the Advanced
Cash Operations (J78) test script.
J60 - Accounts Payable and/or If the Basic (Core) Cash Management is implemented, before the test step Outgoing Integration ensure that: The payment run has been executed and the paying house bank

Scope Item Business Condition
BFB - Basic Cash Operations uses the payment medium format for MBC connectivity in test script Accounts Payable (J60), the process is linked to current test script Bank Integration with SAP Multi-
Bank Connectivity (16R) via a process interface mentioned in the Accounts Payable Bank Integration procedure in the Basic Cash Operations (BFB) test script, because no
approval is needed (no BCM approval function is provided) when using Basic (Core) Cash Management.
● The payment run has been executed and the paying house bank uses the payment medium format for MBC connectivity in test script Accounts Payable (J60), the
process is linked to current test script Bank Integration with SAP Multi-Bank ConnectivityBasic Cash Operations (BFB) test script, because no approval is needed (no
BCM approval function is provided) when using Basic (Core) Cash Management.
4AV - Supplier Financing Supplier Financing is designed to hand over the supplier invoices via payment instructions to bank with automatic approvals if BCM is enabled. Before the test step ISO
CAMT.054 format ensure that Payment Run (4AV) is successfully finished. Make a note of the payment document number, the amount of the each payment, DME refer-
ence number. You can find the information in the app Advanced Cash Operations (J78).
BD9 - Sell from Stock (for SAP S/4HANA En- Before the test step Incoming Integration ensure that either:
terprise Management or SAP S/4HANA Enter- ● Another tester has created a billing document, and its customer item is open (uncleared). You can find open customer items in the app Manage Customer Line Items;
prise Management Cloud) or in order to run this app, add accounts receivable related roles to your user, you may find these roles in the Accounts Receivable (J59) test script.
J14 - Sales Order Processing - Project-Based ● If you cannot find an existing open customer item, create a billing document by yourself. You can use test script Sell from Stock (BD9) or Sales Order Processing -
Services (for SAP S/4HANA Enterprise Man- Project-Based Services (J14) to create a billing document.
agement Cloud or SAP S/4HANA Professional
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
Services Cloud)
(credit) item in an electronic bank statement. In the bank statement, a credit item can be reconciled with customer invoice.
or any other scope items creating customer in-
voice
J59 - Accounts Receivable Before the test step Incoming Integration ensure that either:
● Another tester has created a customer invoice, and its customer item is open (uncleared). You can find open customer items in the app Manage Customer Line Items;
in order to run this app, add accounts receivable related roles to your user, you may find these roles in the Accounts Receivable (J59) test script.
● If you cannot find an existing open customer item, create a customer invoice document by yourself. You can use test script Accounts Receivable (J59).
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.
2O0 - Bank Fee Management Before you execute the Pull Bank Services Billing Files from MBC step, ensure that you:
● Execute the preliminary steps of the Bank Fee Management (2O0) test script. The Cash Scope of General Setting for Cash Management is set as Full Scope.
● Create a Camt_086 Bank Fee file for bank account 33333 and save it locally on your PC. Make sure the file used in MBC has a different name and report ID (for ex-
ample Camt_086_DE_33333_00002.xml). The report ID is maintained in the <RptId> tag (for example RPT_20170816_DE_50070010_1010_0002).
2DP - Contract Accounting - Company Initi- Before the test step Route Payment Transaction Messages Initiated by SAP Systems ensure that you:
ated Payments ● The payment run is conducted, payment media file is generated.
● The mandatory manual configuration is conducted to integrate Contract Accounting with Multi-Bank Connectivity.
4MT - Advanced Payment Management Before the test step Route Payment Files and Payment Transaction Messages ensure that all the preliminary steps of the Advanced Payment Management (4MT) test script
are executed.
31N - Situation Handling You install this scope item for the situation handling steps.

3.5 Preliminary Steps
3.5.1 Create pain.002.001.03_I071234_01.xml
Context
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 MBC 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
In a text editor, paste the following code:

Sample 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>
<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>
<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>
</Cdtr>
</OrgnlTxRef>
</TxInfAndSts>
</OrgnlPmtInfAndSts>
</CstmrPmtStsRpt>
</Document>
Save the file to a folder on your PC as pain.002.001.03_I071234_01.xml.
3.5.2 Create pain.002.001.03_I071234_02.xml
Context

The xml file name must contain the string ‘pain.002.001.03’ (for example, pain.002.001.03_I071234_02.xml). Because MBC does not accept files with the same name, and more than one tester is
Procedure
In a text editor, paste the following code:

Sample 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>1000746725</MsgId>
<InitgPty>
<Nm>COMPANY CODE 1710</Nm>
<PstlAdr>
<StrtNm>Deer Creek</StrtNm>
<BldgNb>3475</BldgNb>
<PstCd>94304-1355</PstCd>
<TwnNm>Palo Alto</TwnNm>
<Ctry>US</Ctry>
</PstlAdr>
</InitgPty>
<DbtrAgt>
<FinInstnId>
<BIC>BOFAUS3M</BIC>
</FinInstnId>
</DbtrAgt>
</GrpHdr>
<OrgnlGrpInfAndSts>
<OrgnlMsgId>1000746725</OrgnlMsgId>
<OrgnlMsgNmId>pain.001.001.03</OrgnlMsgNmId>
<OrgnlCreDtTm>2019-07-25T08:39:08</OrgnlCreDtTm>
<GrpSts>PART</GrpSts>
</OrgnlGrpInfAndSts>
<OrgnlPmtInfAndSts>
<PmtInfSts>ACSP</PmtInfSts>
<TxInfAndSts>
<TxSts>ACSP</TxSts>
<OrgnlTxRef>
<Amt>
</Amt>

<RmtInf>
</RmtInf>
<Cdtr>
<Nm>TEST SE</Nm>
</Cdtr>
</OrgnlTxRef>
</TxInfAndSts>
<TxInfAndSts>
<TxSts>ACSP</TxSts>
<OrgnlTxRef>
<Amt>
</Amt>
<RmtInf>
</RmtInf>
<Cdtr>
<Nm>TEST SE</Nm>
</Cdtr>
</OrgnlTxRef>
</TxInfAndSts>
</OrgnlPmtInfAndSts>
</CstmrPmtStsRpt>
</Document>
Save the file to a folder on your PC as pain.002.001.03_I071234_02.xml.
3.5.3 Create camt.053.001.02_I071234_01.xml
Context

The xml file name must contain the string ‘camt.053.001.02’ (for example, camt.053.001.02_I071234_01.xml). Because MBC does not accept files with the same name, and more than one tester is

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

Sample 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>
<MsgPgntn>
<PgNb>00001</PgNb>
<LastPgInd>false</LastPgInd>
</MsgPgntn>
</GrpHdr>
<Stmt>
<Id>CAMSLINK01000249</Id>
<ElctrncSeqNb>00006</ElctrncSeqNb>
<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>
<Dt>
<Dt>2014-12-22</Dt>
</Dt>
</Bal>
<Ntry>
<Sts>BOOK</Sts>
<BookgDt>
<Dt>2014-12-22</Dt>
</BookgDt>
<ValDt>
<Dt>2014-12-22</Dt>
</ValDt>
<AcctSvcrRef>MBC 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>
<CdtDbtInd>DBIT</CdtDbtInd>
<Sts>BOOK</Sts>
<BookgDt>
<Dt>2014-12-22</Dt>
</BookgDt>
<ValDt>
<Dt>2014-12-22</Dt>
</ValDt>
<AcctSvcrRef>MBC TEST AcctSvcrRef Item 1</AcctSvcrRef>
<BkTxCd>

<Prtry>
<Cd>PMNTICDTDMCT</Cd>
</Prtry>
</BkTxCd>
<NtryDtls>
<TxDtls>
<Refs>
<ChqNb>1000004611</ChqNb>
</Refs>
<AddtlTxInf>4712</AddtlTxInf>
</TxDtls>
</NtryDtls>
<AddtlNtryInf>4712</AddtlNtryInf>
</Ntry>
<AddtlStmtInf>MBC Test AddtlSmtInf</AddtlStmtInf>
</Stmt>
</BkToCstmrStmt>
</Document>
2. Save the file to a folder on your PC as camt.053.001.02_I071234_01.xml.
3.5.4 Create camt.054.001.02_I071234_01.xml
Context

The xml file name must contain the string ‘camt.054.001.02’ (for example, camt.054.001.02_I071234_01.xml). Because MBC does not accept files with the same name, and more than one tester is
Procedure

Sample Code
<?xml version="1.0" encoding="ISO-8859-1"?>
<Document xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:camt.054.001.02 camt.054.001.02.xsd" xmlns:xsi="http://www.w3.org/
2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:camt.054.001.02">
<BkToCstmrDbtCdtNtfctn>
<GrpHdr>
<MsgId>25YDSJO9ZB1D099999911</MsgId>
</GrpHdr>
<Ntfctn>
<Id>25YDSJO9ZB1D099999911</Id>
<Acct>
<Id>
<Othr>
<Id>25800611</Id>
</Othr>
<Cd>CASH</Cd>
</Id>
<Svcr>
<FinInstnId>
<BIC>CITIUS33MIA</BIC>
</FinInstnId>
</Svcr>
<Ccy>USD</Ccy>
</Acct>
<Ntry>
<Sts>BOOK</Sts>
<ValDt>
<Dt>2019-08-13</Dt>
</ValDt>
<BkTxCd>
<Prtry>
<Cd>ZSF054</Cd>
</Prtry>
</BkTxCd>
<NtryDtls>
<TxDtls>
<Refs>
<EndToEndId>2000000070</EndToEndId>
</Refs>
<AmtDtls>
<InstdAmt>

</InstdAmt>
<TxAmt>
</TxAmt>
</AmtDtls>
<RmtInf>
<Strd>
<RfrdDocInf>
<Tp>
<CdOrPrtry>
<Cd>CINV</Cd>
</CdOrPrtry>
</Tp>
<Nb>REF-SF-101</Nb>
<RltdDt>2019-08-13</RltdDt>
</RfrdDocInf>
<RfrdDocAmt>
<DuePyblAmt Ccy="USD">100.00</DuePyblAmt>
<AdjstmntAmtAndRsn>
<Rsn>WHT</Rsn>
</AdjstmntAmtAndRsn>
<RmtdAmt Ccy="USD">100.00</RmtdAmt>
</RfrdDocAmt>
</Strd>
</RmtInf>
</TxDtls>
</NtryDtls>
<NtryDtls>
<TxDtls>
<Refs>
<EndToEndId>2000000071</EndToEndId>
</Refs>
<AmtDtls>
<InstdAmt>
</InstdAmt>
<TxAmt>
</TxAmt>
</AmtDtls>
<RmtInf>
<Strd>

<RfrdDocInf>
<Tp>
<CdOrPrtry>
<Cd>CINV</Cd>
</CdOrPrtry>
</Tp>
<Nb>REF-SF-201</Nb>
</RfrdDocInf>
<RfrdDocAmt>
<AdjstmntAmtAndRsn>
<Rsn>WHT</Rsn>
</RfrdDocAmt>
</Strd>
<Strd>
<RfrdDocInf>
<Tp>
<CdOrPrtry>
<Cd>CINV</Cd>
</CdOrPrtry>
</Tp>
<Nb>REF-SF-202</Nb>
</RfrdDocInf>
<RfrdDocAmt>
<AdjstmntAmtAndRsn>
<Rsn>WHT</Rsn>
</RfrdDocAmt>
</Strd>
</RmtInf>
</TxDtls>
</NtryDtls>
</Ntry>
</Ntfctn>
</BkToCstmrDbtCdtNtfctn>
</Document>

3.5.5 Create camt.053.001.02_I071234_02.xml
Context

The xml file name must contain the string camt.053.001.02 (for example, camt.053.001.02_I071234_0 2 .xml). Because MBC does not accept files with the same name, and more than one tester is
Procedure

Sample 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>20190726074500</MsgId>
<MsgPgntn>
<PgNb>00001</PgNb>
<LastPgInd>false</LastPgInd>
</MsgPgntn>
</GrpHdr>
<Stmt>
<Id>CAMSLINK01000250</Id>
<ElctrncSeqNb>138</ElctrncSeqNb>
<Acct>
<Id>
<Othr>
<Id>33333</Id>
</Othr>
</Id>
<Svcr>
<FinInstnId>
<BIC>BOFAUS3M</BIC>
</FinInstnId>
</Svcr>
</Acct>
<Bal>
<Tp>
<CdOrPrtry>
<Cd>PRCD</Cd>
</CdOrPrtry>
</Tp>
<Dt>
<Dt>2019-08-13</Dt>
</Dt>
</Bal>
<Bal>
<Tp>
<CdOrPrtry>
<Cd>CLBD</Cd>
</CdOrPrtry>

</Tp>
<Dt>
<Dt>2019-08-13</Dt>
</Dt>
</Bal>
<Ntry>
<Sts>BOOK</Sts>
<BookgDt>
<Dt>2019-08-13</Dt>
</BookgDt>
<ValDt>
<Dt>2019-08-13</Dt>
</ValDt>
<AcctSvcrRef>TEST</AcctSvcrRef>
<BkTxCd>
<Prtry>
<Cd>ZSF053</Cd>
</Prtry>
</BkTxCd>
<NtryDtls>
<TxDtls>
<RltdPties>
<Dbtr>
<Nm/>
</Dbtr>
<DbtrAcct>
<Id>
<Othr>
<Id>102030</Id>
</Othr>
</Id>
</DbtrAcct>
</RltdPties>
<RltdAgts>
<DbtrAgt>
<FinInstnId>
<Othr>
<Id>820800001</Id>
</Othr>
</FinInstnId>
</DbtrAgt>

</RltdAgts>
<Refs>
<ChqNb/>
</Refs>
<AddtlTxInf>reference for camt053 item</AddtlTxInf>
</TxDtls>
</NtryDtls>
<AddtlNtryInf>reference for camt053 item</AddtlNtryInf>
</Ntry>
<AddtlStmtInf>TEST1 camt053</AddtlStmtInf>
</Stmt>
</BkToCstmrStmt>
</Document>
3.5.6 Check Alternative Format Type
Use
In this activity, you check the alternative format type. Alternative format type determines how the payment medium file is transmitted to banks or a payment service provider.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert

- Business Process Configuration.
2 Access App Open Manage Your Solution (F1241).
3 Configure Choose Configure Your Solution. The Configure Your Solution: Realize Phase view is displayed.

Step # Comment
4 Select Filter Cri- In the filters area, make the following selections: A filtered list of Configuration Items is displayed.
teria Application Area: Finance
Sub Application Area: Account Payable
5 Select Item At the right side of the Automatic Payments row, choose the The Configure Your Solution - Automatic Payments view is displayed.
arrow button.
6 Choose Configu- For the Set Up Payment Methods for Each Country/Region The "Set Up Payment Methods for Each Country/Reg..": Change view is displayed.
ration Step for Payment Transactions step, choose Configure.
7 Select Payment Double click the payment method (for example, Country US The Change View "Set Up Payment Methods for Each Country/Reg..": Details view is displayed.
Method + Pmt MethodT).
8 Check Alterna- Choose Format in Company Code. The Change View “PMW Format”: Overview view is displayed.
tive Format The alternative format type determines in which way the payment medium file is transmitted to banks or pay-
ment service provider. Ensure that the alternative format type is set SAP Multi-Bank Connectivity.
The other integration option is blank value. Refer to the test procedure in Bank Integration with File
Interface(1EG).
SAP Central Business Configuration:
Test Test Step Name Instruction Expected Result Pass /

Step # Fail /
Comment
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Set Up Payment Meth- In the Product-Specific Configuration phase, navigate to the Configuration Ac- The Change View “Payment Method/Country”: Overview screen displays.
ods per Country for Payment tivities tab and search for the following activity: Set Up Payment Methods for
Transactions Each Country/Region for Payment Transactions.
Choose the line item in the search result to see more details about this configu-
ration activity.
Choose the Go to Activity button to navigate directly to the SAP S/4HANA
Cloud system. Log on to the SAP Fiori launchpad as a Configuration Expert -
Business Process Configuration.
3 Select Payment Method Double click the payment method (for example, Country US + Pmt MethodT). The Change View “Payment Method/Country”: Details view is displayed.

Test Test Step Name Instruction Expected Result Pass /
Step # Fail /
Comment
4 Check Alternative Format Choose Format in Company Code. The Change View “PMW Format”: Overview view is displayed.
The alternative format type determines in which way the payment medium file is
transmitted to banks or payment service provider. Ensure that the alternative format
type is set SAP Multi-Bank Connectivity.
The other integration option is blank value. Refer to the test procedure in Bank Inte-
gration with File Interface(1EG).
3.5.7 Adapt Payment Medium File Structure for Supplier Financing (Optional)
Use
In this activity, you adapt the payment medium file structure to match bank’s standard. The payment medium file used for supplier financing is based on PAIN.001.001.03 format.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
2 Access App Open Manage Your Solution (F1241).
3 Configure Choose Configure Your Solution. The Configure Your Solution: Realize
Phase view is displayed.
4 Select Filter Cri- In the filters area, make the following selections: A filtered list of Configuration Items is dis-
teria Application Area: Finance played.
Sub Application Area: Account Payable

Step # Comment
5 Select Item At the right side of the Payment Medium Formats row, choose the arrow button. The Configure Your Solution - Payment
Medium Formats view is displayed.
6 Choose Configu- For the Map Format Data for Payments step, choose Configure. The Map Format Data view is displayed.
ration Step
7 Copy Format Choose > Expand Node of Format Mapping CGI_CT, select a PAIN.001.001.03 Format Mapping, for example The Copy Format Mapping
Mapping US_CGI_XML_CT and choose Copy. US_CGI_XML_CT pop-up window is dis-
played.
8 Confirm New In the pop-up window, make the following selections: A new Format Mapping is created.
Format Mapping New Format Mapping Name: /DSSF_US_CGI_XML_CT, choose OK.
9 Edit Format Map- Select the new Format Mapping /DSSF_US_CGI_XML_CT, choose > Displays the format mapping. The maintenance view of Map Payment
ping Format Data view is displayed.
10 Adapt Format Expand the structure tree in the Format Mapping Properties subscreen, choose Edit and select node Nm under PmtInf->Cdt- The format mapping is successfully adapted.
Structure TrfTxInf->Cdtr. Choose + Create Note from the toolbar on the top left-hand.
Name the new node as Id. Make the following entries and press Enter:
Name: Id
Short Description: Internal Supplier Id
Status: Standard
Level: 3
Length: 0
Type: Character
Conversion Function: Character string: left-justified, replace leading 0 (CL R0)
Mapping Procedure: Structure Field
Structure Field: FPAYH-GPA1R
Adapt the change for other node as below:
Remove the conditions of node PmtTplnf under PmtInf.
Select the node RltdDt under RmtInf->Strd->RfrdDocInf->RltdDt, choose + Create Note from the toolbar on the top
left-hand side, choose Create Atom > As Subnode to create following elements on at the lower level.
Node YYYY:
Name: YYYY
Status: Standard
Length: 4
Target Offset: 0

Step # Comment
Type: Character
Conversion Function: Character string: left-justified (CL)
Structure Field: FPAYP-BLDAT
Node MM:
Name: MM
Status: Standard
Length: 2
Target Offset: 5
Type: Character
Structure Field: FPAYP-BLDAT+004
Node DD:
Name: DD
Status: Standard
Length: 2
Target Offset: 8
Type: Character
Node -:
Name: -
Status: Standard
Length: 1
Type: Character
Mapping Procedure: Constant
Constant: -
11 Release Format Choose Release to activate the format mapping. The format mapping is successfully re-
Mapping leased.
SAP Central Business Configuration:

Step # Comment
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Map Pay- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab and search for the following activity: The Map Payment Format Data screen dis-
ment Format Data Map Payment Format Data. plays.
Choose the line item in the search result to see more details about this configuration activity.
Choose the Go to Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as
a Configuration Expert - Business Process Configuration.
3 Copy Format Choose > Expand Node of Format Mapping CGI_CT, select a PAIN.001.001.03 Format Mapping, for example The Copy Format Mapping
Mapping US_CGI_XML_CT and choose Copy. US_CGI_XML_CT pop-up window is dis-
played.
4 Confirm New For- In the pop-up window, make the following selections: A new Format Mapping is created.
mat Mapping New Format Mapping Name: /DSSF_US_CGI_XML_CT, choose OK.
5 Edit Format Map- Select the new Format Mapping /DSSF_US_CGI_XML_CT, choose > Displays the format mapping. The maintenance view of Map Payment
ping Format Data view is displayed.
6 Adapt Format Expand the structure tree in the Format Mapping Properties subscreen, choose Edit and select node Nm under PmtInf->Cdt- The format mapping is successfully
Structure TrfTxInf->Cdtr. Choose + Create Note from the toolbar on the top left-hand. adapted.
Name the new node as Id. Make the following entries and press Enter:
Name: Id
Short Description: Internal Supplier Id
Status: Standard
Level: 3
Length: 0
Type: Character
Conversion Function: Character string: left-justified, replace leading 0 (CL R0)
Structure Field: FPAYH-GPA1R
Adapt the change for other node as below:
Remove the conditions of node PmtTplnf under PmtInf.
Modify the node Cd under PmtInf->PmtTpInf->CtgyPurp
Constant: TRAD
Select the node RltdDt under RmtInf->Strd->RfrdDocInf->RltdDt, choose + Create Note from the toolbar on the top
left-hand side, choose Create Atom > As Subnode to create following elements on at the lower level.

Step # Comment
Node YYYY:
Name: YYYY
Status: Standard
Length: 4
Target Offset: 0
Type: Character
Structure Field: FPAYP-BLDAT
Node MM:
Name: MM
Status: Standard
Length: 2
Target Offset: 5
Type: Character
Node DD:
Name: DD
Status: Standard
Length: 2
Target Offset: 8
Type: Character
Node -:
Name: -
Status: Standard
Length: 1
Type: Character
Constant: -

Step # Comment
7 Release Format Choose Release to activate the format mapping. The format mapping is successfully re-
Mapping leased.
3.5.8 Enable Situation Framework
3.5.8.1 Manage Teams and Responsibilities
Use
In this activity, you create a team to specify responsibilities for MBC messages.
Procedure
Execute the Manage Teams and Responsibilities steps in the Responsibility Management (1NJ) test script with the following information:
Name: MBC Monitor Team
Global ID: TeamMBC01
Type: SMBC
Status: Enabled
ReceiverId: for example, <blank>
SenderId: for example, <blank>
Note If the last two fields are left blank, the team is responsible for all MBC messages.
Team Owners tab:

Business Partner: <user ID>, for example, Business Process Specialist
Team Members tab:
Business Partner: <user ID>, for example, Bank Integration Specialist
Functions: S_MBCMON_F

Note To display the connection between the business partner, cash manager, and user ID, see the search help. Generic users are described in the Last Name field.
3.5.8.2 Create Situation Type
Use
In this activity, you create situation types for Multi-Bank Connectivity Situation Handling.
There are situation templates available for Multi-Bank Connectivity:
● Bank Message still in status Created: This situation is triggered when an outgoing message is still in status Create after a few minutes.
● Bank Message entering Error status: This situation is triggered when an incoming message goes into Error status.
● Bank Message requires manual processing: This situation is triggered when an incoming message goes into Error status.
● No MBC status received for Bank Message: This situation is triggered when for an outgoing message no MBC Status has been received.
● Bank Message still in status received: This situation is triggered when an incoming message remains in status received for some time.
You can use the above described situations as templates.
Note Please make sure 31N is activated if you want to execute this step.
Procedure
Test Test Step Instruction Expected Result Pass / Fail /

Step # Name Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert -

Business Process Configuration.
2 Access App Open Manage Situation Types (F2947).
3 Select Filter In the filters area, make the following selections: A situation template is displayed.
Criteria ID: for example, FIN_MBC_BANK_MESSAGE_ERROR
4 Copy Situation Choose the situation template item and choose Copy. A new situation type is to be created in the Situation Type view.
Type

Step # Name Comment
5 Create a Situa- In the Situation Type view, make the following entries and
tion Type choose Create.
ID: for example, ZFIN_MBC_MESSAGE_ERROR
Name: for example, keep default name Bank Message
Entering Error Status
In the Situation Monitoring area, Monitor Instances: <Se-
lected>
6 Add Team Cat- In the Recipients area, choose Add Team Category.
egory In the dialog box, select Multi-Bank Connectivity Connector
and choose Select.
7 Confirm Cre- Choose Create. A new situation type is created and enabled.
ation Choose Yes to confirm the message Enable Situation Type.
8 Create Situa- Repeat step 3 -7 to create situation types based on following Situation types ZFIN_MBC_MESSAGE_CREATED , ZFIN_MBC_MESSAGE_MANPROC, ZFIN_MBC_MES-
tion Types situation templates: SAGE_NO_MBCSTAT , ZFIN_MBC_MESSAGE_RECEIVERED are created.
FIN_MBC_BANK_MESSAGE_CREATED
FIN_MBC_BANK_MESSAGE_MANPROC
FIN_MBC_BANK_MESSAGE_NO_MBCSTAT
FIN_MBC_BANK_MESSAGE_RECEIVED

4 Overview Table
This scope item consists of several process steps provided in the table below.
Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the typical tasks of a business
role.
You can find all other (searchable) apps not included on the homepage using the search bar (2434549).
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.
Process Step, Report or Item Business Role Transaction/App Expected Results
Outgoing Integration
Create Payment Medium [page ] 34 Cash Management Specialist The procedure is completed automatically.
Send Payment Instruction to MBC (Op- Cash Management Specialist The payment medium file is automatically sent to Multi-Bank Connectivity (MBC) and you verify that the
tional) [page ] 35 file displays in the correct folder of the SFTP server.
Monitor Situations [page ] 36 Configuration Expert - Business Monitor Situations Situations can be monitored and instance details can be checked.
Process Configuration (F3264)
Check Notification [page ] 37 Recipient (for example, Business Inte- The notification is checked by the recipient.
gration Specialist - Bank Integration)
Pull Status Message from MBC (Optional) Cash Management Specialist Bank sends the payment status message to MBC to acknowledge that payment medium file has been ac-
[page ] 38 cepted by bank. And SAP S/4HANA pulls the payment status message from MBC.
Incoming Integration
Pull Bank Statement from MBC [page ] Cash Management Specialist Manage Bank State- MBC maps the local bank statement format to correct format and SAP S/4HANA pulls that bank statement
41 ments (F1564) from MBC.
ISO CAMT.054 Format [page ] 41 An ISO CAMT.054 Bank-to-Customer-Debit-Notification is simulated.
ISO CAMT.053 Format [page ] 43 Cash Management Specialist Manage Bank State- An ISO CAMT.053 bank statement is simulated.
ments (F1564)
BAI2 Lockbox Message Format [page ] Cash Management Specialist Manage Bank State-
48 ments (F1564)
Import Electronic Bank Statement [page ] Cash Management Specialist Manage Bank State- After the CAMT.053 bank statement is pulled from MBC, the electronic bank statement is imported auto-
matically and the postings in bank accounting and subledger accounting are then carried out.

Process Step, Report or Item Business Role Transaction/App Expected Results
ments (F1564)
Check Cash Flow Items
(F0735)
Pull Bank Services Billing Files from Cash Management Specialist The file is placed in the SFTP folder.
MBC [page ] 51
Route Payment Transaction Messages Ini-

tiated by SAP Systems [page ] 53
Route Payment Transaction Messages Ini- You simulate a FICA ISO PAIN.001 credit transfer payment message import from MBC.
tiated by SAP Systems [page ] 53
Route Payment Files Initiated by non-SAP A CSV payment file which imported from MBC is simulated.
Systems [page ] 53
Monitor Situations [page ] 54 Configuration Expert - Business Monitor Situations You monitor situations and check instance details.
Process Configuration (F3264)
Check Notification [page ] 55 Business Integration Specialist - Bank The notification is checked by the recipient .
Integration
MBC Message Monitor [page ] 56 Business Integration Specialist - Bank Manage Bank Mes- The message content is displayed.
Integration sages (F4385)

5 Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
5.1 Outgoing Integration
5.1.1 Create Payment Medium
Context
In this process step, the payment medium file (DME file) for the payment medium format of Multi-Bank Connectivity (MBC) is created automatically.
Prerequisite
If the Full (Extended) Cash Management is implemented 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 Advanced Cash Operations (J78) test script), the payment medium file is created automatically. The outgoing payment for Supplier Financing (4AV) is always executed with au-
tomatic approval and corresponding payment batches will be generated as usual.
If the Basic (Core) Cash Management is implemented, after the payment run is executed (described in Accounts Payable (J60) test script and in Supplier Financing (4AV)), the payment medium file
is created automatically if the payment method is using the payment medium workbench (PMW) format.
Note Because Basic and Full Cash Management cannot be tested in the same client at the same time, contact your test organizer to ensure the version of Cash Management to be tested in the
current testing client.
Test scripts relevant to Basic Cash Operations are:
● Basic Cash Operations (BFB)
Test scripts relevant to Full Cash Operations are:
● Advanced Cash Operations (J78)
If in customizing, the PMW medium format for MBC connectivity is assigned to the payment method as the default format. The payment medium file is sent to MBC automatically when SAP S/
4HANA is connected to MBC, which will be described in next procedure.

Procedure
This step is done automatically.
5.1.2 Send Payment Instruction to MBC (Optional)
Context
If SAP S/4HANA is integrated with Multi-Bank Connectivity (MBC), and a payment medium workbench (PMW) format for MBC connectivity is created, the payment medium file is sent to MBC
automatically via the MBC connector. This payment medium file displays in the Secure File Transfer Protocol (SFTP) folder if it has no error.
In this activity, you verify if the payment medium file reaches the SFTP server successfully. The following internal optional test step is the simulation of communication between S/4HANA and
SFTP server. You can skip the step if the connection is not running Instead, check whether the outgoing message is displayed in the MBC Connector Monitor step.
Procedure
Test Test Step Instruction Expected Pass / Fail /

Step # Name Result Comment
1 Access the Access the SFTP folder.

SFTP Folder For example: /home/S4HTESTHCI/simbank/inbox/s4hana/v0115/BankConnectivity/Bank_ModelS/QE4212/PAIN.001.001.03/BOFAUS3M
Note The path of the SFTP server folder depends on testing system, tenant, payment medium format, SWIFT/BIC of house bank.
The path provided in this test script is only an example. To get the specific path in the SFTP folder for your specific testing system and client and to get the infor-
mation about how to access the SFTP folder, contact your test organizer.
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 MBC tenant v0115, and the paying house bank’s SWIFT/BIC is BOFAUS3M (the SWIFT/BIC of house
bank USBK1).
2 Verify File Verify that the payment medium file appears in the SFTP server folder. A new file, for example, DTA150925051453_0279.xml displays in the folder.
3 Review File Open and review the XML file to determine if the information (such as amount or bank information) is consistent with the outgoing payment from a house bank account
you approved.
4 Note Mes- Make a note of the values of the following fields in the XML file:
sage Number ● <MsgId>Message ID</MsgId>. For example, 1000004611

Test Test Step Instruction Expected Pass / Fail /
Step # Name Result Comment
● <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 (formats other than CGI credit transfer or SEPA credit transfer), you may not find the information listed
previously. For these payment media, skip the current test step and proceed to the Pull Bank Statement from MBC procedure.
Use payment method with name such as ISO PAIN.001 Credit Transfer or SEPA CT Credit Transfer for simplicity. The setting is country specific and you can
check the payment media format assigned via SSCUI 101972 Set Up Payment Methods per Country for Payment Transactions.
Purpose
In this activity, you monitor situations and check instance details.
Procedure

Step # Name Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business

Process Configuration.
2 Access App Open Monitor Situations (F3264).

Step # Name Comment
3 Enter Selec- In the upper area, make the following entries and press Enter: A chart and a list with instances that are displayed for outgoing payment situations:
tion Criteria Situation Type ID: ZFIN_MBC_MESSAGE_CREATED ● ZFIN_MBC_MESSAGE_CREATED: Shows all outgoing messages still in status Message Cre-
ZFIN_MBC_MESSAGE_NO_MBCSTAT ated after a few minutes
Year: for example, <current year> ● ZFIN_MBC_MESSAGE_NO_MBCSTAT: Shows all outgoing messages with no MBC status re-
ceived
4 Check In- Expand the hierarchy by respective situation ID, you can check the instance The MBC message ID which triggered the situation is displayed. You can check more details in the
stance triggered by each message. In this case, the Anchor Object Key is the MBC App Manage Bank Messages (F4385). For more details, you can refer to test step MBC Message
message ID. Monitor.
Note If you can not find the Anchor Object Key, you can choose Settings and
select the columns to be visible in the list.
Purpose
In this activity, the notification is checked by the recipient who is assigned to team members in preliminary step.
Procedure
Test Step Test Step Name Instruction Expected Re- Pass / Fail / Com-
# sult ment
1 Log On Log on to the SAP Fiori launchpad as a recipient (for example, Bank Integration Specialist).
2 Check Notifica- On the home page, choose Notifications in the upper right corner.
tion Choose By Type, under type Bank Message Still in Created Status or No MBC Status Received for Bank Message has been identified, choose Ex-
pand Group.

5.1.5 Pull Status Message from MBC (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
The bank sends the payment status file to Multi-Bank Connectivity (MBC) to acknowledge that payment medium file is accepted. The system pulls the payment status file from MBC automatically.
Note When testing in SAP S/4HANA with Basic Cash Management, skip this step. Bank Communication Management (BCM) is not in scope. The Status Message pulled from MBC cannot up-
date the BCM status.
Note If J78 - Advanced Cash Operations is scope and Automatically Reversing Rejected Payments prerequisite is met, a rejection payment status message will trigger automatic reversal work -
flow. After confirmation, the payment document can be reversed. Refer to Process Rejected Payments (Option) in test script of J78Advanced Cash Operations for the business process.
Prerequisite
In the Preliminary Steps section of the Prerequisites, you created the pain.002.001.03_I071234_01.xml file and pain.002.001.03_I071234_02.xml file.
Procedure
Test Test Step Instruction Expected Result Pass /

Step Name Fail /
# Com-
ment
1 Retrieve the As part of the Prerequisites procedures, you created an XML file and added to a folder of your system. The XML file name must contain the
XML File string pain.002.001.03, for example, pain.002.001.03_I071234_01.xml.

Step Name Fail /
# Com-
ment
Retrieve the file for this procedure.

Because MBC does not accept files with the same name, if more than one tester is testing this scenario, always use a different file name each
time you test this step, replacing I071234_01 with a different ID you specify.
2 Open the Open the XML file in a text editor.

XML file
3 Edit XML Replace the values of the following fields:

file pain.002.001.03_I071234_01.xml by the values you noted down in the previous Send Payment Instruction to MBC procedure, and save the
pain.002.001.03_I071234_01.xml file locally.
The following values are provided as examples. Use the values from the previous Send Payment Instruction to MBC procedure.
XML Values:
<MsgId>Message ID</MsgId>, for example <MsgId> BBBB/100928-PSR/00120141222054500</MsgId>
Note 00120141222054500 is the real system data and time 001YYYYMMDDHHMMSS
<BIC>BIC</BIC>, for example, <BIC>BOFAUS3M</BIC>
Note You can find the BIC of house bank USBK1 in the Manage Banks - Basic (F1574) app
<OrgnlMsgId>Original Message ID</OrgnlMsgId>, for example, <OrgnlMsgId>1000004611</OrgnlMsgId>

<OrgnlCtrlSum>Amount</OrgnlCtrlSum> in <OrgnlGrpInfAndSts></OrgnlGrpInfAndSts>, for example,
<OrgnlPmtInfId>Original Payment Information ID</OrgnlPmtInfId>, for example,
<OrgnlCtrlSum>Amount</OrgnlCtrlSum> in <OrgnlPmtInfAndSts>< /OrgnlPmtInfAndSts>, for example,
<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 Upload the XML file you edited to the SFTP server folder. The XML file disappears from the SFTP
XML File For example, upload to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE4212/US BANK 1 server folder. A background job is sched-
uled to pull the payment status from MBC
The internal test step is the simulation of communication between S/4HANA and SFTP server. You can run test program /BSNAGT/ to SAP S/4HANA every 10 minutes.
TEST_INBOUND_MSG2 via transaction code SA38 if the connection is not running. Populate PAIN.002.001.03 in the message type field
and C:\Users\I071234\Desktop\pain.002.001.03_I071234_01.xml. in the file name field via search help. After execution, check whether in-
coming message is displayed in the MBC Connector Monitor.

Step Name Fail /
# Com-
ment
5 Path to Note The path to the SFTP server folder for payment status messages depends on the testing system, country, and house bank. For more
SFTP information on accessing the MBC bank tenants or SFTP server, contact the test organizer for help. In this example, a PAIN002 file for
Server house bank/account ID USBK1/USAC1 in country US is pulled from MBC.
Folder
6 Repeat Repeat the Steps from Step 2 to Step 5 for camt.053.001.02_AB12345_02.xml.

Bank State- Replace the values of the following fields:
ment Up-
pain.002.001.03_I071234_02.xml by the values you noted down in the previous Send Payment Instruction to MBC procedure, and save the
load
pain.002.001.03_I071234_01.xml file locally.
The following values are provided as examples. Use the values from the previous Send Payment Instruction to MBC procedure.
XML Values:
<MsgId>Message ID</MsgId>, for example <MsgId> 1000746725</MsgId>
Note 1000746725 is the payment media message ID, and you can find the ID in the payment media generated after Payment Run in Supplier
Financing (4AV)
<BIC>BIC</BIC>, for example, <BIC>BOFAUS3M</BIC>
Note You can find the BIC of house bank USBK1 in the Manage Banks (F1574) app
<OrgnlMsgId>Original Message ID</OrgnlMsgId>, for example, <OrgnlMs-gId>1000746725</OrgnlMsgId>
<OrgnlCtrlSum>Amount</OrgnlCtrlSum> in <OrgnlGrpInfAnd-Sts></OrgnlGrpInfAndSts>, for example, <OrgnlCtrlSum>600</OrgnlCtrl-
Sum>
<OrgnlPmtInfId>Original Payment Information ID</OrgnlPmtInfId>, for example, <OrgnlPmtInfId>1000746826</OrgnlPmtInfId>
<OrgnlCtrlSum>Amount</OrgnlCtrlSum> in <OrgnlPmtInfAndSts>< /OrgnlPmtInfAndSts>, for example, <OrgnlCtrlSum>600.00</
OrgnlCtrlSum>
first <OrgnlEndToEndId>Payment Document Number</OrgnlEndToEndId>, for exam-ple, <OrgnlEndToEndId>2000000037</OrgnlEnd-
ToEndId>
Note you can find the payment document number in the payment media generated after Payment Run in Supplier Financing (4AV). If there
are multiple payments generated in a payment media file, multiple entries need to be updated according in the corresponding status report.
first <InstdAmt Ccy="USD">Amount</InstdAmt>, for example, <InstdAmt Ccy="USD">100.00 </InstdAmt>
Note you can find the payment amount in the payment media generated after Payment Run in Supplier Financing (4AV). If there are multiple
payments generated in a payment media file, multiple entries need to be updated according in the corresponding status report.

5.2 Incoming Integration
5.2.1 Pull Bank Statement from MBC
Purpose
For banks with a Multi-Bank Connectivity (MBC) connection, for example, USBK1, bank statements are handled by MBC. You can check whether MBC is enabled for a specific combination of
company code, payment method house bank and payment media format in the preliminary step Check Alternative Format Type. SAP S/4HANA pulls the supported bank statement messages from
MBC and then imports it automatically.
A transaction type must be maintained in the field transaction type on the tab of Bank Relationship. You can refer to test script BFA or J77 change bank account section.
You can also define new transaction types in SSCUI 101024 Manage Global Settings for Electronic Bank Statement.
Test Administration
In the Preliminary Steps of the Prerequisites [page ] 4 section, you created an xml file and saved it to a folder of your PC.
The XML file name must contain the string camt.054.001.02, for example, camt.054.001.02_AB12345_01.xml.
Because MBC 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 AB12345 by a dif -
ferent ID you specified.
Access that XML file and using a text editor, edit the file for these XML values:
XML Text Example Comment
<MsgId>Message ID</MsgId> <MsgId>25YDSJO9ZB1D099999911</Ms- 25YDSJO9ZB1D099999911 is the unique message ID for the debit notification. Make
gId> sure you change it to a unique ID.

<Id>Account Number</Id> in <Othr></Othr> <Id>33333</Id> The account number of house bank/account ID USBK1/USAC1
<BIC>BIC</BIC> <BIC>BOFAUS3M</BIC> You can find the BIC of house bank USBK1 using the Manage Banks - Basic (F1574)
SAP Fiori app.
<Amt Ccy="USD">Notification Entry Amount</Amt> in the <Ntry></Ntry> <Amt Ccy="USD">600</Amt> The total amount of notification.
<CdtDbtInd>Credit Debit Indicator</CdtDbtInd> <CdtDbtInd>DBIT</CdtDbtInd> DBIT if the transaction is outflow, CRDT if the transaction is inflow. In this Supplier Fi-
nance business scenario, the indicator is always DBIT.
<RltdDt>Date</RltdDt> <RltdDt>2019-08-13</RltdDt> Replace the date with today
<Dt>Date</Dt> <Dt>2019-08-13</Dt> Replace the date with today
<Cd>Bank Transaction Code</Cd> in <BkTxCd><Partry></Prtry></BkTxCd> <Cd>ZSF054</Cd> The bank transaction code varies depending on the transaction simulated. In this Sup-
plier Finaning business scenario, the code is always ZSF054.
<EndToEndId>Journal Entry Document</EndToEndId> in each <NtryDtls></ <EndToEndId>2000000071</EndToEndId> The payment document number in the test step Send Payment Instruction to MBC (Op-
NtryDtls> if there are more than one payment tional) [page ] 35. If there are multiple payments in a payment media file, maintain the
corresponding entries accordingly.
<Amt Ccy="USD">Payment Amount</Amt> in each <NtryDtls>Entry De- <Amt Ccy="USD">500</Amt> The payment document amount in the test step Send Payment Instruction to MBC. If
tails<TxDtls>Transaction Details<AmtDtls>Amount De-tails</AmtDtls></ there are multiple payments in a payment media file, maintain the corresponding entries
TxDtls></NtryDtls> if there are more than one payment accordingly.
Prerequisite
Per the Business Conditions section in this document, you must execute Payment Run procedure in Supplier Financing (4AV), Make a note of the payment document number, the amount of the each
payment. You use this information when simulating an electronic bank statement.
Note Transaction Type Camt 053 should be set in the payment account. You can use Manage Bank Account app to do the setting, please refer to test script BFA or J77 change bank account sec-
tion.
Procedure
Perform the following steps to simulate an ISO CAMT.054 Bank-to-Customer-Debit-Notification for house bank/account ID USBK1 /USAC1 directly. MBC gets it from the SFTP server and the
SAP S/4HANA system pulls the ISO CAMT.054 bank statements from MBC.

In this example, the simulated debit notification is the follow-up business step of Supplier Financing process after bank has confirmed the payment instruction. The simulation debit notification con -
tains two line items:
● First item: a debit item which should be reconciled with the first payment document created in the payment run in test script Supplier Financing (4AV).
● Second item: a debit item that should be reconciled with the second payment document created in the payment run in test script Supplier Financing (4AV).
Test Test Step Instruction Expected Result Pass / Fail

Step # Name / Com-
ment
1 Access Open the camt.054 xml file with a text editor, for example, camt.054.001.02_AB12345_01.xml. Because MBC does not
the XML accept files with the same name, and more than one tester is testing this scenario, use a different file name every time when
File you test this step, and replace AB12345 by a different ID you specified.
2 Edit the Modify the XML file as previously described in the Prerequisites.
XML File In the ISO CAMT.054 bank statement file, always use ‘.’ as decimal point (don't use ‘,’). The date format should be
YYYY-MM-DD.
3 Upload Upload the XML file you edited to the SFTP server folder. The xml file is removed from the SFTP server folder in several
XML File For example, copy to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE421 2/US/ seconds. A background job is scheduled to pull the bank state-
BANK1 ment from MBC 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 MBC bank tenants or SFTP server, please contact test orga-
nizer for help.
In this example, a CAMT.054 file for house bank/account ID USBK1/USAC1 in country US is pulled from MBC.
Test Administration
In the Preliminary Steps of the Prerequisites section, you created two 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_AB12345_01.xml. File camt.053.001.02_AB12345_02.xml is for integration withSupplier Financing
(4AV) and Because MBC 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
AB12345 by a different ID you specified.camt.053.001.02_AB12345_01.xml is for integration with other business process for simplicity.
Access that XML file and using a text editor, edit the file camt.053.001.02_AB12345_01.xml . Because MBC does not accept files with the same name, name each file if more than one tester uses
the same XML values.
<MsgId>Message ID</MsgId> <MsgId>20141222102146</MsgId> 20141222102146 is the real system data and time YYYYMMDDHHMMSS
<ElctrncSeqNb>Bank Statement Number</ElctrncSeqNb> <ElctrncSeqNb>00006</ElctrncSeqNb> The next bank statement number
find a customer invoice<BIC>BIC</BIC> <BIC>BOFAUS3M</BIC> You can find the BIC of house bank USBK1 using the Manage Banks - Basic (F1574)
SAP Fiori app.
<Amt Ccy="USD">Opening Balance</Amt> in the first <Amt Ccy="USD">5002.30</Amt> Opening balance = closing balance of latest imported bank statement
<Bal></Bal>
<Dt>Opening Balance Date</Dt> in the first <Bal></Bal> <Dt>2014-12-22</Dt>
<Amt Ccy="USD">Closing Balance</Amt> in the second <Amt Ccy="USD">4018.83</Amt> Closing balance = opening balance - debit amount + credit amount; For example,
<Bal></Bal> 4018.83=5002.30+208.25-1191.72
<Dt>Closing Balance Date</Dt> in the second <Bal></Bal> <Dt>2014-12-22</Dt>
<Amt Ccy="USD">Item Amount</Amt> in the first <Ntry></ <Amt Ccy="USD">208.25</Amt> Customer invoice amount
Ntry>
<BookgDt><Dt>Booking Date</Dt></BookgDt> in the first <BookgDt><Dt>2014-12-22</Dt></BookgDt>

<Ntry></ Ntry>
<ValDt><Dt>Value date</Dt></ValDt> in the first <Ntry></ <ValDt><Dt>2014-12-22</Dt></ValDt>

Ntry>
<ChqNb>Reference</ChqNb> in the first <Ntry></ Ntry>. <ChqNb>MMTEST</ChqNb> which is the reference of cus- Customer invoice reference
tomer invoice.
<Amt Ccy="USD">Item Amount</Amt> in the second <Amt Ccy="USD">1191.72</Amt> The payment amount in the Send Payment Instruction to MBC (Optional) [page ] 35 step
<Ntry></ Ntry>

<BookgDt><Dt>Booking Date</Dt></BookgDt> in the sec- <BookgDt><Dt>2014-12-22</Dt></BookgDt>

ond <Ntry></ Ntry>
<ValDt><Dt>Value date</Dt></ValDt> in the second <Ntry> <ValDt><Dt>2014-12-22</Dt></ValDt></ Ntry>
<ChqNb>Reference</ChqNb> in the second <Ntry></ Ntry> <ChqNb>1000004611</ChqNb> The payment information ID in the Send Payment Instruction to MBC (Optional) [page ]
35 step
Edit the file camt.053.001.02_AB12345_02.xml for these XML values:
<MsgId>Message ID</MsgId> <MsgId>20190726074500</MsgId> 201907260745 is the real system data and time YYYYMMDDHHMM
<ElctrncSeqNb>Bank Statement Number</ElctrncSeqNb> <ElctrncSeqNb>138</ElctrncSeqNb> The next bank statement number
find a customer invoice<BIC>BIC</BIC> <BIC>BOFAUS3M</BIC> You can find the BIC of house bank USBK1 using the Manage Banks (F1574) SAP Fiori app.
<Amt Ccy="USD">Opening Balance</Amt> in the first <Bal></ <Amt Ccy="USD">1000.00</Amt> Opening balance = closing balance of latest imported bank statement
Bal>
<Dt>Opening Balance Date</Dt> in the first <Bal></Bal> <Dt>2019-07-26</Dt>
<Amt Ccy="USD">Closing Balance</Amt> in the second <Amt Ccy="USD">400.00</Amt> Closing balance = opening balance - debit amount + credit amount; For example, 400.00=1000.00-600.00
<Bal></Bal>
<Dt>Closing Balance Date</Dt> in the second <Bal></Bal> <Dt>2019-07-26</Dt>
<Amt Ccy="USD">Item Amount</Amt> in the first <Ntry></ <Amt Ccy="USD">600.00</Amt> Total amount of Bank to Customer Debit Notification. The amount should be the same as the total amount
Ntry> maintained in last step.
<BookgDt><Dt>Booking Date</Dt></BookgDt> in the first <BookgDt><Dt>2019-07-26</Dt></

<Ntry></ Ntry> BookgDt>
<ValDt><Dt>Value date</Dt></ValDt> in the first <Ntry></ <ValDt><Dt>2019-07-26</Dt></ValDt>

Ntry>
<Cd>Code</Cd> in <Ntry><BkTxCd><Prtry></Prtry></ <Cd>ZSF053</Cd> The transaction code is always ZSF053 in the Supplier Financing scenario.

BkTxCd></ Ntry>
Prerequisite
Per the Business Conditions section in this document, you must execute the Enter Invoice without Sales Order procedure in Accounts Receivable(J59), Sell from Stock (BD9), Supplier Financing
(4AV) or 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 use 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. MBC gets it from the SFTP server and the SAP S/4HANA system
pulls the ISO CAMT.053 bank statements from MBC.
Note In this example of the first file camt.053.001.02_AB12345_01.xml, the simulated bank statement contains two line items:
● First item: a credit item which should be reconciled with an existing customer invoice (created as per Prerequisites above).
● Second item: a debit item that should be reconciled with the payment document created in the Send Payment Instruction to MBC (Optional) [page ] 35 step.
In the example of the second file camt.053.001.02_AB12345_02.xml, the simulated bank statement contains one line item.
● Bank statement item: a debit item which should be reconciled with an interim bank account (created in test step ISO CAMT.054 Format).

Step Name Fail /
# Com-
ment
1 Log On Log onto the SAP Fiori launchpad as a Cash Management Specialist.
2 Access the Open Manage Bank Statements (F1564).

SAP Fiori
App
3 Enter Crite- To get the latest imported bank statement number, make the following entries and choose Go: The latest bank statement number of the specified bank ac-
ria Company Code: 1710 count displays on the Manage Bank Statements (F1564)
view.
House Bank: USBK1
The next bank statement number is one greater than the
House Bank Account: USAC1 latest bank statement number. For example, if the latest

Step Name Fail /
# Com-
ment
Latest Statement: Latest only bank statement number is 00005, the next number is
00006. If no latest bank statement was found, the next
number should be 00001.
4 Closing Bal- Make a note of the closing balance of the specified bank account. It can be found on the Manage Bank Statements (F1564) The closing balance of the latest bank statement should be
ance of Lat- view. the opening balance of the next bank statement.
est Bank If no latest bank statement was found, the opening balance
Statement 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_AB12345_01.xml. Because MBC does not accept
XML File files with the same name, and if more than one tester is testing this scenario, use a different file name every time when you test
this step, and replace AB12345 by a different ID you specified.
6 Edit the Modify the XML file as previously described in the Prerequisites.
XML File
Note In the ISO CAMT.053 bank statement file, always use ‘.’ as decimal point (don't use ‘,’). The date format should be
YYYY-MM-DD.
7 Upload Upload the XML file you edited to the SFTP server folder. The xml file is removed from the SFTP server folder in
XML File For example, copy to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE421 2/US/BANK1 several seconds. A background job is scheduled to pull the
bank statement from MBC to the S/4HANA system every
The internal test step is the simulation of communication between S/4HANA and SFTP server. You can run test program / 10 minutes.
BSNAGT/TEST_INBOUND_MSG2 via transaction code SA38 if the connection is not running. Populate CAMT.053.001.02
in the message type field and C:\Users\AB12345\Desktop\camt.053.001.02_AB12345_01.xml. in the file name field via search
help. After execution, check whether incoming message is displayed in the MBC Connector Monitor.
Note 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 MBC bank tenants or SFTP server, please contact test orga-
nizer for help.
In this example, a CAMT.053 file for house bank/account ID USBK1/USAC1 in country US is pulled from MBC.
8 Repeat bank Repeat the Steps from Step 3 to Step 7 for camt.053.001.02_AB12345_02.xml.
statement
upload

5.2.1.3 BAI2 Lockbox Message Format
Test Administration
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 Ac -
counts 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 Message from
MBC.
Create a new text file and name it BAI2_US_USBK1.txt. Enter the following text into it and save it locally on your PC:
100LOCKBOXDESLOCKBOXORI1803201454
58000001234567180320LOCKBOXDESLOCKBOXORI
60010010000021200003800108123456789
918833201
400100156011800001051 00000212000000000000GH
8000000123456718030500010000021200
9999900
Procedure
Perform the following steps to simulate a BAI2 bank statement for house bank/account ID USBK1/USAC1, MBC 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 MBC.
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 MBC.

Step # Name Fail /
Comment
1 Save File Refer to the text file BAI2_US_USBK1.txt you previously created in the Prerequisite section. The txt file name must contain the string
BAI2, for example, BAI2_US_USBK1_00006.txt. Because MBC 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.
2 Open File Use a text editor to open this txt file.
3 Edit File Modify the txt file as shown in the note row below.
Edit these Values in BAI2 file:
● In the first line, replace 1803201454 by the current date and time ( format YYMMDDHHMM).
● In the second line, replace 180320 to match the date on the first line.
● On the third line, replace 0000021200 by the sum total of all invoices with 2 decimal places and replace 918833201 to the check
number. ;
● On the fourth line, number 11800001051 is the sequence number invoice number. The first number is the sequence number, and
number 1800001051 is the invoice number. Number 0000021200 is the invoice amount. You can replace these numbers with the
right sequence number, right invoice number and right amount number.
● On the line 400100156011800001051 00000212000000000000GH 8000000123456718030500010000021200, replace the number
180305 to match the date on the first line.
Note In the BAI2 bank statement file, an amount does not contain decimal point, for example 21200 means 212.00. And the date
format should be YYMMDD.
4 Upload ● Upload the txt file you edited to the SFTP server folder. The txt file disappears from the SFTP server
File to For example, upload to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE4212/USUSBK1 folder. A background job is scheduled to pull the
Server bank statement from MBC to SAP S/4HANA ev-
Note The path of SFTP server folder for bank statements depends on testing system, tenant, country, and house bank. If you re- ery 10 minutes.
quire more information on how to access the MBC bank tenants or SFTP server, open a support (BCP) message under the compo-
nent LOD-MBC-INT.
In this example, a BAI2 bank statement file for house bank/account ID USBK1/USAC1 in country US is pulled from SFTP by
MBC, MBC will map it to an ISO CAMT.053 format file.

5.2.2 Import Electronic Bank Statement
Purpose
After the bank statement is pulled from Multi-Bank Connectivity (MBC), SAP S/4HANA imports the electronic bank statement automatically. The postings in bank accounting and subledger ac-
counting should be performed.
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
F011 Bank Fee
F012 Interest Received
F013 Interest Paid
F014 Returns Collection / Direct debit
F015 Returns vendor direct debit

Transactions Text
F016 Unallocated Credit
F017 Unallocated Debit
FCD1 Direct Check Deposit
FCD2 Check Deposit via interim Account
FSF1 SF Transfer (interim account) OI clear
FSF2 SF Outgoing Transfer w OI clearing
Procedure
After the background job pulls the bank statement from MBC, SAP S/4HANA imports the bank statement automatically. You can monitor the imported electronic bank statements in the Fiori App
Manage Bank Statements.
Note There is a column Manual Bank Statement to indicate if the bank statement is a manual bank statement or an imported electronic bank statement.
If the Cash Management Full (Extended) version is implemented in the system, then you review the relevant payment document using the Check Cash Flow Items (F0735), to review the status.
The status of the batch item should now be Stmt. Received.
Restriction The Check Cash Flow Items (F0735) app is not available in the Cash Management Basic (Core) version.
5.2.3 Pull Bank Services Billing Files from MBC
Test Administration

Purpose
In this activity, you simulate an ISO CAMT.086 bank fee file for bank 33333 import from MBC. SAP S/4HANA pulls the ISO CAMT.086 bank fee file from MBC and imports it automatically.
You can either upload the bank fee file manually via the Import Bank Services Billing Files app or import it via Multi-Bank Connectivity. For the manual upload process, see the Bank Fee Manage-
ment (2O0) test script.
Note The CAMT.086 bank fee management is in the scope of Bank Fee Management (2O0), which requires an Advanced Cash Management license.
Procedure
Test Test Instruction Expected Result Pass /

Step Step Fail /
# Name Com-
ment
1 Upload Upload the TXT file you edited to the SFTP server folder. The TXT file disappears from the SFTP server
File For example, upload to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE4212/DEDEBK1 folder in several seconds. A background job is
scheduled to pull the bank statement from MBC
The internal test step is the simulation of communication between S/4HANA and SFTP server. You can run test program /BSNAGT/
to the SAP S/4HANA system every 10 minutes.
TEST_INBOUND_MSG2 via transaction code SA38 if the connection is not running. Populate camt.086.001.01 in the message type field
and C:\Users\I071234\Desktop\Camt_086_DE_1133698_00001.xml. in the file name field via search help. After execution, check whether
incoming message is displayed in the MBC Connector Monitor.
Note The path of SFTP server folder for bank statements depends on the testing system, tenant, country, and house bank. If you want to
get sufficient information on how to access the MBC bank tenants or SFTP server, contact your test organizer for assistance.
5.2.4 Route Payment Files and Payment Transaction Messages

Purpose
In this activity, you simulate payment message and payment file import from MBC. SAP S/4HANA pulls the message and the file from MBC, then imports them automatically.
After import, the messages are routed into Advanced Payment Management for payment monitoring and approval.

Note The payment processing is in the scope of Advanced Payment Management (4MT), which requires an additional license.
5.2.4.1 Route Payment Transaction Messages Initiated by SAP Systems

Purpose
In this activity, you simulate a FICA ISO PAIN.001 credit transfer payment message import from MBC. You can either download the payment media file manually via the Manage Payment Media
app or import it via Multi-Bank Connectivity. For the manual download process, see the Contract Accounting - Company Initiated Payments (2DP) test script.
Note The supported FICA PAIN.001 message routing integration is in the scope of Contract Accounting - Company Initiated Payments (2DP), which requires an additional license.
Procedure
This test step is automatically conducted. The payment message will be converted into APM metaformat and the following test step is described in test step Receive Payment Transaction Messages
initiated by SAP Systems of test script Advanced Payment Management (4MT).
If automation is not supported in some cases such as payment on short notice, payment from subsidiaries, manual upload is also supported in test step Upload Bank Statement of test script Bank Inte-
gration with File Interface (1EG). The import file type is Payment File for Advanced Payment Management and the convert ID is ISO inbound MBC.
5.2.4.2 Route Payment Files Initiated by non-SAP Systems
Test Administration
Purpose
In this activity, you simulate a CSV payment file imported from MBC.
Note The CSV payment template can be found in test step Receive Payment Files Initiated by non-SAP Systems of test script Advanced Payment Management (4MT).

Procedure
Test Test Instruction Expected Result Pass /

Step Step Fail /
# Name Com-
ment
1 Upload Upload the CSV file you edited to the SFTP server folder. The CSV file disappears from the SFTP server
File For example, upload to the folder /home/S4HTESTHCI/simbank/outbox/s4hana/v0115/QE4212/DEDEBK1. The internal test step is the folder in several seconds. A background job is
simulation of communication between S/4HANA and SFTP server. You can run test program /BSNAGT/TEST_INBOUND_MSG2 via scheduled to pull the bank statement from MBC to
transaction code SA38 if the connection is not running. Populate SAP_APM_DEMO_CSV_CT in the message type field and C:\Users\ the SAP S/4HANA system every 10 minutes.
IAB1234\Desktop\IFME_TESTFILE_P1.csv. in the file name field via search help. After execution, check whether incoming message is
displayed in the MBC Connector Monitor.
Note The path of SFTP server folder for bank statements depends on the testing system, tenant, country, and house bank. If you want to
get sufficient information on how to access the MBC bank tenants or SFTP server, contact your test organizer for assistance.
Purpose
In this activity, you monitor situations and check instance details.
Procedure

Step # Name Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process
Configuration.
2 Access App Open Monitor Situations (F3264).
3 Enter Selec- In the upper area, make the following entries and press Enter: A chart and a list with instances that are displayed for outgoing payment situations:
tion Criteria Situation Type ID: ZFIN_MBC_MESSAGE_ERROR ● ZFIN_MBC_MESSAGE_ERROR: Shows all incoming messages with Error status

Step # Name Comment
ZFIN_MBC_MESSAGE_NO_MANPROC ● ZFIN_MBC_MESSAGE_MANPROC: Shows all incoming messages with Manual Processing

ZFIN_MBC_MESSAGE_NO_RECEIVED Required status
Year: for example, <current year> ● ZFIN_MBC_MESSAGE_RECEIVED: Shows all incoming messages with Received status
4 Check In- Expand the hierarchy by respective situation ID, you can check the instance trig- The MBC message ID which triggered the situation is displayed. You can check more details in the
stance gered by each message. In this case, the Anchor Object Key is the MBC mes- App Manage Bank Messages (F4385). For more details, you can refer to test step MBC Message
sage ID. Monitor.
Note If you can not find the Anchor Object Key, you can choose Settings and
select the columns to be visible in the list.
Purpose
In this activity, the notification is checked by the recipient who is assigned to team members in preliminary step.
Procedure
Test Step Test Step Name Instruction Expected Re- Pass / Fail / Com-
# sult ment
1 Log On Log on to the SAP Fiori launchpad as a recipient (for example, Bank Integration Specialist).
2 Check Notifi- On the home page, choose Notifications in the upper right corner.
cation Choose By Type, under type Bank Message Entering Error Status, Bank Message Requires Manual Processing or Bank Message Still in Status Received
has been identified, choose Expand Group.

5.3 MBC Message Monitor
Test Administration
Purpose
In this activity, you monitor all the messages transmitted out of S/4HANA via MBC and messages transmitted into S/4HANA via MBC.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Business Integration Special-

ist - Bank Integration.
2 Access App Open Manage Bank Messages (F4385).
3 Enter Selection Crite- In the upper area, make the following entries and press Enter: The MBC messages are displayed in respective tabs:
ria Message Type: CAMT.053.001.02 ● Outgoing Messages tab: Shows all the payment media files transmitted from SAP S/
4HANA
Creation Date: For example, <today’s date>
● Incoming Messages tab: Shows all bank statements and lockbox files transmitted from
MBC
● For Manual Processing tab: Show all messages received with message types that are un-
known to the MBC Connector.
● Error: Show all messages with error status.
● Created: Show all messages with issues of sending messages.
4 Display Message Con- Select a message and choose View Payload in the detail screen of The message content is displayed.

Step # Comment
tent message.
5 Navigation to Applica- Select a message and choose Log in the detail screen of message. The detail log of the message processing is listed.
tion Log

6 Appendix
6.1 Process Integration

The process to be tested in this test script is part of a chain of integrated processes.
6.2 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 MBC, 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 MBC, check the status in app Bank Statement Monitor.

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. 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 IN-
CLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parame-
ters, 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 documenta-
tion.
<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 .
© 2023 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. The information contained herein may be changed without
prior notice.
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 or its affiliated companies 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 war-
ranty statements accompanying such products 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 Germany and other countries. All other product
and service names mentioned are the trademarks of their respective compa-
nies.
See www.sap.com/copyright for additional trademark informa-

Bank Integration with SAP Multi-Bank Connectivity (16R_US) tion and notices.

16R S4CLD2302 BPD en Us

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

16R S4CLD2302 BPD en Us

Uploaded by

Copyright:

Available Formats

Test Script

SAP S/4HANA Cloud - 26-12-22

Bank Integration with SAP Multi-Bank Connectiv-

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

3.1 System Access

Cash Manage- SAP_BR_CASH_SPECIAL- Cash Management Specialist SAP_BR_CASH_SPECIALIST

Business Inte- SAP_BR_BANK_INT_SPE- Business Integration Specialist - Bank Integration SAP_BR_BANK_INT_SPECIALIST

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Data Sample Value Details Comments

Bank 011000390 820800001

House Bank USBK1 USBK2

House Bank Account ID USAC1

Bank Account Number 33333

Company Code 1710

3.4 Business Conditions

Scope Item Business Condition

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

3.5.1 Create pain.002.001.03_I071234_01.xml

This file is required for a later process step.

In a text editor, paste the following code:

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

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

3.5.2 Create pain.002.001.03_I071234_02.xml

This file is required for a later process step.

In a text editor, paste the following code:

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

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

3.5.3 Create camt.053.001.02_I071234_01.xml

This file is required for a later process step.

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

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

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

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

3.5.4 Create camt.054.001.02_I071234_01.xml

This file is required for a later process step.

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

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

3.5.5 Create camt.053.001.02_I071234_02.xml

This file is required for a later process step.

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

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

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

3.5.6 Check Alternative Format Type

Test Test Step Name Instruction Expected Result Pass / Fail /

1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert

2 Access App Open Manage Your Solution (F1241).

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

SAP Central Business Configuration:

Test Test Step Name Instruction Expected Result Pass /

Bank Integration with SAP Multi-Bank Connectivity (16R_US)

Test Test Step Name Instruction Expected Result Pass / Fail /

2 Access App Open Manage Your Solution (F1241).