Your SlideShare is downloading. ×
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
128 mass data_generator_for_banking
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

128 mass data_generator_for_banking

169

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
169
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Best-Practice Document SAP Mass Data Generator for Banking Dietmar-Hopp-Allee 16 D-69190 Walldorf DATE VERSION August.2011 4.0 SOLUTION MANAGEMENT PHASE SAP SOLUTION Setup Operations SAP Banking Services TOPIC AREA SOLUTION MANAGER AREA SAP Solution Management Configuration Management© 2011 SAP AG
  • 2. Best-Practice DocumentSAP Mass Data Generator for BankingTable of Contents1 Management Summary 3 1.1 Goal of Using This Service 3 1.2 Alternative Practices 5 1.3 Staff and Skills Requirements 5 1.4 System Requirements 6 1.5 Duration and Timing 6 1.6 Case Study or Sample Scenario 72 Best-Practice Document 9 2.1 Preliminary Tasks 9 2.2 Procedure 11 2.3 Starting SAP Mass Data Generator for Banking 11 2.3.1 General Start Screen 12 2.4 Scenario Startup 13 2.4.1 Scenario: Master Data Creation 13 2.4.2 Scenario: Accounts Creation 20 2.4.3 Scenario: Payment Items 22 2.4.4 Scenario: Standing Orders 32 2.4.5 Scenario: Payment/Forward Orders 36 2.4.6 Scenario: Master Contracts 40 2.4.7 Active Monitoring 43 2.4.8 Application Logs 46 2.4.9 Restart Functionality 463 Further Information 47 3.1 Troubleshooting 47 3.1.1 Ineffective Configuration Changes During Monitoring 47 3.1.2 Inserts into Change Pointer Tables 47 3.1.3 High Level of Parallelization 48 3.2 Background Information and References 48© 2011 SAP AG page 2/49
  • 3. Best-Practice DocumentSAP Mass Data Generator for Banking1 Management SummaryMany banking projects face the challenge of creating mass test data to evaluate new business scenarios andtest new functionality in a realistic productive environment. From a performance perspective, optimized corebusiness processes for productive environments are the key requirement for any successful operation in abanking system.In a typical banking project, the system landscape consists of various SAP solutions. Peak times of a bankingsystem are usually end-of-day, month-end, quarter-end, and year-end processing, when high data volumesare transferred and need to be processed in short time frames. For example, banks may need to runsettlement on millions of accounts during the quarter-end processing and still have to fulfill their dailybusiness like money transfer from and to the ATM. The requirement on hardware is to process increasingworkload during peak time within the given time frame.SAP offers the SAP Mass Data Generator for Banking, an easy-to-use and transparent tool for creating highdata volumes, to help banks to simulate peak times and test their critical process chains with mass volumes.The SAP Mass Data Generator for Banking for banking offers the following key advantages:Reduce Infrastructure Expenses – Find optimal workload settings for your systems by using SAP MassData Generator for Banking dynamic functionality for changing your process settings on the fly and observingthe impact on your system as soon as the changes are applied.AImprove Data Quality – Improve quality of development and testing activities by using business-relevant andup-to-date mass data for testing.Increase Efficiency – Increase your system performance from the beginning by working in an environmentwith expected end-state data volumes.Decision Support – Effectively simulate new business scenarios in your specific environment using highdata volumes before making critical business decisions.It often takes longer to create data to test your solution than to write the code for it. It is extremely timeconsuming to ensure correct data formats and object relations. SAP Mass Data Generator for Banking canreduce these efforts significantly. It is easy to use, created for the SAP for Banking customer, and highlyefficient when it comes to real mass data creation.1.1 Goal of Using This ServiceThis document focuses on the best practices and the advantages of applying SAP Mass Data Generator forBanking when facing the challenge of handling high application data volumes efficiently. The objective of thedocument is to enable the customer to set up, configure, and operate the SAP Mass Data Generator forBanking. This service can help banking customers to better test and plan their mission-critical processes.Following our Run SAP recommendations means implementing best-practice documents that will help you toreduce test preparation efforts and will allow more efficient test planning and later operation of your bankingsolution. The SAP Mass Data Generator for Banking approach and the proven method of E2E solutionoperations are aimed at technical risk management.© 2011 SAP AG page 3/49
  • 4. Best-Practice DocumentSAP Mass Data Generator for BankingYou can improve the IT decision processes and therefore lower costs by getting information aboutperformance impacts and data growth sooner and to a broader degree during the implementation project.This document gives guidance on how IT decision makers can take advantage of generated mass data forSAP for Banking solutions.Efficient operation of high data volumes depends on the right selection of tools, optimized processes, and theskill set of people involved. Focus on this topic should be set before real mass data has to be processed in aproductive environment. The SAP Mass Data Generator for Banking tool provides the functionality togenerate high data volumes for early performance optimizations and data volume management tests.SAP Mass Data Generator for Banking enables you to create a future productive environment for your corebanking processes. Productive data can be extracted from template transactional data and template masterdata of a small system and can be replicated long before real mass data migrations are possible. This isshown in the next figure.FIGURE 1-1: M ASS DATA CREATIONThe concept is comparable with the more common SAP Test Data Migration Server (TDMS). The differenceis that TDMS tries to specifically select from a huge system, where SAP Mass Data Generator for Bankingselects from a small system to create a future mass data scenario.© 2011 SAP AG page 4/49
  • 5. Best-Practice DocumentSAP Mass Data Generator for BankingThe SAP Mass Data Generator for Banking can effectively help in the following banking scenarios: 1. End-of-day (EOD) processing – This is one of the most important business processes in banking system. It is especially critical at month end because month-end activities (like settlement) have to be performed for each active account, which results in the processing of high volumes in a short period of time. Being able to quickly and efficiently produce relevant large test data volumes to simulate and optimize EOD runs in peak times is the great advantage SAP Mass Data Generator for Banking offers. It is particularly useful for initial performance measurements and benchmarking of the customer specific EOD process, especially to test the performance of customer developed reports in the EOD job chains. 2. Volume and stress tests for online services – Managing and efficiently processing online transactions of any kind is the core of any banking system. SAP Mass Data Generator for Banking can help you create large volumes of master and transactional data for the stress tests, so you can efficiently configure your system to be able to handle high peaks and volumes. Creating the transactional data with SAP Mass Data Generator for Banking can also be a stress test in itself.1.2 Alternative PracticesManual data creation is a very time-consuming task and prone to human error. There are already severaltools and frameworks available to create test data, so why do you need a new tool? All other approacheshave specific focuses.The most simple solution for creation of mass data—a system copy—can only be used in late project phases,when sufficient data is created for at least one system (or client), which is very often already too late.There are other generic test data creation tools available. The most common one—and since integrated inSE80, the most most widespread—is eCATT, SAP’s automated testing framework. eCATT provides easy-to-use features like recording and replaying on a transaction basis. However, it does not provide a parallelprocessing framework, and replaying transactions has been proved to be relatively slow. Thus it is notsufficient for handling mass volumes.For extracting specific test data out of existing SAP installations, a newer approach called SAP Test DataMigration Server (SAP TDMS) is available. It works closely on data storage level and provides transparentviews for extraction and mappings. However, it requires already existing data from a source system, so is anappropriate tool for later project phases.1.3 Staff and Skills RequirementsIn a typical bank IT-operation environment, two roles exist. All three are relevant for the SAP Mass DataGenerator for Banking service. Role Responsibility Function support Define business requirement, solve business issue. SAP Basis System administration, maintain solution landscape, monitoringTABLE 1-1 ROLES AND RESPONSIBILITIES© 2011 SAP AG page 5/49
  • 6. Best-Practice DocumentSAP Mass Data Generator for BankingThe functional support team is responsible for the definition of IT processes, in particular those with high datavolumes. The function support team needs to define the most critical processes and appropriate servicelevels for these processes. With SAP Mass Data Generator for Banking, we offer a tool that allows earlytesting of critical processes with high data volumes.1.4 System RequirementsThe SAP Mass Data Generator for Banking is available for the following SAP components. SAP Component SAP Component SAP Component Description Version FSAPPL 100, 200, 300 SAP for Banking 5.0, 6.0, 7.0, 8.0 TABLE 1- 2 REQUIRED COMPONENT RELEASE1.5 Duration and TimingSAP recommends implementation as soon as functional implementation provides real, customer-specificbusiness objects. This is usually already possible during an early stage in the implementation project. Thenext picture depicts two ideal points in a project when the SAP Mass Data Generator for Banking servicebrings the highest value.FIGURE 1-2: RECOMMENDED TEST PROCESS OF SAP-CENTRIC SOLUTIONSSAP Mass Data Generator for Banking is provided as a transport request, which can be obtained from theSAP AGS, Global Banking team directly. To establish contact, you can either ask your support advisor ortechnical quality manager, or open a customer message for component SV-SMG-SER.© 2011 SAP AG page 6/49
  • 7. Best-Practice DocumentSAP Mass Data Generator for BankingThe following duration and effort estimation are given as guidelines for an initial implementation of SAP MassData Generator for Banking and test data generation for the relevant scenario: - Setup of SAP Mass Data Generator for Banking in system landscape will take up to two days. - The implementation of customer-specific requirements will require additional effort. The effort can be estimated only after the requirements have been made and the complexity of the change has been analyzed. The main effort is usually to define objects to be generated in the customer system. This will be done in an initial workshop and will be implemented within the successive delivery phase.Because there is the need to adapt existing implementation quickly and flexibly, SAP Master Data Generatorfor Banking is provided with full access to its source code as customer report. After this service you ―own‖your version of SAP Mass Data Generator for Banking for Banking, adapted to your specific requirements.You will know the implementation details and will be able to execute changes within the processing logic onyour own. The principal structure of this service delivery is depicted in the following figure. Initial Setup Ongoing Workshop Results  Obtain software packages  Define requirements on business objects to generate • Real application mass data as defined  Adapt system settings  Implement changes • Wrap-Up  Execute runs Summary of findingsFIGURE 1-3:FIGURE 1-3: PRINCIPAL SERVICE DELIVERY • ReportIn an initial phase of one to two days, relevant packages are be transported intoAction Plan and manual your system Recommendationssteps are carried out to enable your system environment for SAP Mass Data Generator for Banking. In asecond step, we initiate a workshop to define customer requirements in detail. This includes definition ofrequired data volumes, time frames for data creation, and the structure of the business objects. With thisknowledge we can implement changes on your system and start creation of mass runs. We roughly expect aduration of up to two weeks until useful test data is available at your disposal.1.6 Case Study or Sample ScenarioAn SAP for Banking customer has developed a custom job for processing mass payments and debit orders.To performance test this job and check if the current system sizing allows this critical job to finish within onehour during the peak day of end-of-day processing, the customer needed to create two million savingsaccounts. These accounts must also have a positive balance on them, so the debit orders can be sucessfullyprocessed.© 2011 SAP AG page 7/49
  • 8. Best-Practice DocumentSAP Mass Data Generator for BankingThe migration of the two million accounts from the legacy system was not possible because the migration toolwas not yet finished.Using alternative test data creation practices, for exampel eCATT, was not an option because would take toolong to create 2 million accounts.SAP Mass Data Generator for Banking was the tool of choice because it could create the necessary dataefficiently.  Master data scenario was used to create two million business partners and two million savings accounts with customer-specific product and financial conditions.  Payments scenario was used to post payments on the created accounts.The custom developed mass payment job for processing debit orders was successfully run and tested forperformance.The same data was used later for performance testing other customer processes.© 2011 SAP AG page 8/49
  • 9. Best-Practice DocumentSAP Mass Data Generator for Banking2 Best-Practice Document2.1 Preliminary Tasks  Obtain SAP Mass Data Generator for Banking from SAP AGS Global Banking team. SAP Mass Data Generator for Banking is not delivered as a part of the standard SAP for Banking serviceinstallation. It is delivered on request as a separate transport request file which can be then imported into anSAP Banking Services system. At the beginning, we will consult you on how to use SAP Mass DataGenerator for Banking and provide the necessary knowledge transfer and a handover. One or two days arenecessary for this step.  Create template data in the system. To start using SAP Mass Data Generator for Banking, you need to create template data in the system.This includes: 1. Business partner with, at least, roles Account Holder and Correspondence Recipient 2. Account of any product type – Account holder should be the business partner created in step 1. a. In case of a loan account, to be able to automatically disburse the newly created account, a payment advice for disbursement needs to be created. 3. Standing order – Create one or more standing orders for the account created in step 2. 4. Payment order/forward order – Create one or more payment/forward orders for the account created in step 2. 5. Master contract – Create one or more master contracts with all needed participating accounts.© 2011 SAP AG page 9/49
  • 10. Best-Practice DocumentSAP Mass Data Generator for BankingFor example:FIGURE 2-1: BUSINESS PARTNER TEMPLATE© 2011 SAP AG page 10/49
  • 11. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-2: MASTER CONTRACT TEMPLATE2.2 ProcedureSAP Mass Data Generator for Banking consists of six independent scenarios. These are: 1. Master data scenario – Creating business partners and accounts 2. Account scenario – Creating accounts for already existing business partners 3. Payment items scenario – Creating payment items (recipient, ordering party, or turnover items) 4. Standing orders scenario– Creating standing orders for already existing accounts 5. Payment/forward orders scenario – Creating payment or forward orders for already existing accounts 6. Master contract scenario – Creating master contract and all participating account for already existing business partnersThe following chapters contain more details about each of the six scenarios.2.3 Starting SAP Mass Data Generator for BankingYou can start the SAP Mass Data Generator for Banking for banking via transaction ZMass Data Generator.You can start the SAP Mass Data Generator for Banking monitor via transaction ZMass Data Generator_MONI.© 2011 SAP AG page 11/49
  • 12. Best-Practice DocumentSAP Mass Data Generator for Banking2.3.1 General Start ScreenSAP Mass Data Generator for Banking is started as a dialog (online transaction) to set up your run. After thesetup and successful start of the run, the screen switches to the monitoring tool. This feature provides usefulinformation about current processing status and enables the user to influence the run by changing the level ofparallelization and package size, and stopping the run if necessary. It can either be used for active onlinemonitoring or to help to identify the root cause of performance problems during mass processing.SAP Mass Data Generator for Banking can be started using the transaction ZMass Data Generator.In the start screen of SAP Mass Data Generator for Banking you can choose your scenario and make initialsettings for the mass data creation run. 3. Click here to execute the selected scenario 1. Select the scenario you want to start. 2. Enter the initial number of parallel tasks and package size.FIGURE 2-3: START SCREEN - SAP M ASS D ATA GENERATOR FOR BANKING 1. Select the scenario you would like to execute. 2. Enter the initial number of parallel tasks (dialog work processes) and the initial package size. These are only the initial settings. You can change both attributes on the fly, during the mass run, within the SAP Mass Data Generator for Banking monitor. 3. Choose the Execute Scenario button to enter the scenario-specific setup screen.© 2011 SAP AG page 12/49
  • 13. Best-Practice DocumentSAP Mass Data Generator for Banking2.4 Scenario Startup2.4.1 Scenario: Master Data Creation The Master Data Creation scenario enables you to flexibly create business partners and accounts. This scenario is based on a working business partner—called a BP template—with all propertiesrelevant for your business process (for example, role assignments). At the beginning (after choosing yourscenario) the following start screen is displayed. Press the Load BP Template button to search for and loadyour BP template. Click this button to open Business Partner load dialog.FIGURE 2-4 SCENARIO MASTER DATA CREATION - START SCREENYou input the name of your BP template directly in the subsequent displayed dialog. If you do not know theexact ID of the BP, you can use the provided standard search functionality to find it. Search for your BP template. Click the OK button when ready.FIGURE 2-5 SCENARIO SCREEN - SEARCH AND INPUT BUSINESS PARTNER TEMPLATENow your BP template is loaded with all the details, including all accounts belonging to this business partner.The loaded information is displayed on the next screen, where you can define structural details forsuccessive mass data creation.© 2011 SAP AG page 13/49
  • 14. Best-Practice DocumentSAP Mass Data Generator for BankingEnter the number of BPs to be created.Select the Business Partner Grouping(BP number range). Enter the number of accounts to be created per one BP.FIGURE 2-6 SCENARIO MASTER DATA CREATION - DEFINE MASS DATA OBJECT PROPERTIESThe first box shows the loaded business partner template. The second shows all accounts belonging to theloaded business partner.For the business partner you have the ability to change the number of business partners to be created inthe first column, Number to be Created, and to select the BP grouping. You can create a special BP groupingfor SAP Mass Data Generator for Banking, as shown in the figure above, and assign a number range objectused only for the SAP Mass Data Generator for Banking. You can select an internal or external BP grouping.For example if you enter 100 for the number of BPs to be created and you select ZMass Data Generator forthe BP grouping, 100 business partners will be created with IDs defined by the number range object in the BPgrouping.You can create your own SAP Mass Data Generator for Banking BP grouping using the following path in theIMG Customizing: IMGFinancial ServicesSAP Business Partner for Financial ServicesGeneralSettingsBusiness PartnerBasic SettingsNumber Ranges and GroupingsDefine Groupings andAssign Number Ranges. This is shown in the following figures.© 2011 SAP AG page 14/49
  • 15. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-7 IMG CUSTOMIZING - DEFINE GROUPINGS AND ASSIGN NUMBER RANGESFIGURE 2-8 DEFINE BP GROUPING FOR SAP MASS DATA GENERATOR FOR BANKINGFor the number range, you need to create and select an internal number range.If you would like to create BPs with external ID numbers (not generated automatically by the system), youneed to upload a file containing the business partner ID numbers.© 2011 SAP AG page 15/49
  • 16. Best-Practice DocumentSAP Mass Data Generator for BankingThe file structure should be a simple text file, where each line should contain one unique business partner ID.For example:You need to make sure that all the business partner IDs in the file are unique, as the tool does not performthe check itself.Furthermore, you have the ability to add specific identification numbers to business partners, such aspassport number, identity card number, and so on. This information also needs to be uploaded via a separatefile.The file structure is a simple semicolon-separated file, where each line should contain the followinginformation:<IDType>;<IDNumber>;<ResponsibleInstitution-optional>;<ValidFromDate-optional>;<ValidToDate-optional>For example:© 2011 SAP AG page 16/49
  • 17. Best-Practice DocumentSAP Mass Data Generator for BankingFields IDType and IDNumber are mandatory. All the other fields are optional. The date must be in the formatYYYYMMDD.For Accounts in column Number to be Created,you can define how many copies of this specific accountshould be created per one single copy of BP. If you provide zero, no accounts wil be created, only thebusiness partners will be created. If you enter 1 for the first account and 2 for the second account, the finalresult will be a business partner with one account of the first type and two accounts of the second type.For performance reasons we do not read and copy all the information from the account template. Informationcoming from the account product, as well as limits, will be replicated. In case of loan accounts, theagreement, condition fixing, and inpayment agreement will also be replicated. There is also an option to copystandard and individual conditions from the template account. You need to mark the appropriate check box tocopy this information to the replicated accounts.FIGURE 2-9 SCENARIO MASTER DATA CREATION - DEFINE ACCOUNT ATTRIBUTESIf you have created a payment advice on the template account, SAP Mass Data Generator for Banking willcopy the parameters from the account template and create the payment advice on the replicated account.However, you need to provide a file that contains the counterparty account numbers for the payment advices.The file structure is a simple semicolon-separated file, where each line should contain the followinginformation:<Bank_Country>;<Bank_Key>;<Account_Number>;<Account_Holder>© 2011 SAP AG page 17/49
  • 18. Best-Practice DocumentSAP Mass Data Generator for BankingFor example:If the account numbers are using an external number range interval, you need to provide a file that containsthe external account numbers. You need to make sure they are unique, since we do not check this in SAPMass Data Generator for Banking.The file structure is a simple flat file, where each line should contain the following information:<Account_Number>For example:© 2011 SAP AG page 18/49
  • 19. Best-Practice DocumentSAP Mass Data Generator for BankingAfter you have finished your settings, you can start mass processing by choosing the Start Creation of MasterData button. Press this button to start the mass run.FIGURE 2-10 SCENARIO MASTER DATA CREATION - START THE RUNYou are prompted with the common SAP batch job planning screen to schedule your run. For immediatestart, choose the Immediate button and click the Save icon. This triggers the father batch job and forwardsyou to the monitoring screen to observe progression. Details are described in the following chapter, 2.4.7Active Monitoring. Mass processing has started now. Once the job is planned or started, you cannot run theSAP Mass Data Generator for Banking tool until the current run finishes.There is always one business partner created in one logical unit of work (LUW) and all accounts belonging toit in the next. This is done within one RFC. The package size in this particular scenario defines how manyBPs are created in one RFC call.Example (Figure 2-6): You enter 100 for the number of BPs to be created and, for each of the threeaccounts, you enter 1 in the Number to be Created. This results in a total of 100 BPs and 100 accounts of thefirst type, plus 100 accounts of the second type and 100 accounts of the third type, which makes a total of300 accounts to be created. With default package size equal to 10, there are 10 BP and 30 accounts createdper RFC call. This results in 30 total objects, which is the figure relevant for throughput computation. Howexactly you define number of accounts and package size influences processing time per RFC. Any change inpackage size or number of processes has to wait for RFC calls to return until changes become active. Thishas to be taken into consideration before executing any call.2.4.1.1 Fixed-Term Deposits CreationThis scenario allows you to replicate accounts of product type fixed-term deposits (F-T Dep.). You can usethe Master Data scenario or the Account scenario to replicate accounts with a fixed-term agreement.The first step is to create fixed-term deposit contracts using the existing template account. After the accountshave been successfully created, the contract would be in a preliminary phase.The second step is necessary to post the payments on accounts with the fixed-term contract amount. For thepurpose of mass data creation, we recommend using the Payment scenario.© 2011 SAP AG page 19/49
  • 20. Best-Practice DocumentSAP Mass Data Generator for BankingThe third step is fixing the contracts. For that purpose, the standard fixing report (transactionBCA_RC_FTD_FIXING_PP) can be executed to fix the term deposit on every account and finalize thebusiness process.Known Issues: It is not possible to replicate a constellation where completed F-T Dep. agreements exists on one accounts, while a current new agreement was opened (rollover). In this case you would receive an error message.2.4.1.2 Loan Accounts CreationThis scenario allows you to replicate accounts of product type loan, mortgage, or installment loan. If youwould like a loan account to be immediatelly disbursed after it has been created, you need to create apayment advice for disbursement in the template account. - If you already have the accounts in the system where the newly created loan accounts should be disbursed, you need to create a file with the counter-party accounts, as described in the previous chapter, 2.4.1 Scenario: Master Data Creation - If there are no accounts in the system to which the disbursement should be transferred, you can first create those accounts using SAP Mass Data Generator for Banking, either current accounts or savings accounts, and then create a file with the counter-party accounts, as described in the previous chapter, 2.4.1 Scenario: Master Data Creation. - You can also transfer disbursements to external accounts. The file with the counter party account needs to be created, as described in the previous chapter.2.4.2 Scenario: Accounts CreationThis scenario enables the creation of accounts only for already existing business partners. When you executethis scenario the following dialog is displayed.© 2011 SAP AG page 20/49
  • 21. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-11 SCENARIO ACCOUNTS – INITIAL SCREENFirst, you need to load a BP template, as already described in the Master Data Creation section.Then you need to define a range of business partners who will be account holders for the accounts to becreated. Enter or Select the Business Partner range. Enter the number of accounts to be created per one BP. Click the calculate button to check how many accounts will be created© 2011 SAP AG page 21/49
  • 22. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-12 SCENARIO ACCOUNTS – DEFINE ACCOUNT ATTRIBUTESThe settings for the account are the same as in the Master Data scenario, so you can refer to it for details.After you have defined all the necessary attributes, choose the Start Creation of Accounts button to start themass run.FIGURE 2-13 SCENARIO ACCOUNTS – START CREATION OF ACCOUNTS2.4.3 Scenario: Payment ItemsThis scenario enables the creation of payment items on already created accounts. When you execute thisscenario, the following dialog is displayed.© 2011 SAP AG page 22/49
  • 23. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-14 SCENARIO PAYMENT ITEMS – INITIAL SCREENYou can select the variant you have previously saved, so you do not have to fill in the fields in the dialog.© 2011 SAP AG page 23/49
  • 24. Best-Practice DocumentSAP Mass Data Generator for Banking Click here to select your variantFIGURE 2-15 SCENARIO PAYMENT ITEMS – SELECT THE VARIANTIn the Account Selection area, you can select an account range on which the payment items should beposted.FIGURE 2-16 SCENARIO PAYMENT ITEMS – ACCOUNT SELECTIONAlternatively, you can provide a file with the account numbers for which the payment items should be posted.FIGURE 2-17 SCENARIO PAYMENT ITEMS – ACCOUNT SELECTION – ACCOUNT NUMBERS FILE SELECTIONThe file structure is a simple semicolon-separated file, where each line should contain the followinginformation:<Bank_Country>;<Bank_Key>;<Account_Number>© 2011 SAP AG page 24/49
  • 25. Best-Practice DocumentSAP Mass Data Generator for BankingFor example:FIGURE 2-18 SCENARIO PAYMENT ITEMS – ACCOUNT SELECTION – ACCOUNT NUMBERS FILEIn the Payment Item Data area, you can specify the following attributes:  Transaction type: You can select all turnover and recipient transaction types. Enter the transaction type or choose it from the input help FIGURE 2-19 SCENARIO PAYMENT ITEMS – TRANSACTION TYPE SELECTION© 2011 SAP AG page 25/49
  • 26. Best-Practice DocumentSAP Mass Data Generator for Banking  Payment medium FIGURE 2-20 SCENARIO PAYMENT ITEMS – PAYMENT MEDIUM SELECTION  Posting date, value date, and days offset Enter the posting date or choose it from the input calendar FIGURE 2-21 SCENARIO PAYMENT ITEMS – POSTING DATES DEFINITION Posting Date: Enter the posting date range. For example, if you enter 01.01.2009 to 31.12.2009, you will have payment items posted each day for the entire year. Note: In order to enable backdated postings, you need to change the customizing settings accordingly. Value Date: This is optional field. You can enter the value dates range if needed. For example, if you enter 03.03.2008 to 02.07.2008 and the posting date range is from 01.03.2008 to 30.06.2008, you will© 2011 SAP AG page 26/49
  • 27. Best-Practice DocumentSAP Mass Data Generator for Banking have payment items with posting date 01.03.2008 and value date 03.03.2008, posting date 03.03.2008 and value date 05.03.2008, and so on. Days Offset: If you do not want to have payment items posted each day, you can specify here how many days should be skipped between the two postings. For example, if you enter 2 you will have posting every second day, if you enter 3 every third day, and so on. Therefore if you specify posting dates from 01.01.2009 to 31.12.2009 and enter 3 for days offset, you will have postings on 01.01.2009, 04.01.2009, 07.01.2009, and so on.  Number of payment items per account per posting date If you would like to have more postings per day for each account, you can enter this number here. For example, if you enter 3, and we assume that the posting dates were from 01.01.2009 to 10.01.2009 and the days offset was 3, you will have the following payment items for each account. Pstg Date Value Date Transactio Medium Amount AC AcctCrcy Item Type Status Des 10.01.2007 12.01.2007 Cash Deposit Internal 46,09 EUR Turnover Posted 10.01.2007 12.01.2007 Cash Deposit Internal 47,16 EUR Turnover Posted 10.01.2007 12.01.2007 Cash Deposit Internal 44,56 EUR Turnover Posted 07.01.2007 09.01.2007 Cash Deposit Internal 43,47 EUR Turnover Posted 07.01.2007 09.01.2007 Cash Deposit Internal 35,92 EUR Turnover Posted 07.01.2007 09.01.2007 Cash Deposit Internal 45,34 EUR Turnover Posted 04.01.2007 06.01.2007 Cash Deposit Internal 44,52 EUR Turnover Posted 04.01.2007 06.01.2007 Cash Deposit Internal 38,86 EUR Turnover Posted 04.01.2007 06.01.2007 Cash Deposit Internal 20,81 EUR Turnover Posted 01.01.2007 03.01.2007 Cash Deposit Internal 42,7 EUR Turnover Posted 01.01.2007 03.01.2007 Cash Deposit Internal 45,32 EUR Turnover Posted 01.01.2007 03.01.2007 Cash Deposit Internal 48,45 EUR Turnover Posted TABLE 2-1 SCENARIO PAYMENT ITEMS – RESULTING PAYMENTS© 2011 SAP AG page 27/49
  • 28. Best-Practice DocumentSAP Mass Data Generator for Banking  Amount and currency Enter the transaction currency or choose it from the input help. FIGURE 2-22 SCENARIO PAYMENT ITEMS – CURRENCY AND PAYMENT AMOUNT Amount: If you would like different amounts to be posted for each payment item, you can specify a range. The amount will be randomly generated within the specified range. For example, if you enter amounts from 20.00 to 150.00, a random amount between 20.00 and 150.00 will be generated for each payment item. If you want the same amount to be posted, enter the same lower and upper values. Note: Please ensure that the postings will be accepted with the correct product attributes. Currency: Enter the transaction currency or use the input F4 help and choose it from the list of all currencies in the system. If an amount should not contain any cents (decimal values) then select the No Decimals check box. This is usually the case for ATM payments. In addition, if the amount needs to be an increment of a certain value, you can enter this value in the Round to input field. For example, an ATM machine, cannot issue bills smaller than 10 EUR, so for the ATM withdrawal transaction type, you need to enter 10 in the Round to field. Similarly, if an ATM cannot issue bills, smaller than 20 US dollars, then enter 20 into the Round to field.© 2011 SAP AG page 28/49
  • 29. Best-Practice DocumentSAP Mass Data Generator for Banking  Payment notes Note Type: Select a payment note type using the F4 help, or enter the payment note type. If you have defined some custom payment note types, those will appear in the selection options. Note text: Enter the text of your payment note. Number of payment notes: If you would like to have more payment notes per payment item, enter here how many you need to have created.  Create a prenote If a prenote is required, you can select the Create Prenote check box and select a prenote type to be created.  Post payments in bulk© 2011 SAP AG page 29/49
  • 30. Best-Practice DocumentSAP Mass Data Generator for Banking You can either post the payment items in bulk or do a single item posting. If you leave this field unchecked, each payment item will be posted as a single item in a single BAPI call. If you check this field, a number of payment items will be packed, depending on the package size you specified, and will be posted in bulk using a single BAPI call. The second option is commonly used when mass payment posting is needed. The performance is better because the overhead per BAPI call is smaller if you choose bulk processing. SAP Mass Data Generator for Banking can help to determine the optimal package size and the level of parallelization for payment processing in your system, since you can change both the package size and the level of parallelization during the mass run and monitor the change in throughput.  Post or terminate indicator Process Incorrect Items Only If Response Is "Post": Results in incorrect items only being processed if "Post" has been defined in the posting control rules. There are two possible values: o X - check box selected (default value): Incorrect items are only processed if "Post" has been defined in the posting control rules. o - check box not selected: No change to the response from the posting control rules. The latter is useful for the fixed-term deposits scenario, for example, where the posting on the fixed- term deposit needs to be made before it can be fixed. As the contract at the time of payment posting is in the preliminary phase, and the post processing is defined in the posting control rules, the box can be unchecked and the payment items will go into the post-processing and be posted at the time of fixing.  Ignore errors The regular processing of the payment item run will be automatically stopped as soon as an error occurs. However, it may be possible that these errors are normal, expected functional errors and you would like to continue the run even if such errors occur. If you are expecting some items to run into errors, but you do not want the whole run to stop, then select this check box.  Reference account numbers If the transaction type selected is a of a recipient item type that is returnable, you need to specify reference account numbers. You can also provide other reference data, such as reference creation number and reference payment transaction number. This information must be uploaded via a file. The file structure is a simple semicolon-separated file, where each line needs to contain the following data:© 2011 SAP AG page 30/49
  • 31. Best-Practice DocumentSAP Mass Data Generator for Banking <BANK_COUNTRY_REF>;<BANK_CODE_REF>;<ACCOUNT_NUMBER_REF>;<ACCOUNT_CURR ENCY_REF><NAME_BUPA_REF>;<REF_NO_CREATION>;<REF_NO_PAYMENT> For example: DE;85080000;0100000876;EUR;John Smith;1234567;98765 Fields can be optional, depending on the transaction type and the customer-specific customizing. If you do not need to fill in a specific field, you can leave an empty space between the semicolons. For example if you only need the Ref. No Creation, you can enter the following line in the file: ;;;;;1234567;  Calculate the total number of payment items to be created This option is used to help you determine the total number of payments to be created in the system, based on the input you specified. The calculation is done using the following formula: Number of accounts x number of posting dates x payments per posting date  Start payment item creation After you have specified the attributes for payment item creation, you can choose this button to start the run. This will call the job scheduler dialog, where you can specify when you would like to start the run.© 2011 SAP AG page 31/49
  • 32. Best-Practice DocumentSAP Mass Data Generator for Banking FIGURE 2-23 SCENARIO PAYMENT ITEMS – START THE RUN This will create one background job which will trigger RFCs to process payment items. After the job has been successfully started, the monitor will start automatically. You can monitor the progress and throughput of the run, and change the level of parallelization and package size on the fly.2.4.4 Scenario: Standing Orders This scenario enables the creation of standing orders on already created accounts. When youexecute this scenario, the following dialog is displayed.© 2011 SAP AG page 32/49
  • 33. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-24 SCENARIO STANDING ORDERS – INITIAL SCREENIn the Account Selection area, you can select an account range for which the standing orders should becreated.FIGURE 2-25 SCENARIO STANDING ORDERS – ACCOUNT SELECTION© 2011 SAP AG page 33/49
  • 34. Best-Practice DocumentSAP Mass Data Generator for BankingYou can also provide a file with the account numbers for which the standing orders should be created. FIGURE 2-26 SCENARIO STANDING ORDERS – ACCOUNT SELECTION – ACCOUNT NUMBERS FILE SELECTIONThe file structure is a simple semicolon-separated file, where each line should contain the followinginformation:<Bank_Country>;<Bank_Key>;<Account_Number>For example: FIGURE 2-27 SCENARIO STANDING ORDERS – ACCOUNT SELECTION – ACCOUNT NUMBERS FILEIn the Recipient Account area, you can upload a file that contains the account details of the recipientaccounts for standing orders. By default, without providing the file, all standing orders created will have thesame recipient account, which is copied from the template. If you would like to have different recipientaccounts (either internal or external), you can provide the list of accounts in the file. During the creation ofstanding orders, the program will loop through the list and assign different recipients to different standingorders.© 2011 SAP AG page 34/49
  • 35. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-28 SCENARIO STANDING ORDERS – RECIPIENT ACCOUNTSThe file must be given in a specific format:<Bank_Country>;<Bank_Key>;<Account_Number>;<Account_Holder>For example: DE;85080000;0200000320;John DoeIn the Standing Order Template area, you need to select one standing order that you would like to use as atemplate. All the attributes from the template will be used for creating new standing orders. In this screen youcan change the fixed amount of the standing order and define how many standing orders should be createdper account.© 2011 SAP AG page 35/49
  • 36. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-29 SCENARIO STANDING ORDERS – DEFINE STANDING ORDER ATTRIBUTESIf you would like to check how many standing orders will be created in the run, you can choose the Calculatebutton.FIGURE 2-30 SCENARIO STANDING ORDERS – CALCULATE THE NUMBER OF SOS TO BE CREATEDAfter you have selected a template and defined the accounts range, you can start the creation of standingorders.FIGURE 2-31 SCENARIO STANDING ORDERS – START CREATION OF STANDING ORDERS2.4.5 Scenario: Payment/Forward OrdersThis scenario enables the creation of payment or forward orders on already created accounts. When youexecute this scenario, the following dialog is displayed.© 2011 SAP AG page 36/49
  • 37. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-32 SCENARIO PAYMENT / FORWARD ORDERS – INITIAL SCREENIn the Account Selection area, you can select an account range for which the payment or forward ordersshould be created.FIGURE 2-33 SCENARIO PAYMENT / FORWARD ORDERS – ACCOUNT SELECTIONYou can also provide a file with the account numbers for which the standing orders should be created. FIGURE 2-34 SCENARIO PAYMENT / FORWARD ORDERS – ACCOUNT NUMBERS FILE SELECTION© 2011 SAP AG page 37/49
  • 38. Best-Practice DocumentSAP Mass Data Generator for BankingThe file structure is a simple semicolon-separated file, where each line should contain the followinginformation:<Bank_Country>;<Bank_Key>;<Account_Number>For example: FIGURE 2-35 SCENARIO PAYMENT / FORWARD ORDERS – ACCOUNT NUMBERS FILEIn the Recipient Account area, you can upload a file that contains the account details of the recipientaccounts for payment/forward orders. By default, without providing the file, all payment/forward orderscreated will have the same recipient account, which is copied from the template. If you would like to havedifferent recipient accounts (either internal or external), you can provide the list of accounts in the file. Duringthe creation of standing orders, the program will loop through the list and assign different recipients todifferent standing orders. Having the same recipient account as the template will result in an error when tryingto post all payment orders in parallel to the same account. Therefore, it is advised to use the file with alldifferent recipient accounts when using this scenario.The file must be given in a specific format:<Bank_Country>;<Bank_Key>;<Account_Number>;<Account_Holder>For example: DE;85080000;0200000320;John Smith© 2011 SAP AG page 38/49
  • 39. Best-Practice DocumentSAP Mass Data Generator for BankingIn the Payment/Forward Order Template area you need to select one payment/forward order that you wouldlike to use as a template. All the attributes from the template will be used for creating new payment/forwardorders. In this screen you can change the fixed amount of the payment/forward order and define how manypayment/forward orders should be created per account.You can also specify an execution date for forward orders if you would like it to be different than the one inthe template forward order.© 2011 SAP AG page 39/49
  • 40. Best-Practice DocumentSAP Mass Data Generator for BankingFIGURE 2-36 SCENARIO PAYMENT/FORWARD ORDERS – DEFINE PAYMENT/FORWARD ORDER ATTRIBUTESIf you would like to check how many payment and forward orders will be created in the run, you can choosethe Calculate button.FIGURE 2-37 SCENARIO PAYMENT/FORWARD ORDERS – CALCULATE THE NUMBER OF PAYMENT/FORWARD ORDERS TO BE CREATEAfter you have selected a template and defined the accounts range, you can start the creation of paymentand forward orders.FIGURE 2-38 SCENARIO PAYMENT/FORWARD ORDERS – START CREATION OF PAYMENT/FORWARD ORDERS2.4.6 Scenario: Master ContractsThis scenario enables the creation of master contracts and all the participating accounts. When you executethis scenario, the following dialog is displayed. Click this button to open Master Contracts load dialog.© 2011 SAP AG page 40/49
  • 41. Best-Practice DocumentSAP Mass Data Generator for BankingEnter the number of the master contract template and choose Ok.Further parameters can be set when the master contract template is loaded. The range of business partnerswho will be the master contract holders of the newly created master contracts should be specified. Thenumber of master contracts per BP needs to be specified as well.During the creation of master contracts, first all the participating accounts will be created. Participatingaccounts will be the copies of the participating accounts from the template master contract. When theaccounts are created, they will be linked to the newly created master contract and the relationship attributeswill be set according to the template attributes.Currently the following master contract features are supported:- Effective cash pooling- Facilities- Combined settlement (bundle pricing and interest and charge compensation)© 2011 SAP AG page 41/49
  • 42. Best-Practice DocumentSAP Mass Data Generator for Banking Select the Master Contract Holders Set the number of master contracts to be created Check the boxes if the individual or standard conditions of the participating accounts have to be copied.In some cases, payment details must be created for the master contracts. The reference accounts for thepayment details can be uploaded via a flat file.The file structure is a simple semicolon-separated file, where each line should contain the followinginformation:<Bank_Country>;<Bank_Key>;<Account_Number>;<Account_Holder>© 2011 SAP AG page 42/49
  • 43. Best-Practice DocumentSAP Mass Data Generator for BankingFor example:After you have finished your settings, you can start mass processing by choosing the Start Creation of MasterContracts button. Click this button to start creation of Master Contracts.2.4.7 Active MonitoringAfter you have successfully started the mass run, the control panel and monitoring of SAP Mass DataGenerator for Banking will start automatically. The tool is decoupled and can be started at any time viatransaction ZMass Data Generator _MONI.In the scenario, you are automatically forwarded to this screen as soon as you start the run. You can alsomonitor the run from a different computer by starting the monitor itself.Here you can monitor the progress and throughput of the run, as well as change the level of parallelizationand package size on the fly. This makes processing very flexible and increases the scalability of the solutionlandscape to be monitored.© 2011 SAP AG page 43/49
  • 44. Best-Practice DocumentSAP Mass Data Generator for Banking Control Panel Area Logs Area Throughput Graph Progress Bar Tasks allowed and Package Size GraphsFIGURE 2-25 ACTIVE MONITORING - SAP MASS DATA GENERATOR FOR BANKING FOR SAP BANKING  Control panel area Click the refresh button to display the latest figures. Output is refreshed only when you choose Refresh. This option enables you to change the number of allowed task on the fly. This option enables you to change the package size. This option changes the time interval for collecting the latest progress and throughput figures. For example, if time delta is set to 10s, you will have the new figures computed every 10 seconds. If your run will run for hours, you© 2011 SAP AG page 44/49
  • 45. Best-Practice DocumentSAP Mass Data Generator for Banking should increase this number to 60 seconds or more. If you need to stop the mass run for some reason, you can do this by choosing the Stop the mass run button. The run will not break in the middle of an RFC call, but will wait for all RFCs to return and then stop further processing.  Logs area Due to performance reasons only the errors and the most important information will be logged. For example, if an error occurs during the mass run, the error message will be displayed here and the run will be automatically stopped.  Throughput graph Throughput, which is the number of objects created per hour, will be calculated and displayed in the graph so you can easily see how the throughput changes when you change the number of parallel tasks or package size.  Tasks allowed, tasks available and the package size graph Whenever you change the number of parallel task and the package size, the new figure will be shown in this graph. This helps you to easily connect the change in the parallelization and package size to the change in throughput. The number of available tasks will be shown, so you can decide if you can set a higher level of parallelization. Changes are not active until all RFC calls return to the controlling batch job.  Progress bar The progress bar shows how many object have been created so far and the total number of objects that should be created. This helps you to easily determine the number of object yet to be processed.A key feature of monitoring is the combination of changing package size and parallelization, and observingdirect system response key figures. It helps to find answers to questions like: What is an optimal level ofparallelization? When do we see system bottlenecks (DB/SAP)? Where does the linear dependency ofthroughput to number of work processes end?Note: When you change the parallelization or the package size for payment item processing, you should beaware that the number of parallel tasks multiplied by the package size cannot be higher that the total numberof accounts on which you perform the postings because at the same time, two or more payment items will tryto be posted on the same account, which will lead to account locking and a posting error will occur. SAPMass Data Generator for Banking will inform you if you have tried to create a higher package size or paralleltask and will adjust it automatically.© 2011 SAP AG page 45/49
  • 46. Best-Practice DocumentSAP Mass Data Generator for Banking2.4.8 Application LogsAll the logs provided in the SAP Mass Data Generator for Banking monitor will be saved to the application log(transaction SLG1) for later reference and analysis. This is especially useful in case of errors, sinceapplication logs provide long texts with procedures on how to solve errors. You can easily display Mass-Data-Generator- related logs by restricting the application log search to Object ZMDG (Mass Data Generator Logs)and the following Subobjects: ACCOUNTS Accounts scenario MASTER_DATA Master Data scenario MCM Master Contract Management scenario PAYMENTS Payments scenario PAY_FWD_ORDER Payment/Forward Orders scenario STANDING_ORDER Standing Orders scenario2.4.9 Restart FunctionalityIn the case of a functional error, the run will be stopped. The errors will be displayed in the monitor and savedto the application log. This run can be restarted as long as it was the last run performed in the system. TheRestart button will be shown in the entry screen of each scenario if a restart is possible.The restart will try to process the same items that resulted in error and then continue processing theremaining items. A typical case where the restart functionality can be used is when, for example, accountsshould be created for a number of business partners and a few business partners in the range do not have anecessary role or the role is not in the validity range of the account contract. In this case, the run will beautomatically stopped with error messages displayed. You can then add the necessary roles to the faultybusiness partners or correct the validity dates and restart the run.© 2011 SAP AG page 46/49
  • 47. Best-Practice DocumentSAP Mass Data Generator for Banking3 Further Information3.1 Troubleshooting3.1.1 Ineffective Configuration Changes During MonitoringChanges to the package size or number of parallel tasks in the Monitor will be effectivly changed only aftercurrent packages have finished processing. Any change to these settings (see chapter 2.4.7 ActiveMonitoring) has to wait for RFC calls to return until it can be effective. This has to be taken into considerationbefore executing any run. In the worst case, you can create huge package sizes comprising all data to beprocessed in only one RFC call. In this case you are actually doing sequential processing and the key figureswill appear when the RFC has returned, when the run is already finished.As a good basis, start with the low number of parallel tasks and the package size and then increase themgradually during the run.For example:Number of parallel tasks = 5Package size = 5Different package sizes are effective in different scenarios. Use the following sample values to setup yourruns:Master Data scenario – Package size from 2 to maximum 10Accounts scenario – Package size from 2 to maximum 10Master Contract Management scenario – Package size 1Payments scenario – Package size from 50, 100, 200, depending on the systemPayment/Forward Orders scenario – Package size from 50, 100, 200, depending on the systemStanding Orders scenario – Package size from 50, 100, 200, depending on the system3.1.2 Inserts into Change Pointer TablesIf you see a lot of inserts into table CNS_CP table, the change pointer table, when creating business partnersand accounts, and you do not need the change pointers for the testing, you can deactivate the changepointers for specific account products, business partners, and so on in Customizing. This needs to beperformed separately for each client.Change Pointer Service  Activate Application for Change Notification Service.© 2011 SAP AG page 47/49
  • 48. Best-Practice DocumentSAP Mass Data Generator for Banking3.1.3 High Level of ParallelizationParameter rdisp/rfc_max_own_used_wp sets the maximum percentage of work processes that can be usedby a single RFC user. The default value is 75%. Therefore, if you would like to use more than 75% ofavailable processes with SAP Mass Data Generator for Banking, you need to set this parameter accordingly.If the number of tasks in SAP Mass Data Generator for Banking is more than 75% of available processes,and this parameter is not increased, some packages will not be processed. If that happens, it will be recordedin the log as a warning message.3.2 Background Information and ReferencesThis chapter contains useful links to different Run SAP best-practice documents for the banking industry.They comprise valuable additional information. Related best-practice documents for performance topics, likeperformance tests, performance test preparation, performance monitoring, and database setup can be foundat the SAP Service Marketplace. Go to https://service.sap.com/solutionmanagerbp and filter by Solution =Banking.  Table Partitioning for Optimal Performance of a Banking Services System  Best Practice Parallel Processing Framework for Customer Reports  Best Practice Parallelization and Package settings for a Banking Services system  SAP Test Data Migration Server for Deposits Management  Best Practice Business Process Performance Monitoring Banking© 2011 SAP AG page 48/49
  • 49. Best-Practice DocumentSAP Mass Data Generator for Banking© 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein aswell as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (―SAPGroup‖) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituti ng anadditional warranty.© 2011 SAP AG page 49/49

×