SAP S/4HANA
September 2017
English
Bank Account
Management
- Core (J73)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
Copyright
© 2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP 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
Public
Page 2 of 12
SAP Best Practices
Revision
Bank Account Management – Core (J73): Configuration Guide
Change Date
Description
0
© SAP SE
Public
Page 3 of 12
SAP Best Practices
Bank Account Management – Core (J73): 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
Public
Page 4 of 12
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
Content
Bank Account Management – Core (J73): Configuration Guide ............................................... 6
1 Purpose .............................................................................................................................. 6
2 Preparation ......................................................................................................................... 6
2.1
Prerequisites ............................................................................................................ 6
2.2
Supported Deployments ........................................................................................... 6
3 Configuration ...................................................................................................................... 6
3.1
Switch on Basic (Core) Cash Management (Extended/Full CM is off) .................... 6
3.2
Basic Settings .......................................................................................................... 7
3.2.1
Define Number Ranges for Bank Account Technical IDs .................................... 7
3.2.2
Define Number Ranges for Workflow Change Requests .................................... 7
3.2.3
Define Settings for Bank Account Master Data ................................................... 8
3.3
Deactivate the Event Type Linkage for Triggering Workflow Processes ............... 10
3.4
Define Rating ......................................................................................................... 10
3.5
Define BP Role TR0703 ......................................................................................... 11
4 Manual Build Steps .......................................................................................................... 12
© SAP SE
Public
Page 5 of 12
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
Bank Account Management – Core (J73):
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
3.1 Switch on Basic (Core) Cash Management
(Extended/Full CM is off)
Use
Switch on the Basic (Core) version of cash management, meanwhile the extended (full)
version of cash management is switched off.
Procedure
1. Access the transaction using the following navigation path:
Transaction Code
© SAP SE
SPRO
Public
Page 6 of 12
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
Financial Supply Chain Management Cash and Liquidity
Management  General Settings  Basic Settings
IMG Menu
2. On the Change View „General Settings for Cash Management“: overview screen, if there
is no entry available, choose New Entries.
3. Enter the following values:
Field Name
Entry Value
Cash Management Scope
01 Basic Cash
Mass Change Grouping Mode
00 None
Dual Control for Bank Account
Revision
01 Activate Directly
4. If there is alreay entry available, modify it according to the values listed above.
5. Save your entry.
3.2 Basic Settings
3.2.1 Define Number Ranges for Bank Account Technical
IDs
Use
In this Customizing activity, you create number range intervals for bank account technical IDs.
The system automatically assigns a technical ID to a bank account once it is created in the
bank account master data.
Procedure
1. Access the transaction using the following navigation path:
Transaction
Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management
 Bank Account Management  Basic Settings  Define Number
Ranges for Bank Account Technical IDs
1. On the Range Maintenance: Account ID screen, choose Change Intervals.
2. On the Maintain Intervals: Account ID screen, create the following settings:
Field Name
Entry Value
No
01
From No.
1000000000
To Number
1999999999
Ext
Blank
3. Save your entries.
3.2.2
Define Number Ranges for Workflow Change Requests
Use
In this Customizing activity, you create number range intervals for change requests used in
Bank Account Management. The system automatically assigns a number to a change request
once it is created in Bank Account Management.
© SAP SE
Public
Page 7 of 12
Bank Account Management – Core (J73): Configuration Guide
SAP Best Practices
Procedure
4. Access the transaction using the following navigation path:
Transaction
Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management
 Bank Account Management  Basic Settings  Define Number
Ranges for Workflow Change Requests
5. On the Range Maintenance: FC_CREQID screen, choose Change Intervals.
6. On the Maintain Intervals: FC_CREQID screen, create the following settings:
Field Name
Entry Value
No
01
From No.
000000000001
To Number
999999999999
Ext
Blank
7. Save your entries.
3.2.3 Define Settings for Bank Account Master Data
Use
In this Customizing activity, you define the following basic settings for the bank account
master data.
3.2.3.1Assign Bank Account Technical IDs Number Range
Group Number
Use
To do so, you must have maintained number ranges in step 3.2.1 Define Number Ranges for
Bank Account Technical IDs.
Procedure
1. Access the transaction using the following navigation path:
Transaction
Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management
 Bank Account Management  Basic Settings  Assign Number
Ranges
2. On the Change View "Bank Account Master Data Setting ": Details screen, in the Dialog
Structure pane, double-click Bank Account Master Data Setting.
3. Create the following settings:
Field Name
Entry Value
Req. No. Range
01
Tech. ID No. Rang
01
4. Save your entries.
© SAP SE
Public
Page 8 of 12
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
3.2.3.2Define Account Type Definition
Use
In this activity, you define the account type.
Procedure
1. Access the transaction using the following navigation path:
Transaction
Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management
 Bank Account Management  Basic Settings  Define Settings for
Bank Account Master Data
2. On the Change View "Bank Account Master Data Setting ": Details screen, in the Dialog
Structure pane, double-click Account Type Definition.
3. Choose New Entries.
4. On the New Entries: Details of Added Entries screen, create the following settings:
Type
Account Type Description
Direction
Attribute
01
Current Account
B Inflow and Outflow
01 Operating Account
02
Current Account (Internal)
B Inflow and Outflow
01 Operating Account
03
Deposit Account
B Inflow and Outflow
02 Functional Account
04
Loan Account
B Inflow and Outflow
02 Functional Account
05
Investment Account
B Inflow and Outflow
02 Functional Account
06
Tax Account
B Inflow and Outflow
02 Functional Account
07
Margin Account
B Inflow and Outflow
02 Functional Account
08
Salary Account
B Inflow and Outflow
02 Functional Account
09
Checking Account
B Inflow and Outflow
02 Functional Account
10
Lockbox Account
B Inflow and Outflow
02 Functional Account
5. Save your entries.
3.2.3.3Define Import Methods for Bank Statements
Use
On the Additional Data tab for each bank account master record, users can select one of
defined methods as the Import Method for End-of-Day Statements, and one as the Import
Method for Intra-Day Statements.
Procedure
1. Access the transaction using the following navigation path:
Transaction
Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management
 Bank Account Management  Basic Settings  Define Settings for
Bank Account Master Data
2. On the Change View "Bank Account Master Data Setting ": Details screen, in the Dialog
Structure pane, double-click Define Import Methods for Bank Statements.
3. Choose New Entries.
© SAP SE
Public
Page 9 of 12
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
4. On the New Entries :Details of Added Entries screen, create the following settings:
Import Method ID
Description
01_BANK1
Import via BANK1
02_ BANK2
Import via BANK2
NO_IMPORT
No import of bank statement
5. Save your entries.
3.3 Deactivate the Event Type Linkage for Triggering
Workflow Processes
Use
To deactivate the workflow for Bank Account Management process, customers can not use
the approval process for bank account.
Procedure
1. Access the transaction using the following navigation path:
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
1. 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
2. On the Change View "Event Type Linkage ": Details screen, check the following settings:
Field Name
Entry Value
Linkage Activated
(Unselect the checkbox)
3. Save your entries.
3.4 Define Rating
Use
In this IMG activity you can define ratings. Ratings are part of the business partner's credit
standing data.
You can store an internal, time-independent rating for a business partner from an institute
providing credit standing information in the credit standing data.
Procedure
1. Access the activity by using the following navigation option:
Transaction Code
© SAP SE
SPRO
Public
Page 10 of 12
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
Financial Supply Chain Management Cash and Liquidity
ManagementGeneral SettingsMarket DataDefine
Rating
IMG Menu
2. Choose New Entries.
3. Enter the following data:
Rating
Desc.
A
A
AA
AA
AAA
AAA
B
B
BB
BB
BBB
BBB
C
C
CC
CC
CCC
CCC
D
D
4. Choose Save (Ctrl+S).
3.5 Define BP Role TR0703
Use
In this IMG activity, you define the business partner roles and their attributes. You also define
the role categories with other relevant data.
Procedure
2. Access the transaction using the following navigation path:
Transaction
Code
SPRO
IMG Menu
Cross- Application Components SAP Business Partner Business
Partner  Basic Settings  Business Partner Roles  Define BP
Roles
3. On the Change View "BP Roles": Overview screen, check whether BP role TR0703
exists. If BP role TR0703 doesn't exist, choose New Entries.
4. On the New Entries :Details of Added Entries screen, create the following settings:
Field Name
Entry Value
BP Role
TR0703
Title
Bank
Description
Bank
BP Role Cat.
TR0703 Credit Institute
Std Assignment BP Role ->
BP Role Cat.
Select this checkbox
BP View
FS0001
© SAP SE
Public
Page 11 of 12
SAP Best Practices
Bank Account Management – Core (J73): Configuration Guide
5. Save your entries.
4 Manual Build Steps
Some settings cannot automatically be transported between systems or clients. In these
cases, you either transport the settings manually, if possible, or make the settings in the
target system or client.
The following table lists the configuration activities where automatic transport is not possible.
Refer to the details and sequence in the sections above.
Configuration activity
Manual
transport
possible
Manual action in
target system / client
required
3.2.1 Define Number Ranges
for Bank Account Technical IDs
No
Yes
3.4 BAM - House Bank
Accounts Redirection
No
Yes
Remarks
We recommend that you plan especially for doing these manual build steps and rehearse the
sequence in advance, if possible well before cut over.
© SAP SE
Public
Page 12 of 12