October 2014
EnglishEnglish
Organizational Structure Settings for Deposits in Banking Services
(L26)
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Building Block Configuration Guide
© SAP SE Page 2 of 5
SAP Best Practices
Organizational Structure Settings for Deposits in Banking Services (L26): 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.
Icons
/ Caution
/ Example
/ Note
/ Recommendation
/ Syntax
Typographic Conventions
Type Style / DescriptionExample 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.
Contents
1 Purpose 5
2 Preparation 5
2.1 Prerequisites 5
3 Configuration 5
3.1 Creating a Bank 6
3.2 Assigning Banks to Be Managed 8
3.3 Defining a Bank Posting Area 9
3.4 Defining Contract Managing Units 11
3.5 Defining Payment Transaction Areas 14
3.6 Assigning a Bank Key to a Payment Transaction Area 15
3.7 Assigning a Grouping Object and Number Range for a Bank Key 16
3.8 Maintaining Number Range Intervals for a Payment Transaction Area 17
3.9 Setting a Posting Date for a Bank Posting Area 19
3.9.1 Setting a Posting Date for Payment Transactions 19
3.9.2 Setting a Posting Date for End-of-Day Processing 20
3.10 Assigning Check Digit Calculation Methods to Bank Keys 21
© SAP SE Page 22 of 22
SAP Best Practices
Organizational Structure Settings for Deposits in Banking Services (L26): Configuration Guide
Organizational Structure Settings for Deposits in Banking Services
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 deposit life cycle itself, some general settings must be made. Within this document, the organizational structure needed for processing a life cycle is set up.
2 Preparation
2.1 Prerequisites
Banking Services from SAP 8.0 - SP 2 must be installed.
Before you start installing this building block, you must install prerequisite Building Blocks. For more information, see Building Block Prerequisites Matrix for the SAP Deposits Management Rapid-Deployment Solution V1.800.
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.
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.
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 SAPERP 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.
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 (*) – 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 (ARS) with the currency relevant for your RDS).
For more details on personalization, see sections 6.2.1 and 6.2.3.6.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.
Multiple Entities – Independent Testing
Within this RDS the following content is implemented amongst others within this configuration guide:
· One CMU (contract managing unit) with associated Bank Posting Area and so on which is described in all details within this configuration guide (and for usage in the Business Process Documentation)
· Up to 20 additional CMU’s with associated Bank Posting Areas and so on
The scope of this RDS is to provide one Contract Managing Unit with associated Bank Posting Area to run through the defined life cycle of accounts as described. For certain reasons, however, several independent entities might be necessary for using / testing the processes within the life cycle of this account.
Therefore, in addition to the entity described in all details within this configuration guide (and in the business process documentation), the possibility to enter several additional entities is mentioned.
These can be used to:
· Represent a kind of branch structure
· Test the business processes independently.
Independent testing with several entities might become necessary because of the following reasons:
· The posting date is set for each bank posting area and must be changed to simulate a complete deposit life cycle.
· Several testers might require different entities for independent testing
The configuration steps described in sections 3.1 through 3.9, therefore, have to be repeated up to 21 times to create all of the entities in question. For this reason, each time information is provided at the end of respective section.
These 1 + 20 independent entities can then be divided among the testers.
If the additional 20 entities are not or only partly required, the remaining entities do not need to be configured.
3.1 Creating a Bank
Use
This configuration step enables the bank data to be created in the system.
Banks in different countries may have different ways of providing bank information.
There are three ways for banks to create the bank data in SAP Banking Services:
1. Bulk creation of bank data using transaction BIC2 (report RFBVBIC2):
The bank master data (bank directory) can be uploaded initially with report RFBVBIC2 (= Transaction BIC2). This program uses the global bank directory in the BIC+IBAN format to import files, compares these files with existing bank data, and saves the new and changed data in the bank master (table BNKA).
2. Bulk creation of bank data using program BIC2 (report RFBVALL_0):
Some national banks/federal standard banks also provide download files of local bank master data in ASCII format. The function module FILL_BNKA_FIELDS_SAMPLE is available for importing this file. It also describes the interface and the necessary instructions for transferring a country-specific file to an internal table (BNKA). The main program for transferring bank data is RFBVALL_0.
3. Individual Creation of banks using FI01:
If no file for uploading bank master data, banks can be created manually with transaction FI01.
The following section gives the details for creating banks using transaction FI01.
Procedure
1. Access the transaction using the following navigation path:
Transaction code / FI01SAP Menu / Financial Services ® Collateral Management ® Securities ® Create Depository Bank
2. On the Create Bank: Initial Screen, make the following entries:
Field name / User Value and Actions /Bank Country (*) / DE
Bank Key (*) / 12345678
(*) Personalized field
The bank key and bank country for the rapid-deployment solution can refer either to a “real” (existing) bank or a test bank.
In the standard SAP system, certain plausibility checks are implemented to check country-specific settings such as the length of the bank key, postal code, and so on. For this reason, adhere to the rules that apply to the country for which the rapid-deployment solution is implemented.
3. Press Enter.
4. On the Create Bank: Detail Screen, make the following entries:
Field name / User Value and Actions /Bank Name (*) / RDS Bank
City (*) / Buenos Aires
Bank Branch (*) / Head Office
(*) Personalized field
5. Choose the Save pushbutton to save the entries.
If a bulk creation shall be done the transaction BIC2 (report RFBVBIC2) or program BIC2 (report RFBVALL_0) has to be used.
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:
Bank Country (*) / Bank Key (*) / Bank Name (*) / City (*) / Bank Branch (*) /AR / 11111111 / RDS Bank Branch 1 / Buenos Aires / Branch 1
AR / 22222222 / RDS Bank Branch 2 / Buenos Aires / Branch 2
AR / 33333333 / RDS Bank Branch 3 / Buenos Aires / Branch 3
AR / 44444444 / RDS Bank Branch 4 / Buenos Aires / Branch 4
AR / 55555555 / RDS Bank Branch 5 / Buenos Aires / Branch 5
AR / 66666666 / RDS Bank Branch 6 / Buenos Aires / Branch 6
AR / 77777777 / RDS Bank Branch 7 / Buenos Aires / Branch 7
AR / 88888888 / RDS Bank Branch 8 / Buenos Aires / Branch 8
AR / 99999999 / RDS Bank Branch 9 / Buenos Aires / Branch 9
AR / 11112222 / RDS Bank Branch 10 / Buenos Aires / Branch 10
AR / 11113333 / RDS Bank Branch 11 / Buenos Aires / Branch 11
AR / 11114444 / RDS Bank Branch 12 / Buenos Aires / Branch 12
AR / 11115555 / RDS Bank Branch 13 / Buenos Aires / Branch 13
AR / 11116666 / RDS Bank Branch 14 / Buenos Aires / Branch 14
AR / 11117777 / RDS Bank Branch 15 / Buenos Aires / Branch 15
AR / 11118888 / RDS Bank Branch 16 / Buenos Aires / Branch 16
AR / 11119999 / RDS Bank Branch 17 / Buenos Aires / Branch 17
AR / 22221111 / RDS Bank Branch 18 / Buenos Aires / Branch 18
AR / 22223333 / RDS Bank Branch 19 / Buenos Aires / Branch 19
AR / 22224444 / RDS Bank Branch 20 / Buenos Aires / Branch 20
(*) Personalized field
3.2 Assigning Banks to Be Managed
Use
This IMG activity enables the banks created in the system to be available for use in Account Management.
Prerequisites
The bank directory upload [or manual creation of bank(s) (transaction FI01)] needs to be done.
Procedure
1. Access the transaction using the following navigation path: