You are on page 1of 74

Best-Practice Document

Operations Concept
for SAP Banking Services
(Deposits and Loans)

Dietmar-Hopp-Allee 16
D-69190 Walldorf
DATE
November 2010

SOLUTION MANAGEMENT PHASE SAP SOLUTION

Operations & Continuous Improvement SAP for Banking
TOPIC AREA SOLUTION MANAGER AREA

Business Process Operations

© 2010 SAP AG

Best Practice
Operations Concept for SAP Banking Services (Deposits and Loans)

Date Alteration Reason Version

19.07.2010 Creation 0.1

Table of Contents
1 Management Summary 4
1.1 Goal of Using this Service 4
1.2 Staff and Skills Requirements 4
1.3 General Aspects of Banking Operations 7
2 Error and Exception Handling 8
2.1 Usage of Postprocessing Office (PPO) 8
2.1.1 Purpose 8
2.2 Prerequisites 9
2.2.1 Activation of PPO 9
2.2.2 Activation of ECH 9
2.2.3 Usage of Worklists 10
2.2.4 Usage of Priorities for Business Processes 10
2.3 PPO Order Processing 11
2.3.1 Manual Processing via the PPO Desktop 11
2.3.2 Automatic Processing 17
2.4 PPO Setup Checklist 18
3 Parallel Processing Framework 19
3.1 Purpose 19
3.2 Prerequisites 19
3.2.1 Number of Background Jobs 19
3.2.2 Repeat of Mass Runs 19
3.3 Deletion of Mass Run Data 20
3.4 Aborted Mass Runs 21
4 Clearing Payment Items 22
4.1 Purpose 22
4.2 Prerequisites 22
4.3 Clearing Process 23
5 Post Processing of Payment Items via Posting Control Office 25
5.1 Usage of Posting Control Office (PCO) 25
5.1.1 Purpose 25
5.1.2 Post Processing Possibilities 25
5.1.3 Usage of Worklists 26
5.2 PCO Order Processing 27
5.2.1 Manual Processing via the Posting Control Office 27
5.2.2 Automatic Processing 30
5.3 PCO Setup Checklist 31
6 Correspondence Monitoring and Archiving 33
6.1 Purpose 33

© 2010 SAP AG page 2/74

Best Practice
Operations Concept for SAP Banking Services (Deposits and Loans)

6.2 Prerequisites for Archiving and Deletion 33
6.3 Monitoring 33
6.4 Archiving and Deletion 35
7 Automatic Postprocessing of Payment Distribution Items 36
7.1 Purpose 36
7.2 Prerequisites 36
7.3 Reprocessing 36
8 Monitoring of the Banking Services System 38
8.1.1 Performance-Oriented Monitoring and Analysis 38
8.1.1.1 MassMan Monitoring Analysis Tool 38
8.1.1.2 Workload Monitor – ST03 41
8.1.1.3 Single Record Statistics – STAD 42
8.1.1.4 Trace Analysis – ST05/ SE30/ST12 43
8.1.1.5 Database Monitor – ST04 45
8.1.1.6 Operating System Monitor – ST06/ OS07 47
8.1.1.7 Workprocess Overview – SM50/ SM66 48
8.1.1.8 SAP Code Inspector – SCI 50
8.1.2 Technical-Oriented Monitoring and Memory Analysis 52
8.1.2.1 SAP Memory Configuration Monitor - ST02 52
8.1.2.2 ABAP Dump Analysis - ST22 53
8.1.2.3 System Log - SM21 54
8.1.2.4 Computing Center Management System – CCMS/ RZ20 55
8.1.2.5 Analyze Memory Consumption - S_MEMORY_INSPECTOR 56
8.1.2.6 Transactional RFC – SM58 57
8.1.2.7 Message Monitoring- Integration Engine – SXMB_MONI 58
8.1.2.8 Snapshot Monitoring /SDF/MON 58
8.1.3 Application-Oriented Monitoring 61
8.1.3.1 Parallel Processing Monitor - RBANK_PP_MONITOR 61
8.1.3.2 Job Overview – SM37 62
8.1.3.3 Display Application Log – SLG1 64
9 Housekeeping of the SAP Banking Services System 68
9.1.1 Cross-Application Housekeeping 68
9.1.2 Banking Services System Housekeeping 68
9.1.2.1 Deletion Report for RBANK_PP_MONITOR Process Data 68
9.1.2.2 Deletion Report for "Account Settlement" Simulation Data 69
9.1.2.3 Adapt Product Pricing List to Related Contracts Report 69
9.1.2.4 Check Financial Conditions Customizing 69
9.1.2.5 Delete Reports in Account Management via Delete Objects 69
10 Background Information and References 71
10.1 Overview of the Most Important Best Practice Documents 71
10.2 Overview of the Most Important Transactions 71
10.3 Overview of the Most Important Regular Jobs 72

© 2010 SAP AG page 3/74

and any kind of error could lead to delays.2 Staff and Skills Requirements In the document “Best Practices for End-of-Day Processing SAP Deposits Management” in the “Staff and Skills Requirements” section. mostly driven by payments initiated by ATMs. the daily business is affected by system load and certain data is not available on time. automatically generated periodic items. or to keep this document lean and provide a point of entry for customers who are starting with an SAP system for the first time or want to have a check against their current banking operations concept. 1. and error and exception handling. or end-of-day. high volumes have to be processed in the given time window. This best-practice document completes the best practices for end-of-day processing and operations (available on SAP Service Marketplace  Best Practices). During end-of-day processing. processing. In some chapters. The end-to- end performance of the processes is crucial in daily processing. but we do address necessary standard roles that should be defined for smooth operation of the Banking system. We created this operations concept to provide SAP Banking Services customers focusing on deposits and loans with best practices for operating their SAP system. The daily end-of-day processing within a bank is a critical process because the data that is posted or stored during the day is processed and settled. The main focus of the daily business is dialog processing. The first challenge is to provide a suitable environment for the daily business. © 2010 SAP AG page 4/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 1 Management Summary With implementing and operating an SAP Banking Services solution.1 Goal of Using this Service This best-practice document is based on workshops and experiences from the productive operation of different SAP Banking Services customers. you will find an introduction to the needed skill requirements to fulfill the necessary tasks and responsibilities. housekeeping. data throughput is crucial. therefore. display account balance). End-of-day processing groups together a number of steps and reports and executes them in a single process chain (mostly in batch mode) without any manual interaction. Other focus areas are operation topics like system monitoring. you will only find a high-level description or a short introduction to the topic. there is the need to cover two major challenges. The second challenge is nighttime. It provides best-practice guidance to Banking customers about how to operate an SAP Banking Services system and the main daily operations tasks that have to be executed when using Loans on platform and / or Deposit Management on SAP Banking Services. either because there are already best-practice documents available. We do not cover organizational areas in terms of organization structure. 1. or different online calls to the system (for example. If the end-of-day processing runs longer than the given time window.

Provide technical monitoring and special matter expert in case of technical issues . Implement. test. Ensure high availability of the system . Identify criticality of an issue (resolve the error immediately or during the next day) Person / group from the support . test. and operate the job scheduling tool . Get details for job scheduling from banking business control tool of the bank process owner . Hand over tasks of BPMon to first-level support . Define the available number of technical batch work SAP Basis / Administration processes Person(s) responsible for the . Hand over tasks of job control to first-level support . Compare acquired and provided functionalities and find Business Process Monitoring gaps in the tool Person responsible for the . . Implement. (Optional) Monitor banking business process together with first-level support . Analyze and resolve performance issues Basis . Define. Define variants and variables SAP standard program © 2010 SAP AG page 5/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) The following table describes the roles and their major responsibilities during setup and operation of the production system. Define the degree of parallelization per report / program infrastructure. Communicate with the provider of the job scheduling tool . what to do in case of First Level Support /CCoE an error (Service Desk and Command Center) . Section/ Roles Tasks/Responsibilities . Define and implement the technique for file transfers . for every report / program. data base and SAP. Perform root cause analysis . Communicate with the provider of the Business Process Monitoring (BPMon) tool . Set up and run service desk (initial contact in case of team of the bank who will be production errors) responsible for the support of the . It also includes the role that will act as an expert contact person in case of an error during the operation phase. Get detail from banking business process owner and Business Process Monitoring tool job scheduler for operation of the bank . Compare acquired and provided functionalities and find Job Control/Job Scheduler gaps in the tool Person responsible for the job . Provide monitoring and job control during operation productive system . and operate the Business Process Monitoring tool .

Define test cases . defined operations handbook with detailed dependencies between all relevant process steps and detailed expectation handling for known error cases is mandatory. Implement and maintain all IT Service Management processes . Coordinate roles and tasks during setup and system Duty Manager or Service operation Manager . and some of them take place only if there is an error. Some errors that occur during the EoD processing need to be solved immediately. Define dependencies between jobs. Define dependencies between jobs. Define variants and variables Customer specific program contact . © 2010 SAP AG page 6/74 . . Define variants and variables SAP Developer . Be responsible for the efficient delivery of IT services according to SLAs There are different activities during the EoD process. or even later. Resolve errors . Test resolved errors (retest) . Some of the activities take place immediately. Support operations and perform error solving in case of system incidents . Define test cases program Y/Z (customer-specific development) . Test resolved errors (retest) . Decide which programs of the SAP standard are Person who is familiar with the relevant (focus on EoD [end-of-day processing]) process of the existing core . Define test cases . A clear. also cross-system (process owner) Functional responsibility SAP- program X (SAP-standard) . Define dependencies between jobs.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Section/ Roles Tasks/Responsibilities contact . but many errors can be solved the next day. Evaluate dependencies between relevant banking system(s) programs/jobs . also cross-system (process owner) Functional responsibility SAP. some of them take place proactively. Evaluate the functional and / or technical reason for an existing program . also cross-system Developer SAP-program Y/Z (process owner) (customer-owned development) . Evaluate sequence of the programs / jobs . Be responsible for the technical core business process Banking Process Owner (EoD flow and components) . Support operations and perform error solving in case of system incidents .

de/~sapidb/011000358700000671032009E 1. SM37. It introduces you to the different standard functionalities and SAP tools to perform error and exception handling. operations of an SAP Banking Services system can be divided into daily and nightly processing. system and business process monitoring. and fast resolution of errors or to avoid or reduce the error situation proactively. posting cut-off. nightly processing is characterized by high system load via batch processing by automated process chains. for example. Also see RunSAP Document: End of day/Batch Processing Deposit Management https://websmp207. but it is important in both cases to guarantee high system availability. system and core process performance. The operations for daily and nightly processing are different. and basic administration topics. and processing of high data volume in a given time window. While daily processing is driven by online processing and E2E performance. To support the operations team in handling these challenges we created this best-practice document.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) SAP standard transactions (for example. by performing system and business process monitoring. SM66) and SAP Banking-related monitoring tools like RBANK_PP_MONITOR and Business Process Monitoring for Banking help you to get the process status right in time to quickly react to errors.sap-ag.3 General Aspects of Banking Operations As already described in the Management Summary. © 2010 SAP AG page 7/74 .

1 Usage of Postprocessing Office (PPO) 2. The ECH PPO orders are normally used by services.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 2 Error and Exception Handling 2. This type of PPO order is created. The Postprocessing Office has the following advantages:  Overview of all the information required to process the events in any business processes. Therefore.1. for example.1 Purpose The Post Processing Office (PPO) supports the processing of errors that originate in any business process. You only need to call up the error logs to display an overview of the objects that were processed successfully in the mass runs. All the data relevant for processing errors is combined in a postprocessing order. You can therefore process error messages from mass runs of different object types. by the account settlement and account statement mass runs. and these can potentially create PPO orders. the relevant report can be restarted to reprocess the object and the user can set the PPO order to completed.  Possibility to navigate to relevant objects  Extensive selection options  Distribution of postprocessing orders to worklists for processing  Reference to events of same object in other business processes  Reference between objects from different application logs  Authorization checks  Status management  Processing history There are two kinds of PPO orders: “classic” orders and orders created by the Error and Conflict Handler (ECH). Classic PPO orders contain only information about the failed object (such as the account). to post an item triggered by a service. for example. for example. ECH PPO orders contain all data that is necessary to perform a business process step. Many mass runs are executed during end-of-day processing. It is therefore possible to repeat the erroneous step either manually from the PPO Desktop or automatically via a report once the error has been solved. and the error messages that occurred during processing. additional objects (such as business partners). The Postprocessing Office replaces the application logs of the mass runs as the initial function for error processing. Once the error is solved. you should perform monitoring and processing of PPO orders on a daily basis to ensure that all © 2010 SAP AG page 8/74 .

account balance locks. because ECH orders are created by default. by:  Missing or incorrect customizing. Your aim is to solve the causing errors and to complete the PPO orders on the same day. dialog locks. or posting locks  Business rule violations  Authorization issues 2.2. there is no specific transaction for Pricing. creation of “classic” PPO orders is deactivated. leave the business process blank. missing exchange rates or incorrect product settings  Locks. for example.1 Activation of PPO By default. PPO orders may be created.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) business processes have a consistent state from a business process point of view.2.) To activate PPO for all business process of a component.2 Activation of ECH ECH does not need to be activated. At a minimum. It is recommended that you activate PPO for at least the following components:  FS-AM  FS-MCM  PRI (Pricing -. the following entries should exist in the table: Component Business Process Act. You have to activate the creation in Customizing by choosing Cross-Application Components  General Application Functions  Postprocessing Office  Postprocessing Office  Business Processes  Activate Creation of Postprocessing Orders. But other mass runs that run during the day may also create PPO orders. for example. so you should also monitor PPO during the day.2 Prerequisites 2. © 2010 SAP AG page 9/74 . for example. FS-AM X FS-MCM X PRI X 2.Use transaction /n/SAPPO/PPO2 to work on Pricing PPO orders.

If nothing is defined in Customizing. Other users may take care of settlement-specific errors. choose Financial Services  Account Management or Master Contract Management  Postprocessing Office  Worklist.3 Usage of Worklists You should also consider if it makes sense to use worklists for PPO orders. Once a worklist has been created. if specific users should take care of item-specific errors.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) In Customizing. © 2010 SAP AG page 10/74 . the user sees PPO orders that are assigned to his or her worklists and the orders that have no worklist. you are able to assign responsibilities for specific business processes to specific users or organizations. you can assign priority “high” to settlement-related PPO orders and priority “low” to settlement– simulation-related PPO orders. BCA_PPO2 with “Order Assignment” = 1. you can assign users or organizations to the worklist. Afterward. For example. For example. To define worklists in Customizing. 2. It can also be used as a filter criterion within the PPO Desktop. With worklists. the general default resolution strategy is applied. The priority can be used as selection criterion on the selection screen of the PPO transactions.4 Usage of Priorities for Business Processes You can assign a priority to a business process. you can assign these users to an item worklist. The default resolution strategy is:  Create PPO orders  Allow automatic and manual retry  Allow manual finish and fail  Use no residence time and no resubmission group Use the following IMG activity to define your own resolution strategy if the default does not fit in your case: Cross-Application Components  General Application Functions  Error and Conflict Handler  Define Resolution Strategy. When a user starts a PPO transaction.2. 2. You must perform the assignment of users or organizations to a worklist via the SAP Easy Access menu: Financial Services  Account Management / Master Contract Management  Postprocessing Office  Worklist  Change Assignment. You can assign these users to a settlement worklist. you can assign a PPO business processes to it.2. you can define a resolution strategy for the ECH PPO orders per component and business process. for example.

Display Postprocessing Order  General PPO transactions (application-component-independent) /n/SAPPO/PPO2 .Display Postprocessing Order  PPO orders for Posting Lock Management PLM_PPO2 .3.Edit Postprocessing Order /n/SAPPO/PPO3 .Edit Postprocessing Order MCM_PPO3 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) The Customizing path to assign the priority to a business process is: Cross-Application Components  General Application Functions  Postprocessing Office  Postprocessing Office  Business Processes  Assign Priority to Business Processes.Display Postprocessing Order © 2010 SAP AG page 11/74 .Display Postprocessing Order  PPO orders for application component Master Contract Management (FS-MCM) MCM_PPO2 .1 Manual Processing via the PPO Desktop Within banking services from SAP. the following transactions are available to edit or display PPO orders:  PPO orders for application component Account Management (FS-AM) BCA_PPO2 .Edit Postprocessing Order PLM_PPO3 . 2.Edit Postprocessing Order BCA_PPO3 .3 PPO Order Processing 2.

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) PPO Entry Screen of Transaction BCA_PPO2 If you call. the selected PPO orders are displayed after you execute the report. © 2010 SAP AG page 12/74 . for example. transaction BCA_PPO2.

discard.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) PPO Desktop – Overview List In the overview list you will find information about the main object. and so on. the main error message. = Order not processed = Order in process = Order processing completed If you right-click on an order in the overview list. a context menu appears. for example. to display the priority and the worklist. repeat or complete from the context menu. You can then perform an action for multiple orders. If you select Display Details from the context menu or if you double-click on an order. or confirm (only available for ECH PPO orders) You can also select multiple orders by using the Ctrl or Shift keys. the detail screen appears. © 2010 SAP AG page 13/74 . You can use the Select layout icon to modify the appearance of the list. the business process. for example. the status. The status traffic light shows the processing state of an order. The context menu allows you to:  Change status of the order  Change processor  Change worklist  Display details  Repeat.

for example. as well as the messages that occurred during reprocessing. the account or master contract  Log area Contains the messages that were written to the log by the originating process.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) The detail screen is split into the following areas:  Header area Shows important information like the main object. the messages should help you to analyze the causing error © 2010 SAP AG page 14/74 . and the status of the order  Order area Contains detailed information about the order  Object area Provides data about the erroneous object. the main error message.

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) PPO Details Screen of an ECH PPO Order in Edit Mode The Details screen provides the following processing options:  Change Worklist Assignment (via the menu)  Change Processor Assignment (via the menu)  Complete Order (only available for classic PPO orders) You can set the status to Completed by pressing the button. Note: Only press this button if the causing error has been solved! Process Order (only available for ECH PPO orders) © 2010 SAP AG page 15/74 .

If you press this button. See Customizing: Cross- Application Components  General Application Functions  Error and Conflict Handler  Define Resolution Strategy. no further actions are performed. Otherwise. sending of a message to the initiating process. the mass run should be restarted to reprocess the faulty objects. In most cases. the status of the order is changed to Completed. the order is assigned to your user and the status is changed to In process. this could also lead to inconsistencies in the business process! According to the resolution strategy setup in Customizing. so an order should only be discarded if the object is processed in another way or if the error cannot be solved at all. the status of the order is changed to Completed. the item is not posted and a PPO order is created. consider the long texts of the messages for further details. The initiating process is already successfully finished at this stage. buttons may not appear. for example. you can display the mass run log (same as transaction SLG1 to display a log) out of the PPO order by pressing the first log icon in the log area. An order should only be confirmed if the causing error is solved or if the process step has been executed manually. a new PPO order is created. Before you restart. © 2010 SAP AG page 16/74 . nothing is posted.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) When you press the button. The corresponding mass run is for interest. by posting an item in dialog. use the repeat functionality of the PPO to reprocess the object. you should complete the orders. for example. If the PPO order is created by ECH. the actual error must be solved. sending a message to the initiating process. If the order was created out of a mass run. If you press Confirm without solving the causing problem and without repeating. For the error analysis use the messages in the log area. for example. the confirmation can lead to inconsistencies in the business process! Example: Assume you started a process that posts items in the account managing system via service or RFC call. In addition the following buttons appear: Use this button to repeat the process step. As a prerequisite. you should identify the initiating process and perform the necessary steps to achieve a consistent state. because if the mass run is repeated and the causing error is not solved. In most cases no further actions are performed. Because of missing customizing. If you discard a PPO order. If the repetition of the process step is successful. the order is set to status Completed and the log is updated accordingly. In the latter case. because if you analyzed and resolved the causing error. The initiating process relies on the correct processing. If you press this button.

3. Automatic processing is possible in the following ways:  Reprocessing of orders (report /SAPPO/RESUBMIT_ORDERS_2) o Orders that were created because of a lock can be reprocessed. but this should be handled with care. o The report should not be scheduled as a periodic job.  Deletion of orders (report /SAPPO/DELETE_ORDERS) © 2010 SAP AG page 17/74 . Once an order is closed. Selection Screen of Resubmission Report  Closing of orders (report /SAPPO/CLOSE_ORDERS_2) o It is possible to automatically close orders.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 2. o Orders are closed independently.2 Automatic Processing Automatic processing or reprocessing of PPO orders helps you to minimize human intervention. it can no longer be edited. o Orders for which the causing error has been resolved can be reprocessed. whether or not the causing error has been solved. o It is recommended that you schedule the reprocessing report /SAPPO/RESUBMIT_ORDERS_2 periodically (also multiple times a day) depending on the resubmission group.

use organizational data and create worklists for special business processes and users or user groups.  Configure PPO-specific settings (SPRO  Account Management / Master Contract Management  Postprocessing Office). PPO can be integrated into a customer’s own processes.  Start working with the component-specific (BCA_PPO2. MCM_PPO3) or generic (/SAPPO/PPO2. If desired. but this takes a few more activities. because once you have deleted an order you no longer have a history. On top of that. Deletion of orders should also be handled with care. © 2010 SAP AG page 18/74 . MCM_PPO2.  Activate PPO creation for AM or MCM business process (SPRO  Account Management / Master Contract Management  Postprocessing Office  Business Processes  Activate Creation of Postprocessing Orders). o The report should not be scheduled as a periodic job.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) o Once an order is closed (status Completed).4 PPO Setup Checklist The following list describes how to work with PPO for existing processes where PPO is already integrated. /SAPPO/PPO2) PPO transactions. it can be deleted from the system. 2. BCA_PPO3.

All of the mass runs provided by Banking Services from SAP Deposits and Loans Management use the PPF. The tool administers these packages and controls their processing in parallel background jobs. The application allocates the data to be processed to packages that are transferred to the tool. Basis job scheduling controls the execution of these jobs.1 Purpose The Parallel Processing Framework (PPF) supports the parallel execution of application-specific processes. You can set up the number of jobs to be used in Customizing by choosing Financial Services  Account Management / Master Contract Management  Tools  Parallel Processing  Maintain Job Distribution. You can schedule mass runs with an external job scheduling tool. It is also possible to use the PPF for customer-specific mass runs. You should also consider the reports that run in parallel. The number of background jobs depends on your system settings (especially on the number of batch processes among all your application servers) and on other issues.2 Repeat of Mass Runs To avoid errors resulting from lock situations you can define the number of parallel and sequential repeats per application type in the Parallel Processing Framework configuration (Customizing: Financial Services  Account Management / Master Contract Management  Tools  Parallel Processing  Maintain Customer Settings for Application Types).2. a mass run uses only one background job for processing. 3. because if you reserve too many batch jobs for one report.2. like Central Process Scheduling by Redwood for SAP NetWeaver. how many objects should be processed by a mass run. © 2010 SAP AG page 19/74 .1 Number of Background Jobs By default. the other reports running in parallel can use fewer resources and may take longer.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 3 Parallel Processing Framework 3. The tool enables parallel execution (usage of several application servers) of runtime-intensive mass processing. 3. for example. The number of background jobs has to be increased by you so that it suits your requirements.2 Prerequisites 3.

processing errors resulting in PPO orders or a program termination. © 2010 SAP AG page 20/74 . This is to avoid waste in the system. Parallel repeat means that packages that include objects with a certain status are repeated in parallel (with the same number of jobs defined for the run) after all packages have been processed once. Runs should not be deleted until it is clear why certain errors occurred. It is recommended that you check what kind of error happened.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Setup of Direct and Sequential Repeats The application itself makes the decision about repeat behavior. 3. In principle. object worklists. The object can be repeated only if the application sets a certain status for an object within parallel processing. using the same external run ID (if this option is provided by the mass run). the mass-run-related data is stored in the system as long as the mass run is repeated successfully or the administrative data is deleted. If a mass run ends with errors. The only critical thing is that if a report sets locks on which other mass runs rely on. as well as locks. all packages that include objects with a certain status are repeated in one single background job after the parallel repeat(s). these locks are deleted and therefore a succeeding mass run could process the object. If a sequential repeat is defined. for example. it is not that critical if run data is deleted. because the mass run can be re-started with the same parameters. You can use report RBANK_DELETE_RUNS to delete the administrative data. Two to three parallel repeats and one sequential repeat may be sufficient. restart the mass run.3 Deletion of Mass Run Data If a mass runs ends without errors. It is recommended that you analyze the causing error first. and package data for old runs. You should check the state of the mass runs regularly with transaction BANK_PP_MONITOR. all mass-run-related data is deleted from the system automatically. If the root cause of the error is corrected.

© 2010 SAP AG page 21/74 . In this case. Depending on the termination point. If no external run ID is provided by the mass run.4 Aborted Mass Runs If a mass run ends with an application return code 8 = terminated. simply restart the run. the objects of the aborted package have not been counted and therefore are not reflected in the counters. then you must check why the mass run has been aborted. 3. The mass run ends with technical job status finished although there was a short dump. if all other objects are processed successfully. For the whole mass run. The application return code is 8 = terminated. In any case. this means that the available background jobs have to process the rest of the packages. It could be that a short dump occurred during the processing of an object.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) External Run ID of a Mass Run You can select the erroneous mass run from a list by using the F4 value help for the External Run ID field. the counters in the log tell you that x due objects have been selected and x objects have been processed successfully. Furthermore. you should analyze the cause of the error and restart the mass run when the causing error is solved. the related background job is also terminated.

To find out which items have not been cleared. This means that there is a business requirement that each item or item group posted on a working account has one or more offsetting items that clear these items or item groups.2 Prerequisites You have created the products required for the clearing accounts in the customizing under Financial Services  Account Management  Product Management  Product Definition  Account Products  Create Account Products. clearing items reference each other (cleared). 4. which you can use for a temporary posting transfer (such as working accounts). © 2010 SAP AG page 22/74 . you have defined the transaction types for taking differences off the books for manual clearing. because the nature of the postings on these clearing accounts is only temporary. Monitoring of the clearing accounts is necessary to check if open items exists. You can clear items on the same day or at a later date. and for automatic removal from the books with clearing. Furthermore. you have defined the period for the automatic removal from the books and/or the Can Be Cleared Externally attribute.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 4 Clearing Payment Items 4. Items that have not been referenced are thus not part of a cleared business transaction. Examples of this type of clearing account:  Outstanding receivable accounts  Collective accounts  Holding accounts  Clearing accounts for payment transactions  Disbursement accounts for account closure  Process interim accounts (used by Combined Settlement for postings) You can close open items on these accounts by using the clearing functionality. In the Clearing feature.1 Purpose SAP Deposits and Loans Management have accounts for posting processing. and the Period for External Clearing in Days. The aim is to clear all items on these accounts.

3 Clearing Process You should schedule the mass run RBCA_CLEARING_EXT_RUN_PP so that it runs daily in the end-of-day processing. choose Account Management  Account  Turnovers. With report RBCA_PAYMITEM_CLEARING_LIST (transaction BCA_CLEARING_LIST). If this is the case. Display of Open Items with Transaction BCA_CLEARING_LIST © 2010 SAP AG page 23/74 . if there are open items. The report finds all the items that have an external clearing reference and clears them from the system if the total of the generated reference group is zero. Balances and Key Figures  Payment Item Display Open Items for Clearing Account.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Account Product Setup for Clearing 4. you should check. you should analyze the reason why they are still open. on a daily basis. In the SAP Easy Access screen.

© 2010 SAP AG page 24/74 . From the SAP Easy Access screen. the Ext. Use the field catalog to select the fields you want to display. It is also possible to manually clear items. Balances and Key Figures  Payment Item  Clear Payment Item. choose Account Management  Account  Turnovers.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Alternatively you can use transaction BCA_PAYMITEM_MAINTN to find which items are cleared and which are not. Clearing Ref. Exists fields. or Clearing Ref. Clearing Status in Transaction Display Payment Item (BCA_PAYMITEM_MAINTN) Note: Not all relevant fields may be displayed by default. for example.

Reallocation Posted  Response creates posting control order. the following response types might be triggered for the erroneous payment item. All necessary information is collected in a posting control order that for most cases is directly linked to the erroneous payment items. 5.1 Purpose The Posting Control Office is used to handle special situations and problems that occur during posting of payment items. Response Status of item Explanation Post Posted  Item is posted on target account. Redirect Posted  Response creates posting control order for redirection to suspense account. there is only one posting control order for several payment items of one account (for example.2 Post Processing Possibilities Depending on the rules. Postprocessing In Postprocessing  Response creates posting control order. Possible problems that can occur for a payment item might be more technical related errors.1. or cancelled right away. The posting control order is then linked to the account itself instead of the payment item.1.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 5 Post Processing of Payment Items via Posting Control Office 5. such as:  Value (mandatory attribute not entered)  Value range (entered value not within defined value range)  Format (entered value has a format error.  Item is posted on target account. such as text in a date attribute) Or business rules errors.1 Usage of Posting Control Office (PCO) 5. In special cases. you can define actions in the rule set that define if the payment items should be posted nonetheless. © 2010 SAP AG page 25/74 . processed in the Posting Control Office.  New target account specified in the posting control rules in customizing. like:  Account Posting Check failure  Insufficient funds  Access Limit violation  Account Name Check failure  Prenote missing or cannot be matched For each of these problems. insufficient funds cause more than one payment item to fail).

Posting control orders are assigned to different worklists according to specific parameters. A posting control order is created for responses Reallocation.1. This means that a posting control order is created and the person responsible has to process the payment item manually. These criteria can be assigned to priorities/rankings. Any number of worklists can be defined using different criteria (up to six) for worklist determination. After correctly defining the worklist. and matches the criteria.  Rejection reason (optional) specified in the posting Reject Not relevant control rules in customizing.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans)  Return reason (mandatory) specified in the posting Return Returned control rules in customizing. Postprocessing. © 2010 SAP AG page 26/74 . These orders can be processed manually in the Posting Control Office or automatically. the system assigns each payment item to a worklist if it is sent to post processing. and Redirect. Process Overview Posting Control Order 5.3 Usage of Worklists All exceptions that cannot be resolved automatically by the posting control rules are sent to post processing.

One major attribute is the worklist.1 Manual Processing via the Posting Control Office The main entry transaction for the Posting Control Office is PCO. © 2010 SAP AG page 27/74 . They will be shown one posting control order after another that fulfills the filter requirements until all orders are processed.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Users have to be assigned to one or more worklists to be able to work with the Posting Control Office. Users can filter for posting control orders in their worklist and start the PCO processing. Posting Control Order – User Assignment to Worklists 5. and a user will see all orders that are assigned to his or her worklist. Transaction PCO works like a pile of orders. It is possible to define complex filters on which the selection of posting control orders is based.2. one after each other.2 PCO Order Processing 5.

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Change filter settings Choose worklist options The following screen will be displayed for each posting control order. © 2010 SAP AG page 28/74 .

this screen is missing. a resubmission is done trying to post the payment item. If the posting control order is not assigned to an item (account order). For error resolution and individual processing of posting control orders of a single account. including which checks failed. © 2010 SAP AG page 29/74 . the account view is shown. The information area shows the data of the posting control order and relevant account data. You can find general information about the affected account and the posting control order in the header data. The results are shown in the log area. You can use further selection criteria if necessary. all messages are displayed in the log area so that the processor knows what the problem is. You can find the posting control orders directly via GUID or by entering the account identification. When you open a posting control order. all relevant items for the erroneous account are displayed in a list. it is closed and the next one is selected. instead.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Header Area Log Area Information Area Detail Area The desktop is designed to offer all functionality needed to process a posting control order. data of the payment item is displayed so you can get more background about the item that was not successfully processed. The active tab depends on the error category of the posting control order. In case of an error. In the detail area. you can use transactions PCO02 (Edit) and PCO03 (Display). In the account view. If the order is processed successfully.

5. or decline the posting (return / reject an item).2. accept overdraft due to insufficient funds).2 Automatic Processing For automatic processing. posting lock). accept the error and overrule the system response (for example.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Select posting control order by ID Or by account identification You can perform the following actions in PCO to solve posting problems:  Prepare all information relevant for making posting control decision  Post / return / reject / transfer post turnover  Transfer to automatic processing function  Temporarily postpone processing  Close posting control order The processor can remove the issue causing the posting problem (for example. two mass runs are available that offer the following functionality: © 2010 SAP AG page 30/74 . The action taken is saved in the action log of the posting control office and the item processing is finished.

money for a life insurance policy cannot be withdrawn due to insufficient funds. the final processing run will eventually pick up the order when it is due and process it (either post or return/reject) based on the settings in configuration.  Define main rule set and decide what needs to be processed within PCO (SPRO  Financial Services  Account Management  Item Manangement  Posting Control Rules  Define Main Rule Set). the benefit for the customer (compared to direct processing) is that certain problems that prevent a posting are solved within the few hours or days that the posting control order exists. If enough money is not available after two days. no additional manual effort is necessary to provide this service. For the bank. For example. the item will only be parked at the account.  Maintain organizational data (PPOME) and use in worklist assignment (PCO_WL_ASS_MAINTAIN). In this case. © 2010 SAP AG page 31/74 . The main goal is to solve all problems before any legal regulations kick in that require a final processing state. The resubmission run checks if problems are resolved in the meantime (for example.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans)  Resubmission o Check whether limit problems still exist o Item in postprocessing: Renewed posting attempt o Item in reallocation: Renewed check of posted item o Item posted on suspense account: Renewed posting attempt on original account  Execute final processing o Renewed resubmission o Execution of final response from posting control rules These mass runs support the users’ manual work and will clear all posting control orders after certain time elapsed. a regularly scheduled resubmission run checks to see if funds are sufficient.  Configure PCO-specific settings (SPRO  Financial Services  Posting Control Office). The benefit for the customer is that there is a “grace period” of up to two days to provide enough money. 5. and posts the item as soon as it is possible. If this is not the case. Orders can be assigned to automatic processing only so that no manual activity is necessary at all. the item is returned in the final processing run. For two days.3 PCO Setup Checklist  Activate PCO in Configuration (SPRO  Financial Services  Account Management  Basic Settings  Activate Special Components). The first reaction is postprocessing. insufficient funds) and if the payment item can now be posted without error.

© 2010 SAP AG page 32/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans)  Start working with transactions PCO and PCO02.

2 Prerequisites for Archiving and Deletion To archive or delete a correspondence request. you have to perform the necessary setup in Customizing.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 6 Correspondence Monitoring and Archiving 6. correspondence requests can be created as event-controlled. you can use report RBCA_CORR_HISTORY to check if all created correspondences have been printed. set the Delete indictor. If you want to delete correspondence requests without archiving them. correspondence is based on correspondence requests. Once the residence time for a correspondence type is exceeded.1 Purpose Correspondence is used to inform customers about specific events. In the SAP Deposits and Loans Management System. Several mass processing reports create correspondence requests. for example. The report RBCA_COPR_RUN_PP creates and outputs the correspondence based on the correspondence requests. for example. you define the residence time for the correspondence requests depending on the correspondence type. Choose Financial Services  Account Management  Archiving  Archiving Objects  Define Residence Time for Correspondence Types (CORRSPND Object). The PPO business process used is BCA_COPR. It is necessary to monitor correspondence to ensure that all correspondence requests are processed successfully. during termination of an account. you can archive or delete the related correspondence requests. 6. In this activity. use the technical status to select the correspondences that have not been printed. A correspondence request contains the necessary data for printing. for example. Archiving and deletion of correspondence requests helps you to optimize your system performance and to ease the load on your database. during end-of-day processing. On the selection screen of the report. or about periodic events. and should be part of the end-of-day processing.3 Monitoring Report RBCA_COPR_RUN_PP creates PPO orders in case of errors. In addition. To print the correspondence. 6. such as the termination of an account. © 2010 SAP AG page 33/74 . you must schedule the mass run RBCA_COPR_RUN_PP. In addition. in the form of a bank statement.

Best Practice
Operations Concept for SAP Banking Services (Deposits and Loans)

Usage of Technical Status of Report RBCA_CORR_HISTORY to Display Correspondences Not Printed

An additional transaction that you can use for monitoring purposes is transaction SP01 Output Controller.
With this transaction you can check whether all requests sent to the output controller have been processed
successfully.

Status of Spool Request in the Output Controller

© 2010 SAP AG page 34/74

Best Practice
Operations Concept for SAP Banking Services (Deposits and Loans)

6.4 Archiving and Deletion

You have the ability to archive correspondence requests, and you have the possibility to delete
correspondence requests without archiving. You can archive with transaction SARA for the archiving object
CORRSPND. You can delete with report RBCA_CORR_DELETE. Whether a correspondence request can be
archived or deleted depends on the residence type of the related correspondence type.

© 2010 SAP AG page 35/74

Best Practice
Operations Concept for SAP Banking Services (Deposits and Loans)

7 Automatic Postprocessing of Payment Distribution Items
7.1 Purpose

At the end of the day, you must ensure that incoming payments from borrowers are successfully processed.
The processing of incoming payments, for example, the clearing of open items, is done by payment
distribution. Errors can occur during processing. In any scenario, if the payment distribution system
encounters a failure during the clearing process (for example, if the posting date falls before the account
opening date or if the rule set was not found), the payment distribution system sends the payment distribution
items to the Posting Control Office for postprocessing. Some of the Posting Control Orders could be
reprocessed automatically, so human interaction is not always necessary.

7.2 Prerequisites

Payment distribution items are generated by payment distribution when a payment item of any payment type
is posted to a clearing account. Payment distribution items are processed according to the rule set for
payment distribution defined in Customizing or the attached payment distribution directive by report
/FSPD/RIPD_MASS_RUN_PP1.

Also see Customizing: Financial Services  Account Management  Product Management  Payment
Distribution  Define Rules for Payment Distribution.

7.3 Reprocessing

You should run report /FSPD/RIPD_MASS_RUN_PP2 to automatically reprocess failed payment distribution
items. The run can be processed during the day or during end-of-day processing.

Additionally, check the Posting Control Office for failed payment distribution items, because not all failed
items can be reprocessed automatically.

Note: The automatic reprocessing report of the Posting Control Office does not process payment distribution
items.

© 2010 SAP AG page 36/74

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) © 2010 SAP AG page 37/74 .

In the following chapters we will introduce SAP Banking Services customers to the SAP transactions. MassMan is also a data collector for SAP Solution Manager Business Process Monitoring (BPM).1.de/~sapidb/011000358700001878872008E Business Process Performance Monitoring for Banking Solutions https://websmp207. which normally need to be collected using several different transactions.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 8 Monitoring of the Banking Services System It is high priority for the Operations team to monitor the system during nighttime processing as well as during daily processing.1 Performance-Oriented Monitoring and Analysis 8. on one single screen.sap-ag. Besides the daily monitoring of mass runs.de/~sapidb/011000358700001829372008E 8. where all the information from MassMan can be reported and used for automatic alerting. and tools that can be used for performance. Monitoring for SAP Banking https://websmp207.1. Besides the monitoring functionality. You can implement MassMan by applying the latest ST-A/PI package on the relevant satellite system. MassMan is also suitable for performance testing. Also see the following RunSAP Documents: Parallelization.sap-ag. The aim of this functionality is to provide information like parallelization settings. technical. and application monitoring. use transaction ST13 and choose MASS_MAN_MONITORING application with F4 help. Analysis & Service Tools Launchpad © 2010 SAP AG page 38/74 . To open MassMan. reports.1. Packaging. We also provide the necessary information for the Business Process Monitoring for SAP Banking Services that is offered via the SAP Solution Manager.1 MassMan Monitoring Analysis Tool MassMan is a monitoring tool that basically displays the main information about the mass runs (based on the Parallel Processing Framework) that are currently running or have been running on the given system.

MassMan – Mass Run Analysis Tool © 2010 SAP AG page 39/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Always enter a date so old runs are not confused with the list of runs.

PP monitor. and the definition of necessary actions depending on the situation:  Abnormal runtimes (low throughput. like accounts processed successfully or accounts failed o Detailed view of child jobs of a particular mass run o Convenient interface to standard analysis tools (SM37. expected runtime is out of range)  Unusual data volumes  Cancellations of runs  Processing problems (due to data quality) Features:  Cumulated view of mass run information via ALV display: o Status o Duration and estimated duration o Progress o Throughput o CPU and DB usage per server o Number and status of parallel jobs o Amount of processed data with categories. and so on) Historization of data: o To compare behavior of future and past runs o Keep data even for deleted/archived runs © 2010 SAP AG page 40/74 . their analysis. SM66.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Example of a Mass Run The main purpose of MassMan is to ease monitoring of the mass activities on a system and speed up the recognition of problems.

further divided into RFC and HTTP for Dialog. On the screen you can see the statistical performance data from the SAP system. the average response time. Workload Monitor Along with the information for each task type. To collect the statistical records regularly. Update.1. © 2010 SAP AG page 41/74 . you get the number of transaction steps. such as Dialog. you have to schedule and run the RSCOLL00 program (name SAP_COLLECTOR_FOR_PERFORMANCE) every hour as a background job. The Workload Monitor (transaction ST03) displays statistics about response times. Workload analysis can be used to prioritize performance problems and also shows the load distribution for application programs and transactions. you will find a breakdown of statistics on response times and throughput by the different task types. and the average CPU and database time per transaction step. memory use. Background. This information helps you to identify and understand performance problems and possible causes.2 Workload Monitor – ST03 Workload analysis provides a comprehensive overview on throughput and response times. and Spool. You can decide between “total” (for all instances) and the instance itself and select the appropriate time period.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 8. and database accesses for all transaction steps and all SAP components. If you select Workload overview on the left side of the screen.1.

and so on.3 Single Record Statistics – STAD After you have identified programs or single transactions as expensive (for example. database accesses. A screen with the statistical records that match your selection criteria displays: Single-Record Statistics © 2010 SAP AG page 42/74 . The statistical information includes response time.1. These records are collected by the collector RSCOLL00 and are deleted after a certain time. memory requirements.1. after performing a detailed workload analysis) you can start a detailed performance analysis for these programs and transactions by using transaction STAD.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 8.

1. for example. They can be detected via the functionality “List of identical select statements. start the performance analysis.” SQL Summarized Statements Sorted by Duration A suspicious select should be checked in detail by displaying the execution plan. you should perform a second and third SQL trace to deepen your analysis and to get a trace analysis with already buffered data. you identify an SQL statement with a long runtime. through an SQL trace. If. 8. other high CPU times could imply time-consuming calculations. communication problems that have high roll wait times. As a result. © 2010 SAP AG page 43/74 .1. Identical database selects often impact the performance and should therefore be avoided. you can detect. By using transaction ST05 (SQL trace). you trace select statements reading records on database level. Select arguments and indexes chosen by the database or buffer selects should be checked for best performance. If a lot of select statements are processed during your trace. use the summary function of the SQL trace to get an overview of the most expensive SQL statements.4 Trace Analysis – ST05/ SE30/ST12 If a program or a transaction with a critical runtime behavior is identified.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) The single-record statistics allow you to identify a problem that might not be visible in the average values of the transaction profile. Most of the performance issues are based on non-optimal coding or non-optimal database accesses.

Within an ABAP trace. and SQL statements by using transaction code ST12.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) With transaction SE30 (Run time analysis) you can trace ABAP coding by using the name of the program. sort the results by net time first. tracing ABAP code. To begin the analysis for the ABAP trace. you need to switch tracing on or off during the time frame of the performance measurements. You can combine the tools. function module. © 2010 SAP AG page 44/74 . ABAP Trace per Call In both tools. or transaction code. first check if the time consumption is more on database or ABAP level. it is an early sign that select statements should be analyzed in more detail. If database accesses consume more time.

the result can be evaluated via selecting the relevant trace file. based on the time stamp. SAP provides with the Database Monitor. 8. © 2010 SAP AG page 45/74 . traced records are written into a trace file. in transaction SM50 (local work process overview).1. You get database snapshots related to the currently active database processes and the assignment of the database processes to the SAP work processes as shown. for example. Even each database system has its own architecture. transaction ST04 fundamental database analysis and monitoring functions.1.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Select Trace Analyses When you switch on or activate a trace.5 Database Monitor – ST04 SAP supports different relational database systems. After you deactivate or switch off the trace.

the number of logical and physical read accesses per statement. In the “Shared SQL Area” (also called the “Shared Cursor Cache” or “Shared SQL Cache”). in the database interface for the SAP work processes. and the response times. in addition. for example. you find details related to the number of executions of an SQL statement.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Database Monitor The Database Monitor relies on performance data out of the database system and. data collected directly by the SAP system. © 2010 SAP AG page 46/74 . the number of rows that were read.

The main screen of the operation system monitor. The most important buffer in a database system is the “data buffer” or “data cache.1.6 Operating System Monitor – ST06/ OS07 The operation system monitor is a very helpful tool to get an impression of the overall system performance. and CPU. lists the most important performance data for the operation system and the related hardware. For the categories:  CPU  Memory  Disk  LAN  File system © 2010 SAP AG page 47/74 . via transaction ST06 or OS07.1. because non-optimal buffer settings could decrease overall system performance. memory.” which stores parts of the most recently read database tables and their indexes. Program SAPOSCOL renews all data every 10 seconds (if scheduled).Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Shared SQL Area Monitoring the data buffer of the database system is very important. 8. such as hard disk. Reading the buffer is much more effective and faster than reading the data from the hard disks.

Operation System Monitor If the sum of the physical memory and swap space is smaller than the total amount of memory required by the SAP system. the key statistic is the “page-out rate.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) You can check and analyze different key figures. less than 20% of the physical main memory is paged. the time between pressing the key and the screen is available again. like the most UNIX derivates. for example. paging should not be critical for performance if. This enables the system to accommodate temporary workload peaks. You can display these workprocesses with transaction SM50 for the application server on which you are © 2010 SAP AG page 48/74 . The unused CPU capacity should generally be at least 20% per hour. the value is indicated as the “paged-in rate”. the database.1. You get these values by a snapshot--previous hours or the last 30 days--so it is not only possible to get an overview of the current performance situation. You should therefore ensure that there is sufficient swap space available. For asynchronous operation systems like Windows NT. such as utilization. The paging rate should not become too large. this may cause program terminations or even operating system failure. for other operation systems that page only when necessary.1. this processing uses a workprocess. which are used by the dialog or batch processing. For each single process/dialog step. and response times.” 8. but you can also do a review of the last month.7 Workprocess Overview – SM50/ SM66 An SAP instance provides workprocess slots. if you press F8 or Enter within a certain program or report. traffic. every hour. and other programs.

If you watch the work process overview for several minutes and repeatedly choose the REFRESH button to update the overview.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) logged on. The workprocess overview gives you a first impression of the used process slots. If an access on one specific table is very time consuming and the elapsed clock time for the process step increases. Several types of workprocesses are defined. The amount and the allocation of the workprocesses need to be customized to customer needs and application demands. You can get further details and activities of the workprocesses by double-clicking or selecting Process details in the menu (/Process /Details) or by pressing Ctrl+Shift_F11. a further analysis of this process step should be taken into account. You can get additional information about current database accesses of the relevant workprocess in the Action and Table fields in the overview. You can detect insufficient memory consumption via ST02 /Detailed analysis menu /SAP Memory /Mode list by setting focus on the relevant user. You can also check current memory consumption of a certain workprocess by double-clicking on the relevant workprocess ID. © 2010 SAP AG page 49/74 . The main indication of a performance problem for processes is that all the work processes of a particular type (such as DIALOG or UPDATE) are occupied. or with transaction SM66 for all available application servers of the SAP instance (global workprocess overview). you can usually determine whether there is a current performance problem related to the number of work processes in the SAP instance. DIA will support dialog processing and BTC batch jobs or background processing.

and run it Results of an Inspection: After the inspection run is ready.” The respective single objects are then checked with a Default Check Variant.” “Function module. reliability. The inspection results are arranged in a tree. To check a number of objects.1.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Work Process Overview 8. where “Object” stands for “Program. Open the result tree by clicking on the folders.1. Each message contains: © 2010 SAP AG page 50/74 . The leaves of the tree are the check messages. security. function builder (SE37). click Results. You will get a list of identified code lines by using standardized searching methods.8 SAP Code Inspector – SCI The Code Inspector is a tool for checking static ABAP coding and DDIC objects (generally: TADIR objects) under aspects of performance. To call the Code Inspector for a single object from ABAP editor (SE38). use transaction SCI to:  Create an Object Set that contains your objects  Create a Check Variant containing the checks you want to execute on the objects  Create an Inspection combining the Object Set with the Check Variant. or the class builder (SE24) choose Object  Check  Code Inspector from the menu. for example all objects of a package. All results need to be checked in detail before modifying it. and statistical information.” or “Class.

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans)  The source code position (or name of the TADIR object)  A short explanatory text For further explanation:  Click the information icon in front of the message . Code Inspector: Inspection Results © 2010 SAP AG page 51/74 .  Double-click the message text to attain the inspected object.

© 2010 SAP AG page 52/74 .1. SAP Extended Memory (EM). where up to 10.de/~sapidb/011000358700000486422009E 8. and the SAP Heap Memory. A static tool cannot replace the developer’s knowledge of a program. a displacement should not occur (an exception is the program buffer.ST02 You can check the usage and size of the SAP memory areas via transaction ST02 (SAP Memory Configuration Monitor). For SAP buffers.2 Technical-Oriented Monitoring and Memory Analysis 8.sap-ag. After starting the SAP Memory Configuration Monitor for the instance. Also see RunSAP Document: Manage Code Quality with Code Inspector https://websmp207. It displays information on configuration and utilization of the SAP buffer. The Extended Memory or Roll buffer should not become full.1. SE30 (Runtime Analysis). Use ST05 (SQL-Trace).000 displacements is still okay). the main screen Tune Summary appears.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Inspection Results: Help Text for a Message Note: Code Inspector can only inform you that some coding might slow down performance. and/or ST30 (Global Performance Analysis) to trace your running code.1 SAP Memory Configuration Monitor .2.

and the program buffer). Therefore. You can access detailed information that is related to the termination to analyze the cause of the ABAP program dump. © 2010 SAP AG page 53/74 . It is also important that you monitor the SAP Memory with the areas Roll area. you can display the current system settings. By choosing Current Parameters. In the SAP Memory section. If buffers are too small.2.ST22 By executing transaction ST22 you can check if ABAP program dumps occurred on the SAP system.1. and Heap Memory. the database has to be accessed often to reload data. Extended Memory. With the Detailed Analysis Monitor. you should check that the hit ratio for the buffers is 98% or higher (exceptions are the single record buffer. A minimum buffer quality is required to ensure smooth operations of the SAP system. 8. the export/ import buffer.2 ABAP Dump Analysis . Paging Area. allocated memory space. you can find information for the current and max use of memory. free space. you have the possibility to call other monitors and can retrieve more detailed and historical information regarding the buffers. and swaps.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Main Screen of the Memory Configuration Monitor (Tune Summary) In the SAP Buffer area you can find details like hit ratio.

In the System Environment area.2. you can get details on memory consumption. SysLog distinguishes between messages.1. the SysLog gives you the ability to evaluate system messages that are written to a protocol to perform a detailed analysis in case of errors. which could therefore lead to performance problems. Every instance has its own SysLog. warnings. You can get detailed information about the user that has caused the error or the erroneous transaction. © 2010 SAP AG page 54/74 . for example. and Basis developer view.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) ST22 Dump with Coding Detail Screen You can get information for different views.SM21 In addition to ST22 (ABAP Dump Analysis). and errors.3 System Log . 8. by large internal tables. ABAP developer view. such as User view. High memory consumption could be caused.

fine-tuning of the system. the CCMS gives the system administrator central functions in regard to dynamic load distribution. If a value of a monitored attribute is exceeded. You can monitor your chosen attributes by setting thresholds. The following objects can be monitored:  Background Processing  Buffers  Communication © 2010 SAP AG page 55/74 . the value will be displayed as yellow or red.2. Along with some other technical functions. batch job processing. Via the RFC connection. The results of the CCMS should be checked by the system administrators as part of their daily work.4 Computing Center Management System – CCMS/ RZ20 CCMS is another function to configure and monitor the technical status of an SAP system. you can also monitor other systems with different releases.1.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) SysLog SM21 8. and system monitoring.

2.5 Analyze Memory Consumption .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans)  Database  Dialog Overview  Dialog per Application Server  Enqueue  Entire System  File systems  Operating System  Performance Overview  Spool System  Syslog  System Configuration  System Errors To enable the auto-alert mechanism of CCMS. This is particularly the case in the testing and production phases. such as internal table. where you want to check and optimize memory consumption for the best system performance.  Call method CL_ABAP_MEMORY_UTILITIES => WRITE_MEMORY_CONSUPTION_FILE (…) out of your individual ABAP program.S_MEMORY_INSPECTOR You use the Memory Inspector if the programs can already access certain datasets. Therefore. you can analyze the result using the Memory Inspector.1. In the upper area of the screen. choose /System /Utilities /Memory /Analysis /Create Memory Snapshot. You should use this option only for testing purposes. 8. and anonymous data objects will be considered from the Memory Inspector. © 2010 SAP AG page 56/74 . It is also possible to compare two different snapshots to determine which internal table will grow excessively. strings. This tool (transaction S_MEMORY_INSPECTOR) is used to analyze memory snapshots. After the memory snapshot is created. you find all available snapshots and you need to select your snapshot by choosing a user and a relevant time stamp. You can create a memory snapshot by:  Use code /HMUSA in the command field. objects.”  Out of the menu path on top of your local GUI. avoid excessive or frequent use of this method out of an ABAP program. You will get confirmation with message “File abDbgMemory_001_000x created. see SAP Note 617547. dynamic data objects.

de/~sapidb/011000358700000491282008E © 2010 SAP AG page 57/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) You can also use the Memory Inspector during performance analysis for internal tables processing. please see chapter 2.6 Transactional RFC – SM58 You should use transaction SM58 (transactional RFC) on a regular basis when there is RFC communication between applications. Errors in between Application Components. If necessary.2. 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. you can re-start the transfer from the SAP Banking Services system after the problem is solved (it is also possible to perform it in debugging mode). Also see RunSAP Document: RFC Monitoring https://websmp207.com/saphelp_nw2004s/helpdata/en/a2/e5fc84cc87964cb2c29f584152d74e/frameset.sap-ag.sap.htm 8. in the best-practice document Best Practices for End-of-Day Processing - Exception Handling. For more information.6.1. Memory Inspector Also see SAP Documentation: Memory Inspector http://help.

8 Snapshot Monitoring /SDF/MON You can create SM50 snapshots within a predefined interval by using the Snapshot Monitoring /SDF/MON. you can get details for:  Used work processes  CPU consumption © 2010 SAP AG page 58/74 . With this report.6. you can use transaction SXMB_MONI for monitoring and analyzing.1. because you do not have the required authorization. For more information about the use case of SXMB_MONI.Exception Handling (https://websmp207.1. the system only displays XML messages for the current client.Integration Engine – SXMB_MONI For message processed via the Process Integration Server (PI). specify status group Errors and follow your guidelines for troubleshooting.2. If too many messages come up. 8. Message Monitoring via SXMB_MONI You cannot execute options in the menu that have the locked symbol. Report /SDF/MON is included in the ST-PI package. The authorizations for the individual functions are tailored to requirements and are assigned as derivations of the role SAP_XI_MONITOR. You can use this functionality for performance testing within a certain time frame or to analyze overall system performance during an error behavior. follow chapter 2. They are all based on the authorization object S_XMB_AUTH. Select the monitor for XML messages and specify the relevant time interval.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 8. in the best-practice document Best Practices for End-of-Day Processing .7 Message Monitoring. Errors in between Application Components.sap-ag. Authorization object S_XMB_DSP controls the display of the message content. Unless the user has the authorization S_XMB_ADM (administrator).de/solutionmanagerbp).2.

Next. © 2010 SAP AG page 59/74 . As a first step. you can define several details that will be stored during the snapshots. you need to schedule the monitoring. you should define a description of your monitoring session and set the time interval between two snapshots. for a longer monitoring session. or of a certain report that needs to be analyzed regarding performance. define the start time and end time for the session.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans)  Allocated and free space of the different memory areas Before snapshots are taken. it is recommended that you use a higher value like 60 seconds. The default value is 10 seconds. or even more. You can also schedule the monitoring session for the next overnight processing to get details of your system performance during the EoD processing. Finally. To start the Snapshot Monitoring. check and define intervals for the different values that are stored during the monitoring session.

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) You can monitor and analyze the session immediately or later by selecting the relevant session in the selection screen of the report. Below is an example of a monitoring session with a snapshot every 60 seconds. © 2010 SAP AG page 60/74 .

use the report to solve an issue or to get an impression of your system performance during testing or execution of mass runs. In parallel.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) You can display details by double-clicking on the different values. The monitor is available in all systems using SAP Basis 620 or higher.1. along with other details. This monitoring functionality is not intended to be used 24 hours per day.3. you get an overview of the relevant active processes shown by SM50 – Process overview. RBANK_PP_MONITOR shows the status of the currently running jobs and how many packages are already processed in percentage rate. 8.1 Parallel Processing Monitor .1.RBANK_PP_MONITOR You can monitor reports developed based on the PPF (Parallel Processing Framework) by using the RBANK_PP_MONITOR report started via SE38/SA38 or started via transaction BANK_PP_MONITOR. © 2010 SAP AG page 61/74 .3 Application-Oriented Monitoring 8.

8. If errors occurred. Also see SAP Note 1418333 related to this topic. you will find the entries marked in red after the processing of the mass run. Mass Run Monitoring with Transaction BANK_PP_MONITOR.3. After a successful run. the monitor shows how many packages.2 Job Overview – SM37 You get the Job overview of all running. © 2010 SAP AG page 62/74 . in %.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) After the mass run has been successfully processed. You can see currently processed packages in the monitor in the Packages Collected field. It will show only currently running jobs or jobs processed with errors. scheduled. First you need to provide details on the selection screen. are already processed. In the Processing Status field. no more run information can be found in the monitor. Related to the RBANK_PP_MONITOR check. 8.1. deletion report RBANK_DELETE_RUNS deletes process data that was created to process the job within this framework. The Table Data field shows the total number of packages and Packages Init shows the packages that are waiting for processing. released and finished batch jobs in your SAP environment by using transaction SM37. Further details are provided in the document Best Practices for End-of-Day Processing – Exception Handling in chapter 2. this data is not longer needed and can be deleted using this report.

Press F8 or the button to get a detailed list with your selection parameter in the header. you usually select jobs by name of the job. and often the time frame of the processed job or the planned start time. You use this tool to monitor batch jobs during processing to get details of their status. status of the job. to check for runtime and related details of a job. © 2010 SAP AG page 63/74 . to ensure successful processing.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) To see the relevant details of the job. or to schedule jobs for a certain time in the future. name of the user.

job log details.de/~sapidb/011000358700001250602005E 8. Whether success messages are written to the application log depends on the settings in the selections screen of the mass run.sap-ag. The screen only shows a snapshot with selected parameters.1. press F8 to refresh.3 Display Application Log – SLG1 You can analyze the system application log via transaction SLG1. The system logs statistical information about the mass run (number of processed and successful objects).3. Also see RunSAP Document: Job Scheduling Management https://websmp207.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) If a job is finished. error messages for all problems that occurred. Application logs are generated for all application processes based on SAP PPF. © 2010 SAP AG page 64/74 . you can see the duration of the job in seconds. and success messages (if enabled). and if a spool file has been written. if you want to view the current situation.

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) For testing purposes. The log entries are ordered by date/time/user. but during production it is recommended that you have only one success message per object (if at all). There is an individual transaction to display the application log for each mass run in Banking Services. At first glance.12. In this selection screen all settlement mass runs from 01. If you choose Log Off (no message). all entries with the same external ID belong to one mass run. there will not only be no success message. which is described in detail below. transaction BCA_ACBAL_MASS_LOG to display all application logs of the account settlement mass run. the log entry with sub-object Statistical Data is important. You can find these transactions in the Easy Access menu by choosing Account Management  Logs. This is a good way to start analyzing logs depending on date and application. All log transactions have the same look and feel and are based on transaction SLG1. The difference between the transactions is that some parameters.2009 of user C5128636 are selected. which makes it easier to select only the logs you are interested in. This setting is not recommended. it is fine to choose all messages. for example. If you double-click on the line. you © 2010 SAP AG page 65/74 . are filled by default. like Program and External ID. but also no error message in the log and no messages in the postprocessing orders (the creation of orders is independent).

you can find all additional messages for the objects under sub-object Information. Erroneous and successful objects are listed in the entries with sub-object Normal error and Success message. In statistical data. and number of processed and successful objects). you can see all administrative data about the mass run (job IDs. © 2010 SAP AG page 66/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) receive details as displayed below. parameter values.

© 2010 SAP AG page 67/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Red lighted items show errors. You can display long texts by double-clicking on the item.

Check the affected tables BALDAT. You can delete some types of data from your system soon after creation. With SAP Note 706478. application files. BALMP and BALC regarding their growth and unnecessary entries. BALM. In some applications.1 Cross-Application Housekeeping Different kinds of files are created within a SAP system and its related database: working files. not only Banking. These jobs are processed automatically. Especially during mass runs.1.1 Deletion Report for RBANK_PP_MONITOR Process Data There are also some banking-specific housekeeping runs. © 2010 SAP AG page 68/74 . also see chapter 3. Different applications. There you will find application-independent reorganization jobs for jobs (RSBTCDEL2). for example. Reorganization Jobs • 706478 (release-independent): Preventing strong growth of basis tables 9. JBDCPPOS2. and many more. or related to the CML loans solution “Change pointers for loans” with tables VDCHGPTR. change pointer tables. spool entries (RSPO0041/1041).3 in this document. these tables could get a huge number of warning and/or error messages. ABAP Dumps (RSSNAPDL). You should regularly delete or archive data from. log files. See SAP Note 16083 (release-independent) for standard and reorganization jobs related to this topic. Not performed housekeeping jobs could negatively influence overall performance. directories. You need to perform housekeeping manually and automatically to remove any of the files that are no longer required. will write message items into the application log tables. You should carry out reorganization of the data discussed in this section at regular intervals. Check SAP Notes: • 16083 (release-independent): Standard Jobs. Most of these housekeeping jobs are not related to the banking solution and are also required in a non- banking system on a regular basis. like the deletion run of the PPF Monitor (transaction BANK_PP_MONITOR or report RBANK_PP_MONITOR).2 Banking Services System Housekeeping 9.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 9 Housekeeping of the SAP Banking Services System 9.1. The objects to be processed by a mass run using this framework are split into several packages and each package is processed within its own work process. BALHDR. JBDCPHDR2.1. In earlier releases. you can monitor mass runs using the parallelization framework (PPF). With this functionality. it is necessary to schedule these jobs manually. application log tables. For more information. you get an overview of the administrative basis tables that may become big. you can filter which message is stored and which message will be avoided in the application log. BALHDRP.2. TemSe tables. and so on.

1. 9.2. Some customers have already included this report in their end-of-day process. every change of the product pricing list should be adapted to every related contract by using report R_BCA_PRI_PP_PACKAGE_CN via transaction BCA_PRI_PPL_CN_M.1.4 Check Financial Conditions Customizing Use report RFICO_CUSTOMIZING_CHECK on a regular basis to check customizing of the financial conditions. it is deleted using the deletion report RBANK_DELETE_RUNS. If an already created condition group type or condition type needs to be changed. If this report is not included in the EoD. the process data is needed for analysis. you can find several reports for deleting data via delete object. you need first to check if it has already been used in production.1. NEVER CHANGE A USED CONDITION GROUP TYPE OR CONDITION TYPE! 9. this report could also be processed in batch (SAP NetWeaver 710 and 711). Data that is no longer required in the operational system is deleted to improve performance in the operational database. The following objects are currently available:  Account Management  Archiving  Data Deletion o SNITEM – Non-Balance-Changing postings o GL_BALANCE – Financial account balances o GL_BALPREP – Balance sheet preparation data o GL_SUMS – FI totals records o INVENTORY – Inventory data o RECONC – Reconciliation data o PRENOTE_T – Technical Prenotes The delete programs delete the data records of the deletion object from the operational database.2 Deletion Report for “Account Settlement” Simulation Data A simulation run is available for the “Account Settlement” functionality. The results of the simulation run are stored in table BKK92_SIM. If it has already been used. it should be taken into account to run this report once per week to prevent possible errors or incorrect calculations because of non-adapted contracts. For mass runs with errors.2. With changes by SAP Note 1439952. If the data is no longer needed. 9.2. do not change it.1.3 Adapt Product Pricing List to Related Contracts Report If the functionality of pricing is used. 9.2. © 2010 SAP AG page 69/74 .Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) The process data is deleted if the mass run has been processed successfully. You can delete the entries of table BKK92_SIM with report RFBDELSIM.5 Delete Reports in Account Management via Delete Objects In the SAP-Menu.

the delete program generates an application log containing statistical data and simultaneously writes the current status in an activity log. Also check SAP Note 1312823 with the attached PDF document General Ledger Transfer with Sub ledger in Account.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) During the process. © 2010 SAP AG page 70/74 . You can use the archiving monitor to display both logs and monitor the progress of the process flow. Check prerequisites and customizing before running the delete programs for the first time.

de/~sapidb/011000358700000671032009E Job Scheduling Management https://websmp207. Packaging. Monitoring for SAP Banking https://websmp207.de/~sapidb/011000358700001829372008E Exception Handling in Banking Services https://websmp207.sap-ag.de/~sapidb/011000358700001878872008E Business Process Performance Monitoring for Banking Solutions https://websmp207.de/~sapidb/011000358700000491282008E Manage Code Quality with Code Inspector https://websmp207.sap-ag.sap-ag.sap-ag.1 Overview of the Most Important Best Practice Documents End of day/ Batch Processing Deposit Management https://websmp207.de/~sapidb/011000358700000671072009E 10.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) 10 Background Information and References 10.2 Overview of the Most Important Transactions The most important transactions for Operations and Monitoring on the Banking Services system are summarized below. 50 ST06 Operating System Monitor (server dependent) 45 ST12 Trace Analysis 40 ST13 -> Mass Man Monitor for Batch jobs based on PPF 37 MASS_MAN_MONITORING tool © 2010 SAP AG page 71/74 .sap-ag. Performance-Oriented Monitoring Transactions: Transaction Description Page OS07 Operating System Monitor (server in-dependent) 45 SCI SAP Code Inspector 48 SE30 ABAP Trace Analysis 40. 50 SM50 Workprocess Overview (instance/ server based) 46 SM66 Workprocess Overview 46 STAD Statistical Records 39 ST03 (N) Workload Monitor 38 ST04 Database Monitor 43 ST05 SQL Trace Analysis 40. 41.sap-ag.sap-ag.de/~sapidb/011000358700000486422009E Parallelization.de/~sapidb/011000358700001250602005E RFC Monitoring https://websmp207.

Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) Technical-Oriented Monitoring Transactions: Transaction Description Page RZ20 Computing Center Management System 52 S_MEMORY_INSPECTOR Memory Inspector 53 SM21 System Log 52 SM58 Transactional RFC Monitor 54 ST02 SAP Memory Configuration Monitor 50 ST22 ABAP Dump Analysis 51 SXMB_MONI Message Monitoring – Integration Engine 55 /SDF/MON Snapshot Monitoring 55 Application-Oriented Monitoring Transactions: Transaction Description Page BCA_PPOx (2. 38.3) Post Processing Change/ Display for Master 11. Job Frequency Description Page Automatic processing of PPO multiple times a orders after errors has been /SAPPO/RESUBMIT_ORDERS_2 17 day solved or unlocks has been done Collect statistical records RSCOLL00 Every hour 39 automatically Evaluate system message for System Log Daily (minimum) 52 each instance Monitor technical status of the CCMS / RZ20 Daily (minimum) 52 system SXMB_MONI Daily (minimum) Check erroneous PI messages 55 Closed PPO order will be /SAPPO/DELETE_ORDERS Daily 17 deleted Check for open items not RBCA_PAYMITEM_CLEARING_LIST Daily 23 cleared Posting Control Office Daily Check and process erroneous 25 © 2010 SAP AG page 72/74 .3) Post Processing Change/ Display application 9.3 Overview of the Most Important Regular Jobs The most important jobs on the Banking Services system are summarized below.3) Post Processing Office Display/ Change for 10. 18 Contract Management PLM_PPOx (2.3) Post Processing Change/ Display for Posting 11 Log Management RBANK_PP_MONITOR Monitor for jobs based on PPF tool 7. 59 /n/SAPPO/PPOx (2. 18 Account Management MCM_PPOx (2. 11. 12. 65 SLG1 Display Application Log 16. 11 component independent 10. 62 SM37 Job Overview 7. 61. 58. 59.

after EoD occurred during the end-of-day 8 processing via PPO orders Check RFC communication Transactional RFC Daily 54 errors Delete administrative data of RBANK_DELETE_RUNS Monthly 20. 66 mass runs © 2010 SAP AG page 73/74 . 59.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) payment items For daily monitoring and MassMan Monitoring Daily 36 performance testing Post processing of errors Postprocessing Office Daily.

BatchPipes. S/390. World Wide Web Consortium. eServer. either express or implied. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Best Practice Operations Concept for SAP Banking Services (Deposits and Loans) © Copyright 2010 SAP AG. RETAIN. z/OS. Inc. Outlook. including but not limited to the implied warranties of merchantability. System z10. DB2 Universal Database. BladeCenter. System z. GPFS. Business Objects and the Business Objects logo. z/VM. Excel. XML. SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. The information contained herein may be changed without prior notice. developments. Xcelsius. HTML. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. MVS/ESA. and Motif are registered trademarks of the Open Group. POWER6+. z9. Massachusetts Institute of Technology. xSeries. Program Neighborhood. ByDesign. Java is a registered trademark of Sun Microsystems. product strategy. National product specifications may vary.S. MetaFrame. Inc. Oracle is a registered trademark of Oracle Corporation. This document contains only intended strategies. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. Adobe. copied. links. SAP assumes no responsibility for errors or omissions in this document. Power Architecture. iSeries. DB2. indirect. POWER. and MultiWin are trademarks or registered trademarks of Citrix Systems. AS/400. used under license for technology invented and implemented by Netscape. OSF/1. VideoFrame. XHTML and W3C are trademarks or registered trademarks of W3C®. System i. POWER5+. WinFrame. OpenPower. System i5. Crystal Decisions. and PowerPoint are registered trademarks of Microsoft Corporation. PostScript. Linux is the registered trademark of Linus Torvalds in the U. SAP. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. System p. Web Intelligence. or consequential damages that may result from the use of these materials. graphics. the Adobe logo. HACMP. X/Open. All other product and service names mentioned are the trademarks of their respective companies. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. PowerVM. SAP NetWeaver. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. All rights reserved. pSeries. This limitation shall not apply in cases of intent or gross negligence. © 2010 SAP AG page 74/74 . zSeries. and/or development. i5/OS. Netfinity. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. or non- infringement. IBM. S/390 Parallel Enterprise Server. fitness for a particular purpose. or other items contained within this material. OS/390. System p5. Inc. Intelligent Miner. OS/400. UNIX. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. Citrix. JavaScript is a registered trademark of Sun Microsystems. Redbooks. PartnerEdge. SAP does not warrant the accuracy or completeness of the information. z10. Crystal Reports. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Data contained in this document serves informational purposes only. OS/2. text. POWER6. Microsoft. AIX. The statutory liability for personal injury and defective products is not affected.. System x. POWER5. Duet. System z9. RACF. R/3. This document is provided without a warranty of any kind. Windows. PowerPC. Clear Enterprise. SAP shall have no liability for damages of any kind including without limitation direct. DB2 Connect. The information in this document is proprietary to SAP. and other countries. ICA. Please note that this document is subject to change and may be changed by SAP at any time without notice. Parallel Sysplex. special. Acrobat. System Storage. WebSphere. BusinessObjects. No part of this document may be reproduced.