Sap retail smd performance data for mass activities

BP_SMD_Performance_Data_for_Mass_Activities_V30.doc – 11.06.2009

Best Practice

SMD Performance Data for MassActivities

Dietmar-Hopp-Allee 16D-69190 Walldorf

CS STATUS

customer publishedDATE VERSION

June 11 2009 3.0

SOLUTION MANAGEMENT PHASE SAP SOLUTION

Operations & Optimization SAP for Banking

TOPIC AREA SOLUTION MANAGER AREA

SAP Application Management Root Cause Analysis

Best PracticeSMD Performance Data for Mass Activities

© 2009 SAP AG page 2/22

Table of Contents1 Management Summary 3

1.1 Goal of Using the SMD Performance Data for Mass Activities 31.2 Alternative Practices 41.3 Staff and Skills Requirements 41.4 System Requirements 41.5 Duration and Timing 41.6 Case Study or Sample Scenario 4

2 Best Practice 62.1 Design 62.2 Delivered BI Queries 10

2.2.1 Reporting - Top 20 jobs in your Banking Solution Landscape 102.2.2 Reporting for Deposit Management, Banking Services and Payment Engine 132.2.3 Reporting for Bank Analyzer Products 16

2.3 Procedure – Setup 192.3.1 Setup Procedure in Solution Manager 19

3 Further Information 203.1 Troubleshooting 203.2 Background Information and References 20

Index of Figures 21


© 2009 SAP AG page 3/22

1 Management Summary

1.1 Goal of Using the SMD Performance Data for Mass Activities

Optimized performance of core business processes is the key requirement for any successful operation in abanking environment.

The IT department of a bank usually faces different challenges: Complex solution landscape, including modifications, own developments, 3rd party software Legal requirements (limited time window to process data for reporting) Mass data processing Workload is not equally distributed between days/peak times (e.g. end of month) High standards on system stability and data security Difficulties to make exceptions visible and to provide sufficient tools for Root Cause Analysis

In a typical Banking Services project, the system scenario consists of various SAP solutions like BankingServices to handle loans, deposits and other banking specific products as part of time critical mass data runs,FI-CAX (ERP) to manage open items, BI to store the results and eventually analytical solutions like BankAnalyzer. Normally the end-of-day, month-end, quarter-end and year-end processes are the peak time of anentire banking scenario (distributed over a complex system landscape), where high data volumes have to beprocessed within a tight time frame. As an example, large banks may need to run settlement functionality onmillions of accounts during the quarter-end processing. The requirement on the hardware is to processincreasing workload during the peak time within given time frame.

To help the IT department of a bank to monitor their critical jobs and to start a Root Cause Analysis if jobscannot meet the expected time frame the Solution Manager Diagnostics (SMD) Performance Data for MassActivities functionality is offered as part of SAP Solution Manager.

The SMD Performance Data for Mass Activities functionality identifies most critical processes, in terms ofcreated workload (hardware usage) and run times. By optimizing the most critical processes in customer’ssolution landscape you can reduce the workload on the banking system, which will at the end result inreduced hardware requirements.

The goal of the functionality is to identify long running batch jobs or jobs creating high workload on theBanking system during times where the hardware resources should be reserved mission critical corebusiness processes.

The SMD Performance Data for Mass Activities functionality has the following key features: Central view on performance key figures for different processes across Banking applications. Workload Analysis of mass processes in SAP Solution Manager to measure the performance of the

processes in detail. It offers a set of performance relevant counters like throughput of objects, total duration, estimated

remaining run time, estimated total runtime, cancelled jobs and hardware utilization. It can raise alerts for different key figures to prevent critical situations. It provides integrated BI reporting capabilities. All relevant performance figures can be extracted into

InfoCubes for BI queries like trend analysis or throughput.


© 2009 SAP AG page 4/22

Additionally, the tool provides the possibility to conduct historical performance analysis data for the massreports of banking applications.

1.2 Alternative Practices

Besides the SMD Performance Data for Mass Activities functionality our customers can also use theBusiness Process Monitoring functionality, but this means that for all relevant processes the monitoring has tobe setup in advance. If a specific business process, which is not set up in BPMon causes high workload onthe system the BPMon will not collect the relevant statistical information for a detailed root cause analysis.

1.3 Staff and Skills Requirements

The Workload Analysis of the SMD Performance Data for Mass Activities can be used at our customers byapplication support and technical support teams, who are responsible for the operations and monitoring of theSAP Banking Solution. For the setup a SAP Solution Manager expert to install the SMD is required.

1.4 System Requirements

Following system requirements should be met in SAP Solution Manager and satellite systems:

Solution Manager

1. Solution Manager 7.00 with EhP2 / SP 21.2. Activate the BI 7.05 Content with SP01 and set-up BI reporting.3. Solution Manager Diagnostics has to be activated on EhP24. For an upgrade to EhP2 please follow the configuration and update guides on

https://websmp102.sap-ag.de/instguides

Satellit Banking Systems

1. ST-A/PI Release M.2. Released for the following Banking Applications TRBK 3.0 und 4.0 FSAPPL 100 / 200 / 300, Payment Engine 300. Bank Analyzer 4.2 / 5.0

1.5 Duration and Timing

If the SAP Solution Manager Diagnostics tool is implemented, the following steps must be done: Activate the BI Content (SMD Performance Data for Mass Activities, relevant BI queries and web

templates) on the SAP Solution Manager system. Activate the data extractor coding (ST-A/PI Release M) on satellite systems.

The estimated time for the above-mentioned activities is approximately one day.

1.6 Case Study or Sample Scenario

The following scenarios can be seen as use case for the SMD performance data for mass activities:

https://websmp102.sap-ag.de/instguides


© 2009 SAP AG page 5/22

Scenario 1

A customer wants to gather statistical information about the longest running batch jobs in its banking solutionlandscape.

Scenario 2

A customer wants to analyze the collected data (performance statistics) for a certain banking application andtime critical banking processes for a trend analysis based on the historical information.

Scenario 3

A customer wants to analyze statistical relationships between different counters (application specific keyfigures) and technical key figures like duration, throughput and CPU utilization.

Scenario 4

A customer wants to execute a Root Cause Analysis, because time critical banking processes took longerthan expected during the end of day processing.


© 2009 SAP AG page 6/22

2 Best Practice

2.1 Design

By using the standard functionality offered by the SAP Solution Manager Diagnostics infrastructure, statisticaldata related to parallel batch job processing in different satellite systems will be collected and extracted in theBI of SAP Solution Manager in a special designed InfoCube SMD Performance Data for Mass Activities.

This InfoCube will be delivered with the BI content of SAP Solution Manager.

This data collector will be delivered with the software package ST-A/PI as application specific data collector.

The Figure 2-1 shows the most important elements of the described architecture.

Figure 1 Concept of SMD Performance Data for Mass Activities with SAP Solution Manager

The Extractor Framework (EFWK) collects data from different data sources – in general on an hourly basis;however, some data is collected on longer time scales – and performs an enrichment of the collected databased on the data maintained in the landscape model (transaction SMSY).


© 2009 SAP AG page 7/22

Figure 2: Architecture of SMD Performance Data for Mass Activities with SAP Solution Manager

The extractors are started in dialog work processes by a resource manager which is responsible for thecontrol of the resource consumption of all periodic or ad hoc data retrieval processes in the SAP SolutionManager. The primary goal of the resource manager is to start extractors observing configurable constraintson the consumed resources both in the managed and the managing system. The resource manager itself isexecuted once a minute as a background process.

The critical resource is the number of the dialog work processes that are available for the ExtractorFramework. For each extractor started, the resource manager will increase the resource counter of both thelocal resource pool (dialog work processes) and the remote resource pool (the RFC destination to themanaged system), unless the resource cap has been exceeded.

The InfoCube SMD Performance Data for Mass Activities is the data source for BI queries and web templatesfor the managed systems like Bank Analyzer, Deposit Management, Banking Services and Payment Engine.

The Figure 2-4 shows the important dimensions of this InfoCube.


© 2009 SAP AG page 8/22

Figure 3: Dimensions of the InfoCube SMD Performance Data for Mass Activities

The dimension Client contains the characteristic Client.

The dimension Job Parameters includes the following characteristics: Job variant (job variant for a banking job) Parallelization variant (job parallelization variant for a FI-CA job). Application type (application type). Counter ID (counter type).

The dimension Run ID has one characteristic external run ID (external identifier of a job).

The dimension Job Date comprises the important job characteristics:


© 2009 SAP AG page 9/22

Start date (start date of a job) End date (end date of a job) Posting date (business date of a run)

The dimension Job Time includes the time characteristics of jobs as well: Start time (start time of a job). End time (end time of a job).

The dimension Job Information has the following characteristics: Job name (name of a job) Job start user (start user) Job status (status of a job)

The dimension Banking Run contains the characteristics related to Bank Analyzerruns: Logical unit (legal entity or bank posting area) Run type (BASEL II run types: standard approach, IRB-approach, etc.) Step sequence” (BASEL II steps: bundling and calculation)

The figure 2-5 shows key figures of the described InfoCube.

Figure 4:Key figures of the InfoCube SMD Performance Data for Mass Activities

The following key figures are developed to collect statistics related to banking and FI-CAX runs: Average duration per interval (FI-CAX: average duration of processing of one package). CPU utilization (Application Servers) [%]) Canceled jobs (number of canceled jobs) Completed jobs (number of completed jobs) Number of jobs (number of parallel jobs) CPU utilization (Database Servers [%]) Duration (duration of a job) Intervals (total number of packages)


© 2009 SAP AG page 10/22

Maximum duration per interval (FI-CAX: maximum duration per package) Minimum duration per interval (FI-CAX: minimum duration per package) Processed intervals (FI-CAX: number of processed packages) Throughput (throughput of a job).

2.2 Delivered BI Queries

The delivered BI queries and web templates can be divided into three parts: Top 20 jobs reporting: identification of long running batch jobs in customer systems. Reporting for Deposit Management, Banking Services and Payment Engine. Reporting for Bank Analyzer.

Besides, the customer can also create own BI queries to gather additional information out of the InfoCube.

All developed web templates can be integrated in SAP Solution Manager Work Center (Figure 2-4).

Figure 5: SAP Solution Manager Work Center: dashboard reporting

2.2.1 Reporting - Top 20 jobs in your Banking Solution Landscape

The web template Top Jobs Statistics Overview presents the top twenty long running batch jobs in allconnected satellite systems in your SAP Banking solution landscape (Figure 2-5).


© 2009 SAP AG page 11/22

Figure 6: Top job statistics overview

You can get more detail information by using the drill down functionalities of the Parameters selectionnavigation block (Figure 2-6).


© 2009 SAP AG page 12/22

Figure 7: Top job statistics overview: drill down functionalities

The described web template is based on the BI query Activity Monitor: Top Job Statistics.

After the identification of long running batch jobs you can drill down to the detailed analysis in the belongingsatellite systems.

All web templates and BI queries are designed to get the following statistics:Job Statistics Per System & Posting (Start) DateGraphic View (Counters, Duration, Throughput)Application & Counters Statistics

Counters & CPU Utilization Statistics

The time interval for the Job Statistics per System & Posting Date and Job Statistics per System & Start Datereports is defined (default value) for one day (Figure 2-7).


© 2009 SAP AG page 13/22

Figure 8: Time parameters for job statistics reporting

The default value of the time interval for the posting (start) date can be changed by clicking on Select FilterValue button on the right side of the navigation block Parameters Selection (Figure 2-8).

Figure 9: Navigation block: changing of the time interval

2.2.2 Reporting for Deposit Management, Banking Services and Payment Engine

2.2.2.1 Web Template DM: Job Statistics per System & Posting Date

The web template DM: Job Statistics per System & Posting Date is designed to allow a root cause analysisand trend analysis of specific batch processes.

The example of this report is presented below:


© 2009 SAP AG page 14/22

Figure 10: DM: Statistics per System & Posting Date

The web template DM: Job Statistics per System & Posting Date is based on the designed BI query ActivityMonitor: DM Statistics per System & Posting Date.

2.2.2.2 Web Template DM: Graphic View (Counters, Duration, Throughput)

The web template DM: Graphic View (Counters, Duration, Throughput) is developed to analyze statisticalrelationships between the number of selected (processed) objects and key parameters duration andthroughput.

The report example shows statistical relationships for the application type Settlement Account and counter IDAccounts Processed Successfully (Figure 2-10):


© 2009 SAP AG page 15/22

Figure 11: DM: Graphic View (Counters, Duration, Throughput)

The web template DM: Graphic View (Counters, Duration, Throughput) is based on four BI queries:Activity Monitor: DM Statistics (Graphic Views)Activity Monitor: DM Statistics (Posting Date & Counters)Activity Monitor: DM Statistics (Posting Date & Duration)Activity Monitor: DM Statistics (Posting Date & Throughput)

2.2.2.3 Web Template DM: Application & Counters Statistics

The web template DM: Application & Counters Statistics is designed to analyze counters statistics.


© 2009 SAP AG page 16/22

The report example is shown below:

Figure 12: DM: Application & Counters Statistics

The web template DM: Application & Counters Statistics is based on the BI query Activity Monitor: DMStatistics (Application & Counters).

2.2.3 Reporting for Bank Analyzer Products

2.2.3.1 Bank Analyzer: Job Statistics per System & Start Date

The web template Bank Analyzer: Job Statistics per System & Start Date is designed to allow a root causeanalysis of Bank Analyzer specific batch processes like Key Date Valuation.

The example of this report is shown below:

Figure 13: Bank Analyzer: Application & Counters Statistics


© 2009 SAP AG page 17/22

The web template Bank Analyzer: Job Statistics per System & Start Date is based on the BI query ActivityMonitor: BA AFI Statistics per System & Start Date.

The web template BASEL II: Job Statistics per System & Start Date serves to get statistical data of the batchjob processing for credit analyzer (BASEL II).

The mentioned web template is based on the BI query Activity Monitor: BA CRE Statistics per System & StartDate.

2.2.3.2 Bank Analyzer: Graphic View (Counters, Duration, Throughput)

The web template Bank Analyzer: Graphic View (Counters, Duration, Throughput) is developed to analyzestatistical relationships between the number of selected (processed) objects and key parameters duration andthroughput (balance analyzer).

The report example shows statistical relationships for the application type balance analyzer: key datevaluation and for the counter id successful financial positions (Figure 2-14):

Figure 14: Bank Analyzer: Graphic View (Counters, Duration, Throughput)


© 2009 SAP AG page 18/22

The web template Bank Analyzer: Graphic View (Counters, Duration, Throughput) is based on four BIqueries:

Activity Monitor: BA AFI Statistics (Graphic Views).Activity Monitor: BA AFI Statistics (Start Date & Counters)Activity Monitor: BA AFI Statistics (Start Date & Duration).Activity Monitor: BA AFI Statistics (Start Date & Throughput).

The web template BASEL II: Graphic View (Counters, Duration, Throughput) is created to analyze thementioned statistical relationships for Credit Analyzer (BASEL II).

This web template is based on four BI queries:Activity Monitor: BA CRE Statistics (Graphic Views)Activity Monitor: BA CRE Statistics (Start Date & Counters)Activity Monitor: BA CRE Statistics (Start Date & Duration)Activity Monitor: BA CRE Statistics (Start Date & Throughput)

2.2.3.3 Bank Analyzer: Application & Counters Statistics

The web template Bank Analyzer: Application & Counters Statistics is designed to analyze counters statistics(balance analyzer).

The report example is presented below:

Figure 15: Bank Analyzer: Application & Counters Statistics

The web template Bank Analyzer: Application & Counters Statistics is based on the BI query Activity Monitor:BA AFI Statistics (Application & Counters).


© 2009 SAP AG page 19/22

The web template BASEL II: Application & Counters Statistics is created to analyze counters statistics duringbatch job processing for credit analyzer (BASEL II).

The mentioned web template is based on the BI query Activity Monitor: BA CRE Statistics (Application &Counters).

2.3 Procedure – Setup

2.3.1 Setup Procedure in Solution Manager

You should activate relevant elements of the BI content in SAP Solution Manager using the transactionRSA1.Following objects must be activated: The InfoCube“SMD Performance Data for Mass Activities The described BI queries The described web templates


© 2009 SAP AG page 20/22

3 Further Information

3.1 Troubleshooting

3.2 Background Information and References

To find more information regarding Solution Manager and BI reporting, please.http://service.sap.com/solutionmanager

SAP Training “BW305 BI-Enterprise Reporting Part I” SAP Training “BW306 BI-Enterprise Reporting Part II”

http://service.sap.com/solutionmanager


© 2009 SAP AG page 21/22

Index of FiguresFigure 1 Concept of SMD Performance Data for Mass Activities with SAP Solution Manager 6Figure 2: Architecture of SMD Performance Data for Mass Activities with SAP Solution Manager 7Figure 3: Dimensions of the InfoCube “SMD Performance Data for Mass Activities” 8Figure 4:Key figures of the InfoCube SMD Performance Data for Mass Activities 9Figure 5: SAP Solution Manager Work Center: dashboard reporting 10Figure 6: Top job statistics overview 11Figure 7: Top job statistics overview: drill down functionalities 12Figure 8: Time parameters for job statistics reporting 13Figure 9: Navigation block: changing of the time interval 13Figure 10: DM: Statistics per System & Posting Date 14Figure 11: DM: Graphic View (Counters, Duration, Throughput) 15Figure 12: DM: Application & Counters Statistics 16Figure 13: Bank Analyzer: Application & Counters Statistics 16Figure 14: Bank Analyzer: Graphic View (Counters, Duration, Throughput) 17Figure 15: Bank Analyzer: Application & Counters Statistics 18


© 2009 SAP AG page 22/22

© Copyright 2009 SAP AG. All Rights ReservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of CitrixSystems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Allother product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any formor for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP toany particular course of business, product strategy, and/or development. Please note that this document is subject to change and maybe changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you mayaccess through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.

Documents

Sap retail smd performance data for mass activities