October 2014
EnglishEnglish
Lifecycle Current Account (L34)
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Business Process Documentation
© SAP SE Page 64 of 192
SAP Best Practices Current Account Life-Cycle (L34): BPD
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
/ External Process
/ Business Process Alternative/Decision Choice
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 7
2 Prerequisites 7
2.1 Master Data and Organizational Data 7
2.2 Business Conditions 8
2.3 Multiple Entities – Independent Testing 8
2.4 Disclaimer 10
3 Process Overview Table 10
4 Process Steps for Option A(with Payment Engine) 21
4.1 Creating a Business Partner 21
4.2 Maintaining a Business Partner (Optional) 22
4.3 Replicate Business Partner to Bank Analyzer System 22
4.4 Creating a Current Account 22
4.4.1 Creating Current Accounts with Product Pricing Lists (Alternative) 24
4.5 Replicating Account Master Data to Bank Analyzer System 30
4.6 Changing an Account Contract 31
4.6.1 Managing Conditions (Not for Accounts with Product Pricing List) 31
4.6.2 Managing Limits 37
4.7 Setting Locks 39
4.7.1 Setting Locks for a Business Partner 39
4.7.2 Changing a Lock (Optional) 44
4.8 Account Holder Change 45
4.8.1 Creating and Executing an Order for the Account Holder Change 45
4.8.2 Displaying an Account 49
4.9 Payment Transactions 50
4.9.1 Currency Exchange 50
4.9.2 Exception Handling 53
4.9.3 Handling of Payment Transactions via Payment Engine (optional) 63
4.10 Distributing Payment Items to Bank Analyzer 64
4.11 Simulating an Account Settlement 65
4.12 Product Change 66
4.12.1 Displaying an Account 68
4.13 Forward Order 69
4.13.1 Create a Forward Order 69
4.13.2 Changing a forward order (optional) 70
4.13.3 Displaying a forward order (optional) 71
4.13.4 Deleting a forward order (optional) 72
4.13.5 Execution of Forward Order before due date (optional) 72
4.13.6 Checking the transactions on the Account after Forward Order execution 73
4.14 Standing Order 74
4.14.1 Creating a Standing Order 74
4.14.2 Changing a Standing Order (Optional) 76
4.14.3 Displaying a Standing Order (Optional) 77
4.14.4 Deleting a Standing Order (Optional) 78
4.15 Product Version Change 78
4.15.1 Creating a Product Version 79
4.15.2 Mass Product Version Change 80
4.15.3 Displaying an Account 82
4.16 Closing an Account 83
4.17 Process Steps for End-of-Day Processing 92
4.17.1 Setting Posting Date for Payment Transaction 92
4.17.2 Setting Posting Date for End-of-Day Processing 93
4.17.3 Executing a Settlement 94
4.17.4 Bank Statement 97
4.17.5 Forward Orders 99
4.17.6 Standing Orders 101
4.17.7 Setting Posting Date for Payment Transaction 103
4.17.8 Setting the Posting date for End-of-Day Processing 104
4.17.9 Executing Due Account Closures 105
4.17.10 Customer Correspondence 106
5 Process Steps for Option B(without Payment Engine) 110
5.1 Creating a Business Partner 110
5.2 Maintaining a Business Partner (Optional) 111
5.3 Replicate Business Partner to Bank Analyzer System 111
5.4 Creating a Current Account 112
5.4.1 Creating Current Accounts with Product Pricing Lists (Alternative) 113
5.5 Replicate Account Master Data to Bank Analyzer System 119
5.6 Changing an Account Contract 120
5.6.1 Managing Conditions (Not for Accounts with Product Pricing List) 120
5.6.2 Managing Limits 126
5.7 Setting Locks 128
5.7.1 Setting Locks for a Business Partner 128
5.7.2 Changing a Lock (Optional) 133
5.8 Account Holder Change 134
5.8.1 Creating and Executing an Order for the Account Holder Change 134
5.8.2 Displaying an Account 138
5.9 Currency Exchange 139
5.9.1 Creating a Payment Item 139
5.9.2 Displaying Balances and Key Figures 141
5.10 Distribute Payment Items to Bank Analyzer 142
5.11 Exception Handling 142
5.11.1 Creating a Payment Transaction Order 143
5.11.2 Assigning Users to a Worklist 145
5.11.3 Processing a Posting Control Order in the PCO 146
5.11.4 Creating a Payment Transaction Order 147
5.12 Simulating an Account Settlement 152
5.13 Product Change 154
5.13.1 Displaying an Account 156
5.14 Forward Order 156
5.14.1 Creating a Forward Order 156
5.14.2 Changing a forward order (optional) 159
5.14.3 Displaying a forward order (optional) 159
5.14.4 Deleting a forward order (optional) 160
5.14.5 Execution of Forward Order before due date (optional) 161
5.14.6 Checking the transactions on the Account after Forward Order execution 162
5.15 Standing Order 162
5.15.1 Create a Standing Order 162
5.15.2 Changing a Standing Order (Optional) 165
5.15.3 Displaying a Standing Order (Optional) 166
5.15.4 Deleting a Standing Order (Optional) 167
5.15.5 Checking the transactions on the Account after Standing Order execution 168
5.16 Product Version Change 168
5.16.1 Creating a Product Version 169
5.16.2 Mass Product Version Change 170
5.16.3 Displaying an Account 172
5.17 Closing an Account 173
5.18 Process Steps for End-of-Day Processing 177
5.18.1 Setting Posting Date for Payment Transaction 177
5.18.2 Setting Posting Date for End-of-Day Processing 178
5.18.3 Executing a Settlement 178
5.18.4 Displaying Balances and Key Figures (Informational) 180
5.18.5 Bank Statement 181
5.18.6 Forward Orders 184
5.18.7 Standing Orders 185
5.18.8 Setting Posting Date for Payment Transaction 186
5.18.9 Setting the Posting date for End-of-Day Processing 187
5.18.10 Executing Due Account Closures 187
5.18.11 Customer Correspondence 189
Current Account Life-Cycle
1 Purpose
The purpose of this document is to describe and support testing of the complete entire account life cycle, from contract creation to account closure, including the business partner functionalities that are needed for this scenario.
To conduct a current account life cycle, there are two mandatory steps: account creation and account closure.
All other steps are optional and mostly independent from each other. Therefore, the scenario attempts to join all the most common processes that could be activated during the business relationship between a bank and a customer.
The current account life cycle has a special role in the SAP Deposits Management Rapid-Deployment Solution V2.800. It is an integrated part of the solution and is mandatory to be executed.
Within this document, the following most common steps for a current account are described:
The scenario includes:
· Creating or changing business partners
· Creating or changing current accounts
· Creating or changing posting locks
· Changing an account holder
· Creating and processing payment transaction orders, including automatic and manual error handling and payment engine integration
· Changing the product of an existing account
· Forward Order functionality
· Standing Order functionality
· Account closure process with payment engine integration
· Simulating account settlement
· Displaying account balance and turnover figures
· Conducting end-of-day processing including:
o Changing posting dates
o Account settlement
o Executing scheduled account closures
o Creating bank statements
o Creating customer correspondence
· Changing the product version of an existing account
Target groups of this rapid-deployment solution are customers and consultants with no or little knowledge of the SAP deposit accounts concept and features.
Content target groups for this scenario are banks and financial institutes. Especially the departments responsible for managing, holding, and maintaining deposit accounts are addressed by this scenario.
2 Prerequisites
2.1 Master Data and Organizational Data
Default Values
The organizational structure and master data of your company have been created in your Banking Services system during implementation, to the extent it is required to execute this rapid-deployment solution (for example, business partner, reference account, or internal accounts).
The organizational structure reflects the structure of your company with respect to some specific settings such as name, currency, and so on.
2.2 Business Conditions
The business process described in this Business Process Documentation is a stand-alone scenario. It is, therefore, not necessary to complete other processes or business conditions before you can start this scenario.
Nevertheless, the current account life cycle has a special role in the SAP Deposits Management Rapid-Deployment Solution V2.800. It is a mandatory functionality that is part of every implementation. Therefore, certain customizing settings made in line with the current account implementation are a prerequisite for the other life cycles (which are described in other Business Process Documentation).
2.3 Multiple Entities – Independent Testing
Once the content of this rapid-deployment solution has been implemented, it will provide:
· One CMU (contract managing unit) with associated Bank Posting Area (0001) which is described in all details in this Business Process Documentation
· Up to 20 additional CMUs with the associated bank posting areas, which can be used to represent a branch structure and to test the business processes independently (since the posting date is set for each bank posting area and if several people are testing independently, this might differ for each person).
The scope of this rapid-deployment solution is to provide one contract managing unit with associated bank posting area to run through the defined life cycle of deposit accounts as described. It may, however, be necessary to have several independent entities for using / testing the processes within the life cycle of these deposit accounts.
Therefore, in addition to the entity described in detail in this Business Process Documentation, the possibility of using several additional entities is also mentioned.
These entities can be used to:
· Represent a type of branch structure
· Test the business processes independently
Independent testing with several entities might be necessary due to the following reasons:
· The posting date is set for each bank posting area and must be changed to simulate a complete deposit life cycle
· If several people are testing independently, this might differ for each person
For this reason, in addition to the example mentioned within the following sections for the entity:
Bank Key (*) / Bank Name (*) / Bank Posting Area (BPA) / Contract Manager (CMU) (*) / Initial Posting Date for the BPA (*) /12345678 / RDS Bank / 0001 / RDS Bank / 03.01.2000
20 additional entities are provided as follows:
Bank Key (*) / Bank Name (*) / Bank Posting Area (BPA) / Contract Manager (CMU) (*) / Initial Posting Date for the BPA (*) /11111111 / RDS Bank Branch 1 / BR01 / RDS Bnk BR01 / 03.01.2000
22222222 / RDS Bank Branch 2 / BR02 / RDS Bnk BR02 / 03.01.2000
33333333 / RDS Bank Branch 3 / BR03 / RDS Bnk BR03 / 03.01.2000
44444444 / RDS Bank Branch 4 / BR04 / RDS Bnk BR04 / 03.01.2000
55555555 / RDS Bank Branch 5 / BR05 / RDS Bnk BR05 / 03.01.2000
66666666 / RDS Bank Branch 6 / BR06 / RDS Bnk BR06 / 03.01.2000
77777777 / RDS Bank Branch 7 / BR07 / RDS Bnk BR07 / 03.01.2000
88888888 / RDS Bank Branch 8 / BR08 / RDS Bnk BR08 / 03.01.2000
99999999 / RDS Bank Branch 9 / BR09 / RDS Bnk BR09 / 03.01.2000
11112222 / RDS Bank Branch 10 / BR10 / RDS Bnk BR10 / 03.01.2000
11113333 / RDS Bank Branch 11 / BR11 / RDS Bnk BR11 / 03.01.2000
11114444 / RDS Bank Branch 12 / BR12 / RDS Bnk BR12 / 03.01.2000
11115555 / RDS Bank Branch 13 / BR13 / RDS Bnk BR13 / 03.01.2000
11116666 / RDS Bank Branch 14 / BR14 / RDS Bnk BR14 / 03.01.2000
11117777 / RDS Bank Branch 15 / BR15 / RDS Bnk BR15 / 03.01.2000
11118888 / RDS Bank Branch 16 / BR16 / RDS Bnk BR16 / 03.01.2000
11119999 / RDS Bank Branch 17 / BR17 / RDS Bnk BR17 / 03.01.2000
22221111 / RDS Bank Branch 18 / BR18 / RDS Bnk BR18 / 03.01.2000
22223333 / RDS Bank Branch 19 / BR19 / RDS Bnk BR19 / 03.01.2000
22224444 / RDS Bank Branch 20 / BR20 / RDS Bnk BR20 / 03.01.2000
If the entities were personalized when the solution was implemented, the values for testing are adjusted accordingly.