SAP S/4HANA
September 2018
English
Bank Account
Management - Core [local]
(J74)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Copyright
© 2018 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 affiliate
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 informational purposes only, without representation or warranty of any kind, and
SAP SE or its affiliated companies shall not be liable for errors or omissions 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 accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation,
or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy
and possible future developments, products, and/or 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 notice. The information in this document is not a commitment, promise, or legal obligation to deliver
any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 2 of 12
SAP Best Practices
Revision
© SAP SE
Bank Account Management - Core [local] (J74): Configuration Guide
Change Date
Description
Page 3 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field names,
screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example
text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE
TEXT
Names of elements in the system. These include report names, program
names, transaction codes, table names, and individual key words of a
programming language, when surrounded by body text, for example, SELECT
and INCLUDE.
Example
text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as names
of installation, upgrade and database tools.
EXAMPLE TEXT Keys
on the keyboard, for example, function keys (such as F2) or the ENTER
key.
Example
text
Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example
text>
Variable user entry. Pointed brackets indicate that you replace these words
and characters with appropriate entries.
© SAP SE
Page 4 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Content
1 Purpose .............................................................................................................................. 6
2 Preparation ......................................................................................................................... 6
2.1
Prerequisites ............................................................................................................ 6
2.2
Supported Deployments ........................................................................................... 6
3 Configuration ...................................................................................................................... 6
3.1
Create Banks, House Banks, Bank Accounts .......................................................... 7
3.1.1
Create Bank Master Data for House Banks ........................................................ 7
3.1.2
Create Bank Master Data for Demo Data (Customer, Vendor, etc.) ................... 7
3.1.3
Define House Banks - House Banks ................................................................... 8
3.1.4
Create Bank Accounts in Cash Management ...................................................... 9
4 Manual Build Steps .......................................................................................................... 12
© SAP SE
Page 5 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Bank Account Management - Core [local] (J74):
Configuration Guide
1 Purpose
The purpose of this document is to describe the general configuration steps required to
manually set up the configuration within the system landscape that has already been installed
using the corresponding installation or configuration guides for installation.
If you want to install SAP S/4HANA locally (on-premise) and if you do not want to configure
manually and prefer an automated installation process using BC Sets and other tools, you
can set up a best-practice client and activate the implementation content. For more
information, see the Administration Guide for the Implementation of SAP S/4HANA, on
premise edition which is linked in the content library (included in the documentation package).
2 Preparation
2.1 Prerequisites
Before you start installing this scenario, you must install the prerequisite building blocks. For
more information, see the Building Block Prerequisites Matrix.
2.2 Supported Deployments
The configuration guide provides the implementation content for the different SAP S/4HANA
products:

SAP S/4HANA Cloud – (CE) minimal scope and content
 SAP S/4HANA – (OP) installed locally (on-premise), full scope and content coverage
Depending on the use case/deployment option/ S/4HANA product version, you need to
implement the required scope/content starting with the Public cloud chapter and proceed with
the next required sections.

For the full scope of the on premise scope & content – PC and OP are required

For the SAP S/4HANA Cloud scope & content – CE is required; OP is not required
3 Configuration
The following section describes the complete settings for this building block. These settings
can be divided into three main groups:

Prerequisite settings that have to be checked and which were delivered by SAP (as part
of the standard delivery)
The term Check refers to these prerequisite settings.

Settings defined by the customer (in the customer namespace and customer-specific):
The system uses automation to request individual customer settings during the
personalization process. These settings can be initial or reused from existing SAP ERP
layers and are indicated in the text by <your value>.

Additional settings that must be made, covered either by automation or manual
configuration (in the customer namespace).
The term Create refers to these additional settings in the text.
© SAP SE
Page 6 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
3.1 Create Banks, House Banks, Bank Accounts
3.1.1
Create Bank Master Data for House Banks
Use
If you want to run the automatic payment run program or if you want to post a bank statement
automatically you must set up bank master data in your system.
In this step, create the bank keys for house banks.
Procedure
1. Access the activity using one of the following navigation options:
SAP menu
SAP Menu  Accounting  Financial Accounting  Banks  Master
Data  Bank Master Record  Create
Transaction
code
FI01
2. On the Create Bank: Initial Screen, make the following entries:
Field name
Description
User action and values
Bank Country
MX
Bank Key
012
Note
3. On the Create Bank: Detail Screen, make the following entries:
Field name
Description
User action and values
Note
Bank 1 – SAMPLE BANK
Bank Name
Region
Street
AV. PASEO DE LA REFORMA 510
City
Distrito Federal
Swift Code
BCMRMXMM
Bank Group
4. Save your entries.
5. Repeat the steps above to create other bank keys::
Bank Key
Bank
coun
try
key
Name of
bank
House
number
and
street
City
SWIFT Code
for
International
Payments
014
MX
Bank 2 SAMPLE
BANK MX
Prol.
Reforma,
800
Distrito
Federal
BMSXMXMMXX
X
3.1.2
Create Bank Master Data for Demo Data (Customer,
Vendor, etc.)
Use
Create the bank keys which should be used for demo data, like customer, vendor, etc.
© SAP SE
Bank
Nunmber
Page 7 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu
SAP Menu  Accounting  Financial Accounting  Banks  Master
Data  Bank Master Record  Create
Transaction
code
FI01
2. On the Create Bank: Initial Screen, make the following entries:
Field name
Description
User action and values
Bank Country
MX
Bank Key
044
Note
3. On the Create Bank: Detail Screen, make the following entries:
Field name
Bank Name
Description
User action and values
Note
Bank 5 - SAMPLE BANK (MX)
Region
Street
Calle, 30
City
Distrito Federal
Swift Code
MBCOMXMM
Bank Group
4. Save your entries.
5. Repeat activity 2 to 4 for creating other bank keys in following Excel sheet:
Bank keys.xlsx
3.1.3
Define House Banks - House Banks
Use
Each house bank of a company code is represented by a bank ID in the SAP system, every
account at a house bank by an account ID.
In the SAP system, you use the bank ID, and the account ID to specify bank details
Procedure
1. Access the activity using one of the following navigation options:
IMG menu
N/A
Transaction code
FI12_HBANK
2. On the Determine Work Area: Entry dialog box, in the Company Code field, enter 1010,
and choose Enter.
3. On the Change View "House Banks": Overview screen, choose New Entries.
4. On the New Entries: Details of Added Entries screen, make the following entries:
Field name
Description
User action and values
House Bank
MXBK1
Bank Country
MX
© SAP SE
Page 8 of 12
Note
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Field name
Description
User action and values
Bank Key
012
Customer number
5510001
Company number
5510
Create Central Bank Report
Select
Note
Area number
Forward pay. Data
Select
5. Choose Back.
6. On the Change View "House Banks": Overview screen, choose New Entries.
7. On the New Entries: Details of Added Entries screen, make the following entries:
Field name
Description
User action and values
House Bank
DEBK2
Bank Country
DE
Bank Key
82080000
Customer number
2220002
Company number
1010
Note
8. Save your entries.
3.1.4
Create Bank Accounts in Cash Management
Use
For each house bank several bank accounts must be maintained.
Procedure
1. Access the activity using one of the following navigation options:
IMG menu
Financial Supply Chain Management Cash and Liquidity
Management  Bank Account Management  Maintain the
Event Type Linkage for Triggering Workflow Processes
Transaction code
SWETYPV
2. On the Change View "Event Type Linkage ": Overview screen, choose the default entry
with the following field values and choose Details.
Field Name
Entry Value
Object Category
BO(BOR Object Type)
Object Type
FCLM_CR
Event
CREATED
Receiver Type
WS74300043
3. On the Change View "Event Type Linkage ": Details screen, check the following settings:
Field Name
Entry Value
Linkage Activated
(Unselect the checkbox)
4. Save your entries.
5. Access the activity using one of the following navigation options:
© SAP SE
Page 9 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Fiori
Launchpad
Please contact system administrator to get the url of Fiori Launchpad,
the user and password.
The user must be assigned with business role:
SAP_BR_CASH_SPECIALIST
Fiori app
Manage Bank Accounts
6. On the Bank Hierarchy: Active Accounts (XX Accounts) screen, choose New Bank
Account.
7. On the New Bank Account screen, enter the following data:
Field Name
Entry Value
Company Code
5510
Account Holder
Company Code 5510
Bank Country
MX
Bank Key
012
Currency
MXN
Account Number
012180123456789019
Description
Bank 1 Giro
Account Type
01
IBAN
IBAN Valid From
<Current Date>
Opening Date
<Current Date>
8. Choose Save as Active.
9. Choose Edit.
10. Choose tab Connectivity Path, choose Add, and enter the following data:
Field Name
Entry Value
ID Category
Central System: House Bank Account
Company Code
5510
House Bank
MXBK1
House Bank Acct ID
MXAC1
G/L Account
0011001000 (leave blank if the G/L account doesn’t exist in
company code 5510)
11. Choose Save as Active.
12. Create another two bank accounts by repeating the steps in Fiori Launchpad above, and
use the following data:
Field Name
Entry Value
Company Code
5510
Account Holder
Company Code 5510
Bank Country
MX
Bank Key
014
Currency
MXN
Account Number
014180123456789019
© SAP SE
Page 10 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Field Name
Entry Value
Description
Bank 2 Giro
Account Type
01
IBAN
IBAN Valid From
<Current Date>
Opening Date
<Current Date>
ID Category
Central System: House Bank Account
Company Code
5510
House Bank
MXBK2
House Bank Acct ID
MXAC2
G/L Account
0011002000 (leave blank if the G/L account doesn’t exist in
company code 5510)
Field Name
Entry Value
Company Code
5510
Account Holder
Company Code 5510
Bank Country
MX
Bank Key
012
Currency
USD
Account Number
012456789011167549
Description
Bank 1 USD account
Account Type
01
IBAN
IBAN Valid From
<Current Date>
Opening Date
<Current Date>
ID Category
Central System: House Bank Account
Company Code
5510
House Bank
MXBK1
House Bank Acct ID
MXDAC
G/L Account
0011001100 (leave blank if the G/L account doesn’t exist in
company code 5510)
13. Access the activity using one of the following navigation options:
IMG menu
Financial Supply Chain Management Cash and Liquidity
Management  Bank Account Management  Maintain the
Event Type Linkage for Triggering Workflow Processes
Transaction code
SWETYPV
14. On the Change View "Event Type Linkage ": Overview screen, choose the default entry
with the following field values and choose Details.
© SAP SE
Page 11 of 12
SAP Best Practices
Bank Account Management - Core [local] (J74): Configuration Guide
Field Name
Entry Value
Object Category
BO(BOR Object Type)
Object Type
FCLM_CR
Event
CREATED
Receiver Type
WS74300043
15. On the Change View "Event Type Linkage ": Details screen, check the following settings:
Field Name
Entry Value
Linkage Activated
X (Select the checkbox)
16. Save your entries.
4 Manual Build Steps
The following table lists the configuration activities where automatic transport from Q2P is not
possible. We recommended that you should manually create the below listed master data in
the target system.
Configuration activity
Manual
transport
possible
Manual action in
target system /
client required
Remarks
3.1.1 Create Bank
Master Data for House
Banks
No
Yes
Refer to test script BFA
Create bank account.
3.1.2 Create Bank
Master Data for Demo
Data (Customer, Vendor,
etc.)
No
Yes
Refer to test script BFA
Create bank account.
3.1.3 Define House
Banks - House Banks
No
Yes
Refer to test script BFA
Create bank account.
3.1.4 Create Bank
Accounts in Cash
Management
No
Yes
Refer to test script BFA
Create bank account.
© SAP SE
Page 12 of 12