banking services from sap 8.0 (fsappl400, fsappl450)

Application Operations Guide

PUBLIC

Banking services from SAP

®

8.0

(FSAPPL400, FSAPPL450)

Target Audience

System administrators

Technology consultants

Document version: 7 – December 19, 2014

History of Changes

The Application Operations Guide is regularly updated and can be found on SAP Service

Marketplace at http://service.sap.com/instguides.

The following table provides an overview of the most important changes that were made in the

latest versions.

Version Date Description

1 September 5, 2011 Initial version

2 November 8, 2011 Update for CRM EhP 2

3 June 21, 2013 4.6.4.1: Update on report and transaction

/BA1/RFP_OBSDB_DELETE

4 August 23, 2013 2.1, 2.2, 3.1.4, 3.2.4, 4.6.4: Version of CRM

guides updated

3.1.5: Chapter “Monitoring for Financial Services

Business Partner“ added

4.6.4: Chapter “Scheduled Periodic Tasks: FS

Business Partner” added

4.6.4.2: Information on report

BCA_BL_DD_PP_RUN added

4.6.5: Chapter “Required Manual Periodic Tasks:

FS Business Partner” added

5 August 30,2013 1.2: Note 1354442 added

2.1: Note on NetWeaver version for FSPOT400

added

3.2.4: Information on archiving objects “Banking

Customer Quote and Banking Sales Contract”

and “Personal Financial Statement” added

3.2.4.1: Information on transactions for New Loan

Boarding added

6 February 21, 2014 No changes

http://service.sap.com/instguides

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1354442

7 December 19, 2014 Chapters 3.1.6 (“Monitoring SAP Fiori Apps”) and

7.3 (“Troubleshooting: Fiori Apps”) added

Make sure that you have the latest version of this document before you start the

implementation. You can find the latest version on SAP Service Marketplace at

http://service.sap.com/instguides → Industry Solutions → Industry

Solution Guides → SAP for Banking → Solution Guides.


Contents

1 Getting Started ............................................................................. 8

1.1 Global Definitions .......................................................................... 8

1.2 Important SAP Notes ..................................................................... 9

2 Technical System Landscape ................................................... 13

2.1 Scenario/Component Matrix ....................................................... 13

2.2 Related Documentation ............................................................... 14

3 Monitoring of SAP for Banking ................................................. 16

3.1 Alert Monitoring ........................................................................... 16

3.1.1 Monitoring Installation and Setup .................................................. 16

3.1.2 Monitoring for Bank Analyzer ........................................................ 16

Data Delivery to Bank Analyzer ........................................................................................... 16

3.1.3 Monitoring for Transactional Banking ........................................... 18

3.1.4 Monitoring for Scenarios ................................................................ 18

Account Origination ............................................................................................................. 19

Leasing................................................................................................................................... 19

Funding Management ........................................................................................................... 20

3.1.5 Monitoring for Financial Services Business Partner ................... 20

3.1.6 Monitoring SAP Fiori Apps ............................................................. 20

3.2 Detailed Monitoring and Tools for Problem and Performance

Analysis .................................................................................................. 21

3.2.1 Introduction to technical monitoring ............................................. 21

Monitoring with Solution Manager Business Process Monitoring .................................. 22

3.2.2 Detailed Monitoring and Tools for Problem and Performance

Analysis (Bank Analyzer) ............................................................................ 22

ABADRGEN – Code Generation for ABADR Derivations ................................................. 22

SDL Configuration Check .................................................................................................... 22

Error Handling in SDA .......................................................................................................... 23

Error Handling PPO for IOA ................................................................................................. 23

Generic BI Data Extraction................................................................................................... 23


Analysis (Transactional Banking) ............................................................... 25

Parallel Processing Monitor - RBANK_PP_MONITOR ...................................................... 25

Job Overview – SM37 ........................................................................................................... 26

Display Application Log – SLG1 ......................................................................................... 26

Transactional RFC – SM58 ................................................................................................... 27

Message Monitoring- Integration Engine – SXMB_MONI ................................................. 27


Analysis (Scenarios) .................................................................................... 27

Account Origination ............................................................................................................. 27

Transactions for New Loan Boarding (application component

FSPOT) ............................................................................................. 30

Data Archiving ................................................................................. 30

Leasing................................................................................................................................... 31

Funding Management ........................................................................................................... 34

3.2.5 Trace and Log Files ......................................................................... 34

Application Log ..................................................................................................................... 34

Base Level Logs .................................................................................................................... 35

Trace files .............................................................................................................................. 35

3.2.6 Workload Monitors .......................................................................... 35

3.2.7 Interface Monitors ........................................................................... 36

3.2.8 Data Growth and Data Archiving Monitors ................................... 36

Data Growth and Data Archiving Monitors: Bank Analyzer ............................................. 36

4 Management of SAP for Banking ............................................. 38

4.1 Starting and Stopping .................................................................. 38

4.2 Software Configuration ............................................................... 39

4.3 Administration Tools ................................................................... 39

4.4 Backup and Restore .................................................................... 39

4.4.1 Application Data .............................................................................. 40

4.4.2 Operating System, Software, and Configuration Data ................. 41

4.4.3 Database .......................................................................................... 41

4.4.4 Further Information ......................................................................... 42

4.5 Application Copy .......................................................................... 42

4.6 Periodic Tasks .............................................................................. 42

4.6.1 General Checks in the ABAP Environment ................................... 43

Checks for Database and Operating System ..................................................................... 44

Automated Checks ............................................................................................................... 44

4.6.2 Specific Checks for SAP NetWeaver Usage Types ...................... 45

Application Server ABAP ..................................................................................................... 45

Business Intelligence ........................................................................................................... 45

Process Integration (XI) ........................................................................................................ 45

4.6.3 Checks in banking services from SAP .......................................... 45

4.6.4 Scheduled Periodic Tasks .............................................................. 46

Scheduled Periodic Tasks: Bank Analyzer ........................................................................ 46

Scheduled Periodic Tasks: Transactional Banking .......................................................... 47

Scheduled Periodic Tasks: Scenarios ................................................................................ 49

Scheduled Periodic Tasks: FS Business Partner .............................................................. 52

4.6.5 Required Manual Periodic Tasks ................................................... 53

Required Manual Periodic Tasks: Bank Analyzer ............................................................. 53

Required Manual Periodic Tasks: Transactional Banking ............................................... 54

Required Manual Periodic Tasks: FS Business Partner ................................................... 55

5 High Availability ......................................................................... 57

6 Software Change Management ................................................. 58

7 Troubleshooting ........................................................................ 59

7.1 Problem Analysis Scenarios for SAP NetWeaver ..................... 59

7.2 Troubleshooting: Bank Analyzer ................................................ 59

7.2.1 Sending of General Ledger Documents ........................................ 59

7.2.2 Specific Problem Analysis Scenarios ........................................... 59

Communication with Services ............................................................................................. 59

Generated Objects ................................................................................................................ 60

Calculation and Valuation Process Manager (CVPM) ....................................................... 61

Data Processing Framework (DPF): .................................................................................... 62

The Module Editor Tool ........................................................................................................ 62

Problems while Post processing ........................................................................................ 62

Delivery of Positions and Business Transactions ............................................................ 62

Data Volume .......................................................................................................................... 63

Performance .......................................................................................................................... 63

Credit Risk ............................................................................................................................. 63

Set Free Shared Memories (FICO) ....................................................................................... 64

Further Recommendations .................................................................................................. 64

7.3 Troubleshooting: Fiori Apps ....................................................... 64

8 Support Desk Management ....................................................... 68

8.1 Remote Support Setup ................................................................ 68

8.2 Problem Message Handover ....................................................... 68

9 Appendix .................................................................................... 69

Getting Started

1 Getting Started

This guide does not replace the daily operations handbook that we recommend

customers to create for their specific production operations.

About this Guide

Designing, implementing, and running your SAP applications at peak performance 24 hours a day

has never been more vital for your business success than now.

This guide provides a starting point for managing your SAP applications and maintaining and

running them optimally. It contains specific information for various tasks and lists the tools that you

can use to implement them. This guide also provides references to the documentation required for

these tasks, so you will sometimes also need other guides such as the Master Guide, Technical

Infrastructure Guide, and SAP Library.

Target Groups

Technical Consultants

System Administrators

Solution Consultants

Business Process Owner

Support Specialist

1.1 Global Definitions

SAP Application:

An SAP application is an SAP software solution that serves a specific business area like ERP,

CRM, PLM, SRM, SCM.

Business Scenario:

From a microeconomic perspective, a business scenario is a cycle, which consists of several

different interconnected logical processes in time. Typically, a business scenario includes several

company departments and involves other business partners. From a technical point of view, a

business scenario needs at least one SAP application (SAP ERP, SAP SCM, or others) for each

cycle and possibly other third-party systems. A business scenario is a unit which can be

implemented separately and reflects the customer’s prospective course of business.

Component:

A component is the smallest individual unit considered within the Solution Development Lifecycle;

components are separately produced, delivered, installed and maintained.

1.2 Important SAP Notes

Check regularly for updates available for the Application Operations Guide.

Important SAP Notes

SAP Note

Number

Title Comment

83458 OCS Info: Patch download

from SAP Service Marketplace

Describes the technical steps for

the download of required support

packages for the components

SAP_BASIS, SAP_ABA,

PI_BASIS, SAP_BW, FINBASIS,

and SEM-BW.

617547 RZ20: Sending alerts as mail

and SMS

Describes how to use transaction

RZ20 to send alerts from the

CCMS monitoring architecture as

an e-mail, SMS, or other

message types to one or several

recipients.

1166529 Performance: banking services

from SAP

As an integrated knowledge

base for performance-related

topics in FSPP banking services

from SAP this note links to other

relevant notes. Can be updated

at any time.

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=83458&



Getting Started

1134076 CCMS: Monitor sets for SAP

Financial Services

16083 Standard jobs, reorganization

jobs

Jobs that must run periodically in

a live R/3 installation

1343674 Integration operational banking

with accounting

Further information about

configuration and processes in

IOA

706478 Preventing Basis tables from

increasing Considerably

This note helps to reduce the

process of growing for

administrative basis tables by

regularly deleting or archiving the

entries.

1391272 SDL: Source Data Aggregation

(rollout support)

This note provides additional

documents about the source

data aggregation.

1447431 Optimizing performance for

worklist creation




SAP_BASIS, SAP_ABA,


and SEM-BW.

889948 Bank Analyzer 4.0 New Basel

Capital Accord perform tips

The characteristic value of

important process steps occurs

in Customizing which can have a

considerable effect on the

performance of the processes.

1396778 Generic Delta Queue BI

Extraction with CVPM

Restartability and performance of

BI extractions




https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=706478



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=889948


954374 Performance in BA Basel II

processes Release 5.0 and

higher

Important process steps are defined in

Customizing, which can have a

considerable effect on the performance

of the processes.

1007325 Generic Bank Analyzer

DataSources with Delta Queue

The attached How-To guide describes

how the data selection within the

source system can be separated from

the data extraction to the BI system.

The stand-alone data selection in the

source system supports parallel

processing and restartability.

1373479 Authorizations for Generic BI

Extractions

Authorizations for generic BI

extractions.

1534315 How to analyse Generic BI

data extraction errors

How to analyze generic BI data

extraction errors.

496904 Performance notes database

parameters FS-AM for DB2

z/OS

This note contains summarized

recommendations for database

parameters on DB2/S390 for

Deposits Management.

494171 Performance notes FS-AM This note summarizes the most

important settings for optimizing

performance in FS-AM.

884865 PI/XI Admin Check You are administrating an

Exchange Infrastructure System

and would like to get an overview

of the most important daily and

weekly checks.




https://service.sap.com/sap/support/notes/1534315




Getting Started

132484 Predelivery of PS Salary

Structur and Increment

This note contains information

about the predelivery of an

additional part of HRMS Public

Sector Version, - PS Salary

Structure and Increment

Progress for Pilot Customer

Only.

1147208 Consistency check in Bank

Analyzer clients

You want to copy a Bank

Analyzer client or check the

integrity of BA-specific

Customizing.

1083365 Upgrade behaviour of Addon

ST-A/PI

System upgrade with add-on ST-

A/PI

69455 Servicetools for Applications

ST-A/PI (ST14, RTCCTOOL,

ST12)

As preparation for an SAP

EarlyWatch/ GoingLive session

you want to implement the

application-specific tools from

SAP Support (Application

monitor ST14, RTCCTOOL,

ST12 and application specific

SDCC data collectors).

1354442 Integration Account Origination

– Business Partner

Describes a sample

configuration for the replication

of business partners for

integration scenario “Account

Origination and Loans

Management”






2 Technical System Landscape

2.1 Scenario/Component Matrix

Most scenarios of SAP for Banking use component FSAPPL as a business process platform.

Banking services from SAP is a SAP NetWeaver add-on that uses functions from the components

FINBASIS and SEM-BW.

A minimal system landscape consists of the following components:

SAP NetWeaver 7.1 AS ABAP enhancement package 1 for banking services from SAP 7.0

(also valid for banking services from SAP 8.0) with the following components:

o SAP_BASIS 711 – SP 07

o SAP_ABA 711 – SP 07

o SAP_BW 711 – SP 07

o PI_BASIS 711 – SP 07

o ST-PI 2008_1_710 – SP 04

Note that while Process Object Types (software component FSPOT400) run on

NetWeaver 7.40 on a separate instance, Banking Services 8.0 cannot be installed

on NW 7.40.

FINBASIS 700 – SP 15

SEM-BW 700 – SP 15

BI_CONT 711 – SP 02 (only relevant if you use SAP Bank Analyzer)

ST-A/PI 01N* (for more information, see SAP Notes 69455 and 1083365).

Note that some scenarios of SAP for Banking require more than the mentioned

components. For example, the scenario Multi-GAAP (AFI) uses SAP ERP with FI-

GL for postings of accounting data on the general ledger. Other scenarios are built

on a completely different stack of components (for example, Leasing and Account

Origination).

For more details about components, see Chapter 2.1 in the Master Guide for

Banking 2013 at http://service.sap.com/instguides Industry Solutions Industry

Solution Guides SAP for Banking Solution Guides.




Technical System Landscape

For more information about Leasing and Account Origination, see:

http://service.sap.com/crm-inst SAP EHP3 for SAP CRM 7.0 Operate

Application Operation Guide EhP3 for SAP CRM 7.0.

Note that Bank Analyzer scenarios on a HANA DB (software component

FSAPPL450) run on NetWeaver 7.40 on a separate instance, Banking Services 8.0

cannot be installed on NW 7.40. See the respective component installation guide for

the required technical landscape.

For more information about the technical landscape, see the Component Installation

Guide for banking services from SAP 8.0.

2.2 Related Documentation

The following table lists where you can find more information about the technical system

landscape.

Topic Guide/Tool Quick Link on SAP Service

Marketplace

(service.sap.com)

Master Guide for Banking Master Guide instguides Industry

Solutions Industry Solution

Guides SAP for Banking

Solution Guides

Component Installation

Guide for banking services

from SAP 8.0

Component Installation

Guide

instguides Industry

Solutions Industry Solution

Guides SAP for Banking

http://service.sap.com/crm-inst

Component Guides

Application Operations

Guide SAP enhancement

package 1 for SAP CRM

7.0

Application Operations Guide crm-inst SAP EHP3 for

SAP CRM 7.0 Operate

Application Operation Guide

EhP3 for SAP CRM 7.0

Solution Operations Guide

for SAP ERP 6.0

Solution Operations Guide instguides SAP

Business Suite Applications

SAP ERP 6.0 Operations

Operation of SAP

NetWeaver

Technical Operations Manual NetWeaver

For more information, see

http://help.sap.com/netweaver

→ SAP NetWeaver 7.0 → SAP

NetWeaver 7.0 including

Enhancement Package 1 →

SAP NetWeaver 7.0 Library

(including Enhancement

Package 1) → Administrator's

Guide → Technical Operations

for SAP NetWeaver

Sizing Quick Sizer Tool sizing

Technical

Configuration

Master Guide instguides

Scalability Master Guide instguides

High Availability Master Guide instguides

Security Security Map

Security Guide

security

securityguide


Monitoring of SAP for Banking

3 Monitoring of SAP for Banking

Within the management of SAP Technology, monitoring is an essential task. A section has

therefore been devoted solely to this subject.

You can find more information about the underlying technology in the Technical Operations Manual

for SAP NetWeaver on SAP Help Portal at http://help.sap.com/netweaver → SAP

NetWeaver 7.1 → SAP NetWeaver Library → Administrator's Guide → Technical Operation Manual

(TOM).

3.1 Alert Monitoring

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system

environment. SAP provides you with the infrastructure and recommendations needed to set up your

alert monitoring to recognize critical situations for banking services from SAP as quickly as

possible.

3.1.1 Monitoring Installation and Setup

In order to enable the auto-alert mechanism of CCMS, see SAP Note 617547.

To setup CCMS monitoring of banking services from SAP, use the templates as described in SAP

Note 1134076.

3.1.2 Monitoring for Bank Analyzer

Data Delivery to Bank Analyzer

One of the most important processes in monitoring is the data provisioning to applications.

In Bank Analyzer there are several interfaces on the basis of different techniques available, which

use different monitors.

BAPI

The BAPI is an API, which is used to create data in Bank Anlayzer (for all available BAPIs choose

transaction BAPI and then Financial Services -> Bank Analyzer).




BAPIs are only an interface and not a process. They return only standardized messages that

document the status of the process you are executing. The calling process is responsible for

creating an appropriate log and reacting appropriately to the BAPI response. The calling process is

also the owner of the logical unit of work (LUW) and the transaction handling (commit or rollback).

Therefore, no monitoring for these interface calls is available in Bank Analyzer.

Services

As part of service enablement (SOA), the new interfaces to Bank Analyzer are implemented as

services. The infrastructure is responsible for the handling of services. The infrastructure is the

active component and is responsible for the logging of information, the transaction management

and the necessary monitoring capabilities. The SAP infrastructure component for handling

messages is Process Integration (PI), which contains the following monitoring tools:

Technical monitoring: SXMB_MONI

Error and Conflict handling (/SAPPO/PPO2)

Both tools are not specific to Bank Analyzer and common descriptions are therefore available.

While implementing the service usage, you must ensure that the monitors are connected to an

alerting meachanism so that an operator/ responsible person is immediately informed (by SMS or

e-mail for example)-. in case of an incident.

For more detailed information about the provided Business Objects and the corresponding

services, see FSP Business Object Map.

Data Load Layer (DLL)

The data load layer is a tool to load data from a BW system to Bank Analyzer. This is relevant if the

customer is using BW as a data warehouse layer to map and restructure data.

For a functional and technical description, see the guide SMG – Extraction Transformation and

Data Load Layer at http://service.sap.com/instguides Industry Solutions Industry Solution

Guides SAP for Banking Component Guides SMG – Extraction Transformation and Data

Load Layer.

The data load layer owns a process type, which can be included in a BW process chain. The

process loads data according to existing change pointers. The change pointers always document

the current status of each object to be loaded. The change pointers are also used to restart the

process again to handle the objects with errors.

http://uscisdo.wdf.sap.corp:50015/socoview(bD1lbiZjPTAwMCZkPW1pbg==)/render.asp?&id=F46DC2F0B5D011DA2B24000F20DAC9EF&fragID=&packageid=4B0BCBCFF9B9128DE10000000A421666&iv=#v3C9AF6A0375C4E6FA05CD9B5400F9E09



Introduction to Process Chains

For an introduction to process chains, see http://help.sap.com → SAP NetWeaver → SAP

NetWeaver 7.0 including Enhancement Package 1 → SAP NetWeaver 7.0 Library (including

Enhancement Package 1) → SAP NetWeaver by Key Capability →Information Integration by Key

Capability → Business Intelligence →Data Warehousing →Data Warehouse Management

→Process Chain.

Furthermore, the best practices guide SAP Business Warehouse 3.x – Data Target Upload

illustrates the optimization of the upload of transactional data into SAP Business Warehouse.

Usage of Process Chains in the context of DLL

The following guide presents some information about the DLL in BI Process Chains: SMG –

Extraction Transformation and Data Load Layer on http://service.sap.com/instguides Industry

Solutions Industry Solution Guides SAP for Banking Component Guides SMG –

Extraction Transformation and Data Load Layer.

3.1.3 Monitoring for Transactional Banking

The most important monitoring tools for Transactional Banking:

Parallel Processing Monitor RBANK_PP_MONITOR

Job Overview SM37

Display Application Log SLG1

Transactional RFC SM58

Message Monitoring SXMB_MONI

3.1.4 Monitoring for Scenarios

In addition to the required monitoring of each component, some additional monitoring objects are

designed to monitor cross-component communication and other scenario-specific critical situations.

In this chapter only those scenarios are mentioned that do not use banking services from SAP as

the main component.

http://help.sap.com/

https://websmp105.sap-ag.de/~sapidb/011000358700004745572003E


Account Origination

Alert Monitoring with CCMS

For more information about the generic part of alert monitoring with CCMS, see

http://service.sap.com/crm-inst SAP CRM SAP enhancement package 2 for SAP

CRM 7.0 Operate Application Operation Guide SAP CRM 7.0 EhP1.

CRM-specific qRFC Monitors

CRM queue groups Description

Outbound queues

CSA*

Send queues of CRM Server Applications:

Document replication to ERP via BDocs

R3A*


XBQS*,XBTS

Business Partner distribution via Proxy

Inbound queues

XBQR*, XBTR*

Business Partner distribution via Proxy

Leasing

Alert Monitoring with CCMS

For detailed information about the generic part of alert monitoring with CCMS, see


SAP EHP3 for SAP CRM 7.0 Operate Application Operation Guide EhP3 for SAP CRM 7.0.

CRM-specific qRFC Monitors

CRM queue groups Description

Outbound queues




CSA*

Send queues of CRM Server Applications:


R3A*


XBTS, XBQS* Business Partner distribution via Proxy

Inbound queues

XBQR*, XBTR* Business Partner distribution via Proxy

Funding Management

There is no special CCMS alert monitoring for Funding Management.

3.1.5 Monitoring for Financial Services Business Partner

The following are the most important monitoring tools for Financial Services (FS) Business Partner

Web services:

Description Monitoring Tool

(Transaction)

Comments

Message Monitoring SXMB_MONI For XI 3.0 messages

3.1.6 Monitoring SAP Fiori Apps

SAP Gateway plays an important role within the system landscape for SAP Fiori apps. Therefore,

monitoring SAP Gateway is essential for monitoring SAP Fiori apps.

SAP Gateway

SAP Solution Manager 7.1 SP04 or higher supports a root-cause analysis for SAP

Gateway. For more information, see https://service.sap.com/support SAP Solution

Manager Run SAP like a Factory Application Operations End-to-End Root Cause

Analysis .

Also, see SAP Note 1478974.

For more information about monitoring SAP Gateway, see the following documentation:

https://service.sap.com/support

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1478974&_NLANG=en&_NVERS=0

o For SAP NetWeaver 7.40, see SAP Help Portal at http://help.sap.com/nw74

Application Help Function-Oriented View SAP Gateway Foundation

(SAP_GWFND) SAP Gateway Foundation Technical Operations Guide .

o For more information about the error log for SAP Gateway hub, see SAP Help

Portal at http://help.sap.com/nw74 Application Help Function-Oriented View

SAP Gateway Foundation (SAP_GWFND) SAP Gateway Foundation Technical

Operations Guide Supportability Error Log .

User Interface Add-On for SAP NetWeaver

For more information about administrative tasks, see SAP Help Portal at

http://help.sap.com/nw74 Application Help UI Technologies in SAP NetWeaver UI

Frameworks based on HTML5, JavaScript and CSS SAP NetWeaver User Interface

Services Administration Guide .

For more information about problem solving related to the SAP Fiori launchpad, see SAP

Help Portal at http://help.sap.com/nw74 Application Help UI Technologies in SAP

NetWeaver UI Frameworks based on HTML5, JavaScript and CSS SAP Fiori Launchpad

Troubleshooting .

3.2 Detailed Monitoring and Tools for Problem and Performance

Analysis

3.2.1 Introduction to technical monitoring

The technology of banking services from SAP is based on the Web Application Server. For

information about technical problem analysis (such as with a database, the operating system, or

workload analysis), see the Technical Operations Manual for SAP NetWeaver at

http://help.sap.com/netweaver → SAP NetWeaver 7.0 → SAP NetWeaver 7.0 including

Enhancement Package 1 → SAP NetWeaver 7.0 Library (including Enhancement Package 1) →

Administrator's Guide → Technical Operations for SAP NetWeaver.

For software component FSAPPL450, follow the respective path for SAP NetWeaver 7.4.

For more information about sizing, see the standard sizing guidelines that are published on SAP

Service Marketplace at http://service.sap.com/sizing. There is also an online sizing tool

Quick Sizer that is available at http://service.sap.com/quicksizing.

You can find more information about benchmarks under

http://www.sap.com/solutions/benchmark/trbk.epx.

http://help.sap.com/nw74





http://service.sap.com/sizing

http://service.sap.com/quicksizing

http://www.sap.com/solutions/benchmark/trbk.epx


For more information about performance, especially database parameter settings,

see SAP Notes 496904, 494171, and 1166529.

Monitoring with Solution Manager Business Process Monitoring

The Solution Manager offers a wide range of tools to monitor critical jobs in a bank’s entire process

chain. These tools are grouped in the Business Process Monitoring (BPM) functions. For more

information, see Monitoring SAP Banking Parallel Processing Jobs with Solution Manager Business

Process Monitoring (https://websmp205.sap-ag.de/~sapidb/011000358700000743982010E). Chapter 2

Design also contains a table with technical and economical key figures.


Analysis (Bank Analyzer)

ABADRGEN – Code Generation for ABADR Derivations

ABADR derivations are used widely across the Bank Analyzer system. As of banking services 7.0, a

code generation tool has been implemented that generates code instead of interpreting the derivations

at runtime. This improves system performance.

When you install a new Bank Analyzer client or you change the Customizing of a derivation, the code for

the respective derivations needs to be (re-)generated. The code is generated on demand, in other words

when a process uses the respective derivation. This is different to the handing of the module editor, for

example, where the code is generated in the after-import method (which in turn can potentially fail, and

then makes a manual (re-)generation necessary).

Usually, no manual intervention in this mechanism is necessary. However, you can display the status of

the generated code and manually trigger (re-)generation of the code using report

/ba1/r_al_d0_genprog_analyzer.

SDL Configuration Check

The configuration of the infrastructure and the SDL is spread across a number of Customizing activities.

You can use the SDL configuration check to check the consistency of the infrastructure and SDL

Customizing.






Transaction /ba1/f0_fdb_check allows you to run this check in online mode (the checks themselves are

started in background mode, and the refresh button on the UI can be used to follow their progress).

Alternatively or additionally, you can use the report /ba1/rf0_check_config for scheduling the check with

a variant in SM37. In this way you can, for example,be sent a daily e-mail if the check finds an error.

Inconsistencies in the infrastructure and SDL Customizing can arise when a Customizing transport that

is consistent in the source system arrives in a target system where the surrounding Customizing differs

from the source system.

Error Handling in SDA

Source data aggregation (SDA) is an infrastructural part of Accounting for Financial Instruments

and is responsible for aggregating financial and business transactions and results for these

financial products. Accounting processing is more efficient through SDA. For information about

error handling in SDA, see SAP Note 1391272. This note describes how you can prevent

Customizing errors and other errors during process runtime, for example.

Error Handling PPO for IOA

For Operational and Analytical Banking, all services communication is asynchronous. During the

delivery process of an XML message to the receiving system, an application error could occur, but

error and conflict handling is in place. Application errors can be displayed as messages and

processed by the Post Processing Office.

For more information about PPO for IOA (Integration of operational banking with

accounting), see SAP Note 1343674.

Generic BI Data Extraction

You can use generic BI Data Extraction to extract data from the RDL and the SDL into SAP

NetWeaver Business Intelligence (BI). After the extraction process, you can use the data for Basel

II reports, for example.

For more information about performance issues in BI extraction and reporting, see the following

SAP Notes:




SAP Note

Number

Title Comment

1447431 Optimizing performance for

worklist creation




SAP_BASIS, SAP_ABA,


and SEM-BW.

889948 Bank Analyzer 4.0 New Basel

Capital Accord perform tips

The characteristic value of

important process steps occurs

in Customizing which can have a

considerable effect on the

performance of the processes.

1396778 Generic Delta Queue BI

Extraction with CVPM

Restartability and performance of

BI extractions

954374 Performance in BA Basel II

processes Release 5.0 and

higher

Important process steps are defined in

Customizing. This can have a

considerable effect on the performance

of the processes.

1007325 Generic Bank Analyzer

DataSources with Delta

Queue

The attached How-To guide describes

how the data selection within the

source system can be separated from

the data extraction to the BI system.

The stand-alone data selection in the

source system supports parallel

processing and restartability.

1534315 How to analyse Generic BI

data extraction errors

How to analyze generic BI data

extraction errors

1373479 Authorizations for Generic BI

Extractions

Authorizations for generic BI

extractions









Analysis (Transactional Banking)

Parallel Processing Monitor - RBANK_PP_MONITOR

You can monitor reports developed based on the PPF (Parallel Processing Framework) by using

the RBANK_PP_MONITOR report that you start using transaction SE38/SA38 or

BANK_PP_MONITOR. The report displays the status of the jobs currently running and how many

packages have already been processed as a percentage rate along with other details. At the same

time, the system gives you an overview of the relevant active processes using transaction SM50 –

Process Overview.

This monitor is available in all systems that use SAP Basis 620 or higher.

Once the mass run has been processed, the monitor no longer contains any run information. It

displays only jobs that are currently running or jobs that have been processed with errors. If errors

occurred, the entries are marked in red after the mass run has been processed.

In the Processing Status field, the monitor displays in percent how many packageshave already

been processed. The Table Data field displays the total number of packages and the Packages Init

field displays the packages awaiting processing. You can see the packages currently being

processed in the Packages Collected field.

In connection with theRBANK_PP_MONITOR check, the deletion report RBANK_DELETE_RUNS

deletes process data that was created to process the job within this framework. After a successful


run, this data is no longer needed and can be deleted using this report (see also SAP Note

1418333).

Job Overview – SM37

You can use transaction SM37 to obtain an overview of all running, scheduled, released and

finished batch jobs in your SAP environment.

You use this tool to monitor batch jobs during processing and to view details of their status, to

make sure processing is successful, to check for runtime and related details of a job, or to schedule

jobs for a specific time in the future.

When a job is finished, the system displays the duration of the job in seconds, the job log details,

andwhether a spool file has been written.

Display Application Log – SLG1

You can analyze the system application log using transaction SLG1. Application logs are generated

for all application processes based on SAP PPF. The system logs statistical information about the

mass run (number of processed and successful objects), error messages for all problems that

occurred, and success messages (if enabled).

Whether success messages are written to the application log depends on the settings in the

selections screen of the mass run.

For testing purposes, it is fine to choose all messages, but during production we recommend that

you have only one success message per object (if at all). If you choose Log Off (no message),

there will not only be no success message, but also no error message in the log and no messages

in the postprocessing orders (the creation of orders is independent). We do not recommend this

setting.

A separate transaction is available to display the application log for each mass run in Banking

Services, for example, transaction BCA_ACBAL_MASS_LOG to display all application logs of the

account settlement mass run. You can find these transactions by choosing Account Management

Logs on the Easy Access screen. All log transactions have the same look and feel and are

based on transaction SLG1, which is described in detail below. The difference between the

transactions is that some parameters, such as Program and External ID, are filled by default. This

makes it easier to select only the logs that you are interested in.

On this selection screen, all settlement mass runs from 2009-12-01 of user C5128636 are selected.

This is a good way to start analyzing logs based on date and application.

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1418333%5e

Transactional RFC – SM58

You should use transaction SM58 (transactional RFC) on a regular basis when there is RFC

communication between applications, especially when Loans on Platform is used to check whether

all Billing Request Items are sent over from the SAP Banking Services system to the SAP FI-CAx

system for open item management. If necessary, you can restart the transfer from the SAP Banking

Services system after the problem is solved (it is also possible to perform it in debugging mode).

For more information, see RFC Monitoring (https://websmp207.sap-

ag.de/~sapidb/011000358700000491282008E).

Message Monitoring- Integration Engine – SXMB_MONI

You can use transaction SXMB_MONI to monitor and analyze messages processed using the

Process Integration Server (PI),. Select the monitor for XML messages and specify the relevant

time interval. If too many messages come up, specify status group Errors and follow your

guidelines for troubleshooting.

Message Monitoring using SXMB_MONI

You cannot execute options in the menu that have the locked symbol because you do not have the

required authorization. The authorizations for the individual functions are tailored to requirements

and are assigned as derivations of the role SAP_XI_MONITOR. They are all based on the

authorization object S_XMB_AUTH.

Authorization object S_XMB_DSP controls the display of the message content. Unless the user has

the authorization S_XMB_ADM (administrator), the system only displays XML messages for the

current client.

For more information about the use case of SXMB_MONI, see Best-Practice Documents

(https://websmp207.sap-ag.de/solutionmanagerbp).


Analysis (Scenarios)

Account Origination

Interfaces

Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and

HTTP.


https://websmp207.sap-ag.de/solutionmanagerbp


CRM Server Analysis Tools

qRFC Outbound Queue Monitor:

CRM Server Central Monitoring

Activities I Functions

Monitoring Tool

(Transaction)

Used in FS AO to Monitor:


o Monitors data transfer between

the ERP back-end system and

the CRM server

SMQI Document replication to CML,

CMS via BDocs

Business Partner distribution via

proxy

qRFC Inbound Queue monitor:

o Monitors data transfer

between the ERP back-end

system and the CRM server

SMQ2 Document replication to CML,

CMS via BDocs


proxy

Integration Engine - Monitoring SXMB_MONI Document replication to CML,

CMS via XIF Adapter

Business Partner distribution via proxy

BDoc MessagesISummary

o Monitors the status of the BDoc messages and detects the application or Customizing errors during data exchange.

o SMW0I: Displays BDoc

message content and possible

validation or receiver errors

o SMW02: Displays BDoc

message summary according

to the sender site ID

o SMW02a: Groups BDoc

messages according to

validation or receiver errors

• SMW03: Displays client-independent

BDoc message summary

SMW0I / SMW02 /

SMW02A / SMW03

Document replication to CML,

CMS via BDocs

For more information, see http://service.sap.com/crm-inst




Transactions for New Loan Boarding (application component FSPOT)

NLB_EXC_DISPLAY_UI: You can use this transaction to display the process object “New Loan

Boarding". For this, you need the role ‘SAP_NLB_UI_DISPLAY’ or ‘SAP_NLB_UI_EXPERT’

(created for the profile ‘Onboarding Manager’).

NLB_EXC_SEARCH_UI: You can use this transaction to abort the process object “New Loan

Boarding”. For this, you need the role ‚SAP_NLB_UI_EXPERT’.

Data Archiving

FS Product

You can use data archiving to store product master data that is no longer required and subsequently

delete it from the database. The SAP Product Archiving Environment is completely controlled by

status and is connected to the SAP Archive Information System. The archiving object for the SAP

Product is called PRODUCT_MD. A product can be selected for archiving directly from product

maintenance (transaction COMMPR0I) by setting the status To Be Archived. You can find the

archiving administration in transaction SARA.

For more information, see Archiving the SAP Product.

Business Partner

You can use archiving to store business partner data that is no longer required and subsequently

delete it physically from the database. The archiving object for business partners is CA_BUPA.

For more information, see Business Partners.

FS Quotation, Banking Customer Quote and Banking Sales Contract

You can use archiving to store business transactions that are no longer relevant including FS

Quotations, Banking Customer Quote and Banking Sales Contract in archives and subsequently

delete them physically from the database.

Opportunity

You can use archiving to store opportunity data that is no longer required and subsequently delete

it physically from the database. The archiving object for opportunities is CRM_OPPT

For periodic tasks that have to contain data growth (that is, to reorganize temporary data), see the

Periodic Tasks section in this guide.

http://help.sap.com/saphelp_crm50/helpdata/en/d0/493a40a63bc65de10000000a155106/frameset.htm

http://help.sap.com/saphelp_crm50/helpdata/en/52/cff837a9aae651e10000009b38f8cf/frameset.htm

Personal Financial Statement

You can use archiving to store personal financial statement data (of a business partner) that is no

longer required and subsequently delete is physically from the database. The archiving object for

the personal financial statement of a business partner is CRM_FS_PFS.

Leasing

Interfaces

Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and

HTTP.

CRM Server Analysis Tools


CRM Server Central Monitoring


Monitoring Tool

(Transaction)

Used in Leasing to Monitor:


Monitors data transfer between the CRM server and the ERP back-end system

SMQ1 Document replication to ERP via BDocs


proxy

Proxy


Monitors data transfer between the ERP back-end system and the CRM server

SMQ2 Update processes from ERP

proxy

Integration Engine - Monitoring SXMB_MONI Purchase process integration with

SRM via XIF Adapter


BDoc MessagesISummary

Monitors the status of the BDoc messages and detects the application or Customizing errors during data exchange

SMW01: Displays BDoc message content and possible validation or receiver errors

SMW02: Displays BDoc message summary according to the sender site ID

SMW02a: Groups BDoc messages according to validation or receiver errors

SMW03: Displays client-independent

BDoc message summary

SMW01 / SMW02 /

SMW02A / SMW03

Document replication to ERP using BDocs

For more information, see http://service.sap.com/crm-inst SAP CRM SAP

enhancement package 2 for SAP CRM 7.0 Operate Application Operation Guide SAP CRM

7.0 EhP2.

ERP Backend System Analysis Tools


Monitoring Tool

(Transaction)

Used in Leasing to

Monitor:_


Monitors data transfer

between the ERP back-

end system and the CRM

server

SMQ2 Incoming Request to

ERP

System Application log SLG1 Application Monitoring for objects type FILA in SAP ERP.

For more information about SAP ERP generic periodic tasks, see:


http://service.sap.com/instguides SAP Business Suite Applications SAP ERP

SAP ERP 6.0 Operations Solution Operations Guide for SAP ERP 6.0


SAP enhancement packages for SAP ERP 6.0

Data Archiving

FS Product

You can use data archiving to store product master data that is no longer required and subsequently

delete it physically from the database. The SAP Product Archiving Environment is completely

controlled by status and is connected to the SAP Archive Information System. The archiving object

for SAP Product is called PRODUCT_MD. A product can be selected for archiving directly from

product maintenance (transaction COMMPR0I) by setting it to the To Be Archived status. You can

find the archiving administration in transaction SARA.

For more information, see Archiving the SAP Product.

Business Partner

You can use archiving to store business partner data that is no longer required and subsequently

delete it physically from the database. The archiving object for business partners is CA_BUPA.

For more information, see Archiving Business Partners.

FS Quotation; FS Contract

You can use archiving to store business transactions that are no longer relevant, including FS

Quotations and FS Contracts, and subsequently delete them physically from the database. The

archiving object for FS Quotations and Contracts is CRM_LEAS.

Opportunity

You can use archiving to store opportunity data that is no longer required and subsequently delete it

physically from the database. The archiving object for opportunities is CRM_OPPT.


periodic tasks section in this guide.



http://help.sap.com/saphelp_crm50/helpdata/en/d0/493a40a63bc65de10000000a155106/frameset.htm

http://help.sap.com/saphelp_crm50/helpdata/en/52/cff837a9aae651e10000009b38f8cf/frameset.htm


Funding Management

There are no special problem and performance analysis tools provided for Funding Management.

You can carry out problem analysis using SAP Application Logs (SLG1). All Funding Management

applications, reports, services and jobs are enabled to use logs for reporting problems and errors.

The main application log object for all logs is /TXS/. You can configure additional subobjects in

Customizing. For more information about these settings, see SAP Funding Management

Configuration Guide.

3.2.5 Trace and Log Files

Trace files and log files are essential for analyzing problems. Log files are written whenever the

database system and database tools are in operation.

Application Log

You can display application logs with transaction SLG1. Each logged event is classified by object

and any subobjects which belong to it. There are application log objects that are specific for

banking services from SAP 8.0. The following are the central objects and start with the prefixes:

FS_* Financial Services component

/BA1* Bank Analyzer component

BCA* Operational Banking components

/TXS/ Funding Management component

In addition, there are generic application log objects, for example, derivation tools, archiving, and

technical interfaces like BAPIs.

For a complete list of application log objects, start transaction SLG1, and in the Object field choose

an entry from the list of objects. When you have entered an object, you can also display the

subobjects that belong to this object. For a complete list of these subobjects use the input help on

theSubobject field.

For more information about analyzing application logs, start transaction SLG1 and choose Help →

Application Help.

Base Level Logs

SAP servers record events and problems in system logs. Each SAP application server maintains a

single local log. When this log file reaches the maximum permitted size, the system starts to

overwrite the file from the beginning. You can configure your server so that messages are issued to

a central log file as well as to a local log.

Central logging is not available on AS/400 and Windows NT host systems.

You can display these base level logs with transaction SM21.

Trace files

To locate errors more easily, you can use various traces that log additional actions.

For more information about log files and traces, see the Technical Operations Manual for SAP

NetWeaver at http://help.sap.com/netweaver → SAP NetWeaver 7.0 → SAP NetWeaver 7.0

including Enhancement Package 1 → SAP NetWeaver 7.0 Library (including Enhancement

Package 1) → Administrator's Guide → Technical Operations for SAP NetWeaver.

3.2.6 Workload Monitors

Customizing of parallel jobs and package size

Parallel processing and packaging settings affect the processing time and the usage of the

hardware resources for the Banking Services solution. You can find the configuration steps for

package size settings in Chapter 2 Best Practice Procedure and Verification of the Best Practice

Guide Parallelization, Packaging, Monitoring of SAP Banking (https://websmp205.sap-

ag.de/~sapidb/011000358700001878872008E).

You can use monitoring tools like MassMan and RBANK_PP_MONITOR to verify the parallel

processing and package size settings that lead to the expected throughput of a mass process. For

more information about these tools, see Chapter 3 Operations and Optimization of this Best

Practice Guide.

For transactionsthat are also relevant for monitoring, see the table in the section

General Checks in the ABAP Environment.




3.2.7 Interface Monitors

You can access interface monitors for analyzing problems with interfaces such as RFC, IDoc, and

HTTP using transactions SMQ1 (Outbound Queue) and SMQ2 (Inbound Queue).

For the analysis of services used by banking services from SAP, you can use the following tools:

Postprocessing Office (PPO)

Error and Conflict Handler (ECH)

You can access these functions from the SAP Easy Access screen by choosing Cross-Application

Components → Postprocessing Office. For more information, see the application help.

3.2.8 Data Growth and Data Archiving Monitors

SAP provides standard functions for archiving master data and results data. You can find the

archiving administration in transaction SARA with an overview of all archiving objects of banking

services from SAP. For more information, see the application help for transaction SARA.

There are some restrictions for archiving in the Business Partner for Financial

Services component. For more information, see SAP Library for SAP Banking

Services → SAP Business Partner for Financial Services → Functions → Archiving.

Partitioning of Large Tables

The Best Practice Guide for Banking Services – Database Performance – Settings for DB2/OS390

describes technical partitioning settings for large tables in DB2/OS390. This process helps to

improve performance and scalability (see also SAP Note 706478).

Data Growth and Data Archiving Monitors: Bank Analyzer


Periodic Tasks section in this guide.

Archiving in SAP Bank Analyzer

For detailed Information about the archiving processes in SAP Bank Analyzer, see the Archiving



Guide SAP Bank Analyzer at http://service.sap.com/instguides Industry Solutions Industry

Solution Guides SAP for Banking Component Guides "Archiving Guide - SAP Bank

Analyzer.


Management of SAP for Banking

4 Management of SAP for Banking

SAP provides you with an infrastructure to help your technical support consultants and system

administrators effectively manage all SAP components and complete all tasks related to technical

administration and operation.

4.1 Starting and Stopping

In the simplest case, an SAP system consists of only a database and a single application server.

You can start and stop the SAP system and its database using operating system tools (special

scripts are available for this) or you can use the appropriate program icons.

Start and Stop Sequence

The start sequence of the entire system landscape depends on the applications used and the

distribution of the applications. The systems that make data available, such as SAP BW must be

started first, so the data is already available when the systems that further process or display this

data are started. The sequential order must be reversed accordingly for the stop sequence.

If you are using several applications in one instance and you start or stop one application of this

instance, all other applications of this instance start or stop running.

Tools

ABAP-based components and add-ons installed in the same instance start and stop in the

administrative environment of SAP NetWeaver.

For more information about usage type Application Server ABAP, see SAP Help Portal at

http://help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 7.1 → SAP

NetWeaver Library → Administrator's Guide → Technical Operation Manual (TOM) under the

following paths:

General Administration Tasks → Starting and Stopping SAP NetWeaver ABAP and Java

Administration of SAP NetWeaver Systems → Application Server ABAP (AS ABAP) →

Administration → Starting and Stopping the System

Administration of SAP NetWeaver IT Scenarios → Enabling Application-to-Application

Processes → Tasks → Starting and Stopping


4.2 Software Configuration

SAP for Banking does not recommend custom code changes. They are considered as

modifications and are not supported. There are tools to perform changes without modifications,

such as the standard BAdIs or the module editor.

4.3 Administration Tools

There are no specific administration tools in SAP for Banking. Standard administration tools are

part of SAP NetWeaver. For more information, see the Technical Operations Manual for SAP

NetWeaver referenced in chapter 2.2.

4.4 Backup and Restore

You need to back up your system landscape regularly to enable you to restore and recover it in the

event of a failure.

The backup and restore strategy for your system landscape should not only consider SAP systems

but should also be embedded in overall business requirements and incorporate your company’s

entire process flow.

You must back up your system landscape regularly to ensure that you can restore and recover it in

case of failure. You perform a backup in the following cases:

After the initial installation and configuration of the system landscape

After changes, for example, changes to the configuration, the software upgrade of

individual components or after the replacement of components made to the system

landscape. This depends on the frequency of such changes.

The banking services from SAP component contains application data. All reports can be run in

parallel mode and can be restarted when canceled.

The backup and restore strategy for banking services from SAP consists of two parts:

Backup and restore coverage for each component

You must back up individual components regularly to ensure that you can restore and

recover them if there is a system failure.

Cross-system data dependencies and handling

The backup and restore strategy for your system landscape should not only consider SAP


systems but should also be embedded in overall business requirements and incorporate

your company’s entire process flow.

In addition, the backup and restore strategy must cover disaster recovery processes, such as the

loss of a data center through fire. In this context, it is important that you ensure that backup devices

are not lost together with normal data storage, for example, by the separation of storage locations.

You must take the following elements into account when you plan a backup and recovery strategy

for application, software and configuration files:

Operating system

Database data files

Database software

SAP software and file systems

Log files (SAP and others)

Software of other system components (file systems and configuration files)

Based on the type of application data contained in a component, we have

introduced a categorization scheme for system components that can be used to

analyze the backup requirements of any system component and to easily determine

an appropriate backup method for this component.

4.4.1 Application Data

Application data is stored in a database. Depending on the database software, you can conduct

either full or incremental database backups, for example, on a daily basis.

Information is also stored in file systems on the application servers (usually in file systems shared

between all application servers). This includes job logs and batch input log files. This information

can be very valuable, so it must also be included in a backup strategy. If files are used for data

exchange with other systems, these files must be included as well.

For more information about possible backup scenarios, see SAP Service Marketplace at

http://service.sap.com/atg Advanced Technology Group Backup&Restore

Documentation.

http://service.sap.com/atg

4.4.2 Operating System, Software, and Configuration Data

Apart from business-critical application data (held in databases), you can also back up the system

and application software (including configuration files). If you do this, you do not have to reinstall

the system and application software in the event of the software being damaged.

It is always possible to reinstall the operating system, software, and configuration data. However,

reinstallation and configuration can take a long time. Therefore, if a backup of the software and

configuration is available, you can reduce the time needed to restore your system after a system

failure.

Online Backup

The data contained in the database can be backed up online. However, it is not possible to do the

same for the runtime infrastructure. An online backup refers to the system landscape and not the

databases that contain the business-critical application, or the infrastructure components.

If you perform a backup while the server is running, open files may not be backed up.

File System Backup versus Full System Backup

A file system backup only applies to specific files or file systems, whereas a full system

backup applies to all files and file systems, including the operating system.

After new software components are installed, certain entries in the configuration files of the

operating system cannot be found in the file systems where the software installation

occurred. We therefore recommend that you perform a full system backup after installation,

and that you back up the file systems of both the installed software and the operating

system on a regular basis

For more information about possible backup scenarios, see SAP Service Marketplace at

http://service.sap.com/atg Advanced Technology Group Backup&Restore

Documentation.

4.4.3 Database

To back up your database, proceed as follows:

Run the database in archive mode

This means that all actions on the database that modify data are recorded by the database

and written into a transaction log. With regular full backups of your database (either offline

or online), as well as a complete set of transaction logs since the last backup, it is possible



to restore a crashed database to any point in time before the database crashed.

Back up your database every day

Since the log files fill up, you must perform several backups of the log files during the day.

4.4.4 Further Information

Type of Information Quick Link / Path Description

Backup and Restore for

SAP Business Suite

http://service.sap.co

m/atg → Advanced

Technology Group →

Backup&Restore → Backup

& Restore for SAP Business

Suite

Collection of best practices for

backup and restore

4.5 Application Copy

For more information about client copies for Bank Analyzer, see the Component Installation Guide

for banking services from SAP 8.0.

4.6 Periodic Tasks

This section lists the most important tasks to be performed by the administrator regularly. You can

find a synoptical table with the relevant transactions in the ABAP environment in the following

section. The tasks are differentiated by the frequency of their execution and this information is

given for each task. Most of the tasks have to be performed on a daily basis, but some only on a

weekly basis.

The periodic tasks listed here help to keep your SAP system stable.

These tasks are not critical for system availability. Avoid running additional tasks

when the system is stalled by an overload of work processes and needs to be

restarted.



4.6.1 General Checks in the ABAP Environment

ABAP transactions that should be checked regularly are listed in the following table with a short

description of what they display. Even though you can automate the checks in part, the most

important transactions are listed.

Transaction

code

Content / Meaning Interval for

Checks

RZ04 Maintenance of Operating Mode Weekly

SM12 Lock Entries: Locked tables can be viewed and deleted Daily

SM13 Show Update Requests: You can select order status, date,

and so on

Daily

SM21 System Log: The log can be read individually Daily

SM35 Batch Input Daily

SM37 Job Selection/Job Control: Overview of planned, released,

prepared, active, finished, or aborted jobs

Daily

SM50 / SM66 Work Process Overview: Overview of all work processes

used by you (SM50) or a global overview of the SAP work

process system (SM66)

Daily

SM59 Configuration of RFC Connection Weekly

SP01 Spool Administration: Overview of spool and output orders Daily

SP12 TemSe Check: Administration of temporary sequential data Weekly

ST02 Buffer Monitor: provides a buffer statistic and shows the

memory allocation

Daily

ST03 Workload Monitor /System Load Monitor: This monitor is

used for performance monitoring in particular

Daily

ST04 Database Monitor: Provides statistic data on activities of the

respective RDBMS

Daily

ST06 Operating System Monitor: Provides information about Daily


memory, CPU, LAN, and so on

ST10 Table Call Statistics: You can select tables, time frames, or

servers

Daily

ST22 ABAP Runtime Error (Dump Analysis): Analysis occurs for

different criteria

Daily

DB02 Information about the Database: Used database system;

information about database objects; allocated memory

Daily

DB13 DBA Planning Calendar: Check planning of data backup Daily

OS16 Operating System Monitor Daily

For more information about periodic tasks and jobs in operation, see SAP Notes

132482 and16083.

Checks for Database and Operating System

For information about specific tasks for the database and the operating system, see SAP Help

Portal at http://help.sap.com → SAP NetWeaver → Administrator’s Guide → Technical

Operations for SAP NetWeaver → Administration of SAP NetWeaver Systems → Application

Server ABAP (AS ABAP) → Monitoring → Tasks → Monitoring the ABAP Performance.

Automated Checks

If possible, the checks mentioned in the previous section should be automated to facilitate

administration. When you automate the checks, the administrator should be notified if an error

occurs (for example, by SMS to a mobile phone). For more information about auto-reaction

methods, see the SAP Help Portal at http://help.sap.com → SAP NetWeaver →

Administrator’s Guide → Technical Operations for SAP NetWeaver → Administration of SAP

NetWeaver Systems → Application Server ABAP (AS ABAP) → Monitoring → Tools.





4.6.2 Specific Checks for SAP NetWeaver Usage Types

Application Server ABAP

For more information about periodic tasks for the Application Server ABAP, see:

o SAP Help Portal at http://help.sap.com/netweaver → SAP NetWeaver →

Administrator’s Guide → Technical Operations for SAP NetWeaver → Administration of

SAP NetWeaver Systems → Application Server ABAP (AS ABAP) → Monitoring → Tasks.

Business Intelligence

For more information about periodic tasks for BI, see:

o SAP Help Portal at http://help.sap.com → SAP NetWeaver → Administrator’s Guide

→ Technical Operations for SAP NetWeaver → Administration of SAP NetWeaver

Systems → Business Intelligence (BI) → Administration.

o SAP Service Marketplace at http://service.sap.com/solutionmanagerbp → Best

Practice for Solution Operations → Periodic Jobs and Tasks in SAP BW.

Process Integration (XI)

For more information about periodic tasks for the usage type PI, see SAP Help Portal at

http://help.sap.com → SAP NetWeaver → Administrator’s Guide → Technical Operations for

SAP NetWeaver → Administration of SAP NetWeaver Systems → Process Integration (PI) →

Monitoring.

See also SAP Note 884865.

4.6.3 Checks in banking services from SAP

Periodic tasks include reports on the daily processing of accounts and business transactions. The

sequence in which you run these reports, and their interdependencies, depend on the configuration

of your system. You have to define the order in which the system runs the reports, and how the

reports interrelate, according to your business needs .



http://service.sap.com/solutionmanagerbp




You can find more information about periodic tasks for the components in banking services from

SAP in SAP Library on SAP Help Portal at http://help.sap.com →Industry Solutions → SAP

for Banking → banking services from SAP.

4.6.4 Scheduled Periodic Tasks

This chapter describes all automatable tasks that have to run periodically to keep the application

running smoothly. These tasks may be required at component level and are therefore relevant in

each scenario that uses the component. For information abouthow these are mapped, see the

Scenario/Component Matrixchapter . Other tasks may be relevant for specific business scenarios

only. It is important that you monitor the successful execution of these tasks on a regular basis.

Scheduled Periodic Tasks: Bank Analyzer

Scheduled periodic tasks

Program Name/Task Task

scheduling

tool

Recommended

Frequency

Detailed Description

Archiving using transaction SARA Details are listed in the Archiving

Guide SAP Bank Analyzer on


Industry Solutions Industry

Solution Guides SAP for

Banking Component Guides

Archiving Guide - SAP Bank

Analyzer.

Report /BA1/RFP_OBSDB_DELETE

(transaction

/BA1/FP_OBSDB_DELETE)

Weekly

This report deletes the entries of

the bundle DB of specific

bundling runs. These are

intermediate results and

therefore do not need to be kept

or archived. Job can be

restarted.



Report

/BA1/R6_REP_DPF_REORG

Weekly This report deletes temporary

cluster and aggregation tables of

processes that have terminated

unexpectedly. Job can be

restarted.

Report

/BA1/R6_JC_APPLOG_DPF_REORG

Weekly This report deletes temporary

logs (application logs) for

processes that have terminated

unexpectedly. Job can be

restarted.

RBANK_DELETE_RUNS See SAP note

1439952

Deletion report for

RBANK_PP_MONITOR Process

Data

Transaction

/BA1/HW_PREAGGREGATE (resp.

/BA1/HW_PREAGG2)

Schedules preaggregation of

RDL results based on

requirements of the reading

applications. For more

information about RDL

preaggreation, see


Industry Solutions Industry

Solution Guides SAP for

Banking Component Guides

Scheduled Periodic Tasks: Transactional Banking


Program Name/Task Task

Scheduling

Tool

Recommended

Frequency


RBANK_DELETE_RUNS See SAP Note

1439952

Deletion report for

RBANK_PP_MONITOR process



data

R_BCA_PRI_PP_PACKAGE_CN At least once

per week (if

product price

list function is

used)

Adopt product pricing list to

related contracts report

Account Management Archiving

Data Deletion

SNITEM – Non-Balance-Changing postings

GL_BALANCE – Financial account balances

GL_BALPREP – Balance sheet preparation data

GL_SUMS – FI totals records

INVENTORY – Inventory data

RECONC – Reconciliation data

PRENOTE_T – Technical Prenotes

Delete reports in Account

Management via Delete Objects

The delete programs delete the

data records of the deletion

object from the operational

database. Data that is no longer

required in the operational

system is deleted to improve

performance in the operational

database. During the process,

the delete program generates

an application log containing

statistical data and

simultaneously writes the

current status in an activity log.

You can use the archiving

monitor to display both logs and

monitor the progress of the

process flow.

RBCA_PAYMITEM_PROCESS_ENQ Multiple times a

day

In the operational banking

scenarios you must regularly

reset the lock table for payment

items.

/SAPPO/RESUBMIT_ORDERS_2

Multiple times a

day

Automatic processing of

PPO orders after errors have

been solved or unlocks have

been performed.

RSCOLL00

Every hour Collects statistical records

automatically

System Log Daily

(minimum)

Evaluates system message for

each instance

CCMS / RZ20 Daily

(minimum)

Monitors technical status of the

system

SXMB_MONI Daily

(minimum) Checks for PI error messages

/SAPPO/DELETE_ORDERS

Daily Closed PPO order will be

deleted

RBCA_PAYMITEM_CLEARING_LIST

Daily Checks for open items not

cleared

Posting Control Office

Daily Checks and processes payment

items with errors

MassMan Monitoring

Daily For daily monitoring and

performance testing

Postprocessing Office

Daily, after EoD

Postprocessing of errors

performed during end-of-day

processing using PPO orders

Transactional RFC

Daily Checks for RFC communication

errors

BCA_BL_DD_PP_RUN – SEPA

Direct Debit Mass run

Daily

Report to process the SEPA

direct debits (SDD) and direct

debits based on the billing items

in the banking services system.

Scheduled Periodic Tasks: Scenarios

Account Origination

There are no required scheduled periodic tasks for this scenario. For more information, see


the SAP CRM generic periodic tasks at http://service.sap.com/crm-inst


Leasing

Standard/Housekeeping Jobs

Program Name/Task Recommended Frequency Detailed Description

/1BEA/R_CRMB_DL_JOBS_CREATE

[transaction /BEA/CRMB06]

As required Creation of billing and

posting to Accounting

RSPPFPROCESS As required Certificate of

Acceptance (COA);

inception of the contract

can be performed as a

job

CRM_FS_INTEREST_ADJUSTMENT

[transaction CRM_FS_INTADJ]

As required Floating rate adjustment

both periodic and adhoc

FILA_ACE_PERIODIC_POSTING As required Accruals posting from

Accrual Engine to FI-GL

/LSIERP/TQ_CHECK_INCEPT Daily Termination Quote

Inception

/LSIERP/TQ_PAYLOT_PROCESS Daily after job

/LSIERP/TQ_CHECK_INCEPT

Clearing of open items

linked to contract

terminated with

termination quote

For more information about SAP CRM generic periodic tasks, see:

http://service.sap.com/crm-inst SAP CRM SAP enhancement package 2 for SAP

CRM 7.0 Operate Application Operation Guide SAP CRM 7.0 EHP2.





SAP ERP 6.0 Operations Solution Operations Guide for SAP ERP 6.0.


SAP enhancement packages for SAP ERP 6.0.

Funding Management

SAP Funding Management 2.0 relies on several periodic background tasks that provide or update

master data and transaction data. The following jobs should be scheduled:

Standard/ Housekeeping Jobs

Program Name/Task Recommended Frequency Detailed Description

TXS/R_EVENTS Daily Processes buffered

events

TXS/R_TRIGGER Daily Executes trigger

/TXS/R_BATCH_CALC_NPV Daily Calculates net present

values for all assets

/TXS/R_BATCH_CALC_POOLVOLUME Daily Calculates effective

pool volume for all

funding transactions

/TXS/R_BATCH_CHK_FPGRSV Daily Checks and removes

outdated asset

reservations

/TXS/R_BATCH_FILL_FIX Daily (as required for

reporting)

Prepares reporting

data for “Display

Changes for Assets

with Fixed

Transactions” report

/TXS/R_BATCH_TRA_END As required Automatic closing of

finished funding

transactions




/TXS/R_BATCH_NFY As required (typically daily or

hourly)

Notifes FS-CML about

funded or unfunded

loans assets


http://service.sap.com/instguides SAP Business Suite Applications SAP ERP 6.0

Operations Solution Operations Guide for SAP ERP 6.0.

User Management

SAP delivers user roles for banking services from SAP. You can access these roles with

transaction PFCG.

Scheduled Periodic Tasks: FS Business Partner


Program Name/Task Recommended

Frequency


Program OAFR_PP_RUN_AGENTS

Execute Agent

As required, presumably

hourly or daily (scheduled

execution)

Collects open change pointers

for the specified agent IDs and

sends the corresponding

information messages.

For more information about

this program, its parameters,

and scheduling its execution,

see the program

documentation in the system.

Transaction

OAFT_PP_RUN_AGT_LOG Execute

Agent Application Log

As required Can be used to monitor the

agent runs.

See SAP Help Portal at http://help.sap.com/bankingservices -> Integration & Analytics Information -

> Enterprise Services Documentation.

If you schedule program OAFR_PP_RUN_AGENTS, make sure you send the information

messages in the following recommended order:

http://help.sap.com/bankingservices

1. Business Partner 2. Business Partner Relationship

If you are using information messages to synchronize the operational and analytical business partner and relationship data, it is important that you select and process open change pointers for an appropriate time period (for example, process sequence 1 and 2, as mentioned above one day at a time).

This is because if business partner relationship changes are processed, new business partner versions are created as successors of the current business partner version at the same time. Therefore, if business partner changes are processed for a long time period (such as one month), analytical business partner relationship changes become visible after the most recent business partner change. This might be at the end of the long time period, even if the relationship change happened at the beginning of the long time period. This can lead to a loss of analytical relationship data from a user perspective and a potential risk for subsequent analytical processes.

Use the parameters Creation Date and Creation Time of program OAFR_PP_RUN_AGENTS to define appropriate time periods or selection subsets.

4.6.5 Required Manual Periodic Tasks

This chapter describes all manual tasks that have to be run periodically to ensure that the

application runs smoothly over time. You need to execute manual tasks yourself as opposed to the

scheduled tasks listed above that you can automate by using a task scheduler program. These

tasks may be required at component level and are therefore relevant in every scenario that uses

the component. You can find the mapping for this in the Scenario/Component Matrix chapter

above. Other tasks may be relevant for certain business scenarios only. It is important that you

monitor the execution of these tasks on a regular basis.

Required Manual Periodic Tasks: Bank Analyzer

Manual tasks

Task Tool(s)

Supporti

ng this

Task

Recommend

ed

Frequency


Transaction

/BA1/R0_JOB_ADM_02

Deletes credit exposure runs. This is a

prerequisite for the manual archiving of RDL

results.


Report

/BA1/AL_FW_DELETE_RUN_FR

OM_CLU

Deletes data packages from cluster data

(CVPM)

Transaction

/BA1/R6_DPF_REORG

Deletes data packages from cluster data

(CVPM, DPF)

Transaction /BA1/FW_PROCMON Monitors all current jobs for CVPM

processes. You can also archive the data,

display more information for each job (run

status, detailed log, statistics,

interdependencies of runs), abort corrupt jobs

and restart jobs (if the CVPM process uses

the step controller

/BA1/CL_AL_FW_STEP_CONTROL).

Transaction RSPC Process Chain Maintenance

Report

/BA1/RF0_CHECK_CONFIG

In Analytical Banking, you need to run the

SDL check daily. This report generates an

e-mail if it detects errors when it checks the

SDL.

Transaction

/BA1/HW_PREAGG_RUN

Analyzes the preaggregation runs and

triggers further steps, like error analysis,

continuation or cancellation of runs.

Required Manual Periodic Tasks: Transactional Banking

Manual tasks

Task/Transaction Tool(s)

Supporting

this Task

Recommended

Frequency


BCA_PPOx (2,3) Daily

(minimum)

Postprocessing Office Display/

Change for Account

Management

MCM_PPOx (2,3) Daily

(minimum)

Postprocessing Change/ Display

for Master Contract Management

PLM_PPOx (2,3) Daily

(minimum)

Postprocessing Change/ Display

for Posting Log Management

RFBDELSIM Deletion report for account

settlement simulation data in

table BKK92_SIM

RFICO_CUSTOMIZING_CHECK Checks Customizing for financial

conditions

Use report

RFICO_CUSTOMIZING_CHECK

on a regular basis to check

Customizing of the financial

conditions. If a condition group

type or condition type that has

already been created needs to

be changed, you first need to

check if it has already been used

in production. If it has already

been used, do not change it.

Required Manual Periodic Tasks: FS Business Partner

The tasks below are manual tasks that are only required if data is inconsistent between the sender

and target system, and requires reconciliation.

Program Name/Task Recommended

Frequency


Program: FSBP_SEND_INFO

Select Business Partner and Info About BP Relationship To Be Sent

As required Creates change pointers for the

specified business partners and

business partner relationships

for reconciliation purposes.

Transaction OAFT_PP_RUN_AGENTS Execute Agent

As required (online

execution)

Collects open change pointers

for the specified service

operations and sends the

corresponding reconciliation

messages using program


OAFR_PP_RUN_AGENTS.

Transaction OAFT_PP_RUN_AGT_LOG Execute Agent Application Log

As required Can be used to monitor the

agent runs.

For more information about the above reconciliation program/transaction, its input parameters, and its

execution, see the program/transaction documentation in the system. The reconciliation program

mentioned above creates change pointers for the specified service operation.

5 High Availability

See the standard SAP NetWeaver documentation referenced in chapter 2.2...

Software Change Management

6 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance,

and testing procedures for complex software landscapes and multiple software development

platforms. These functions support your project teams, development teams, and application

support teams.

The goal of Software Change Management is to establish consistent, solution-wide change

management that allows for specific maintenance procedures, global rollouts (including

localizations), and open integration with third-party products.

SAP for Banking uses the standard software change management functions of SAP NetWeaver.

For more information, see the Technical Operations Manual for SAP NetWeaver referenced in

chapter 2.2.

7 Troubleshooting

A productive SAP system needs to be running and stable at all times. When errors occur during

runtime, the cause of the problem should be detected and remedied as soon as possible to ensure

the productive operation of your SAP system.

7.1 Problem Analysis Scenarios for SAP NetWeaver

SAP NetWeaver offers problem analysis scenarios that help you to resolve performance issues.

The problem analysis scenarios referred to in the Problem Analysis Guide describe all the activities

required to analyze a potential problem with SAP NetWeaver and the sequence in which the

activities need to be performed. These scenarios refer to the corresponding usage type.

7.2 Troubleshooting: Bank Analyzer

7.2.1 Sending of General Ledger Documents

If a problem occurs during the sending process of a general ledger document, you can send this

document again. For more information, see General Ledger Connector (FS-BA-AN-GL).

7.2.2 Specific Problem Analysis Scenarios

Some problems may arise from specific processes within banking services from SAP. The following

list provides information about how to analyze and solve these problems.

Communication with Services

To analyze errors in services used by banking services from SAP, you can use the following tools:

Postprocessing Office (PPO)

Error and Conflict Handler (ECH)

The system stores messages that could not be processed completely in the ECH, which is

integrated in the PPO. With this integration you can configure a workflow that forwards errors to an

http://help.sap.com/saphelp_banking70/helpdata/en/43/9601b9debb25e5e10000000a1553f7/frameset.htm

Troubleshooting

administrator to handle the problem.

In the event of a configuration error, a change in the application configuration can be applied and

the message can be reprocessed locally. In the event of data errors, the issue has to be solved in

the sending system because the data errors must be corrected.

You can access these functions from the SAP Easy Access screen by choosing Cross-Application

Components → Postprocessing Office. For more information, see the application help.

Generated Objects

Some Bank Analyzer functions require objects that are generated when you copy clients , while

postprocessing using a client copy or when you save/activate Customizing objects. Automatic

generation takes place without checking data for consistency. To check whether the client was

copied successfully, the data in the source client and target client has to be compared.

If object generation fails, you can manually start reports that create the necessary objects or give

an overview of all generated objects.

Check report for Customizing and the configuration of source data

This check routine identifies inconsistencies in Customizing and activation of generated

objects. In Customizing for Bank Analyzer, choose Source Data Layer → Utilities →

Execute Configuration Checking.

Characteristics and Key Figures

o Check current status of characteristics and correct errors:

In Customizing for Bank Analyzer, choose Basic Settings → Settings for Metadata

→ Characteristics → Characteristic Monitor.

o Check current status of key figures and correct errors:

In Customizing for Bank Analyzer, choose Basic Settings → Settings for Metadata

→ Key Figures → Key Figure Monitor.

Object Transfer Structures (OTS)

You can check the current status of OTS and correct errors. In Customizing for Bank

Analyzer, choose Source Data Layer → Source Data Services→ Access to Source Data

→ Object Transfer Structure (OTS) → Edit OTS for Primary Objects → OTS Monitor.

Derivations

Calculations using Module Editor

Results Data Base (RDB)

For more information, see SAP Note 1147208.

For more about consistency checks in Bank Analyzer, see SAP Note 1147208.

Calculation and Valuation Process Manager (CVPM)

The CVPM is the central infrastructure component in Bank Analyzer as of Bank Analyzer 6.0.

1. Depending on the step controller, there are different reorganization reports:

a.) Step controller /BA1/CL_AL_FW_STEP_CONTROL:

/BA1/AL_FW_DELETE_RUN_FROM_CLU deletes data packages from cluster data

base '/BA1/R6_TAB_CLUS' that are written before and after an aggregation for

example.

b.) Step controller /BA1/CL_AL_FW_STEP_CONTROL_DPF: For all the CVPM

processes that have an aggregation or a repackaging step, use transaction

/BA1/R6_DPF_REORG instead to clear the cluster DB.

2. CVPM Process Monitor (Transaction /BA1/FW_PROCMON): You use transaction

/BA1/FW_PROCMON to monitor all current jobs for CVPM processes. You can also archive

the data, display more information for each job (run status, detailed log, statistics,

interdependencies of runs), abort corrupt jobs and restart jobs (if the CVPM process uses the

step controller /BA1/CL_AL_FW_STEP_CONTROL).

3. Restart function for CVPM processes:

a.) All CVPM processes: If you define that the generation of run groups for a

particular CVPM process is optional, and the sequence defined in Customizing is

a simple sequence that does not contain any aggregation or repackaging steps,

the parallel processing framework (PPF) provides a restart function for failed

packages of the job in question (the status of these runs is set to incomplete). That

is, if the same process is restarted using the same process parameters, only the

failed packages of the incomplete run are processed again.


https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1147208&nlang=E&smpsrv=https%3a%2f%2fwebsmp102%2esap-ag%2ede

Troubleshooting

b.) For CVPM processes using the step controller

/BA1/CL_AL_FW_STEP_CONTROL: You can enter settings in Customizing to

define that these processes can be restarted on a single record basis (which is not

provided with the PPF) at synchronization points (after worklist creation,

before/after aggregation, and after repackaging). In this case, you can use the

process monitor to restart the jobs (transaction /BA1/FW_PROCMON).

Data Processing Framework (DPF):

For processes that are not based on CVPM, but on the DPF (such as limit utilization run or BI

extraction), you use transaction /BA1/R6_DPF_REORG to reorganize the corresponding cluster

database. This means that you should run this transaction even if you have not run any CVPM

reports.

The Module Editor Tool

The after-import and post-processing methods of the Module Editor attempt to generate all active

and inactive module versions in the system. Deactivated versions are not generated. This is a

requirement of the test functions provided by this tool.

If the source client contains inconsistent modules, their activation fails in the target client. You can

use report /BA1/P3_REGENERATE to activate individual modules or start mass activation. If the

activation fails, it might be due to incomplete or inconsistent Customizing. You must analyze these

modules in the source client.

The report has a No Generation flag. If you set this flag, the report simply checks whether the

modules need to be generated.

Problems while Post processing

In the Bank Analyzer component, a cockpit is available with the transaction code /BA1/AT_INIT to

check problems that occur in postprocessing after client copies and transports.

Delivery of Positions and Business Transactions

A reconciliation report checks the consistent delivery of positions and business transactions for

Bank Analyzer. If there are differences, business transactions can be automatically generated to

make corrections and solve discrepancies.

In Customizing for Bank Analyzer, choose Source Data Layer → Source Data Services → Plan/

Actual Comparison.

Data Volume

Bank Analyzer has a full versioning strategy for most of its objects that increases the data volume.

The data volume can be reduced by archiving the data as soon as possible.

For more information, see Archiving Guide SAP Bank Analyzer at http://service.sap.com/instguides

Industry Solutions Industry Solution Guides SAP for Banking Component Guides

Archiving Guide - SAP Bank Analyzer.

Performance

You may need to create a secondary index for performance when processing mass data and for

the scalability of the Bank Analyzer solution. For more information about the configuration process,

see the Best Practice Guide Bank Analyzer – Index Creation (https://websmp205.sap-

ag.de/~sapidb/011000358700001829352008E).

In addition, the Solution Management Guide contains further information about index creation and

primary data sources: SMG – Datasource, Indexfunction at http://service.sap.com/instguides

Industry Solutions Industry Solution Guides SAP for Banking Component Guides SMG

– Datasource, Indexfunction

For more information about performance, in particular about database parameter

settings, see SAP Notes 496904, 494171, and 1166529.

Credit Risk

Customizing

Check report for Customizing and configuration for source data

This check routine identifies inconsistencies in the Customizing of the credit exposure calculation.

In Customizing for Bank Analyzer choose Processes and Methods → Credit Risk → Credit

Exposure → Analyze Credit Exposure Customizing.

Runtime

The detail reporting (transaction: /BA1/R2_CE_07) allows you to analyze online the results of the

credit exposure calculation in detail for a small set of data.







Troubleshooting

Set Free Shared Memories (FICO)

If the shared memory flow error occurs, you have the following two options:

1. Install shared memory (use transaction SHMM → initialize and delete all regions)

2. Increase shared memory

To increase system parameter ABAP shared opjekt size_MB, choose transaction SHMA.

The parameter must be set to the same value on all application servers.

Further Recommendations

To solve problems quickly and efficiently, you should make a note of problems and their solutions

for future reference. We therefore suggest that you put together a troubleshooting section, for

example, as part of the operations handbook that we recommend you create. This collection should

help you when problems reoccur. It should include the cause of the problem as well as the solution

with a step-by-step description.

7.3 Troubleshooting: Fiori Apps

General Tips

Make sure the following is done:

Components, Support Packages, and SAP Notes are installed.

Communication channels are configured.

All relevant OData services and ICF nodes are active.

Roles and authorizations are assigned.

Launchpad and Launchpad Designer

Symptom: Launchpad does not display catalogs.

Symptom: Launchpad does not start.

For general information about troubleshooting launchpad and launchpad designer, see the

documentation on SAP Help Portal at http://help.sap.com/nw74 Application Help UI

Technologies in SAP NetWeaver UI Frameworks based on HTML5, JavaScript and CSS SAP

Fiori Launchpad Troubleshooting .

Symptom: Launchpad designer does not start.

Possible Causes Solution

SAP Gateway is not active. Activate SAP Gateway.


ICF node for launchpad is not active. Configure SAP Fiori launchpad.

Services for launchpad are not active. Configure SAP Fiori launchpad.

User is not authorized to start launchpad.

For example, the error log shows HTTP error 401

Unauthorized.

Assign roles and authorizations.

SAP Gateway not available.

ABAP back end not available.

For example, the error log shows HTTP error 5nn.

SAP Note1797736

Symptom: Launchpad designer does not display catalogs.


User is not authorized to display catalogs. Assign roles and authorizations.

SAP Gateway


SAP Jam Integration

Symptom: HTTP error 400 Bad Request


This error can occur in the case of an incorrect

request.

If you are sure that your request is correct, the

ict/odata_compatible_urls instance profile

parameter may not be set to true. This can cause a

truncation in the request URL.

1. Add the instance profile parameter

ict/odata_compatible_urls=tru

e.

2. Restart the server on which you set the

instance profile parameter.

For information about troubleshooting the SAP Jam integration SAP Help Portal at

http://help.sap.com/nw74 Application Help UI Technologies in SAP NetWeaver Social Media

Integration Information for Administrators Monitoring Collaboration SAPUI5 Components

Search




Troubleshooting

Symptom: Search does not display results.

Symptom: Search field is not displayed.

For more information, see Setup of SAP Fiori Search.

SAP Fiori Apps

SAP Fiori Apps in General

Symptom: A specific app is not displayed in the launchpad.

Symptom: App does not start.

Symptom: App does not display any data.

Symptom: App Launcher does not display dynamic data for app (counter or similar).


User is not authorized to display the app. Assign roles and authorizations.

Check the browser log.

Check the SAP Gateway error log (transaction

/iwfnd/error_log).

Check if the back end is connected.

Symptom: The app displays data of other users or data that is created by another user ID.

Symptom: Error message “Your user is not configured properly. Please contact system

administrator”.


Trusted RFC not configured correctly. Communication Between ABAP Front-End and ABAP

Back-End Server

Fact Sheets

Symptom: Fact Sheet is not displayed.

For more information, see Setup of SAP Fiori Search.

Analytical Apps

Symptom: OData service returns a 500 (Internal Server) error with a message in the response

“Invalidated View”.

Symptom: Activation error while importing delivery units.


http://help.sap.com/fiori_bs2013/helpdata/en/12/af5252b10d5a64e10000000a423f68/frameset.htm

http://help.sap.com/fiori_bs2013/helpdata/en/0b/9e3e536f6a0050e10000000a44176d/frameset.htm

http://help.sap.com/fiori_bs2013/helpdata/en/0b/9e3e536f6a0050e10000000a44176d/frameset.htm

http://help.sap.com/fiori_bs2013/helpdata/en/12/af5252b10d5a64e10000000a423f68/frameset.htm


Support Desk Management

8 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support

organization that seamlessly integrates your end users, internal support employees, partners, and

SAP Active Global Support specialists with an efficient problem resolution procedure.

For support desk management, you need the methodology, management procedures, and tools

infrastructure to run your internal support organization efficiently.

8.1 Remote Support Setup

SAP for Banking does not offer specific support tools. The functions provided by SAP NetWeaver

should be used for remote support.

The central tool used by SAP remote support is SAP Solution Manager. For more

information about monitoring SAP systems using SAP Solution Manager, see SAP

Help Portal at http://help.sap.com → Documentation → SAP Solution

Manager → Solution Monitoring.

8.2 Problem Message Handover

The following application components (including their subcomponents) are relevant for SAP for

Banking and should be used to report problems via CSS:

FS-BA

FS-AM

FS-BP

FS-CMS

FS-MCM


9 Appendix

The following table contains links to information relating to the Application Operations Guide:

Content Quick Link to the SAP Service Marketplace

(service.sap.com)

Master Guide, Installation Guide and

Upgrade Guide

instguides Industry Solutions Industry

Solution Guides SAP for Banking

Related SAP Notes notes

Released Platforms platforms

Network Security securityguide

network

SAP Solution Manager solutionmanager

Appendix

Typographic Conventions

Type Style Description

Example

Text

Words or characters quoted from the screen. These include

field names, screen titles, pushbuttons labels, menu names,

menu paths, and menu options.

Cross-references to other documentation

Example

text

Emphasized words or phrases in body text, graphic titles,

and table titles

EXAMPLE

TEXT

Technical names of system objects. These include report

names, program names, transaction codes, table names,

and key concepts of a programming language when they are

surrounded by body text, for example, SELECT and

INCLUDE.

Example

text

Output on the screen. This includes file and directory names

and their paths, messages, names of variables and

parameters, source text, and names of installation, upgrade

and database tools.

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. Angle brackets indicate that you replace

these words and characters with appropriate entries to make

entries in the system.

EXAMPLE

TEXT

Keys on the keyboard, for example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types

of information at a glance. For more information, see Help on Help General Information

Classes and Information Classes for Business Information Warehouse on the first page of

any version of SAP Library.

Appendix

© 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. All other product and service names mentioned are the

trademarks of their respective companies. Please see http://www.sap.com/corporate-

en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark