Payment Engine from
SAP 7.0
October 2014
English
Payment Engine for
Deposit Management
(L90)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Copyright
© 2014 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 26
SAP Best Practices
Payment Engine for Deposit Management (L90): 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 3 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Contents
1
2
Purpose ................................................................................................................................................ 5
Preparation ........................................................................................................................................... 5
2.1
Prerequisites .............................................................................................................................. 5
3 Configuration ........................................................................................................................................ 5
3.1
Payment Order Settings............................................................................................................. 6
3.1.1
Defining Payment Order Types ............................................................................................. 6
3.1.2
Maintaining Enrichment & Validation Check Set Rules ......................................................... 7
3.2
AM Proxy.................................................................................................................................... 9
3.2.1
Maintaining Transfer of Posting Date .................................................................................... 9
3.3
SWIFT Format Converter......................................................................................................... 10
3.3.1
Changing Hierarchy Derivation for SWIFT Transaction Types ........................................... 10
3.4
SEPA Format Converter .......................................................................................................... 12
3.4.1
Determining Payment Order Type ....................................................................................... 12
3.4.2
Determining PE Transaction Type (SEPA Format Converter) ............................................ 14
3.4.3
Determining Payment Order Priority (SEPA Format Converter) ......................................... 15
3.4.4
Determining the Authorization Flag for Payment Orders..................................................... 16
3.5
File Handler .............................................................................................................................. 17
3.5.1
Maintaining Converter.......................................................................................................... 17
3.5.2
Maintaining Default Values for Format Converters ............................................................. 18
3.5.3
Determining PE Transaction Type ....................................................................................... 18
3.6
XML Converter ......................................................................................................................... 20
3.6.1
Defining Converter Implementation for Format Converter .................................................. 20
3.7
Functional Monitoring ............................................................................................................... 20
3.7.1
Maintaining Functional Monitoring Statuses ........................................................................ 20
3.8
Mater Data ............................................................................................................................... 22
3.8.1
Creating Current Account .................................................................................................... 22
3.8.2
Changing Clearing Agreement ............................................................................................ 23
© SAP SE
Page 4 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Payment Engine for Deposit Management
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 do not want to configure manually and prefer automated installation using BC Sets and other
tools, refer to the Quick Guide of your SAP rapid-deployment solution that is attached to the SAP
Note.
This document supplements the existing Customizing documentation in the Implementation Guide
(IMG) and provides additional information where required.
In general, to be able to start configuring the attributes related to the loan life cycles, some general
settings for Banking Services must be made.
2 Preparation
This building block is built for Payment Engine from SAP 7.0
2.1 Prerequisites
Before starting the installation, complete the following activities:

Read the Quick Guide document delivered with the specific SAP RDS package.

Ensure that you meet the recommended prerequisites.

Install the prerequisite building blocks.
- For more information, see the document Prerequisites_Matrix_<pc>_<pv>_EN_XX. xls.
The placeholder [pc] depends on the RDS Packages you use, for example
RDS_FS_LOANS refers to the SAP Loans Management rapid-deployment solution, the
placeholder [pv ] depends on the product version, for example BNK80 refers to Banking
services from SAP 8.0, EN refers to the language like EN for English language and [xx]
depends on the country version for example XX for Cross Country, in full for example
Prerequisites_Matrix_RDS_FS_LOANS_BNK80_EN_XX.xls.
-
This document can be found in the Step-by-Step Guide on Deploy  Implement Options
Manual Activation  Content Library  Prerequisites Matrix.
3 Configuration
The following section describes the complete settings for this building block. These settings can be
divided into three main groups:
1. 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.
Specify all prerequisites necessary for the configuration of this building block (even if this
means describing a complete table). Prerequisite settings are those settings that direct or
influence the business process. Do not describe settings that are for documentation
purposes only and that do not influence the process, such as generic code lists for
currencies or countries. These settings are not described as prerequisites.
2. 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 made initially or can be reused from
existing SAP ERP layers and are indicated in the text by <your value>.
© SAP SE
Page 5 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
If you need to explain the customer value, choose one of the following options:

If you have a short explanation, enter it directly in the table.

If you need a longer explanation, add an asterisk * after the customer value (<your
value>*) and explain the value in the Comment paragraph.
3. Additional settings that need to be made, which are covered either by automation or by manual
configuration (in the customer namespace):
The term Create refers to these additional settings in the text.
Personalization
In this configuration guide, some fields are marked with (*) – Personalized field.
If the solution is implemented manually using the delivered configuration guides, the fields marked
for personalization have to be taken into consideration.
During the configuration, you have to adjust the values provided for these fields in line with the
values relevant for your implementation (for example, the currency in the configuration guides is
marked as personalized field. Always replace the specified currency (EUR) with the currency
relevant for your RDS).
For more details on personalization, see sections 7.2.1 and 7.2.3.5.2 in the Quick Guide. The
overview table in the Quick Guide lists all the fields/values that are personalized along with a brief
explanation.
3.1 Payment Order Settings
3.1.1 Defining Payment Order Types
Use
A payment order type identifies the product of an incoming or outgoing transaction. It is used to
control the detailed process of a payment order within Payment Engine.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  Payment Order  Define Payment Order
Types
2. Choose the New Entries pushbutton and create the following settings:
Field name
Entry Value
Clearing Area
RDS000
Order Type
100103
PO Type Desc.
SCT Inc. Order
Long Desc.
SEPA SCT Order (incoming)
PO Category
1001
PO No. Range
01
CLR No. Range
01
ORP No. Range
01
RCP No. Range
01
TOV No. Range
01
Auth. Timeout
00:00:00
PI Emb. Timeout
00:00:00
© SAP SE
Page 6 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Field name
Entry Value
Enrich. & Valid. Grp
EV_STD
Func. Monitor. Grp
FM_STD
3. Choose Save.
Steps for Creating Multiple Entities for Independent Testing
If several independent entities need to be configured, the configuration step described above must
be performed x more times (up to 20) with the following settings:
Clearing Area
Clearing Area Name (*)
RDS001
Clearing Area RDS 001
RDS002
Clearing Area RDS 002
RDS003
Clearing Area RDS 003
RDS004
Clearing Area RDS 004
RDS005
Clearing Area RDS 005
RDS006
Clearing Area RDS 006
RDS007
Clearing Area RDS 007
RDS008
Clearing Area RDS 008
RDS009
Clearing Area RDS 009
RDS010
Clearing Area RDS 010
RDS011
Clearing Area RDS 011
RDS012
Clearing Area RDS 012
RDS013
Clearing Area RDS 013
RDS014
Clearing Area RDS 014
RDS015
Clearing Area RDS 015
RDS016
Clearing Area RDS 016
RDS017
Clearing Area RDS 017
RDS018
Clearing Area RDS 018
RDS019
Clearing Area RDS 019
RDS020
Clearing Area RDS 020
(*) Personalized field
3.1.2 Maintaining Enrichment & Validation Check Set Rules
Use
Here the check setsare defined determining which different checks are applied to payment orders
and payment items during processing in the Payment Engine.
Procedure
4. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  Payment Order  Payment Order
Enrichment & Validation  Maintain Enrichment & Validation
Check Sets
© SAP SE
Page 7 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
5. Choose Assign E&V Check Set for Payment Order under Dialog Structure.
6. On the Change View “Assign E&V Check Set for Payment Order”: Overview screen, choose the
New Entries pushbutton.
7. On the New Entries: Overview of Added Entries screen, create the following settings:
User
Action
Clearing
Area (*)
E&V
Group
E&V Set
Type
Executi
on Time
Channel
Format
Check
Set ID
Create
RDS000
EV_STD
1
1
1
4
4
4
E
S
X
E
S
X
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
21
21
21
4
4
4
8. Choose Save to save your entries.
9. Choose Assign E&V Check Set for Payment Item under Dialog Structure.
10. On the Change View “Assign E&V Check Set for Payment Item”: Overview screen, choose the
New Entries pushbutton.
11. On the New Entries: Overview of Added Entries screen, create the following settings:
Use
r
Acti
on
Clear
ing
Area
(*)
Transacti
on Type
Group for
E&V
E&V
Set
Type
Execution
Time
Cre
ate
RDS
000
EV_SEPA
EV_SEPA
EV_SEPA
EV_SEPA
EV_SEPA
EV_SEPA
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
EV_STD
2
2
2
2
2
2
1
1
1
2
2
2
2
2
2
2
2
2
E
E
S
S
X
X
E
S
X
E
E
E
S
S
S
X
X
X
Int.
Ro
ute
X
X
X
X
X
X
X
X
X
Channel
For-mat
Internal
Chec
k Set
ID
/SEPA
/SEPA
/SEPA
/SEPA
/SEPA
/SEPA
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/SWIFT
/XML
/XML
/XML
/XML
/XML
/XML
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
/1SW101
N
Y
N
Y
N
Y
Y
Y
Y
N
Y
Y
N
Y
Y
N
Y
Y
23
23
23
23
23
23
02
02
02
03
03
03
03
03
03
03
03
03
(*) Personalized field
12. Choose Save to save your entries.
Steps for Creating Multiple Entities for Independent Testing
If several independent entities need to be configured, the configuration step described above must
be performed x more times (up to 20) with the following settings:
Clearing Area
Clearing Area Name (*)
RDS001
Clearing Area RDS 001
© SAP SE
Page 8 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Clearing Area
Clearing Area Name (*)
RDS002
Clearing Area RDS 002
RDS003
Clearing Area RDS 003
RDS004
Clearing Area RDS 004
RDS005
Clearing Area RDS 005
RDS006
Clearing Area RDS 006
RDS007
Clearing Area RDS 007
RDS008
Clearing Area RDS 008
RDS009
Clearing Area RDS 009
RDS010
Clearing Area RDS 010
RDS011
Clearing Area RDS 011
RDS012
Clearing Area RDS 012
RDS013
Clearing Area RDS 013
RDS014
Clearing Area RDS 014
RDS015
Clearing Area RDS 015
RDS016
Clearing Area RDS 016
RDS017
Clearing Area RDS 017
RDS018
Clearing Area RDS 018
RDS019
Clearing Area RDS 019
RDS020
Clearing Area RDS 020
(*) Personalized field
3.2 AM Proxy
3.2.1 Maintaining Transfer of Posting Date
Use
The posting date can either be calculated within Payment Engine and transferred to the account
management system or can be can be ignored. This activity defines this per clearing area and
account management area based on payment transaction type and payment item category.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  AM Settings  AM Proxy  Posting 
Maintain Transfer of Posting Date
2. Choose the New Entries pushbutton and create the following settings in the fields listed:
User
Action
Clrng
Area
Acct
Mng.
PE Tr.Type
Item Cat.
Transfer
Create
RDS000
BR00
200000
03
1
3. Choose Enter.
4. Save entries.
Steps for Creating Multiple Entities for Independent Testing
© SAP SE
Page 9 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
If several independent entities need to be configured, the configuration step described above must
be performed x more times (up to 20) with the following settings:
Clearing Area
Clearing Area Name (*)
RDS001
Clearing Area RDS 001
RDS002
Clearing Area RDS 002
RDS003
Clearing Area RDS 003
RDS004
Clearing Area RDS 004
RDS005
Clearing Area RDS 005
RDS006
Clearing Area RDS 006
RDS007
Clearing Area RDS 007
RDS008
Clearing Area RDS 008
RDS009
Clearing Area RDS 009
RDS010
Clearing Area RDS 010
RDS011
Clearing Area RDS 011
RDS012
Clearing Area RDS 012
RDS013
Clearing Area RDS 013
RDS014
Clearing Area RDS 014
RDS015
Clearing Area RDS 015
RDS016
Clearing Area RDS 016
RDS017
Clearing Area RDS 017
RDS018
Clearing Area RDS 018
RDS019
Clearing Area RDS 019
RDS020
Clearing Area RDS 020
(*) Personalized field
3.3 SWIFT Format Converter
3.3.1 Changing Hierarchy Derivation for SWIFT Transaction Types
Use
In this Customizing activity, you can change the hierarchy derivation tree (HDS tree) for SWIFT
transaction types. This enables the SWIFT converters to determine a transaction category for the
recipient and ordering party, which is necessary for processing the related payment items.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
/PE1/SWIFT_HDS
IMG menu
Payment Engine  File Handler  SWIFT Format Converter 
Change Hierarchy Derivation for SWIFT Transaction Types
2. On the HDS: Change Derivation Tree SWIFT_TRAS_TYPE/PE1/SWIFT_TRANS_TYPE screen,
double click node.
3. Choose Select Node tab and choose Create under Condition section. Make the following
entries:
© SAP SE
Page 10 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Field name
Entry Value
Condition Field
MSG_TYPE SWIFT Msg. No.
Condition Cat
NE Not Equal
Value
4. Select the node which condition is SWIFT Msg. No. <> and choose Create Node  As First
Lower-Level Node.
5. Choose Select Node tab and choose Create under Condition section. Make the following
entries:
Field name
Entry Value
Condition Field
MSG_TYPE SWIFT Msg. No.
Condition Cat
EQ Equal
Value
101 SWIFT MT101
6. Select the node which condition is SWIFT Msg. No. = SWIFT MT101 and choose Create Node
 As First Lower-Level Node.
7. Choose Select Node tab and choose Create under Condition section. Make the following
entries:
Field name
Entry Value
Condition Field
PI_KIND Payt Item Cat.
Condition Cat
EQ Equal
Value
01 Ordering Party
8. Choose Create under Target section. Make the following entries:
Field name
Entry Value
PE Trans. Type
020000
9. Select the node which condition is SWIFT Msg. No. = SWIFT MT101 and choose Create Node
 As Last Lower-Level Node.
10. Choose Select Node tab and choose Create under Condition section. Make the following
entries:
Field name
Entry Value
Condition Field
PI_KIND Payt Item Cat.
Condition Cat
EQ Equal
Value
02 Recipient
11. Choose Create under Target section. Make the following entries:
Field name
Entry Value
PE Trans. Type
051000
12. Repeat step 4 to step 11 to create condition SWIFT Msg. No. = SWIFT MT103 and SWIFT Msg.
No. = SWIFT MT103+.
13. Choose the node which condition is SWIFT Msg. No. <> and choose Create Node  As Last
Lower-Level Node.
14. Choose Select Node tab and choose Create under Condition section. Make the following
entries:
Field name
Entry Value
Condition Field
PI_KIND Payt Item Cat.
© SAP SE
Page 11 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Field name
Entry Value
Condition Cat
EQ Equal
Value
01 Ordering Party
15. Choose Create under Target section. Make the following entries:
Field name
Entry Value
PE Trans. Type
020000
16. Select the node which condition is SWIFT Msg. No. <> and choose Create Node  As Last
Lower-Level Node.
17. Choose Select Node tab and choose Create under Condition section. Make the following
entries:
Field name
Entry Value
Condition Field
PI_KIND Payt Item Cat.
Condition Cat
EQ Equal
Value
02 Recipient
18. Choose Create under Target section. Make the following entries:
Field name
Entry Value
PE Trans. Type
051000
19. Save entries.
20. Choose Activate Derivation Tree.
3.4 SEPA Format Converter
3.4.1 Determining Payment Order Type
Use
Here settings are defined for the determination of the internal payment order type. The system uses
this control information for certain validation and processing throughout the Payment Engine.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  File Handler  SEPA Format Converter 
Determine Payment Order Type
2. Choose the New Entries pushbutton and create the following settings in the fields listed:
Field name
Entry Value
Clrng Area
RDS000
Message Type
PAIN.001.001.02
Original Message Type
Channel
/SEPA
Format
/XML
Medium
/555
Stlmt Mtd
© SAP SE
Page 12 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Field name
Entry Value
Local Instrument
Unspecified
PO Type
100103
Long Description
SEPA SCT Order (incoming)
3. Save.
4. Go back
5. Choose the New Entries pushbutton and create the following settings in the fields listed:
Field name
Entry Value
Clrng Area
RDS000
Message Type
PAIN.001.001.03
Original Message Type
Channel
/SEPA
Format
/XML
Medium
/555
Stlmt Mtd
Local Instrument
Unspecified
PO Type
100103
Long Description
SEPA SCT Order (incoming)
6. Choose Enter.
7. Save entries.
Steps for Creating Multiple Entities for Independent Testing
If several independent entities need to be configured, the configuration step described above must
be performed x more times (up to 20) with the following settings:
Clearing Area
Clearing Area Name (*)
RDS001
Clearing Area RDS 001
RDS002
Clearing Area RDS 002
RDS003
Clearing Area RDS 003
RDS004
Clearing Area RDS 004
RDS005
Clearing Area RDS 005
RDS006
Clearing Area RDS 006
RDS007
Clearing Area RDS 007
RDS008
Clearing Area RDS 008
RDS009
Clearing Area RDS 009
RDS010
Clearing Area RDS 010
RDS011
Clearing Area RDS 011
RDS012
Clearing Area RDS 012
RDS013
Clearing Area RDS 013
RDS014
Clearing Area RDS 014
RDS015
Clearing Area RDS 015
© SAP SE
Page 13 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Clearing Area
Clearing Area Name (*)
RDS016
Clearing Area RDS 016
RDS017
Clearing Area RDS 017
RDS018
Clearing Area RDS 018
RDS019
Clearing Area RDS 019
RDS020
Clearing Area RDS 020
(*) Personalized field
3.4.2 Determining PE Transaction Type (SEPA Format Converter)
Use
In this activity it is defined how the system determines the internal transaction type based on the
information of the incoming SEPA file. The control information is used for various validation and
processing steps throughout the system. If the system cannot determine the internal transaction
type it uses a default value that is set in customizing.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  File Handler  SEPA Format Converter 
Determine PE Transaction Type
2. Choose the New Entries pushbutton and create the following settings in the fields listed:
User
Acti
on
Clear
ing
Area
(*)
PO
Typ
e
Crea
te
RDS
000
100
103
C
oll
.
ty
pe
Ite
m
C
at.
S
eq
ue
nc
e
Local
Instr.
01
02
1
1
Unspecifie
d
Unspecifie
d
RTra
ns.
Cu
rre
nc
y
EU
R
M Max. Amt.
i
n
.
A
m
t
.
Trans
action
Type
9.999.999.999.
999.999,00
02000
0
05100
1
(*) Personalized field
1. Choose Save to save your entries.
Steps for Creating Multiple Entities for Independent Testing
If several independent entities need to be configured, the configuration step described above must
be performed x more times (up to 20) with the following settings:
Clearing Area
Clearing Area Name (*)
RDS001
Clearing Area RDS 001
RDS002
Clearing Area RDS 002
RDS003
Clearing Area RDS 003
RDS004
Clearing Area RDS 004
RDS005
Clearing Area RDS 005
RDS006
Clearing Area RDS 006
© SAP SE
Page 14 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Clearing Area
Clearing Area Name (*)
RDS007
Clearing Area RDS 007
RDS008
Clearing Area RDS 008
RDS009
Clearing Area RDS 009
RDS010
Clearing Area RDS 010
RDS011
Clearing Area RDS 011
RDS012
Clearing Area RDS 012
RDS013
Clearing Area RDS 013
RDS014
Clearing Area RDS 014
RDS015
Clearing Area RDS 015
RDS016
Clearing Area RDS 016
RDS017
Clearing Area RDS 017
RDS018
Clearing Area RDS 018
RDS019
Clearing Area RDS 019
RDS020
Clearing Area RDS 020
(*) Personalized field
3.4.3 Determining Payment Order Priority (SEPA Format
Converter)
Use
Based on the information in the incoming SEPA file the Payment Engine internal priority of payment
orders is determined. Using the priority various specific processing logics can be configured
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  File Handler  SEPA Format Converter 
Determine Payment Order Priority
2. Choose the New Entries pushbutton and create the following settings in the fields listed:
Field name
Entry Value
Clrng Area
RDS000
PO Type
100103
Format
/XML
Medium
/555
Channel
/SEPA
Sequence
1
Crcy (*)
EUR
Minimum Transaction Amount
Maximum Transaction Amount
0
PO Prio.
02
© SAP SE
Page 15 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
3. (*) Personalized field
4. Choose Enter.
5. Save entries.
Steps for Creating Multiple Entities for Independent Testing
6. If several independent entities need to be configured, the configuration step described above
must be performed x more times (up to 20) with the following settings:
Clrng
Area
PO
Type
Format
Medium
Chann
el
Seq
uen
ce
Crcy
(*)
Maximum
Transaction
Amount
PO
Prio.
RDS001
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS002
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS003
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS004
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS005
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS006
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS007
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS008
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS009
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS010
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS011
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS012
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS013
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS014
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS015
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS016
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS017
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS018
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS019
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
RDS020
PACS8I
/XML
/555
/SEPA
1
EUR
9999,99
01
3.4.4 Determining the Authorization Flag for Payment Orders
Use
This IMG activity is used to set up the determination of the authorization flag for payment orders.
The authorization flag indicates whether the feeder systems have checked the authorization of the
sending user. A mapping of the authorization flag with the value “Y” prevents an (external)
authorization check from being executed again.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  File Handler  SEPA Format Converter 
Determine the Authorization Flag for Payment Orders
2. Choose the New Entries pushbutton and create the following settings in the fields listed:
© SAP SE
Page 16 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
User
Action
Clrng
Area
PO Type
Format
Medium
Channel
Flag Auth
Create
RDS000
100103
/XML
/555
/SEPA
Y Yes
3. Choose Enter.
4. Save entries.
Steps for Creating Multiple Entities for Independent Testing
5. If several independent entities need to be configured, the configuration step described above
must be performed x more times (up to 20) with the following settings:
Clrng
Area
PO Type
Format
Medium
Channel
Flag Auth
RDS001
0103
/XML
/555
/SEPA
Y Yes
RDS002
0103
/XML
/555
/SEPA
Y Yes
RDS003
0103
/XML
/555
/SEPA
Y Yes
RDS004
0103
/XML
/555
/SEPA
Y Yes
RDS005
0103
/XML
/555
/SEPA
Y Yes
RDS006
0103
/XML
/555
/SEPA
Y Yes
RDS007
0103
/XML
/555
/SEPA
Y Yes
RDS008
0103
/XML
/555
/SEPA
Y Yes
RDS009
0103
/XML
/555
/SEPA
Y Yes
RDS010
0103
/XML
/555
/SEPA
Y Yes
RDS011
0103
/XML
/555
/SEPA
Y Yes
RDS012
0103
/XML
/555
/SEPA
Y Yes
RDS013
0103
/XML
/555
/SEPA
Y Yes
RDS014
0103
/XML
/555
/SEPA
Y Yes
RDS015
0103
/XML
/555
/SEPA
Y Yes
RDS016
0103
/XML
/555
/SEPA
Y Yes
RDS017
0103
/XML
/555
/SEPA
Y Yes
RDS018
0103
/XML
/555
/SEPA
Y Yes
RDS019
0103
/XML
/555
/SEPA
Y Yes
RDS020
0103
/XML
/555
/SEPA
Y Yes
RDS001
0103
/XML
/555
/SEPA
Y Yes
3.5 File Handler
3.5.1 Maintaining Converter
Use
In this step format converters are defined that convert the incoming files or messages from their
external format into an internal metaformat used for internal processing of payment orders and
payment items, recalls or other transactions. The same is also done for outgoing transactions; from
an internal metaformat to the required external format.
Procedure
© SAP SE
Page 17 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  File Handler  Basic Settings  Maintain
Converter
2. Check if the entry below exists already. Otherwise proceed with step 3.
3. Choose the New Entries pushbutton and create the following settings in the fields listed:
Field name
Entry Value
Channel
/SWIFT
Medium
/001
Format
/1SW103
Directn
IN Incoming
Conv. ID
S103AI
Class Name
/PE1/CL_IPM_P_XML_FORMAT_CONV
Class Content
Swift 103 In
Class Description
Swift 103 ASCII Input-Converter
R. File
No Correspondence
Df.Conv.Id
4. Choose Enter.
5. Save entries.
3.5.2 Maintaining Default Values for Format Converters
Use
In this IMG activity, you maintain default values for format converters.
This IMG activity is used to customize the default value ( clearing area, payment order type,
transaction type symbol and priority) for incoming order conversion. If a value cannot be determined
during the process of incoming order conversion (that is clearing area, payment order type,
transaction type symbol or priority), the value will be extracted from this table.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  File Handler  Basic Settings  Maintain
Default Values for Format Converters
2. Choose the New Entries pushbutton and create the following settings in the fields listed:
Conv. ID
PO Type
PO Prio.
Clrng Area
TranTypSym
SEPA_N
100101
02
SAP001
TR_SYM_DEF
3. Choose Enter.
4. Save entries.
3.5.3
Determining PE Transaction Type
Use
Definition of a rule set in order to determine the priority of a payment order type for an incoming
payment order creation request via SAP Enterprise Web Service.
© SAP SE
Page 18 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Procedure
1. Access the transaction using the following navigation path:
IMG menu
SAP Customizing Implementation GuidePayment Engine 
File HandlerProcess Integration Format Converter 
Determine PE Transaction Type
Transaction code
SPRO
2. On the Change View “Determine PE Transaction Type”: Overview screen, choose the New
Entries pushbutton.
3. On the New Entries: Overview of Added Entries screen, define the following settings:
User
Acti
on
Crea
te
Cleari
ng
Area
(*)
RDS00
0
Pay
men
t
Proc
.
Cod
e
Ba
nk
Pm
t.Ba
sed
Bu
sin
ess
Tr.
Typ
e
Co
de
Pa
y
m
en
t
Ite
m
Ca
te
go
ry
Trans
actio
n
Type
Code
0000
1
003
1
02
08600
0
D
ir
e
c
t
D
e
b
it
T
y
p
e
Se
que
nce
Cur
renc
y
M Max. Amt.
i
n
.
Transac
tion
Type
A
m
t
.
1
EU
R
999.999.999.99
9,00
051001
(*) Personalized field
4. Choose Save to save your entries.
Steps for Creating Multiple Entities for Independent Testing
If several independent entities need to be configured, the configuration step described above must
be performed x more times (up to 20) with the following settings:
Clearing Area
Clearing Area Name (*)
RDS001
Clearing Area RDS 001
RDS002
Clearing Area RDS 002
RDS003
Clearing Area RDS 003
RDS004
Clearing Area RDS 004
RDS005
Clearing Area RDS 005
RDS006
Clearing Area RDS 006
RDS007
Clearing Area RDS 007
RDS008
Clearing Area RDS 008
RDS009
Clearing Area RDS 009
RDS010
Clearing Area RDS 010
RDS011
Clearing Area RDS 011
RDS012
Clearing Area RDS 012
RDS013
Clearing Area RDS 013
RDS014
Clearing Area RDS 014
© SAP SE
Page 19 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Clearing Area
Clearing Area Name (*)
RDS015
Clearing Area RDS 015
RDS016
Clearing Area RDS 016
RDS017
Clearing Area RDS 017
RDS018
Clearing Area RDS 018
RDS019
Clearing Area RDS 019
RDS020
Clearing Area RDS 020
(*) Personalized field
3.6 XML Converter
3.6.1 Defining Converter Implementation for Format Converter
Use
In this Customizing activity you define a specific converter implementation for an IPM/OPM XML
format converter.
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  File Handler  XML Converter  Define
Converter Implementation for Format Converter
2. Choose the New Entries pushbutton and create the following settings in the fields listed:
Field name
Entry Value
Format
/1SW103
Medium
/001
Channel
/SWIFT
Direction
IN
Converter ID
S103AI
Class Name
/PE1/CL_IPM_P_XML_FORMAT_CONV
Converter Package
/PECROSS/XML_SWIFT_IPM
Converter MsgIdent
/SWIFT_MT103
Message Identifier
/SWIFT_MT103
Validation
Full Validation
File Handler
Enable
3. Save entries.
3.7 Functional Monitoring
3.7.1 Maintaining Functional Monitoring Statuses
Use
Here is defined the relationship between the status category and the status ID with the status group
and the status group category. This is done in order to create a group of statuses to be used in
© SAP SE
Page 20 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Function Monitoring. The status groups will be stored instead of the statuses themselves and will be
used to reduce the number of existing statuses to a few status groups.
Procedure
3. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Payment Engine  Tools  Functional Monitoring  Maintain
Functional Monitoring Statuses
4. Choose the New Entries pushbutton and create the following settings in the fields listed:
User
Action
Clrng
Area
Sts Categ.
Status ID
Gen.St.Gr.
StsGrpFM
Create
RDS000
01
29
002
IG5
Create
RDS000
02
228
001
OG5
Create
RDS000
04
29
002
IG5
Create
RDS000
05
29
002
IG5
5. Choose Enter.
6. Save entries.
Steps for Creating Multiple Entities for Independent Testing
1. If several independent entities need to be configured, the configuration step described above
must be performed x more times (up to 20) with the following settings:
Clrng Area
RDS001
RDS002
RDS003
RDS004
RDS005
RDS006
RDS007
RDS008
RDS009
RDS010
RDS011
RDS012
RDS013
RDS014
RDS015
RDS016
RDS017
RDS018
RDS019
RDS020
© SAP SE
Page 21 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
3.8 Mater Data
3.8.1 Creating Current Account
Use
The purpose of this business step is to manually create a current account contract in BS based on
the reference product.
The current account is an account for customers to maintain the payment transactions/money
transfers. Payments are debited from and credited to this account, and customers can perform
transactions on a daily basis.
For this rapid-deployment solution, this step allows a current loan account contract to be created in
Banking Services based on the reference product (ACC_RDS_C1).
While creating the current account, several tab pages are provided on which the
content of current account data can be defined and entered at different levels of detail.
For this rapid-deployment solution, there is no need to create details for the current
account.
Procedure
1. To create a current account contract, access the transaction using the following navigation
path:
Transaction code
BCA_CN_ACCT_01
SAP Menu
Financial Services  Account Management  Account  Account
Master Data  Create Account
2. On the Create Account: Initial Screen overview screen, make the following entries:
Field name
User action and
values
User action and
values
User action and
values
Contract Start
Enter start date, for
example,
03.01.2000.
Enter start date, for
example,
03.01.2000.
Enter start date, for
example,
03.01.2000.
Contract Manager
(*)
Select the
corresponding
organizational unit
from the dropdown list,
for example, RDS
Bank.
Select the
corresponding
organizational unit
from the dropdown
list, for example,
RDS Bank.
Select the
corresponding
organizational unit
from the dropdown
list, for example,
RDS Bank.
Account Number (*)
95
100200
100300
Deactivate Check
Digit Calc.
Flagged
Flagged
Flagged
Product
Select ACC_RDS_C3
from the dropdown list.
Select ACC_RDS_I2
from the dropdown
list.
Select ACC_RDS_I3
from the dropdown
list.
Account Holder ID
Enter the business
partner ID, for
example, BP_DM_02.
Enter the business
partner ID, for
example, RDS_BANK.
Enter the business
partner ID, for
example, RDS_BANK.
3. Choose the Enter pushbutton.
On the following screen, various tab pages are displayed where the contractual agreements of
the account between the customer and the bank can be adjusted.
4. On the Basic Data tab page, make following entries:
© SAP SE
Page 22 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Field name
User action and values
Contr.Currency(*)
Select the currency code, for
example, EUR.
Comment
Defines the currency in which the
contract is managed.
(*) Personalized field
For the purposes of this rapid-deployment solution, the data is preconfigured at product
level. Therefore, there is no need to enter further details at the current account creation
level.
5. Choose the Save pushbutton.
6. A dialog box appears with the words Display log [with the information that the account has been
created]. Accept the dialog box by choosing Continue (Enter) and select the account number
for the next steps.
Steps for Creating Multiple Entities for Independent Testing
If several independent entities need to be configured, the check described above can also be
performed for the other Contract Manager:
Contract Manager
RDS Bnk BR01
RDS Bnk BR02
RDS Bnk BR03
RDS Bnk BR04
RDS Bnk BR05
RDS Bnk BR06
RDS Bnk BR07
RDS Bnk BR08
RDS Bnk BR09
RDS Bnk BR10
RDS Bnk BR11
RDS Bnk BR12
RDS Bnk BR13
RDS Bnk BR14
RDS Bnk BR15
RDS Bnk BR16
RDS Bnk BR17
RDS Bnk BR18
RDS Bnk BR19
RDS Bnk BR20
3.8.2 Changing Clearing Agreement
Use
The purpose of this business step is to manually create clearing agreements for the internal and
external routes already created. The clearing agreements define in detail how the clearing process
should be performed. For example for external transactions it is defined wihich format has to be
used for external communication and which clearing account has to be used.
© SAP SE
Page 23 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Procedure
1. Access the transaction using the following navigation path:
2.
3.
4.
5.
6.
7.
8.
SAP Menu
Payment Engine  Master Data  Routing Control  Manage
Routes and Clearing Agreements
Transaction code
/n/PE1/RN
Choose menu Extras  Change Clearing Area.
Within dialog-box Select Clearing Area enter Clearing Area RDS000.
Choose Continue (Enter).
Choose External Routes on the left side of the screen and open the menu.
Choose SEPA_RDS –SEPA Route RDS and double-click CREDIT_RDS.
Choose the Display/Change pushbutton.
On the screen Change Clearing Agreement CREDIT_RDS To Route SEPA_RDS enter the
following data:
Field name
Entry Value
Collect Items
X
Forward Directly
X
9. Choose Collector Process. tab and make the following entries:
Field name
Entry Value
Collection Type
01 Collector
Collector Crcy
EUR
10. Choose External Clearing Agreem. tab and make the following entries:
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Field name
Entry Value
Account Symbol
CLACH
Save settings.
Select External Routes on the left side of the screen and open the menu.
Choose SWIFT_RDS –SWIFT Route RDS and double-click CREDIT_RDS.
Choose the Display/Change pushbutton.
On the screen Change Clearing Agreement CREDIT_RDS To Route SWIFT_RDS enter the
following data:
Field name
Entry Value
Forward Directly
X
Save settings.
Select External Routes on the left side of the screen and open the menu.
Choose DEBIT_RDS –Debit Route RDS and double-click DEBIT_RDS.
Choose the Display/Change pushbutton.
On the screen Change Clearing Agreement DEBIT_RDS To Route DEBIT_RDS enter the
following data:
Field name
Entry Value
Forward Directly
X
21. Save settings.
22. Choose button Release.
23. In dialog-box Release Release Objects for Routing Control mark the lines mentioning your
clearing area and choose Continue (Enter).
© SAP SE
Page 24 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
24. Accept the Messages dialog-box with Continue (Enter).
Steps for Creating Multiple Entities for Independent Testing
1. If several independent entities need to be configured, the configuration step described above
must be performed x more times (up to 20) with the following settings:
Clrng Area
Route
Clearing Agreement
RDS001
SEPA_RDS
CREDIT_RDS
RDS001
SWIFT_RDS
CREDIT_RDS
RDS001
DEBIT_RDS
DEBIT_RDS
RDS002
SEPA_RDS
CREDIT_RDS
RDS002
SWIFT_RDS
CREDIT_RDS
RDS002
DEBIT_RDS
DEBIT_RDS
RDS003
SEPA_RDS
CREDIT_RDS
RDS003
SWIFT_RDS
CREDIT_RDS
RDS003
DEBIT_RDS
DEBIT_RDS
RDS004
SEPA_RDS
CREDIT_RDS
RDS004
SWIFT_RDS
CREDIT_RDS
RDS004
DEBIT_RDS
DEBIT_RDS
RDS005
SEPA_RDS
CREDIT_RDS
RDS005
SWIFT_RDS
CREDIT_RDS
RDS005
DEBIT_RDS
DEBIT_RDS
RDS006
SEPA_RDS
CREDIT_RDS
RDS006
SWIFT_RDS
CREDIT_RDS
RDS006
DEBIT_RDS
DEBIT_RDS
RDS007
SEPA_RDS
CREDIT_RDS
RDS007
SWIFT_RDS
CREDIT_RDS
RDS007
DEBIT_RDS
DEBIT_RDS
RDS008
SEPA_RDS
CREDIT_RDS
RDS008
SWIFT_RDS
CREDIT_RDS
RDS008
DEBIT_RDS
DEBIT_RDS
RDS009
SEPA_RDS
CREDIT_RDS
RDS009
SWIFT_RDS
CREDIT_RDS
RDS009
DEBIT_RDS
DEBIT_RDS
RDS010
SEPA_RDS
CREDIT_RDS
RDS010
SWIFT_RDS
CREDIT_RDS
RDS010
DEBIT_RDS
DEBIT_RDS
RDS011
SEPA_RDS
CREDIT_RDS
RDS011
SWIFT_RDS
CREDIT_RDS
RDS011
DEBIT_RDS
DEBIT_RDS
© SAP SE
Page 25 of 26
SAP Best Practices
Payment Engine for Deposit Management (L90): Configuration Guide
Clrng Area
Route
Clearing Agreement
RDS012
SEPA_RDS
CREDIT_RDS
RDS012
SWIFT_RDS
CREDIT_RDS
RDS012
DEBIT_RDS
DEBIT_RDS
RDS013
SEPA_RDS
CREDIT_RDS
RDS013
SWIFT_RDS
CREDIT_RDS
RDS013
DEBIT_RDS
DEBIT_RDS
RDS014
SEPA_RDS
CREDIT_RDS
RDS014
SWIFT_RDS
CREDIT_RDS
RDS014
DEBIT_RDS
DEBIT_RDS
RDS015
SEPA_RDS
CREDIT_RDS
RDS015
SWIFT_RDS
CREDIT_RDS
RDS015
DEBIT_RDS
DEBIT_RDS
RDS016
SEPA_RDS
CREDIT_RDS
RDS016
SWIFT_RDS
CREDIT_RDS
RDS016
DEBIT_RDS
DEBIT_RDS
RDS017
SEPA_RDS
CREDIT_RDS
RDS017
SWIFT_RDS
CREDIT_RDS
RDS017
DEBIT_RDS
DEBIT_RDS
RDS018
SEPA_RDS
CREDIT_RDS
RDS018
SWIFT_RDS
CREDIT_RDS
RDS018
DEBIT_RDS
DEBIT_RDS
RDS019
SEPA_RDS
CREDIT_RDS
RDS019
SWIFT_RDS
CREDIT_RDS
RDS019
DEBIT_RDS
DEBIT_RDS
RDS020
SEPA_RDS
CREDIT_RDS
RDS020
SWIFT_RDS
CREDIT_RDS
RDS020
DEBIT_RDS
DEBIT_RDS
© SAP SE
Page 26 of 26