Business Process Procedures s8

Banking Services 8.0
October 2014
English
End-of-Day-Processing (L84)
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Business Process Documentation

SAP Best Practices End-of-Day-Processing (L84)

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

Icon / Meaning
/ Caution
/ Example
/ Note
/ Recommendation
/ Syntax
/ External Process
/ Business Process Alternative/Decision Choice

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.

Contents

End-of-Day-Processing 5

1 Purpose 5

2 Prerequisites 5

2.1 Master Data and Organizational Data 5

2.2 Multiple Entities – Independent Testing 5

2.3 Disclaimer 7

3 Process Overview Table 7

4 Process Steps 7

4.1 Maintaining Values for Selection Variables 7

4.2 Submitting Job Chain 9

4.3 Monitor Jobs 9

End-of-Day-Processing

1 Purpose

Although Banking Services from SAP is an online real-time platform for banking operations, there are many processes that require jobs to run after business hours and execute different actions on various contracts in mass processing mode.

That brings several benefits:

· The performance of the online transactions is not impacted by mass processes that are not required to run immediately. These processes are moved to a time window with less system activity where they can be scheduled easily in parallel to the remaining online activities.

· Some processes like account settlement require the current posting day to be finished and can only be executed after all activities of the day are done. That can be achieved by running an end-of-day job chain.

· Planning and handling of system load is possible by scheduling certain tasks at night and keeping the sequence of processes in order is mandatory for certain bank processes.

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 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 detail in this Business Process Documentation

· Up to 20 additional CMUs with 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 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 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.

To facilitate independent testing, each of the above-mentioned entities can be assigned to a single tester. This enables you to avoid conflicts in the posting date settings and testing can be performed completely independently.

Note that each life cycle of a deposits account starts with an initial Posting Date for the Bank Posting Area on 03.01.2000. If you want to test more than one life cycle for each Bank Posting Area, you have to adjust the starting date of the life cycle to the current Posting Date. All other dates mentioned for examples in the respective life cycles have to be adjusted accordingly.

If you are not sure what the current posting date is, you can check it as follows:

For more details, refer to the corresponding section in the Master Data Procedure Document “Set Posting Date for Payment Transactions” (155.89)

The necessary activities to be performed in this step are:

· Check Posting Date for Payment Transactions in Deposit Management System

· Check Posting Date for End-of-Day Processing

2.3 Disclaimer

Note that certain process steps described in this document will only lead to the specified results if you use the proposed currency (EUR) and the proposed amounts.

If you use another currency (such as USD), the proposed amounts would have to be adjusted.

3 Process Overview Table

Process step /
Step of Scope item / External process reference / Business condition / Business role (not technical role for BP) / Transaction code / Expected results /
Maintain Values for Selection Variables / The selection variables are defined in the table STVARV / STVARV / The values are maintained for the relevant selection variables in the table STVARV
Submit Job Chain / The end-of-day processing job chain is defined / The job chain is scheduled
Monitor Jobs / The job chain is scheduled / The job logs are shown

4 Process Steps

4.1 Maintaining Values for Selection Variables

Use

This step process is used to maintain the selection variables in the table TVARVC.

Procedure

1. Log on to SAP banking back-end systems.

2. Access the transaction using the following navigation path:

Transaction code / STVARV

3. Click on the Display ↔ Change icon.

4. In the Parameter tab, choose the selection variable and click on the Change icon to maintain the values. Maintain the following selection variables in the relevant SAP banking systems:

Name / System / Values / Comment /
BPARE / DM / < bank posting area > / the bank posting area in which you need to run the end-of-day processing jobs, for example BR01
DESTINATION_TO_BA / DM / < destination to Bank Analyzer > / the destination to Bank Analyzer, for example XXXCLNTXXX
EXECUTION_VARIANT / DM / < execution variant for sending information > / the execution variant which determines the selection criteria of the reports for extracting flow data and sends this as information messages, for example BR01
CLEARING_AREA / PE / < clearing area > / the clearing area in which you need to run the end-of-day processing jobs, for example, RDS001
LEGAL_ENTITY / BA / < legal entity > / the legal entity, for example YLE00
SOURCE_SYS / BA / < source system of DM > / the source system of Deposit Management, for example XXXCLNTXXX

5. Go to the Selection Options tab. Maintain the following selection variables in the relevant SAP banking systems:

Name / System / Values / Comment /
BPARE / DM / < bank posting area, also select option equal to = > / the bank posting area in which you need to run the end-of-day processing jobs, for example BR01
CLEARING_AREA / PE / < clearing area, also select option equal to = > / the clearing area in which you need to run the end-of-day processing jobs, for example, RDS001

6. Choose Save.

4.2 Submitting Job Chain

Use

This step process is used to schedule the end-of-day processing job chain.

Procedure

1. Log on to SAP Central Process Scheduling by Redwood system.

2. Choose Definitions > Job Chains in the Navigation bar.

3. Choose the end-of-day processing job chain RDS_AM_JC_EOD, and choose Submit from the context-menu.

4. In the opened window, directly choose Submit.

4.3 Monitor Jobs

Use

This step is to monitor the scheduled jobs.

Procedure

1. Log on to SAP Central Process Scheduling by Redwood system.

2. Choose Monitoring > Jobs in the Navigation bar.

3. Check the job logs.