Sap Bankingh

RAMBABU.NAMAMULAWWW.STRIVEERP.COM

E-MAIL:[email protected]

SAP BANKING CONSULTANT

Banking Services

Best Practice

Exception Handling in SAP Banking Services

Table of Contents

Table of Contents2

1Management Summary3

1.1Goal of Using This Service3

1.2Staff and Skills Requirements3

1.3System Requirements4

1.4Duration and Timing4

1.5Case Study or Sample Scenario4

2Best Practice5

2.1Preliminary Tasks5

2.2Design5

2.2.1Application log monitor7

2.2.2 User exit Application log data collector7

2.2.3 Data collector for exception handling7

2.3Procedure Setup8

2.3.1 Setup procedure in satellite system8

2.3.2 Setup procedure in SAP Solution Manager9

2.4Procedure Operation and Handling28

2.4.1 SAP Solution Manager work centers28

2.4.2General application logs29

2.4.3 Application Log user exit (account number)30

2.4.4 Exception handling (PPO, PCO, CpD)33

3Further Information36

3.1Background Information and References36

Index of Figures37

Index of Figures38

2009 SAP AGpage 2/39

Best Practice


1Management Summary

1.1 Goal of Using This Service

For banking customers using SAP core banking products like Deposit Management (DM), Loans Management based on Banking Services or Transactional Banking (TRBK) products, business exceptions (e. g. account cannot be settled, payment cannot be posted) are registered in different areas of the application: Postprocessing Office (PPO), Posting Control Office (PCO), suspense accounts (CpD) and application logs. If error occurs during the data processing (e. g. an account cannot be settled because it is locked), the error with the relevant data for processing events are combined into one postprocessing order and sent to the PPO for further activities. If a payment order or item has broken the predefined posting control rules, it will be sent to PCO for postprocessing. Payment items that cannot be posted to any bank account is posted to CpD account until the reason of the failure has been figured out. Furthermore, application errors are also recorded in the application log (SLG1).

The document provides an idea how banking customers can make use of the SAP Solution Manager Business Process Monitoring to help them increase efficiency in the production support dealing with a couple of different business exceptions during the daily operation of a banking system. Every exception on a banking environment is very important and need to be handled either manually or by automated procedures to guarantee a correct processing and to increase the end user (bank and banks customer) satisfaction.

So in general for banks using the SAP core banking solution, the following areas should be regularly monitored to guarantee the stability and correctness from an application point of view:Postprocessing Office Posting Control Office Suspense accounts Application log

Beyond these exception handling functionalities, SAP Solution Manager offers a central Business Process Monitoring functionality (BPMon) to monitor all the connected SAP systems. In BPMon we offer banking-specific application collectors to gather exceptions from the connected banking sources. The collector is able to send alerts if unexpected high volume of post-processing orders or payment items are created in PPO, PCO, or CpD, and can also list each postprocessing order or payment item in SAP Solution Manager which is relevant for manual postprocessing. It enables the processor to directly jump into the corresponding transactions in the connected banking solution.

1.2 Staff and Skills Requirements

To implement the monitoring capabilities for exceptions, specific skills and roles are required from the bank. The following tasks should be assigned to the corresponding teams.

Verify the software requirements in different systems within the monitoring landscape SAP basis team Maintain system landscape within SAP Solution Manager SAP basis team

Identify banking application-specific exceptions Application team

Set up a monitoring solution and implement the identified exceptions and alerting mechanism in the monitoring solution Production support team

Monitor the solution and handle the exceptions Production support team


Best Practice


1.3 System Requirements

Following system requirements are required in SAP Solution Manager and the relevant satellite systems.

SAP Solution Manager

SAP Solution Manager 7.0 EHP1 (Enhanced Package 1).

Satellite systems

ST-A/PI release M

Latest ST-PI release

If satellite system has SAP product Banking Services in place, its release should be at least FSAPPL 100. If satellite system has SAP product Transactional Banking in place, its release should be at least TRBK 3.0.

1.4 Duration and Timing

For an initial implementation of BPMon for banking exceptions, the following duration and effort estimation can be given as general guidelines:

1 week to identify exceptions, set up monitoring

1 week for fine-tuning, BI reporting, knowledge transfer, training

Note: Depending on the complexity of the customer requirements, the implementation might take less or more time.

1.5 Case Study or Sample Scenario

Below is a short description of a customer use case explaining how the bank solves the exceptions in PCO currently and how it can benefit from the monitoring of exceptions.

Without the exception handling tool described in this paper, the responsible person from the banks functional support or exception handling team needs to log on to different satellite system and starts different transactions to analyze the problems of the payment process and starts performing the postprocessing tasks. For example, to monitor the payment items in PCO, they need to log on to the Banking Services system every 30 minutes to check if there are any new payment orders in PCO. If there are new orders for post-processing, they bank needs to find the receivers account number for each order and check the bank account to find out why the payments cannot be posted. Identifying the receivers bank account is a time-consuming process, they need to go through different tables to get the relevant account number.

With the help of SAPs Exception Handling Data Collector, they will get notification per e-mail or SMS if there are new orders in PCO. After they receive the notification, they can open the alert list in SAP Solution Manager. Each PCO order will be listed with necessary information like account number or order ID to help the production support team to speed up the Root Cause Analysis process. They can click on the preconfigured analysis buttons to jump into Banking Services to display the account or process the order. After the order is processed, they can confirm the order and it will disappear from the alert list. The alerting in

SAP Solution Manager gives the colleague from bank a better overview of what needs to be processed, and exposes more information to them to help them work more efficiently.


Best Practice


2Best Practice

2.1 Preliminary Tasks

Ensure that you perform the following preliminary tasks or checks in the system before you start the

implementation:

Check the software requirements in SAP Solution Manager. Check the software requirements in the satellite systems.

SAP Solution Manager

SAP Solution Manager 7.0 with BPMon should be implemented.

Check SAP Note 521820: Availability of Business Process Monitoring for software requirements.

Check SAP Note 784752: BPMon in SAP Solution Manager Prerequisites for technical details.

Implement ST-A/PI release M and run report RTCCTOOL in SE38 to activate the data collector and clear all the red alerts.

2.2 Design

In a typical monitoring architecture, SAP Solution Manager should be linked to various satellite systems. In this case, SAP Solution Manager is the central system where all relevant monitoring information is stored and displayed. It should be used as the central tool to monitor all satellite systems where critical business processes or jobs are running, e. g. SAP Deposit Management. For different monitoring purposes, there are different data collectors running in satellite systems. They collect information periodically and send it back toSAP Solution Manager. This architecture gives a clear overview of the whole solution landscape. The monitoring team can easily monitor their solution, which spreads in different monitored systems. In addition to the already mentioned functionality, the monitoring on SAP Solution Manager also allows the usage of the central BPM framework to create alerts or incidents if certain thresholds for key figures reached. The alerts can be sent to the recipients through different communication channels, e. g. e-mail, SMS, and fax. By receiving the alert message, the responsible is aware of the alert and can deliver quick reaction to deal with the alert. It is also possible to jump from SAP Solution Manager to different satellite system to do a detail analysis of the received alert and make processing decision. The collected statistics and alerts are stored centrally in SAP Solution Manager BI InfoCube for trend analysis. Based on the data in InfoCube, queries and dashboards can be created for reporting. The reporting can be Excel-based or Web-based.

Figure 1 shows the overview of functionalities of Business Process Monitoring in SAP Solution Manager.


Best Practice


Figure 1: Overview Business Process Monitoring in SAP Solution Manager

Exception handling for Banking System is designed based on the SAP Solution Manager BPMon infrastruc-ture described above. Figure 2 shows a typical system landscape of a banking solution with two scenarios: loans and deposit management. In the Banking Services and FI-CAx systems exceptions will come up during the execution of different business processes. In Banking Services, exceptions are registered in CpD, PPO, PCO and the application log. In FI-CAx, exceptions can be found in the application log or in PPO.

Figure 2: Architecture of exception handling with SAP Solution Manager


Best Practice


Use the standard functionality offered by the BPM infrastructure to monitor application logs in different connected satellite systems. With the banking-specific data collector, you can catch exceptions in PPO, PCO and CpD.

To cover special customer requirements, like monitoring specific bank accounts for certain problem classes from the application log, you can use a user exit. Additionally, the solutions Banking Services or Transactional Banking offer a special data collector to monitor postprocessing orders, erroneous payment orders and payment items in PCO and CpD. The data collector is provided as application-specific monitor with software package ST-A/PI release M.

In summary, in order to collect the exceptions, you need to monitor application log, PPO, PCO and CpD. The next section will explain the purpose and the use case for each monitoring type.

2.2.1 Application log monitor

Application errors that occur during the processing of the data (e. g. accounts, documents) are written to the application log. The application log is a SAP standard functionality. In a normal bank production environ-ment, the application log can contain a huge amount of log entries. The bank support team should check each application error recorded in the application log. It is time-consuming to find and check all the application error messages in the application log.

BPMon provides an application log monitor. With this monitor you can define search patterns and, based on the search pattern, monitor the number of log messages inside a log entry and trigger alerts if the number of messages is too high. Furthermore, it can raise an alert if a specific log message (within the log entry) occurs. See section 2.3.2.12 to find out how to configure the application log monitor.

2.2.2 User exit Application log data collector

Additionally, it is possible to develop your own monitor through user exit and use it in BPMon. You can use the Application Log Data Collector user exit for example if you want to monitor a specific account and be alerted if the log message linked to this account with a critical problem class occurs. For that, you need to specify the account number that you want to monitor and the critical problem class to make it work. Section 2.3.2.13 explains how you can use the user exit.

You can find this user exit in SAP Note 1267677.

2.2.3 Data collector for exception handling

In addition to the application log monitor, SAP offers a banking-specific monitor for exception handling. It monitors the postprocessing orders stored in PPO, the payment items in the PCO and in CpD (suspense) accounts. As each order or payment item in PPO, PCO or CpD has to be processed, you can raise alerts based on the residence time (difference between time of creation and current time). For payments in PCO and CpD, the amount of the payments can be critical as well. You can raise alerts if the critical amount is reached. To get a better overview of orders that require postprocessing in PPO, PCO or CpD, you can use the relevant work list in SAP Solution Manager. From the work list, the production support team can jump into the banking system to do the postprocessing or an analysis. If any new item or a specific number of items appear in the work list, alerts can be raised to get the attention from the production support team.


Best Practice


The collector can be configured in a flexible manner based on bank-specific information (e. g. bank posting area, bank key, CpD accounts). Section 2.3.2.11 describes how to configure this collector.

2.3 Procedure Setup

This section describes the setup procedures in satellite system and SAP Solution Manager.

2.3.1 Setup procedure in satellite system

The section describes the setup procedure that is required in the satellite system. Execute it prior to the configuration in SAP Solution Manager. The procedures 2.3.1.1 and 2.3.1.2 are only relevant for Banking Services or Transactional Banking systems. The procedure 2.3.1.3 is relevant for all monitored systems.

2.3.1.1 Starting setup /SSA/CM2

In the monitored system (Banking Service or Transactional Banking), run report /SSA/CM2 in SE38. Figure 3 shows the starting screen of the /SSA/CM2. Choose Maintain CpD Customizing and click the Execute button .

Figure 3: Starting screen of /SSA/CM2 in satellite system

2.3.1.2 Define group of CpD accounts

After the click on the Execution button, a second screen as displayed in Figure 4 appears where you can configure and maintain the assignment of CpD accounts to suspense account groups.

Figure 4: Define CpD account groups


Best Practice


Click button Click button Click button Click button

to create a new assignment at the end of the list. to insert a new assignment at cursor.

to delete a selected assignment. to save the assignments.

The advantage of assigning CpD accounts into groups is the flexibility to assign alerts from CpD account groups to the person or the team who is responsible for it, and reduce the number of collector instances maintained in SAP Solution Manager.

2.3.1.3 Finalize ST-A/PI in satellite system

After installing the ST-A/PI package, start the program RTCCTOOL in each satellite system with transaction SE38 to finalize the installation process. All red alerts displayed in the tool have to be fixed manually according to the instruction. Figure 5 shows the correct result from RTCCTOOL. Please also follow SAP Note 69455.

Figure 5: RTCCTOOL

2.3.2 Setup procedure in SAP Solution Manager

In this section, the setup procedure SAP Solution Manager is explained. Follow the steps in the same sequence as described below.

2.3.2.1 Required user and RFC connection in SAP Solution Manager

Create user CSMREG in SAP Solution Manager and configure it according to SAP Note 455356. Then create the local RFC connection BPM_LOCAL_ in SAP Solution Manager, with communication user CSMREG.

Please check the other preconditions according to SAP Note 784752.


Best Practice


2.3.2.2 Create a new solution in SAP Solution Manager

First of all, create a new solution in SAP Solution Manage by starting transaction DSWP. In the solution

overview (Figure 6), select the Create button to create a new solution.

Figure 6: Solution overview

2.3.2.3 Maintain solution landscape in SAP Solution Manager

Maintain the solution landscape in the newly created solution. The path is Solution Landscape Solution Landscape Maintenance.

First, assign different logical components to this solution. A logical component is a group of SAP instances that represent the same product in the transport landscape. You can create and maintain the logical component in transaction SMSY or in path Solution Landscape Solution Landscape Maintenance.

Figure 7: Maintain solution landscape

After assigning the logical components, decide on the Leading Role of the Solution. The leading role decides which SAP systems in the transport landscape should be monitored. In Figure 7, the leading role is set to production system, so the systems specified under the Production System column are to be monitored. The leading role can only be defined once; when the solution is saved, it cannot be modified anymore.


Best Practice


2.3.2.4 Maintain contacts

In the screen shown in Figure 8, click the button.

Figure 8: Solution landscape maintenance

In Figure 9, click button or to create a new entry. The added user should be already defined in transaction SU01. Double-click on the User field to select a user from SU01. The user maintained here will be assigned later to different monitoring organizations. The user that shall be the alert sender must have a valid e-mail address.

Figure 9: Maintain contacts in solution


Best Practice


2.3.2.5 Create scenario

A scenario or business process can be created newly or import from SAP repository or existing solutions.

Figure 10: Maintain scenario

As shown in Figure 10, two scenarios are created. After configuring, switch the status from Planned to

Production, otherwise you cannot activate the scenario later if it is in status Planned.

2.3.2.6 Create business processes

After creating the business scenario, business processes can be created under business scenario. In Figure 11, the scenario has one business process Check Exceptions. Its status is set to Production and the availability is 7 days a week and 24 hours per day.

Figure 11: Create business process

The possible process availability is

5x16 h 5x8 h 5x24 h 7x24 h

Choose availability according to the business requirements.


Best Practice


2.3.2.7 Create business process steps

After creating an empty business process, we can define different business process steps inside the business process. To create a new step, a logical component and processing type need to be specified.

Figure 12: Create business processes steps

Figure 12 shows the business process steps within the business process Check Exceptions. They are maintained under the tab Structure. Column Step Name specifies the name of the process step. It is a text that describes the business step. Column Logical Component specifies the logical component that this step is running. It can be chosen from the logical components assigned to this solution. Column Process Type specifies the run type of this business step in the logical component. These can be Dialog, Background andDialog/Background.

You can sort the process steps by clicking the Up and Down buttons .

2.3.2.8 Start business process monitoring setup

After creating the business process steps and maintaining the contacts, go back to the solution screen shown in Figure 13. Go to Operations Setup Solution Monitoring Business Process Monitoring and click

Setup Business Process Monitoring to start configuring monitoring objects in the business process steps.

Figure 13: Set up business process monitoring


Best Practice


2.3.2.9 Maintain solution support organization

Figure 14: Create support teams

In the column Name, choose the user that you want to add to the team. The user is defined in transaction

code SU01.

Figure 15: Assign user to support organization


Best Practice


In the second tab, Monitoring Roles, assign the role of the team.

Figure 16: Select monitoring roles

2.3.2.10 Activate business processes

After having configured the support organization, activate the business processes and steps so that different monitors can be assigned to them.

As shown in Figure 17, select the check box and click the Save button and the selected business processes or steps will be displayed on the left side, within the Business Processes tree.

Figure 17: Activate business process steps


Best Practice


2.3.2.11 Configure Exception Handling Data Collector

This section describes how to configure the Exception Handling Data Collector in SAP Solution Manager.

Choose collector

The first step is to choose the data collector. In the selected business process step, activate the application monitor. As shown in Figure 18, if the ST-A/PI package in the monitored system has been modified, first click button to load the current data collectors from monitored system. In the example the monitored satellite system is BPP. Afterwards click to add a new monitoring entry.

Figure 18: Collector Create new monitoring object

In field Monitor Name, click F4 and the table shown in Figure 19 will be displayed. It shows a list of available application monitors in the satellite system. From the list, choose Exception Handling for Banking. After selection of the collector, click the button to configure the detail information of the collector.

Figure 19: Collector List of available monitors


Best Practice


Select key figures

In this step, go to the Key Figure tab to choose the key figures you want to activate. Then click the second tab

Detail Information.

The alerts are raised based on the configuration of each key figure.

Figure 20: Collector Activate key figures

The following key figures are available for exception handling.

IndexKey figure description

1Nr. of PPO orders with critical residence time

2Nr. of PCO orders with critical residence time

3Nr. of PCO orders with critical amount

4Nr. of payments in CpD with critical residence time

5Nr. of payments in CpD with critical amount

6PPO order list (low volume customer)

7PCO order list (low volume customer)

8CpD payment item list (low volume customer)

Table 1: List of available key figures

The above eight key figures can be grouped into three categories:

Critical residence time

Critical amount

Work list of open items


Best Practice


The residence time can be monitored to identify orders which are not processed in time. The amount of unprocessed payment items can be critical, especially if service level agreements are defined, if the time without any processing is too high and exceeds a certain limit. The work list of open items shows all the orders that are relevant for postprocessing.

Before you can activate the key figures, you have to configure the parameters in the Detail Information tab.

Configure detail information

In the Detail Information tab, double-click Counter 001 and a pop-up screen is shown as in Figure 21. In the pop-up screen, type in the Banking Posting Area relevant for monitoring and the Posting Date Range to limit the posting date. In the example the Posting Date Range is not limited. The F4 help is available for parameters Bank Posting Area and Posting Date Range.

Figure 21: Collector Configure detail information

If you use F4 in the Posting Data Range input field, Table 2 is displayed. There are five predefined posting

data ranges.

Posting Date RangeDescription

AllPosting data from 01.01.1900 to 31.12.9999

CurrentThe current posting date for payment.

LastThe posting date before current one.

Last + CurrentThe last valid and current posting dates for payment (two posting dates in total)

Last 5 + CurrentThe last 5 valid and current posting dates for payment (six posting dates in total)

Table 2: Possible value of posting date range


Best Practice


Configure monitoring schedule

Click tab Monitoring Schedule to define when the data collector should be started.

Figure 22: Collector Monitoring schedule

In the example, the data selection is on a weekly base, each working day, every 60 minutes.

Configure key figure Nr of PPO orders with critical residence time

Figure 23 shows the selection screen of key figure Nr. of PPO orders with critical residence time. The residence time for the order is calculated based on the difference between the creation time stamp and the current system time.

Figure 23: Key figure Nr. of PPO with critical residence time Selection screen

The following five parameters are available in the selection screen.

Business Process: You can choose F4 help to select the business process steps. The collector will only check the PPO orders that are generated from selected business steps. Order Status defines the status of the PPO order that the data collector should check.

Time Comparison Operator defines how to compare the residence time of the order with the defined critical time. Critical Residence Time defines the critical residence time in minutes.

Alert Comparison Operator defines how to compare the number of PPO-selected orders with defined alert rating threshold.


Best Practice


Figure 24 shows the threshold settings. If the number of PPO orders is higher than 10, the alert message will be rated as yellow. If it is higher than 20, the alert message will be rated as red.

Figure 24: Key figure Nr. of PPO with critical residence time Threshold

With the above settings, the rating distribution is:

Green : Less than 10 postprocessing orders satisfy the condition. Yellow : Between 10 and 20 postprocessing orders satisfy the condition. Red : More than or equal 20 postprocessing orders satisfy the condition.

Based on the collector configuration, each time the collector measures the number of orders in the PPO according to the specified conditions. An alert message is generated in the alert inbox. The rating of the message depends on the measured value and the defined thresholds.

Configure key figure Nr. of PCO orders with critical residence time

Figure 25 shows the selection screen of key figure Nr. of PCO orders with critical residence time. The

same logic is applied here as for the above key figure.

Figure 25: Key figure Nr. of PCO with critical residence time Selection screen

In this case, all posting control orders with the status New or Processing and the residence time greater or equal 10 minutes will be selected.

Based on the collector configuration, each time the collector measures the number of orders in PCO according to the specified conditions. An alert message is generated in the alert inbox. The rating of the message depends on the measured value and the thresholds.


Best Practice


Configure key figure Nr. of PCO orders with critical amount

Figure 26 shows the selection screen of key figure Nr. of PCO orders with critical amount. A logic similar to the preceding key figure is applied here. The currency will be taken over from each payment order.

Figure 26: Key figure Nr. of PCO with critical amount Selection screen

In this case, all posting control orders that have reached and exceeded a critical amount of 1,000,000 will be selected.

Each time the collector is running, it measures the number of orders in PCO according to the specified condition. An alert message is generated in the alert inbox. The rating of the message depends on the measured value and the thresholds.

Configure key figure Nr. of payments in CpD with critical residence time

Figure 27 shows the selection screen of key figure Nr. of payments in CpD with critical residence time.

Figure 27: Key figure Nr. of payments in CpD with critical residence time Selection screen


Best Practice


For parameter CpD Account Group, select the account group defined in 2.3.1.2.

For parameter Order Status, click F4 to choose the order status. Figure 28 shows the available status.

Figure 28: F4 help for item status

The other parameters are similar to those described in the above key figures.

Each time the data collector is running, a message is generated for each CpD account defined in the specified account group. The message describes the number of payment items in the suspense account that satisfy the selection condition (residence time). The rating of the message depends on the threshold defined for the residence time.

Configure key figure Nr. of payments in CpD with critical amount

Figure 29 shows the selection screen of key figure No. of payments in CpD with critical amount.

Figure 29: Key figure Nr. of payments in CpD with critical amount Selection screen

Each time the data collector is running, for each CpD account defined in the specified account group a message is generated. The message describes the number of relevant payment items in the CpD account according to the selection condition (critical amount). The rating of the message depends on the defined thresholds.


Best Practice


Configure key figure PPO Order List

Figure 30 shows the selection screen of key figure PPO Order List (low volume customer).

Figure 30: Key figure PPO Order List Selection screen

Based on the configuration, each time the collector is running, an alert message is generated in the alert screen for each PPO order that satisfies the condition and was created between the last and the current data collector run. The rating of each PPO order depends on the threshold setting. For the same order, only one alert message should be generated.

Configure key figure PCO Order List

Figure 31 shows the selection screen of key figure PCO Order List (low volume customer).

Figure 31: Key figure PCO Order List Selection screen

In this case all posting control orders that have the status New or Processing and that are new in the system will be selected.

Based on the configuration, each time the collector is running, an alert message is generated in the alert box for every payment order in PCO with the specified posting control order status. The alert contains mainly the posting control order ID, the IBAN number to enable a direct analysis of the recipient account, the account holder, the transaction type, and the amount. The posting control order is linked to the associated SAP transactions PCO03 (Posting Control Order) to be able to display the order from the Business Process Monitoring Exception Handling solution.


Best Practice


Configure key figure CpD Payment Item List

Figure 32 shows the selection screen of key figure CpD Payment Item List (low volume customer).

Figure 32: Key figure CpD Payment Item List Selection screen

Based on the configuration, each time the collector is running, an alert message is generated in the alert screen for each payment item in the CpD accounts that satisfies the condition and was created between the last and the current data collector run. The rating of each payment item depends on the threshold setting.

2.3.2.12 Setup application log monitor

The application errors are written into the application log. To set up the Application Log Monitor as shown in Figure 33, check monitoring type Application Log and click on business process step level.

Figure 33: Application log Activate application log monitor

In the screen shown in Figure 34, click to insert a new entry, check it and click .

Figure 34: Application log Add monitoring object


Best Practice


In the screen shown in Figure 35, check the two alert types in the Alert Types tab, and then go to the second tab Detail Information.

Figure 35: Application log Select alert type

In the Detail Information tab, you can specify the selection conditions Object and Sub-object to select the log message that belongs to that category. You can also select the program or transaction that creates the messages according to the user that creates the messages. In the Aggregation field, you have three alternatives of configuration: per log, per hour and per day. After you configured Detail Information, go to the next tab Monitoring Schedule.

Figure 36: Application log Define detail information

In the Monitoring Schedule tab, you can specify how often the application log should be checked. In Figure 37, the log is checked every 60 minutes. After you have done that, click button to go to the next checks.

Figure 37: Application log Set monitoring schedule


Best Practice


In next check, you can configure alerting based on the above conditions. As shown in Figure 38, you can configure it to trigger yellow or red alerts when the number of log message is higher or lower than the thresholds.

Figure 38: Application log Total N* of Messages

For each log entry that fulfils the conditions, an alert message is generated in the alert inbox. The rating of the alert message depends on the number of messages in the log entry and the defined thresholds. If the rating is yellow or red, the log number for the log entry will also be displayed.

In the next tab N* of Critical Messages, you can define alerts on more detail log message information like message type, message class and message number. You can trigger alerts when the number of log messages with specific message types, message class, or message number is higher than the thresholds. To do that, click on the Object field to choose one of above configurations and make the detail settings in the blank fields.

Figure 39: Application log N* of Critical Messages

Each time the data collector is running, it sums up the log messages from the application log that fulfill the selection conditions. And for log messages that satisfy the conditions, an alert message is generated in the alert inbox. The rating of the alert message depends on the number of log messages which are defined as threshold. For yellow and red rating, the log number is also displayed

2.3.2.13 Setup user exit Application log

For some bank customers, it is important to monitor a specific bank account. They want to get informed when log message of a specific bank account is written into the application log and the log message has a critical problem class.

For the example shown in Figure 40, a red alert will be triggered if a log message for the exemplary bank account 14006 is detected and the problem class is 1 (very critical). If the problem class is 2 (critical), a yellow alert is triggered.


Best Practice


Figure 40: Application log Bank account

Based on the configuration, each time the data collector is running, it checks the message fields (from msgv1 to msgv4). If the log message created that day contains the specified account number, an alert message will be generated in the alert inbox. The rating of the alert message depends on the problem class of the log entry and the defined thresholds.

2.3.2.14 Alert notification

When an alert is triggered, it is sent to the responsible person from the production support team to solve it. In the alert notification check, you can configure sender and receiver. If the number of yellow or red alerts exceeds the threshold, alerts will be sent to the recipient address.

Figure 41: Configure alert notification for each monitoring object

Figure 42 shows notification methods. Five different methods are available.

Figure 42: Recipient type


Best Practice


2.4 Procedure Operation and Handling

After the setup, you will get alerts based on the defined setting. This section describes how to use the operation mode and deal with alerts.

2.4.1 SAP Solution Manager work centers

In SAP Solution Manager, use transaction code SOLMAN_WORKCENTER to launch the SAP Solution Manager work centers. It gives a graphic overview of the triggered alerts for each solution, business processes and steps.

Figure 43: SAP Solution Manager work centers Alert inbox

In the screen shown in Figure 43, click on one of the listed alert types to jump to the alert detail view (see Figure 44) where each alert message that belongs to the key figure is listed.

Figure 44: Alert inbox detail view


Best Practice


2.4.2 General application logs

This section shows how to check the alerts generated from the application log monitor. As shown in Figure 45, in the alert inbox detail view, mark the log message and click the Detail Info button above to jump into the monitored system, and the log with the marked log number is displayed. Figure 46 shows the application log with log number 440919.

Figure 45: Operation Application log detail info

Figure 46: Operation Application log in monitored system

After checking the application log and solving the error, go back to SAP Solution Manager and click the button to confirm the alert message.


Best Practice


2.4.3 Application Log user exit (account number)

This section explains how to deal with alerts triggered from Application Log user exit (account number).

As shown in Figure 47, for bank account 0010000154, log messages with a critical problem class are listed in the Alert List view. The time that the alert message was created can be found in column Date Time. For the first log message it is 09:00:14.

Click the button , to jump into the application log (transaction code SLG1) in system QBK.

Figure 47: Operation Application Log user exit

Figure 48 shows the selection screen of transaction SLG1 in system QBK. The fields Object, Subobject, from (Date/Time) and To (Date/Time) are filled with values from the alert message. Adjust from (Date/Time) and to (Date/Time) to a small time window to select the log message.After the adjustment, click button to execute.


Best Practice


Figure 48: Operation Application log in monitored system: Start screen

Figure 49 shows the results. The log message with log number 25008 is found. It contains one message with problem class very important. The log message contains the monitored account number 0010000154.

Figure 49: Operation Application log message (bank account number)

Click on the Detail button and the screen shown in Figure 50 is displayed. It shows the Standing Order Number and Contract Account Number, the message was generated in these two objects.


Best Practice


Figure 50: Operation Application log message details

Click on Standing Order to display the detail order information (see Figure 51). Click on the Account

Number to display the account detail information (see Figure 52).

Figure 51: Operation Display standing order


Best Practice


Figure 52: Operation Display bank account information

Check the account- and standing order details to analyze the error in the application log or on account level.

2.4.4 Exception handling (PPO, PCO, CpD)

2.4.4.1 PPO Nr. of PPO with critical residence time

Figure 53 shows the alert list for the PPO key figure Nr. of PPO orders with critical residence time.

Figure 53: Operation Alert list for Nr. of PPO with critical residence time


Best Practice


Figure 54 shows the thresholds for rating, and Figure 55 shows the value range of the selection conditions.

Figure 54: Operation Alert configuration for Nr. of PPO with critical residence time

Figure 55: Operation Parameter value range for Nr. of PPO with critical residence time

The exception processor can click on the analysis button to display the order in PPO or use the analysis button to process the order in PPO. It will jump into system BPP and start the transaction BCA_PPO3 and BCA_PPO2.

2.4.4.2 PPO PPO Order List

Figure 56 shows the alert detail view for key figure PPO Order List (low volume customer). For each newly created PPO order there is an alert message. In the alert message, the PPO order ID is displayed in the

Order ID column. The columns Process and Process ID provide the information on the related process where the order was created. Alert Message gives a summary of the alert.

Figure 56: Operation Alert list for PPO Order List (low volume customer)


Best Practice


In Figure 57, you can mark one alert message and click the button to directly jump into the PPO edit screen in the core banking system. The marked PPO order will be displayed for postprocessing as shown in Figure 58. The processor gets an overview of all PPO orders that should be processed in one screen and can directly jump into the core banking system for the postprocessing. After processing the order in the core banking system, the processor goes back to SAP Solution Manager and confirms the marked alert by using button , the confirmed alerts will disappear from the alert detail view. When all red alerts are confirmed in SAP Solution Manager, all PPO orders are solved.

Figure 57: Operation Deal with alerts in PPO Order List

Figure 58: Operation Process PPO order in Banking Services system

With the help of the exception handling monitor you get a central overview of the business exceptions in SAP Solution Manager. The exceptions are presented in a structured manner. The processor does not need to search for exceptions manually and frequently in the core banking system. Possible human error like overlooking exceptions can be prevented. It helps the bank to run SAP core banking products in a more efficient way and reduces the possibilities of human failure.


Best Practice


3Further Information

3.1 Background Information and References

Below is a list of useful information regarding SAP Solution Manager and Business Process Monitoring

http://service.sap.com/bpm Media Library Technical Information http://service.sap.com/solutionmanager http://service.sap.com/solutionmanagerbp List of Best Practice Documents

SAP Note 521820 SAP Note 784752



Date post:	02-Oct-2015
Category:	Documents
Upload:	rambabu-namamula
View:	6 times
Download:	1 times