Post on 15-Jan-2015
description
transcript
Best_Practice_Parallelization_Packaging_Monitoring_V21.doc – 03.11.2008
Best Practice
Parallelization, Packaging, Monitoringfor SAP Banking
Dietmar-Hopp-Allee 16D-69190 Walldorf
CS STATUScustomer published
DATE VERSION
Nov-03 2008 2.1
SOLUTION MANAGEMENT PHASE SAP SOLUTION
Operations & Optimizations Banking Services, Bank Analyzer,SAP Deposits Management
TOPIC AREA SOLUTION MANAGER AREA
Business Process Operations Job Scheduling Management
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 2/34
Table of Contents1 Management Summary 3
1.1 Goal of Using This Service 31.2 Parallelization and Packaging as Part of an Overall Performance Optimization Strategy 31.3 Staff and Skill Requirements 31.4 Design 31.5 System Requirements 4
2 Best Practice Procedure and Verification 52.1 Procedure 5
2.1.1 Configuration of Parallelization in Banking Services 52.1.1.1 Account Management & Loans 52.1.1.2 Bank Analyzer 62.1.1.3 Parallel Processing for Invoicing & Outbound Interface FPOITR in FI-CAx 7
2.1.2 Set Package Size 82.1.2.1 Account Management & Loans 8
2.1.3 Customizing Configuration for the Package Size 102.1.3.1 Invoicing & Outbound Interface FPOITR in FI-CAx 122.1.3.2 Accounting Scenarios 132.1.3.3 Basel II – Credit Exposure – Package Size and Individual Parallelization 142.1.3.4 BW Extraction – Package Size 152.1.3.5 Historization Runs (HDB) 17
3 Operations and Optimization 203.1 Monitoring Tools 203.2 Mass Activity Monitor Called MassMan 203.3 Using RBANK_PP_MONITOR 23
4 Further Information 254.1 Background Information and References 254.2 Feedback and Questions 254.3 Available Application Categories in the Banking Services Solution 25
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 3/34
1 Management Summary
1.1 Goal of Using This Service
In the Banking Services environment, Framework for Parallel Processing (FPP) enables applications toprocess mass data more efficiently. Performance is improved by processing the data in several processeswith a specified package size.
By using FPP, it is possible to use the available hardware resources in an optimal way, by using parallelbatch processes depending on the available CPU resources. This approach allows the distribution of theworkload to many work processes, which reduces at the overall processing time and allows the completeusage of all available hardware resources.
Besides the Parallelization, there is also a Packaging mechanism implemented that allows the processing ofa pre-defined number of objects. From a technical point of view, Packaging prevents negative performanceimpact by processing huge internal tables because of the data volume that has to be handled.
Packaging and Parallelization are a prerequisite to build a scalable solution and to optimize throughput and,therefore, part of most of the Banking Services mass processes.
This document describes how to set up a Parallelization and package size for mass processes of the BankingServices solution, and gives some general recommendations about a useful package size based on theexperiences of previous banking releases and our customer experiences. In addition to that, the documentalso provides helpful information about monitoring tools, which provide the relevant information about theParallelization settings of a mass run, and about progress and throughput.
1.2 Parallelization and Packaging as Part of an Overall Performance OptimizationStrategy
Besides the general remarks given in this document, customer-specific recommendations regarding optimalParallelization and Packaging in terms of system performance are given as part of a Business ProcessPerformance Optimization (BPPO) service with banking experts from SAP AGS. Appropriate package sizesand Parallelization settings specifically for an individual system landscape are recommended in this service.The BPPO is exclusively available within SAP support engagements (that is SAP Enterprise Support, SAPMaxAttention, SAP Safeguarding).
1.3 Staff and Skill Requirements
To implement this Best Practice, you require an expert performance banking team that proposes the settingsbased on the output of the BPPO settings.
The general, Parallelization and package size setting should be used as a first “best guess” setup forperformance testing that has to be verified and fine-tuned by performance experts.
1.4 Design
The basic principle of the FPP is to divide processing into individual processing steps or events, in whichbusiness or application-specific logic is run. The application prepares this logic in function modules (“callbackmodules”).
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 4/34
The prerequisite for the implementation of the FPP is that the data to be processed is stored in the database.This does not apply for application processes that create data.
The application is identified by the FPP using a unique application type, which must be entered incustomizing and transferred when the framework is started.
You can divide processing into three areas: Preparation Parallel processes (threads/jobs) End processing
From the point of view of the main process, the parallel processes run asynchronously in batch jobs. Thismeans that: It is usually possible to transfer data to this process using database tables or persistent saves only. The callback functions assigned to this area cannot access any data that the application stored previously
in global areas.
Architectural context
The following figure shows an overview of the structure of FPP and integration by the application.
1.5 System Requirements
FPP as underlying basis of the SAP Banking applications is part of the SAP application basis SAP_ABA as ofSAP NetWeaver release 620 and is therefore used frequently in nearly all mass processing reports of theBanking Services environment (operational & analytical banking).
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 5/34
2 Best Practice Procedure and Verification
2.1 Procedure
The following sections describes the steps to be taken to configure an appropriate Parallelization andpackage size.
2.1.1 Configuration of Parallelization in Banking Services
Almost all Banking Services applications use FPP. There are two settings which have a significant impact onthroughput and resource consumption. Number of background jobs invoked in parallel (parallel processing) Number of objects processed in one step (package size)
These settings are done in customizing and are usually created in a test system and then moved intoproduction using the transport system. Nevertheless, the production settings for Parallelization usually do notfit to the settings of the test environment, due to different hardware environment.
2.1.1.1 Account Management & Loans
Start IMG (TA SPRO): Financial Services Account Management Tools Parallel Processing Maintain Job Distribution
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 6/34
2.1.1.2 Bank Analyzer
Start IMG (TA SPRO): Financial Services Bank Analyzer Basic Settings Parallel Processing Maintain Job Distribution
Per Application Type and ServerName or Logon/server group, you can set the Number of parallel tasks.Prefer using Logon/server group to be able to react to changed distribution of work processes withoutchanging the customizing.
During runtime, the Parallelization framework tries starting as many jobs as defined. If there are not sufficientfree background work processes available, the jobs that cannot be started in that moment remain in status“released”. They will start as soon as a free background work process is available. Check with TA SM37.
Note: To find the best degree of Parallelization, it is recommended to start with the double of the number ofbatch processes per CPU. Afterwards, it is recommended to increase or decrease the number of batchprocesses in an iterative test process as long as the processing time is still reduced.
A list of all available application categories of Banking Services 6.0 linked to the mass processes can befound in section 4.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 7/34
2.1.1.3 Parallel Processing for Invoicing & Outbound Interface FPOITR in FI-CAx
For the process Invoicing & Outbound Interface FPOITR, the relevant setting for the Parallelization is set onthe selection screen before each run.
In the second section of the Technical Settings tab, the number of processes to be involved in the parallelprocessing is maintained.
Note: For some FI-CAx processes, Mass Processing and Parallel Processing are available. Only ParallelProcessing allows a Parallelization.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 8/34
2.1.2 Set Package Size
The package size setting depends on the application. Therefore, several settings are mentioned in thedocument to configure a package size.
With the package size, you define how many objects are processed in one step. That is: Number of objects that are read from DB and stored in an internal table – memory consumption Implicit control of DB commit rate because it is done at the end of a package
Note: The best throughput results are generally achieved with a package size of 50 or 100, which usually fitsto almost all processes. Therefore it is recommended starting with a package size of 50 or 100 for eachprocess and to change the package size only in case of serious issues.
2.1.2.1 Account Management & Loans
In the Account Management and Loans application, there are two different ways of defining a package size.
The first option is to define the package size on the application screen.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 9/34
For some mass processes like Account Settlement Run, it is not possible to define a package size; the settingon the screen just allows specifying the total number of packages. In such a case, the number of packagesshould be calculated as follows: Expected number of packages / ***Number of Packages*** = should bebetween 50 and 150.
To get an idea of the expected number of objects, MassMan offers a forecast functionality that calculates thenumber of objects to be settled on the execution date. Additional information about MassMan can be found insection 3.1.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 10/34
2.1.3 Customizing Configuration for the Package Size
To ensure that the customizing setting will be used, the option Dynam. Determin. Package Number has to beflagged and then the package size will be chosen from the customizing.
Start IMG (TA SPRO): Financial Services Account Management Tools Parallel Processing SetPackage Size for Parallel Processing
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 11/34
All application categories where the package size can be defined in customizing are listed below.
Application Category Process Description
/FSBPR/SET Mass Run - Execute Combined Settlement
/FSPD/PDI1 Mass Run - Execute Payment Distribution
BAPA_PCO1 Posting Control Office: Priority Update
BAPA_PCO2 Posting Control Office: Automatic Resubmission
BAPA_PCO3 Posting Control Office: Automatic Final Processing
BCA_BOCP Product Change (Account): Execute Due PC
BCA_BODC Product Change (Card): Execute Due PC
BCA_BODP Product Change (Card Pool): Execute Due PC
BCA_BOTC Acct Closure: Edit Due Account Closures
BCA_CA01 Renewal Run - Cards
BCA_CA02 Ordering File - Cards
BCA_CA04 Confirmation of Ordered Cards from Processor
BCA_CLEARG Clear Old Open Item
BCA_CLREXT External Clearing
BCA_COPR Correspondence Print Run
BCA_CRRV CM: Credit Review
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 12/34
Application Category Process Description
BCA_DORM Dormancy and Escheat
BCA_FORD Forward Order
BCA_SORD Standing Order
BCA_BL Billing Run
2.1.3.1 Invoicing & Outbound Interface FPOITR in FI-CAx
For the process Invoicing & Outbound Interface FPOITR in FI-CAx, the relevant setting for the package sizeare set on the selection screen before each run. The settings can be saved as a variant for future use.
Go to the Technical Settings tab, and choose either the contract account or the business partner as ParallelProcessing Object.
Press
Press the Create button to define a new variant. In the new variant, either Interval Length, which specifies thenumber of objects per package, or Number of Intervals, which equals the number of packages, can bedefined.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 13/34
In addition, there is an option to choose between static and dynamic interval number calculation. For thedynamic interval handling, the limit is calculated before every run. In the static approach, the limit ismaintained by running the report RFKKDI01 periodically. That means, if the number of objects (for example,VKONT for contract accounts or GPART for business partner) grows, the report RFKKDI01 must run to keepthe performance stable.
Note: In general, sufficient throughput results are achieved with an interval length of 100. Nevertheless, it isrecommended to test the optimal package size.
2.1.3.2 Accounting Scenarios
Start IMG (transaction SPRO) Accounting “Merge-Scenario”: Financial Services Bank Analyzer Accounting Balance Analyzer
After Generation Basic Settings Performance Optimization Set Package Size for ParallelProcessing
Accounting for “Financial Instruments”: Financial Services Bank Analyzer Processes and Methods Accounting for Financial Products After Generation Basic Settings Performance Optimization Set Package Size for Parallel Processing
With the package size, you define how many objects are processed in one step. That is: Number of objects that are read from DB and stored in an internal table – memory consumption Implicit control of DB commit rate because it is done at the end of a package
The higher the package size the higher the likelihood of locks. Refer to restart packages inRBANK_PP_MONITOR. This is especially relevant for ‘Posting external BT (BBP1)’. Choosing a packagesize that is too high often results in disproportionately increasing memory consumption and performancedegradation. An exception is Master Data Transfer.
The lower the package size, the higher the administration overhead.
Press . Define the package size per Application ID. If you do not specify a number, the default value is100. Refer to section IFRS package sizes / job name recognition for start values.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 14/34
2.1.3.3 Basel II – Credit Exposure – Package Size and Individual Parallelization
Start IMG (Transaction SPRO): Financial Services Bank Analyzer Credit Risk Analyzer CreditExposure General Settings Selection Define Application Parameters for Data Selection
Here, you determine the size of the packages per applications type (for example, “Exposure: CounterpartyRisk”). The right combination of data source package size SDPckSz and bundle package size Pack.Size hasto be determined with mass volume tests. It is an iterative process. Data source package size
- Start value = 100 (depending on complexity, far lower values might be necessary) Bundle package size
- Start value = 100 (depending on complexity, far lower values might be necessary) Factors influencing the decision to decrease or increase the values:
- Increased memory consumption in SM50/SM66 (> 1GB) – lower values- Throughput/hour measured with RBANK_PP_MONITOR – play to get optimal values- Long duration of parallel processing – decrease bundle package size- If you experience non-scalable run time of process step – play to get optimal values
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 15/34
Besides the general settings, there is another possibility to set the package size and parallelization perselection group under Edit Selection Groups.
Note: It is recommended to use this customizing setting per selection group only in case of a performanceissue, because the configuration per selection group ID overrides the general setting.
2.1.3.4 BW Extraction – Package Size
Start IMG (TA SPRO): Financial Services Bank Analyzer Disclosure & Reporting General Settingsfor Data Selection Selection Settings for Data Extraction Edit Basic Settings for Data Sources
Mark Group ID of Selection in the right pane and double-click Selection IDs in the left pane to get a view withall selection IDs.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 16/34
Double click the Description entry of the Selection ID you want to maintain to access the detailed view.
Here, the Package Size and the Number of Jobs can be maintained.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 17/34
2.1.3.5 Historization Runs (HDB)
Package Size
The settings for package size and job distribution can be individually set for each HDB selection ID.Depending of the HDB process, there are the different possible IMG entries where you might have toconfigure:
Financial Services Bank Analyzer Analytics Historical Database Set Up Data Layers SelectionSettings for Data Layers Edit Basic Settings for Data Sources
or
Financial Services Bank Analyzer Analytics Historical Database Configure CalculationFunctions Selection Settings for Calculation Functions Edit Basic Settings for Data Sources
or
Financial Services Bank Analyzer Analytics Historical Database Register In-House ModelSelection Settings for Model Edit Basic Settings for Data Sources
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 18/34
Mark Group ID of Selection in the right pane and double-click Selection IDs in the left pane to get a view withall selection IDs.
Double-click the Description entry of the Selection ID you want to maintain to access the detailed view.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 19/34
Then, enter the Package Size.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 20/34
3 Operations and Optimization
3.1 Monitoring Tools
The following sections Mass Activity Monitor Called MassMan and RBANK_PP_MONITOR describemonitoring tools that can be used to verify if the Parallelization and package size settings lead to theexpected throughput of a mass process.
3.2 Mass Activity Monitor Called MassMan
MassMan is a monitoring tool that basically displays the main information about the mass runs that arecurrently running or have been running on a given system. The aim of this functionality is to provideinformation like Parallelization settings that normally have to be collected using several different transactionson one single screen. Besides the monitoring functionality, MassMan is also a data collector for SAP SolutionManager business process monitoring, where all the information from MassMan can be reported and used forautomatic alerting.
MassMan can be implemented by applying the latest ST/API package on the relevant satellite system.
To open MassMan, use transaction ST13 and choose MASS_MAN_MONITORING application with F4 help.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 21/34
Always enter a date to avoid that old runs confuse the list of runs.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 22/34
The main idea is to ease the monitoring of the mass activities on a system and speed up the recognition ofproblems, their analysis, and the definition of necessary actions depending on the situations: Abnormal runtimes (low throughput, expected runtime is out of range) Unusual data volumes Run cancellations Processing problems (data quality)
Features: Cumulated view of mass runs information via ALV display:
- Status- Duration and estimated duration- Progress- Throughput- CPU and DB usage per server- Number and status of parallel jobs- Amount of processed data with categories, like accounts processed successfully, accounts failed- Detailed view of children jobs of a particular mass run- Convenient interface to standard analysis tools (sm37, sm66, PP monitor etc…)
Historization of data:- To compare behavior of future and past runs- Keep data even for deleted/archived runs
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 23/34
3.3 Using RBANK_PP_MONITOR
RBANK_PP_MONITOR provides information on currently active mass data processing.
Always choose a date to avoid that old runs confuse the following screen. Double-click the run you want tomonitor.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 24/34
Processing Status Percentage processed
Table data Total number of packages to be processed
Initial packages Packages not yet processed.
Collected packages Number of packages currently being processed, means also the no. of parallelprocesses
Returned packages No. of packages already processed
Restart packages No. of packages that were set to status “restart”. When all initial packages areprocessed then these packages are done again. Common reason is a lock problem.
Possible measure avoiding locks is reducing the package size.
Restart objects No. of objects with restart status
Retry packages No. of packages already processed but terminated because of an application-relatedproblem. Refer to the application log (SLG1)
Retry objects No. of objects not processed because of errors in the application.
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 25/34
4 Further Information
4.1 Background Information and References
More detailed information regarding FPP can be found: RunSAP DeveloperHandbook_FPP for Customer_Reports RunSAP Roadmap Quick-Link in SAP Service Marketplace – service.sap.com
https://service.sap.com/solutionmanagerbp Run SAP Roadmaps
4.2 Feedback and Questions
Click Feedback to send any comments on the content.
4.3 Available Application Categories in the Banking Services Solution
A list of all available application categories of Banking Services 6.0 linked to the mass processes is shown inthe list below.
To get the process description just use the F4 help
Application_Category Process Description
/BA1/B0AFR Balance Analyzer: Balance Data Transfer
/BA1/S2_IX RR Interface: Create Index
/BA1/S3_EX
/FSBPR/ACC Execute Mass Run Comb.Sttlmnt Accrual/Deferral
/FSBPR/BDC Mass Run - Determine Backdated Changes
/FSBPR/REV Mass Run - Reverse Combined Settlement
/FSBPR/SET Mass Run - Execute Combined Settlement
/FSBPR/TSE Mass Run - Request Account Settlement Date
/FSCCP/REQ Mass Run CCPC - Request Completion
/FSECP/ECP Mass Run for Cash Pooling
/FSFAC/EXT Mass Run for Extraction of Utilization Data
/FSFAC/GUA Mass Run for Monitoring Facilities
/FSFAC/MFA Mass Run for Activating Facilities
/FSFAC/MON Mass Run for Utilization Monitor - Fac. Processing
/FSFAC/REO Mass Run for Reorganization of Facilities Data
/FSPD/PDI1 Mass Run - Execute Payment Distribution
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 26/34
Application_Category Process Description
/FSPD/PDI2 Mass Run for Payt Distribution Postprocessing
/FSPD/PDI3 Mass Run for Monitoring Payment Distribution
/FSPDM/AMT Amount Calculation RMD and FMV
600 Print GL Data (Balance Sheet Preparation)
605 Archiving: Delete Object GL_BALPREP
615 Archiving: Delete Object GL_BALANCE
620 Archiving: Delete Object INVENTORY
625 Archiving: Delete Object SNITEM
630 Archiving: Delete Object RECONC
635 Archiving: Delete Object PRENOTE_T
640 Delete Object GL_SUMS
AF
AGG1 Strategy Analyzer(Aggregation Run:Pre-Aggregation)
AGG2 Strategy Analyzer (Aggregation Run:Interpretation)
AL Assets/Liabilities Determination
ALBOF Analytics Layer - Balance Object Framework
ALBOF_EPP Postprocessing for Event-Based SO Creation
ALWLSDL Analytics Layer - Creation of Worklist
AOST Balance Analyzer: Status Mgmt for Accounting Obj.
APLH Mass Run - Get Application Locks
AR01 Archiving: Analysis Object PAYMITEM
AR02 Archiving: Write Object PAYMITEM
AR03 Archiving: Analysis Object SETTLEMENT
AR04 Archiving: Write Object SETTLEMENT
AR05 Archiving: Analysis Object FIGURES
AR06 Archiving: Write Object FIGURES
AR07 Archiving: Analysis Object COUNTER
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 27/34
Application_Category Process Description
AR08 Archiving: Write Object COUNTER
AR09 Archiving: Analysis Object DISPORDER
AR10 Archiving: Write Object DISPORDER
AR11 Archiving: Analysis Object RELEASELOG
AR12 Archiving: Write Object RELEASELOG
AR13 Archiving: Analysis Object PLMDOC
AR14 Archiving: Write Object PLMDOC
AR15 Archiving: Analysis Object PRENOTE_B
AR16 Archiving: Write Object PRENOTE_B
AR17 Archiving: Analysis Object INDCOND
AR18 Archiving: Write Object INDCOND
AR19 Archiving: Analysis Object ORDER_COCP
AR20 Archiving: Write Object ORDER_COCP
AR21 Archiving: Analysis PAYMORDER
AR22 Archiving: Write Object PAYMORDER
AR23 Archiving: Analysis Object STANDORDER
AR24 Archiving: Write Object STANDORDER
AR25 Archiving: Analysis Object ORDER_COP
AR26 Archiving: Write Object ORDER_COP
AR27 Archiving: Analysis Object AM_CARD
AR28 Archiving: Write Object AM_CARD
AR29 Archiving: Analysis Object NOW_ABS
AR30 Archiving: Write Object NOW_ABS
AR31 Archiving: Analysis ORDER_TOC
AR32 Archiving: Write ORDER_TOC
AR33 Archiving: Analysis ORDER_NOW
AR34 Archiving: Write ORDER_NOW
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 28/34
Application_Category Process Description
AR35 Archiving: Analysis AM_ACCOUNT
AR36 Archiving: Write AM_ACCOUNT
AR37 Archiving: Analysis ORDER_CXA
AR38 Archiving: Write ORDER_CXA
ARE1 Archiving Engine - Analysis
BAETR Balance Analyzer: Process Results of Eff. Test
BAFP Balance Analyzer: Totals Calculation
BAPA_PCO1 Posting Control Office: Priority Update
BAPA_PCO2 Posting Control Office: Automatic Resubmission
BAPA_PCO3 Posting Control Office: Automatic Final Processing
BAPS Balance Analyzer: Process Standards
BAUS Balance Analyzer: Transfer of Int. BT: Fin. Trans.
BBP1 Balance Analyzer: Read SDL Business Transactions
BBP2 Balance Analyzer: Read Excel Business Transactions
BCA_ACCRUE Selection
BCA_ACR_EX Extraction of Accrual/Deferral Results
BCA_AISMGR Migration of AIS Data
BCA_BACKCH Backdated Changes
BCA_BANO Balance Confirmation
BCA_BAST Bank Statement
BCA_BL Mass Run for Billing (Generate)
BCA_BL_COR Mass Run for Billing (Adjustment)
BCA_BL_REV Mass Run for Billing (Reversal)
BCA_BOCA Product Change (Account): Edit Mass PC
BCA_BOCL Notice
BCA_BOCP Product Change (Account): Execute Due PC
BCA_BODC Product Change (Card): Execute Due PC
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 29/34
Application_Category Process Description
BCA_BODP Product Change (Card Pool): Execute Due PC
BCA_BORS Rescission
BCA_BOSC Product Change (Card): Edit Mass PC
BCA_BOSP Product Change (Card Pool): Edit Mass PC
BCA_BOTC Acct Closure: Edit Due Account Closures
BCA_BOTP Master Contract Termination: Edit Due
BCA_BSCHCK Balance Sheet Preparation Check
BCA_BSPREP Balance Sheet Preparation
BCA_BSPRPR Print Balance Sheet Preparation Data
BCA_CA_CRV CM: Credit Review
BCA_CA01 Renewal Run - Cards
BCA_CA02 Ordering File - Cards
BCA_CA04 Confirmation of Ordered Cards from Processor
BCA_CCON Cash Concentration
BCA_CHPAYR Change Payment Details
BCA_CL_CLO
BCA_CLEARG Clear Old Open Item
BCA_CLREXT External Clearing
BCA_CMPJOU Posting Journal
BCA_CNLINK Parallel Proc of Consistency Check - Link Table
BCA_CNS
BCA_COPR Correspondence Print Run
BCA_CRRV CM: Credit Review
BCA_DEBPOS TRBK: Instalment Savings Debit Position
BCA_DORM Dormancy and Escheat
BCA_DTCL TRBK: Posting Date Settlement Postings; No PP
BCA_DTPO TRBK: Posting Date Payment Transactions; No PP
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 30/34
Application_Category Process Description
BCA_DTTM TRBK: Close Posting Day for GL; No PP
BCA_ENQ1 TRBK: Process Items from ENQ; No PP
BCA_FORD Forward Order
BCA_GLTRAN TRBK: Transfer Postings to GL; No PP
BCA_INSMON TRBK: Instalment Monitoring
BCA_INV Inventory Preparation
BCA_INVA Inventory Preparation for Legacy Data Transfer
BCA_INVPR Print Result of Inventory
BCA_IT_EX Extraction of Item Data
BCA_LCFC Create Notices of Maturity
BCA_LCFD Call Fixed-Term Deposits
BCA_LCFX Fix Fixed-Term Deposits
BCA_LCIA Parallel Proc. - Action at End of Savings Scheme
BCA_LCIE Par. Proc. - Notice of Maturity - Sav. Agmnt End
BCA_LCIS Par. Proc. - Notice of Maturity Install. Agrmnt
BCA_MCCH Consistency Check for Master Contracts
BCA_MCM Master Contract - Master Data Distribution
BCA_PDM PDM Statement
BCA_PLMACT Activate PLM Document
BCA_PLMEN2 Close PLM Documents (Archiving Support)
BCA_PLMEND Close PLM Documents
BCA_PLMWF Start PLM Document Workflow
BCA_PP_SIF Small PP Interface
BCA_PPAUTO Parallel Proc. for Single Reports (Callback)
BCA_PVCA Product Version Change: Edit Mass Run PVC
BCA_PVCC Card Product Version Change
BCA_PVCP Card Pool Product Version Change
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 31/34
Application_Category Process Description
BCA_RENW
BCA_RLIM Trigger BP Role Check (No PP)
BCA_RREP Regulatory Reporting
BCA_RREPAV Regulatory Reporting - Worklist
BCA_SAB SAb MCM Mass Run Test
BCA_SET_AN Card Settlement Analysis
BCA_SETTLA Alternative Account Settlement
BCA_SETTLE Settlement (Acct, Mst Ctrct, Card, Card Pool)
BCA_SETTLP Simulate Account Settlement in Closed Period
BCA_SETTLR Reverse Settlement (Acct, Mst Ctrct, Card, C.Pool)
BCA_SL_EX Extraction of Settlement Data
BCA_SL_TX Control Run for Brazil
BCA_SORD Standing Order
BCA_TBBWAN BW Analysis
BCA_TBBWPS BW Postprocessing
BCA_UNDMGR Correct Erroneous Migration
BCA_UPDPER BCA_CN_PER_ACBAL Process Entries
BM01 Master Data Generation
BPBA Balance Analyzer: Balance Processing Basis
BPBA-FSIM Balance Processing Basis: FS Methods
BPTOB Balance Analyzer: Copy from Ledger
BPYEC Balance Analyzer: Annual Financial Statements
CA03 Master Data Changes - Card
CFHR Cash Flow Hedge Analysis: Main Run
CMS_AOU_CH
CMS_BCM_CG
CMS_BII_DX
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 32/34
Application_Category Process Description
CONVERTPB Changeover of Package Creation
DEMO Demonstration of Parallel Processing
DP Data Processing Framework (DPF)
EFT_ITEM Effectiveness Test for Granularity Items
F3_ODS_CC BA SDL: Client Copy of DataStore Object Data
FKKCORRA Analysis for Correspondence Archiving
FKKCORRW Write for Correspondence Archiving
FP_CBD_UPG Migration Position-Specific Calculation Basis
FP_CPA Method for Comparison of Plan and Actual Values
FPP1 Connection PPF to FPP
FPT_ Balance Analyzer: Preliminary Calc. Position Total
FS_DLL Bank Analyzer DLL: Data Transfer Process
FS_SGS_GEN Segmentation Service: Regeneration
FSBP_IDCHD Conversion of Change Document for Table BPID001
FSBP_IDNUM Replacement of Table BPID001
FSBP_MIGCS FSBP: Migration of Credit Standing Data
FSODP Overdraft Protection
FVH-BTS Fair Value Hedge Analysis: Create Time Series
FVHE Effectiveness Test for Fair Value Hedge
GLCP General Ledger Connector: Prepare Documents
GLCS General Ledger Connector: Send Documents
HMDA Hedge Management - Data Retrieval
HW_AGG RDL: Parallel Processing in Aggregation Function
KVAL Balance Analyzer: Key Date Valuation
KVALIA Balance Analyzer: Key Date Valuation
LM01 Parallel Processing of Totals Records for Limit M.
LMSM Limit Manager: Totals Record Processing
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 33/34
Application_Category Process Description
LMSN Limit Manager: Individual Record Processing
PA Processing Framework: Applications
PA_F Processing Framework Applications: For Files
PCAT Balance Analyzer: Create Accounting Totals
PCO1 Posting Control Office: Priority Update
PCO2 Posting Control Office: Automatic Resubmission
PCO3 Posting Control Office: Automatic Final Processing
PFVH Effectiveness Test for Portfolio Fair Value Hedge
PPF_TEST Test Application for Framework for Parallel Processing
PRCCAT_UPG Migrate Processing Category in Flows
PRI_BP_CNG Change of Business Partner Hierarchy
PRI_CN_CNG Change of Product Pricing List
PXAC_EXTSC Test
R201 Credit Exposure: CCR for Country Risk
R202 Credit Exposure: Issuer Risk
R205 Credit Exposure Framework for Basel II
RDB Result Database
SACO Strategy Analyzer (Correction Run)
SAEV Strategy Analyzer (Valuation Run)
TBBW Parallel Processing - BW Formatting
UPDPICC Balance Analyzer: Update PICC Documents
VPM Portfolio Items for Portfolio FV Hedging Rel.
VREV Balance Analyzer: Reversal of Key Date Valuation
VREVIA Balance Analyzer: Reversal of Key Date Valuation
YECL Balance Analyzer: Initialize Profit and Loss
Best PracticeParallelization, Packaging, Monitoring of SAP Banking
© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 34/34
© Copyright 2007 SAP AG. All Rights ReservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of CitrixSystems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Allother product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any formor for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP toany particular course of business, product strategy, and/or development. Please note that this document is subject to change and maybe changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you mayaccess through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.