Best Practice  Parallelization, Packaging, Monitoring             for SAP Banking                                         ...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingTable of Contents1 Management Summary                   ...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking1                  Management Summary1.1                ...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingThe prerequisite for the implementation of the FPP is th...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking2                  Best Practice Procedure and Verificat...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.1.2            Bank AnalyzerStart IMG (TA SPRO): Fin...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.1.3            Parallel Processing for Invoicing & O...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.2              Set Package SizeThe package size sett...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingFor some mass processes like Account Settlement Run, it ...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.3              Customizing Configuration for the Pac...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingAll application categories where the package size can be...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication Category           Process DescriptionBCA_DO...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingIn addition, there is an option to choose between static...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.3.3            Basel II – Credit Exposure – Package ...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingBesides the general settings, there is another possibili...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingDouble click the Description entry of the Selection ID y...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.3.5            Historization Runs (HDB)Package SizeT...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingMark Group ID of Selection in the right pane and double-...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingThen, enter the Package Size.© 2008 SAP AG - Best_Practi...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking3                  Operations and Optimization3.1       ...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingAlways enter a date to avoid that old runs confuse the l...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingThe main idea is to ease the monitoring of the mass acti...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking3.3                Using RBANK_PP_MONITORRBANK_PP_MONITO...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingProcessing Status        Percentage processedTable data ...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking4                  Further Information4.1               ...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process Description/FSPD/...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process DescriptionAR08  ...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process DescriptionAR35  ...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process DescriptionBCA_BO...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process DescriptionBCA_DT...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process DescriptionBCA_RE...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process DescriptionCONVER...
Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category           Process DescriptionLMSN  ...
Best PracticeParallelization, Packaging, Monitoring of SAP Banking© Copyright 2007 SAP AG. All Rights ReservedNo part of t...
Upcoming SlideShare
Loading in …5
×

Parallelization, packaging, monitoring for sap banking

1,952 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,952
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
97
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Parallelization, packaging, monitoring for sap banking

  1. 1. Best Practice Parallelization, Packaging, Monitoring for SAP Banking Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS customer 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 ManagementBest_Practice_Parallelization_Packaging_Monitoring_V21.doc – 03.11.2008
  2. 2. Best PracticeParallelization, Packaging, Monitoring of SAP BankingTable of Contents1 Management Summary 3 1.1 Goal of Using This Service 3 1.2 Parallelization and Packaging as Part of an Overall Performance Optimization Strategy 3 1.3 Staff and Skill Requirements 3 1.4 Design 3 1.5 System Requirements 42 Best Practice Procedure and Verification 5 2.1 Procedure 5 2.1.1 Configuration of Parallelization in Banking Services 5 2.1.1.1 Account Management & Loans 5 2.1.1.2 Bank Analyzer 6 2.1.1.3 Parallel Processing for Invoicing & Outbound Interface FPOITR in FI-CAx 7 2.1.2 Set Package Size 8 2.1.2.1 Account Management & Loans 8 2.1.3 Customizing Configuration for the Package Size 10 2.1.3.1 Invoicing & Outbound Interface FPOITR in FI-CAx 12 2.1.3.2 Accounting Scenarios 13 2.1.3.3 Basel II – Credit Exposure – Package Size and Individual Parallelization 14 2.1.3.4 BW Extraction – Package Size 15 2.1.3.5 Historization Runs (HDB) 173 Operations and Optimization 20 3.1 Monitoring Tools 20 3.2 Mass Activity Monitor Called MassMan 20 3.3 Using RBANK_PP_MONITOR 234 Further Information 25 4.1 Background Information and References 25 4.2 Feedback and Questions 25 4.3 Available Application Categories in the Banking Services Solution 25© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 2/34
  3. 3. Best PracticeParallelization, Packaging, Monitoring of SAP Banking1 Management Summary1.1 Goal of Using This ServiceIn 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 Optimization StrategyBesides 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 RequirementsTo 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 DesignThe 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”).© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 3/34
  4. 4. Best PracticeParallelization, Packaging, Monitoring of SAP BankingThe 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 processingFrom 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 contextThe following figure shows an overview of the structure of FPP and integration by the application.1.5 System RequirementsFPP 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).© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 4/34
  5. 5. Best PracticeParallelization, Packaging, Monitoring of SAP Banking2 Best Practice Procedure and Verification2.1 ProcedureThe following sections describes the steps to be taken to configure an appropriate Parallelization andpackage size.2.1.1 Configuration of Parallelization in Banking ServicesAlmost 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 & LoansStart IMG (TA SPRO): Financial Services Account Management Tools Parallel ProcessingMaintain Job Distribution© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 5/34
  6. 6. Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.1.2 Bank AnalyzerStart IMG (TA SPRO): Financial Services Bank Analyzer Basic Settings Parallel ProcessingMaintain Job DistributionPer 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 6/34
  7. 7. Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.1.3 Parallel Processing for Invoicing & Outbound Interface FPOITR in FI-CAxFor 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 7/34
  8. 8. Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.2 Set Package SizeThe 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 packageNote: 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 & LoansIn 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 8/34
  9. 9. Best PracticeParallelization, Packaging, Monitoring of SAP BankingFor 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 9/34
  10. 10. Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.3 Customizing Configuration for the Package SizeTo 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© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 10/34
  11. 11. Best PracticeParallelization, Packaging, Monitoring of SAP BankingAll 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 DistributionBAPA_PCO1 Posting Control Office: Priority UpdateBAPA_PCO2 Posting Control Office: Automatic ResubmissionBAPA_PCO3 Posting Control Office: Automatic Final ProcessingBCA_BOCP Product Change (Account): Execute Due PCBCA_BODC Product Change (Card): Execute Due PCBCA_BODP Product Change (Card Pool): Execute Due PCBCA_BOTC Acct Closure: Edit Due Account ClosuresBCA_CA01 Renewal Run - CardsBCA_CA02 Ordering File - CardsBCA_CA04 Confirmation of Ordered Cards from ProcessorBCA_CLEARG Clear Old Open ItemBCA_CLREXT External ClearingBCA_COPR Correspondence Print RunBCA_CRRV CM: Credit Review© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 11/34
  12. 12. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication Category Process DescriptionBCA_DORM Dormancy and EscheatBCA_FORD Forward OrderBCA_SORD Standing OrderBCA_BL Billing Run2.1.3.1 Invoicing & Outbound Interface FPOITR in FI-CAxFor 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.PressPress 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 12/34
  13. 13. Best PracticeParallelization, Packaging, Monitoring of SAP BankingIn 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 ScenariosStart IMG (transaction SPRO) Accounting “Merge-Scenario”: Financial Services Bank Analyzer Accounting Balance Analyzer After Generation Basic Settings Performance Optimization Set Package Size for Parallel Processing 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 ProcessingWith 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 packageThe 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 13/34
  14. 14. Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.3.3 Basel II – Credit Exposure – Package Size and Individual ParallelizationStart IMG (Transaction SPRO): Financial Services Bank Analyzer Credit Risk Analyzer CreditExposure General Settings Selection Define Application Parameters for Data SelectionHere, 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© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 14/34
  15. 15. Best PracticeParallelization, Packaging, Monitoring of SAP BankingBesides 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 SizeStart IMG (TA SPRO): Financial Services Bank Analyzer Disclosure & Reporting General Settingsfor Data Selection Selection Settings for Data Extraction Edit Basic Settings for Data SourcesMark Group ID of Selection in the right pane and double-click Selection IDs in the left pane to get a view withall selection IDs.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 15/34
  16. 16. Best PracticeParallelization, Packaging, Monitoring of SAP BankingDouble 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 16/34
  17. 17. Best PracticeParallelization, Packaging, Monitoring of SAP Banking2.1.3.5 Historization Runs (HDB)Package SizeThe 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 SourcesorFinancial Services Bank Analyzer Analytics Historical Database Configure CalculationFunctions Selection Settings for Calculation Functions Edit Basic Settings for Data SourcesorFinancial Services Bank Analyzer Analytics Historical Database Register In-House ModelSelection Settings for Model Edit Basic Settings for Data Sources© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 17/34
  18. 18. Best PracticeParallelization, Packaging, Monitoring of SAP BankingMark 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 18/34
  19. 19. Best PracticeParallelization, Packaging, Monitoring of SAP BankingThen, enter the Package Size.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 19/34
  20. 20. Best PracticeParallelization, Packaging, Monitoring of SAP Banking3 Operations and Optimization3.1 Monitoring ToolsThe 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 MassManMassMan 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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 20/34
  21. 21. Best PracticeParallelization, Packaging, Monitoring of SAP BankingAlways enter a date to avoid that old runs confuse the list of runs.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 21/34
  22. 22. Best PracticeParallelization, Packaging, Monitoring of SAP BankingThe 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© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 22/34
  23. 23. Best PracticeParallelization, Packaging, Monitoring of SAP Banking3.3 Using RBANK_PP_MONITORRBANK_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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 23/34
  24. 24. Best PracticeParallelization, Packaging, Monitoring of SAP BankingProcessing Status Percentage processedTable data Total number of packages to be processedInitial packages Packages not yet processed.Collected packages Number of packages currently being processed, means also the no. of parallel processesReturned packages No. of packages already processedRestart packages No. of packages that were set to status “restart”. When all initial packages are processed 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 statusRetry packages No. of packages already processed but terminated because of an application-related problem. Refer to the application log (SLG1)Retry objects No. of objects not processed because of errors in the application.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 24/34
  25. 25. Best PracticeParallelization, Packaging, Monitoring of SAP Banking4 Further Information4.1 Background Information and ReferencesMore 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 Roadmaps4.2 Feedback and QuestionsClick Feedback to send any comments on the content.4.3 Available Application Categories in the Banking Services SolutionA 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 helpApplication_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© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 25/34
  26. 26. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_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 FMV600 Print GL Data (Balance Sheet Preparation)605 Archiving: Delete Object GL_BALPREP615 Archiving: Delete Object GL_BALANCE620 Archiving: Delete Object INVENTORY625 Archiving: Delete Object SNITEM630 Archiving: Delete Object RECONC635 Archiving: Delete Object PRENOTE_T640 Delete Object GL_SUMSAFAGG1 Strategy Analyzer(Aggregation Run:Pre-Aggregation)AGG2 Strategy Analyzer (Aggregation Run:Interpretation)AL Assets/Liabilities DeterminationALBOF Analytics Layer - Balance Object FrameworkALBOF_EPP Postprocessing for Event-Based SO CreationALWLSDL Analytics Layer - Creation of WorklistAOST Balance Analyzer: Status Mgmt for Accounting Obj.APLH Mass Run - Get Application LocksAR01 Archiving: Analysis Object PAYMITEMAR02 Archiving: Write Object PAYMITEMAR03 Archiving: Analysis Object SETTLEMENTAR04 Archiving: Write Object SETTLEMENTAR05 Archiving: Analysis Object FIGURESAR06 Archiving: Write Object FIGURESAR07 Archiving: Analysis Object COUNTER© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 26/34
  27. 27. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category Process DescriptionAR08 Archiving: Write Object COUNTERAR09 Archiving: Analysis Object DISPORDERAR10 Archiving: Write Object DISPORDERAR11 Archiving: Analysis Object RELEASELOGAR12 Archiving: Write Object RELEASELOGAR13 Archiving: Analysis Object PLMDOCAR14 Archiving: Write Object PLMDOCAR15 Archiving: Analysis Object PRENOTE_BAR16 Archiving: Write Object PRENOTE_BAR17 Archiving: Analysis Object INDCONDAR18 Archiving: Write Object INDCONDAR19 Archiving: Analysis Object ORDER_COCPAR20 Archiving: Write Object ORDER_COCPAR21 Archiving: Analysis PAYMORDERAR22 Archiving: Write Object PAYMORDERAR23 Archiving: Analysis Object STANDORDERAR24 Archiving: Write Object STANDORDERAR25 Archiving: Analysis Object ORDER_COPAR26 Archiving: Write Object ORDER_COPAR27 Archiving: Analysis Object AM_CARDAR28 Archiving: Write Object AM_CARDAR29 Archiving: Analysis Object NOW_ABSAR30 Archiving: Write Object NOW_ABSAR31 Archiving: Analysis ORDER_TOCAR32 Archiving: Write ORDER_TOCAR33 Archiving: Analysis ORDER_NOWAR34 Archiving: Write ORDER_NOW© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 27/34
  28. 28. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category Process DescriptionAR35 Archiving: Analysis AM_ACCOUNTAR36 Archiving: Write AM_ACCOUNTAR37 Archiving: Analysis ORDER_CXAAR38 Archiving: Write ORDER_CXAARE1 Archiving Engine - AnalysisBAETR Balance Analyzer: Process Results of Eff. TestBAFP Balance Analyzer: Totals CalculationBAPA_PCO1 Posting Control Office: Priority UpdateBAPA_PCO2 Posting Control Office: Automatic ResubmissionBAPA_PCO3 Posting Control Office: Automatic Final ProcessingBAPS Balance Analyzer: Process StandardsBAUS Balance Analyzer: Transfer of Int. BT: Fin. Trans.BBP1 Balance Analyzer: Read SDL Business TransactionsBBP2 Balance Analyzer: Read Excel Business TransactionsBCA_ACCRUE SelectionBCA_ACR_EX Extraction of Accrual/Deferral ResultsBCA_AISMGR Migration of AIS DataBCA_BACKCH Backdated ChangesBCA_BANO Balance ConfirmationBCA_BAST Bank StatementBCA_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 PCBCA_BOCL NoticeBCA_BOCP Product Change (Account): Execute Due PCBCA_BODC Product Change (Card): Execute Due PC© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 28/34
  29. 29. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category Process DescriptionBCA_BODP Product Change (Card Pool): Execute Due PCBCA_BORS RescissionBCA_BOSC Product Change (Card): Edit Mass PCBCA_BOSP Product Change (Card Pool): Edit Mass PCBCA_BOTC Acct Closure: Edit Due Account ClosuresBCA_BOTP Master Contract Termination: Edit DueBCA_BSCHCK Balance Sheet Preparation CheckBCA_BSPREP Balance Sheet PreparationBCA_BSPRPR Print Balance Sheet Preparation DataBCA_CA_CRV CM: Credit ReviewBCA_CA01 Renewal Run - CardsBCA_CA02 Ordering File - CardsBCA_CA04 Confirmation of Ordered Cards from ProcessorBCA_CCON Cash ConcentrationBCA_CHPAYR Change Payment DetailsBCA_CL_CLOBCA_CLEARG Clear Old Open ItemBCA_CLREXT External ClearingBCA_CMPJOU Posting JournalBCA_CNLINK Parallel Proc of Consistency Check - Link TableBCA_CNSBCA_COPR Correspondence Print RunBCA_CRRV CM: Credit ReviewBCA_DEBPOS TRBK: Instalment Savings Debit PositionBCA_DORM Dormancy and EscheatBCA_DTCL TRBK: Posting Date Settlement Postings; No PPBCA_DTPO TRBK: Posting Date Payment Transactions; No PP© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 29/34
  30. 30. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category Process DescriptionBCA_DTTM TRBK: Close Posting Day for GL; No PPBCA_ENQ1 TRBK: Process Items from ENQ; No PPBCA_FORD Forward OrderBCA_GLTRAN TRBK: Transfer Postings to GL; No PPBCA_INSMON TRBK: Instalment MonitoringBCA_INV Inventory PreparationBCA_INVA Inventory Preparation for Legacy Data TransferBCA_INVPR Print Result of InventoryBCA_IT_EX Extraction of Item DataBCA_LCFC Create Notices of MaturityBCA_LCFD Call Fixed-Term DepositsBCA_LCFX Fix Fixed-Term DepositsBCA_LCIA Parallel Proc. - Action at End of Savings SchemeBCA_LCIE Par. Proc. - Notice of Maturity - Sav. Agmnt EndBCA_LCIS Par. Proc. - Notice of Maturity Install. AgrmntBCA_MCCH Consistency Check for Master ContractsBCA_MCM Master Contract - Master Data DistributionBCA_PDM PDM StatementBCA_PLMACT Activate PLM DocumentBCA_PLMEN2 Close PLM Documents (Archiving Support)BCA_PLMEND Close PLM DocumentsBCA_PLMWF Start PLM Document WorkflowBCA_PP_SIF Small PP InterfaceBCA_PPAUTO Parallel Proc. for Single Reports (Callback)BCA_PVCA Product Version Change: Edit Mass Run PVCBCA_PVCC Card Product Version ChangeBCA_PVCP Card Pool Product Version Change© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 30/34
  31. 31. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category Process DescriptionBCA_RENWBCA_RLIM Trigger BP Role Check (No PP)BCA_RREP Regulatory ReportingBCA_RREPAV Regulatory Reporting - WorklistBCA_SAB SAb MCM Mass Run TestBCA_SET_AN Card Settlement AnalysisBCA_SETTLA Alternative Account SettlementBCA_SETTLE Settlement (Acct, Mst Ctrct, Card, Card Pool)BCA_SETTLP Simulate Account Settlement in Closed PeriodBCA_SETTLR Reverse Settlement (Acct, Mst Ctrct, Card, C.Pool)BCA_SL_EX Extraction of Settlement DataBCA_SL_TX Control Run for BrazilBCA_SORD Standing OrderBCA_TBBWAN BW AnalysisBCA_TBBWPS BW PostprocessingBCA_UNDMGR Correct Erroneous MigrationBCA_UPDPER BCA_CN_PER_ACBAL Process EntriesBM01 Master Data GenerationBPBA Balance Analyzer: Balance Processing BasisBPBA-FSIM Balance Processing Basis: FS MethodsBPTOB Balance Analyzer: Copy from LedgerBPYEC Balance Analyzer: Annual Financial StatementsCA03 Master Data Changes - CardCFHR Cash Flow Hedge Analysis: Main RunCMS_AOU_CHCMS_BCM_CGCMS_BII_DX© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 31/34
  32. 32. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category Process DescriptionCONVERTPB Changeover of Package CreationDEMO Demonstration of Parallel ProcessingDP Data Processing Framework (DPF)EFT_ITEM Effectiveness Test for Granularity ItemsF3_ODS_CC BA SDL: Client Copy of DataStore Object DataFKKCORRA Analysis for Correspondence ArchivingFKKCORRW Write for Correspondence ArchivingFP_CBD_UPG Migration Position-Specific Calculation BasisFP_CPA Method for Comparison of Plan and Actual ValuesFPP1 Connection PPF to FPPFPT_ Balance Analyzer: Preliminary Calc. Position TotalFS_DLL Bank Analyzer DLL: Data Transfer ProcessFS_SGS_GEN Segmentation Service: RegenerationFSBP_IDCHD Conversion of Change Document for Table BPID001FSBP_IDNUM Replacement of Table BPID001FSBP_MIGCS FSBP: Migration of Credit Standing DataFSODP Overdraft ProtectionFVH-BTS Fair Value Hedge Analysis: Create Time SeriesFVHE Effectiveness Test for Fair Value HedgeGLCP General Ledger Connector: Prepare DocumentsGLCS General Ledger Connector: Send DocumentsHMDA Hedge Management - Data RetrievalHW_AGG RDL: Parallel Processing in Aggregation FunctionKVAL Balance Analyzer: Key Date ValuationKVALIA Balance Analyzer: Key Date ValuationLM01 Parallel Processing of Totals Records for Limit M.LMSM Limit Manager: Totals Record Processing© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 32/34
  33. 33. Best PracticeParallelization, Packaging, Monitoring of SAP BankingApplication_Category Process DescriptionLMSN Limit Manager: Individual Record ProcessingPA Processing Framework: ApplicationsPA_F Processing Framework Applications: For FilesPCAT Balance Analyzer: Create Accounting TotalsPCO1 Posting Control Office: Priority UpdatePCO2 Posting Control Office: Automatic ResubmissionPCO3 Posting Control Office: Automatic Final ProcessingPFVH Effectiveness Test for Portfolio Fair Value HedgePPF_TEST Test Application for Framework for Parallel ProcessingPRCCAT_UPG Migrate Processing Category in FlowsPRI_BP_CNG Change of Business Partner HierarchyPRI_CN_CNG Change of Product Pricing ListPXAC_EXTSC TestR201 Credit Exposure: CCR for Country RiskR202 Credit Exposure: Issuer RiskR205 Credit Exposure Framework for Basel IIRDB Result DatabaseSACO Strategy Analyzer (Correction Run)SAEV Strategy Analyzer (Valuation Run)TBBW Parallel Processing - BW FormattingUPDPICC Balance Analyzer: Update PICC DocumentsVPM Portfolio Items for Portfolio FV Hedging Rel.VREV Balance Analyzer: Reversal of Key Date ValuationVREVIA Balance Analyzer: Reversal of Key Date ValuationYECL Balance Analyzer: Initialize Profit and Loss© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 33/34
  34. 34. Best PracticeParallelization, Packaging, Monitoring of SAP Banking© 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 tradem arks 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 tradem arks 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 agreem ent 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-infringem ent.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.© 2008 SAP AG - Best_Practice_Parallelization_Packaging_Monitoring_V21.doc page 34/34

×