Banking Services
from SAP 8.0
October 2014
English
Configuration for
Combined Statements
(L83)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Configuration for Combined Statements (L83): 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 11
SAP Best Practices
Configuration for Combined Statements (L83): 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 11
SAP Best Practices
Configuration for Combined Statements (L83): Configuration Guide
Content
1
2
Purpose .............................................................................................................................. 5
Preparation ......................................................................................................................... 5
2.1
Prerequisites ............................................................................................................ 5
3 Configuration ...................................................................................................................... 5
3.1
Business Partners .................................................................................................... 6
3.1.1
Defining BP Role Groupings ................................................................................ 7
3.1.2
Defining Number Ranges for Business Partner Relationships ............................ 7
3.2
Account Management .............................................................................................. 7
3.2.1
Changing Account Product .................................................................................. 7
3.2.2
Activating Derivation Rules for Dynamic Recipient Determination ...................... 8
3.3
Master Contract Management ................................................................................. 9
3.3.1
Defining Number Range for Master Contracts .................................................... 9
3.3.2
Defining Product Groups and Assign Products ................................................. 10
3.3.3
Creating Product for Combined Statement ........................................................ 10
3.4
Service Interface .................................................................................................... 11
© SAP SE
Page 4 of 11
SAP Best Practices
Configuration for Combined Statements (L83): Configuration Guide
Configuration for Combined Statements
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 an automated installation process using
BC Sets and other tools, refer to the Quick Guide of the SAP Loans Management rapiddeployment solution V3.800 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.
Before you can start to configure the attributes related to the loan life cycles, some general
settings for loans have to be made.
2
Preparation
This building block is built for Banking services from SAP 8.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.
-
3
This document can be found in the Step-by-Step Guide on Deploy  Implement
Options Manual Activation  Content Library  Prerequisites Matrix.
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):
© SAP SE
Page 5 of 11
SAP Best Practices
Configuration for Combined Statements (L83): Configuration Guide
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>.
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, covered either by automation or 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 a (*) – 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 the 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 Business Partners
Use
Business partners are the contractual partners for loans and accounts in Banking Services as
well as contract partners for appropriate contract accounts in FI-CAx.
Business partners are divided into different categories, which are assigned different attributes.
The system distinguishes between:

Persons (for example individuals)

Organizations (for example banks, companies)
 Groups (for example people living in shared apartments)
The functions of the business partner in the contract account are determined by using
business partner roles, such as ‘Contract Partner’.
The business partners are replicated from the Banking Services system in the role type
‘Contract Partner’.
Since the RDS focuses on consumer loans, the business partner category ‘Person’ will be
used for the loan borrower.
The functions of the business partner in the contract are determined by using business
partner roles such as Account Holder, Correspondence Recipient, or Contract Partner.
In order to assign a group of business partner roles at once role grouping are defined and can
be selected during the business partner creation process.
Baseline configuration of the Banking Services provides presettings for some Customizing
entries. In order to ensure that each required entry fulfills the assumptions for the RDS, check
following configuration settings and amended them if necessary:

Define Number Ranges

Define Groupings and Assign Number Ranges
 Configure Field Attributes per BP Role
Certain Customizing settings are required to create a business partner.
The following paragraphs explain in detail the Customizing settings and the application level
settings required to use of the Business Partner function.
© SAP SE
Page 6 of 11
SAP Best Practices
3.1.1
Configuration for Combined Statements (L83): Configuration Guide
Defining BP Role Groupings
Use
Roles can be combined in a role grouping, which then can be selected on the screen.
The BP Roles for RDS Bank grouping has to be created for the RDS solution. .
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG Path
Financial Services  SAP Business Partner for Financial Services
 General Settings  Business Partner  Basic Settings 
Business Partner Roles  Define BP Role Groupings
2. Choose subscreen BP Role Groupings  BP Roles for BP Role Grouping ‘BANK’.
3. Choose New Entries on the Change View “BP Role Groupings  BP Roles”: Overview
screen and select the following business partner roles:
User
Action
Field name
Value
Select
BP Role
BCA080
4. Save the entries.
3.1.2
Defining Number Ranges for Business Partner
Relationships
Use
For internal administration of BP relationships and BP role definitions an internal number is
required from the number range interval "01".
Procedure
1. Access the transaction using the following navigation path:
Transaction code
SPRO
IMG menu
Cross-Application Components  SAP Business Partner 
Business Partner Relationships  Basic Settings  Define
Number Ranges
2. On the Interval Maintenance: BP relationships screen choose Change intervals.
3. On the Maintain Intervals: BP relationships screen choose Insert Line and make the
following entries:
User
Action
Field name
Value
Check
No
01
Check
From No.
000000100000
Check
To No.
000000199999
Check
External
4. Save your entries.
3.2 Account Management
3.2.1
© SAP SE
Changing Account Product
Page 7 of 11
SAP Best Practices
Configuration for Combined Statements (L83): Configuration Guide
One of the prerequisites is to use the combined statement functionality on master
contract management that the product feature for Combined Statement –
Participants is enabled to green for the products (ACC_RDS_S1, ACC_RDS_C1,
ACC_RDS_F1) used for combined statement as described below.
Use
Being able to use the combined statement functionality for saving account, the feature for
combined statement needs activated on product level.
Procedure
1. Access the transaction using the following navigation path:
SAP Menu
SAP Customizing Implementation Guide  Financial Services 
Account Management  Product Management  Product
Definition  Account Products  Change Account Product
Transaction code
FSPRD2_Y
The combined statement feature needs to be switched on for the already existing consumer
loan product LO_RDS_IPP.
Therefore follow the instruction below.
2. From the Product Change: Initial screen
Field name
Description
User action and values
Product
Select the product
which needs to be
changed.
Enter the value:
ACC_RDS_S1
Current Version
Specifies the
current active
product version.
Select “Current Version”
Comment
3. Press yellow arrow button Next Screen in the left screen in order to display the product
attributes.
4. Changes setting for product attribute “Combined Statement” as described below.
Field name
Description
User action and values
Comment
Combined Bank
Statement Participants
If this feature is
switched on, a new
tab for “combined
statement
participants” is
displayed while
creating the
account.
Enable the traffic light to green
Traffic lights
for all Sub
attributes
automatically
switch to
green.
5. Save your entries.
3.2.2
Activating Derivation Rules for Dynamic Recipient
Determination
Use
In order to execute the combined statement for the participant account (TA:
BCA_CST_MASSRUN) the activation of the software component that uses HDS is needed. The
software component for the application RCV_DYN_REC_DET needs to be activated.
Procedure
© SAP SE
Page 8 of 11
SAP Best Practices
Configuration for Combined Statements (L83): Configuration Guide
SAP Menu
Financial Services  Account Management  Tools
Correspondence Recipient Administration  Define Derivation
Rules for Dynamic Recipient Determination
Transaction code
RCV_DYN_REC_DET_HDS
1. Enter the following details in initial screen
Field name
2.
3.
4.
5.
Description
User action and values
Application
Select
RCV_DYN_REC_DET
Tree Category
Select
Customizing Tree
Comment
Press button “Overview of derivation trees”.
Press button “Execute”.
Mark the line for application ID “RCV_DYN_REC_DET”.
Press Activate button.
3.3 Master Contract Management
3.3.1
Defining Number Range for Master Contracts
Use
In order to be able to create Master Contract Accounts in Banking Services a number range
interval needs to define. While creating the master contract account automatically the account
number for master contract will be assigned.
Procedure
1. Access the transaction using the following navigation path:
SAP Menu
IMG Financial Services  Master Contract Management 
Master Contract  General Settings  Define Number Range for
Master Contracts
Transaction code
SPRO
2. Enter button “Change intervals” and enter the following details:
Field name
Description
User action and values
No
Enter the value:
01
From No.
Enter the value:
00000000000000000001
To No.
Enter the value:
00000000000001000000
NR Status
Leave the field blank
Ext.
Leave blank
© SAP SE
Comment
Information
will be
automatically
defined and
eneterd by
the System
Page 9 of 11
SAP Best Practices
Configuration for Combined Statements (L83): Configuration Guide
3. Save the entry.
3.3.2
Defining Product Groups and Assign Products
Use
This configuration is used to simplify the creation of participant conditions. For the combined
statement this setting becomes relevant in order to predefine the relationship attributes
Binding Agreement and Data Set while attaching the participant accounts to the master
contract account.
Procedure
1. Access the transaction using the following navigation path:
2.
3.
4.
5.
SAP Menu
IMG Financial Services  Master Contract Management 
Product Management  Product Definition  Define Product
Groups and Assign Products
Transaction code
SPRO
Mark the line for Product Group 100 – Checking Products
Double click on folder Products for Product Groups
Press button New Entries
Assign the account products
Field name
Description
User action and values
Comment
Enter the value:
ACC_RDS_C1
Enter the value:
ACC_RDS_C3
Product
Product
Repeat the same steps in order to assign the account product for saving and Time Deposit
for Product Groups:

400 – Time Deposit Accounts
o Assign Account Product: ACC_RDS_F1
 600 – Saving Book
o Assign Account Product: ACC_RDS_S1
6. Press button Save
3.3.3
Creating Product for Combined Statement
Use
This configuration is used to configure a RDS specific template product for master contract
with combined statement functionality in the product configurator.
Procedure
1. Access the transaction using the following navigation path:
SAP Menu
IMG Financial Services  Master Contract Management 
Product Management  Product Definition  Master Contract
Products  Create Master Contract Product
Transaction code
SPRO
2. From the Product Create: Initial screen
Field name
© SAP SE
Description
User action and values
Comment
Page 10 of 11
SAP Best Practices
Configuration for Combined Statements (L83): Configuration Guide
Field name
Description
User action and values
New Product
The new product
that is to be
created for
Combined
Statement
Enter the value:
MC_CST
Template Prod.
The template
product to be used
Enter the value:
_MC_CST
Product Version
Product version
Select value:
0001
Comment
Press Enter to continue
Product Create: Administration screen
Product Desc.
Product
Description
Enter the value:
Master Contract for
Combined Statement
Valid from
Valid from date
Enter the value:
For eg. 01.01.2000
The date
from which
the validity
has to start
Valid To
Valid to date
Enter the value:
For eg. 31.12.9999
When Enter
is pressed,
“Used
Attributes”
product
configuration
screen
opens up
Press Enter to continue
3. Choose button for Flag for Activation
4. Choose button Activate
5. Choose Save from the Menu
3.4 Service Interface
Use
In general for Banking Services System, the Master Contract Management component and
Account Management needs to be able to communication to each other. This mainly
becomes relevant for the following cases:



MCM needs to read the master contract participation from AM component.
MCM needs to request Participation change from AM
Furthermore Confirmation and Notification for Participation changes have to be send
from AM to MCM.
Therefore standard interface services have been designed and needs to be configured in
SAP PI.
But even so, for the combined statement component, services needs to be configured in order
to request/confirm communication for the participation of accounts in master contracts.
The details of services configuration relevant for Banking Services 8.0 are described in SAP
note 1563982 and 1348308.
© SAP SE
Page 11 of 11