Data management concept for sap bank analyzer

6,252 views

Published on

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

No Downloads
Views
Total views
6,252
On SlideShare
0
From Embeds
0
Number of Embeds
28
Actions
Shares
0
Downloads
350
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Data management concept for sap bank analyzer

  1. 1. Best Practice Data Management Concept for SAP Bank Analyzer Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS customer published DATE VERSION Oct-28 2008 2.1 SOLUTION MANAGEMENT PHASE SAP SOLUTION Operations & Continuous Improvement Generic Best Practices for Bank Analyzer TOPIC AREA SOLUTION MANAGER AREA Data Management Concept for Bank Analyzer Data Volume ManagementBest_Practice_DVM_SAP_BA_V21.doc – 28.10.2008
  2. 2. Best PracticeData Management Concept for SAP Bank AnalyzerTable of Contents1 Management Summary 4 1.1 Goal of Using This Service 4 1.2 Alternative Practices 4 1.3 Staff and Skill Requirements 4 1.4 System Requirements 4 1.5 Duration and Timing 42 Best Practice Procedure 5 2.1 Why Data Management? 5 2.2 SAP Bank Analyzer Landscape 5 2.3 Archiving Objects 6 2.3.1 Source Data Layer 6 2.3.1.1 SDL Integration 6 2.3.1.2 SDL Archiving Objects 6 2.3.1.3 Reversal of Business Transaction 9 2.3.2 Business Partner (BP) 9 2.3.2.1 Versioning of Business Partners 9 2.3.2.2 Original Data of Business Partner 10 2.3.3 Accounting for Financial Instruments – Merge (AFI Merge) 11 2.3.3.1 Integration 11 2.3.3.2 Master Data Archiving Objects 11 2.3.3.3 Flow Data 11 2.3.3.4 Archiving According to the Residence Time 13 2.3.3.5 Archiving of Invalid Data 14 2.3.3.6 Archiving of Obsolete Data 14 2.3.4 Financial Position Balances 15 2.3.4.1 Balance Objects and Financial Statement Items 16 2.3.4.2 Archiving According the Residence Time 16 2.3.4.3 Archiving of Invalid Data 17 2.3.4.4 Archiving of Obsolete Data 17 2.3.5 Postings from Balance Processing 18 2.3.6 Financial Position Objects 18 2.3.7 Accounting Objects 19 2.4 Credit Exposure with Result Data Base (CRE-RDB) 20 2.4.1 Implementation Considerations 20 2.4.2 Integration 20 2.4.3 Result Data of Credit Exposure Runs 21 2.5 Credit Exposure with Result Data Layer (CRE-RDL) 22 2.5.1 Result Data Layer 22 2.5.2 Result Data of Credit Exposure Runs 22 2.5.3 Historical Database (HDB) 23 2.5.3.1 Data Aareas 24 2.5.3.2 Scenario Data Storage 24 2.5.3.3 Review Data Storage 25 2.5.3.4 Historical Data Storage 25 2.5.3.5 Data Processing Storage 26© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 2/34
  3. 3. Best PracticeData Management Concept for SAP Bank Analyzer 2.5.4 Other Objects 27 2.5.4.1 Correction Entries of Correction Server 27 2.5.4.2 Data Flow Entries of Correction Server 27 2.5.4.3 Administration Data of Processing Framework Runs 28 2.5.4.4 Archive Administration Data 29 2.5.4.5 Application Logs 29 2.6 House-Keeping 30 2.7 Deletion of Cross-Application Data 30 2.8 SAP Bank Analyzer Application-Specific Reorganization Programs 31Index of Table 34© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 3/34
  4. 4. Best PracticeData Management Concept for SAP Bank Analyzer1 Management Summary1.1 Goal of Using This ServiceCompanies expect high availability and continuity of their solutions, flexibility to react in a short time on legalor business changes, and lowering total cost of ownership (TCO).Optimized database growth of core business processes is one of key requirement for any successfuloperation in a banking environment.The IT department of a bank is usually facing the following challenges in this area: Legal requirements (governmental restrictions regarding archiving and retention periods) High performance requirements of mass data processing, which can be negatively impacted by huge database tables and fast database growth Reduction of TCO costs for the operation of the system, e.g. cost for system administration and disks requirements or increased time frame for DB reorganization. Limited time windows for archiving of tables because of the high workload of the system.This document will focus especially on the reduction/stabilization of total cost of ownership, by supporting youin setting up a data volume management concept for your SAP Bank Analyzer. The concept aims to definethe archiving objects that are mandatory for an archiving service for SAP Bank Analyzer.This Best Practice document introduces the SAP Bank Analyzer landscape by pointing out the differentcomponents and their relationship and dependencies for the data management of the solution. The chapter2.3 includes the entire, SAP Bank Analyzer-relevant archiving objects, the archiving prerequisites, archivingexecution and the cross-dependencies of the archiving objects with other system and components objects.1.2 Alternative PracticesSAP Bank Analyzer data management experts can deliver this Best Practice on-site by ordering a DataVolume Management service as part of a premium support engagement. This service is available within anSAP support engagement (that is SAP Enterprise Support, SAP Max Attention, SAP Safeguarding).1.3 Staff and Skill RequirementsTo implement this Best Practice, you require a Data Volume Management team, which is responsible for thesetup and monitoring of a data volume management strategy that defines how to manage and reduce futuredata growth and reduce existing database size by following a holistic approach that considers and integratesthe following options: data avoidance, data summarization, data deletion and data archiving.1.4 System RequirementsThe document is based on the releases SAP Bank Analyzer 4.2 and 5.0 and higher. For lower releases thearchiving objects and the recommendations may differ. Some archiving features are not available with earlierreleases than SAP Bank Analyzer 5.0.1.5 Duration and TimingThe duration and the timing of the Data Volume Management service have to be determined based on thescope and the needs of the customer.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 4/34
  5. 5. Best PracticeData Management Concept for SAP Bank Analyzer2 Best Practice ProcedureBefore performing this Best Practice, ensure that you perform the following preliminary tasks or checks in thesystem: Complete all installation and post-installation actions and procedures including customizing Ensure that the initial download has been successfully executed Apply all SAP recommendations from SAP service sessions and any SAP recommendations resulting from customer problem messages Implement all current SAP Support Packages upon availability2.1 Why Data Management?A Data Volume Management strategy contributes to Risk mitigation through early identification of unusual data volume increase with expert guidance how to reduce the data growth and data volume Reduction of TCO by early monitoring and control of data volume development and by minimizing the database size or the monthly data growth of SAP systems and SAP system landscape solutions using Best Practices and E2E operation standards.2.2 SAP Bank Analyzer LandscapeSAP Bank Analyzer supports overall bank controlling by calculating, evaluating, and analyzing financialproducts. The structure of SAP Bank Analyzer is based on the Integrated Finance and Risk Architecture(IFRA) and meets current requirements (International Accounting Standards (IAS), Basel II, Risk AdjustedPerformance Measurement, Sarbanes-Oxley) for the value range of financial products.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 5/34
  6. 6. Best PracticeData Management Concept for SAP Bank AnalyzerThe SAP Bank Analyzer solution is built up on a complex architecture and is spread over many components: Source Data Layer (SDL) Business Partner (BP) Accounting for Financial Instruments – Merge-Scenario (AFI Merge) Accounting for Financial Instruments – Subledger-Scenario (AFI Subledger) Credit Exposure (CRE) with Result Data Base Credit Exposure (CRE) with Result Data Layer Historical Database (HDB) Regulatory Reporting Analyzer (RRA) Profitability Management (PAMA) Asset Liability Management (ALM) Cross application (CA)There are strong dependencies between objects from different components or systems, e.g. SDL Contractsand Financial Position Objects of AccountingArchiving objects for Asset Liability Management, Profitability Management, Accounting for FinancialInstruments – Subledger and Regulatory Reporting Analyzer are currently not described in the document.2.3 Archiving Objects2.3.1 Source Data LayerThe following chapters describe the archiving objects in Source Data Layer (SDL).The system uses the Data Load Layer component to load original data from other operational systems orsource systems into SDL by means of an extraction, transformation, and loading process (ETL process).SDL saves, consolidates, and manages the original data. At the same time it provides interfaces to additionaloperational systems.The primary objects of SDL and their scenario versions are a flexible way of saving master data, flow data,and market data. They also group this data into units that belong together logically from a businessperspective. This ensures that the Bank Analyzer components that are linked to SDL have a standard,consistent data source.In addition to storing primary object data, SDL provides the following primary objects functions forapplications linked to it: Access to source data General functions for source data layer Methods for source data General access to corrections Tools2.3.1.1 SDL IntegrationSDL provides both, the central original data basis and a part of the underlying infrastructure for linkedapplications. It is therefore a key element in ensuring the consistency of data and results.2.3.1.2 SDL Archiving ObjectsWithin SDL, the following archiving objects are available.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 6/34
  7. 7. Best PracticeData Management Concept for SAP Bank AnalyzerArchiving object ObjectBA1_F1_040 Financial TransactionBA1_F1_041 Financial InstrumentsBA1_F1_042 Settlement AccountsBA1_F1_043 Securities Pos. AccountBA1_F1_044 G/L AccountBA1_F1_045 Customer Position AccountBA1_F1_047 Hedge RelationshipBA1_F1_048 Physical AssetsBA1_F1_049 Position Master DataBA1_F2_030 PositionBA1_F2_035 Business TransactionBA1_F4_FX Exchange RatesBA1_F4_FXV Exchange Rate VolatilitiesBA1_F4_IR Interest RatesBA1_F4_IRS Interest Rates SpreadsBA1_F4_IRV Interest Rates VolatilitiesBA1_F4_SEC Security PricesBA1_F4_SEV Security Prices VolatilitiesBA1_F5_016 Generic Market DataTable 1 Archiving Objects SDLArchiving PrerequisitesFrom the business point of view the residence has to be defined. This parameter can not be maintained intothe system settings. Basis of the definition of residence time is the business date of the data or the key dateof the object.From the technical point of view there are no existing prerequisites to archive data in archiving mode pro rata.The following cross dependencies between several objects are not checked because it is not needed.For archiving data in mode complete archiving there are following prerequisites The definition of selection criteria to find out which data can be archived is finalized.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 7/34
  8. 8. Best PracticeData Management Concept for SAP Bank Analyzer Select options to archive Master Data and Positions have to be stored into Index Data Store Objects (DSO) of BI. Archiving of Balance Master Data (AO Accounting Objects (AO), Financial Position Objects FPO) is executed previously therefore you have to define a process how to inactivate AO. The definition of the end of the lifecycle of Master Data and Position Data has to be implemented. To sign the closing of the data the unique field status has to be maintained with the value inactive or invalid. Archiving of Flow Data of SDL (Position, Business Transaction) is executed before Master Data. Archiving of Position of SDL is not executed before Position Master Data. Archiving of Market Data for Financial Instruments or Financial Transactions is executed before archiving of Financial Instruments or – Transactions. On Archiving of Master Data with any object relationship to other Master Data first it has to be archived the dependent object (e.g. loan with collateral has to be archived before collateral).For archiving data in mode obsolete data there are no prerequisites to be defined.For archiving data in mode pro rata there are no prerequisites to be defined.Archiving Execution Go to transaction SARA Select via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from Database tables Optional place file in Storage SystemCross-Dependencies with other system / components objects Between Master Data e.g. collateral and loan Between Master Data and Flow Data e.g. loan and the position of the loan Between Master Data and the Business Partner Between Master Data and Market Data Accounting Objects of the AFI Merge scenario based on Master Data and Flow Data in SDL. The assignment of primary objects is stored in table /BA1/B0_AO_PO3 SDL Data are the basis of the analytical processes of the Bank AnalyzerThis dependencies will be checked during archiving process if you use the flag “with dependency check”.Recommendation of Residence Time DefinitionBest practice benchmark for the definition of residence time is 15–18 months beginning from the first day ofthe new fiscal year.Due to the low data volume of market data, except generic market data, there is no archiving executed inpractice.Best practice benchmark for the definition of residence time for generic market data is also 15–18 monthsbeginning from the first day of the new fiscal year.To find out which data are archivable pro rata you can select archivable master data and position data viabusiness date or key date.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 8/34
  9. 9. Best PracticeData Management Concept for SAP Bank AnalyzerTo find out which data can be archived complete you should use the field AO_STATUS of the Index DSO ofthe BI. All closed deals and position data with status inactive or invalid have stored the value 08 in IndexDSO.Recommendation of Parallelization of ArchivingArchiving of master data and position data can be processed in parallel mode by manually packaging of thearchivable objects. To execute archiving jobs in parallel mode there is the possibility to use the fieldPACK_NO in the DSO of the frameworkobject.Depending on your settings on SAP Bank Analyzer and also on the value of available batch processes, youcan define following ranges: 1. 000000 – 099999 2. 100000 – 199999 3. ……. 4. 900000 – 9999992.3.1.3 Reversal of Business TransactionReversal of business transaction only can be processed if the original business transaction is stored intoDatabase of the application. If the original business transaction is archived it is not possible to reverse thisautomatically.2.3.2 Business Partner (BP)To archive business partner data there are two archiving objects used.Archiving object ObjectFSBP_VERS Versions of BPCA_BUPA Original Data of BPTable 2 Archiving Objects of BP2.3.2.1 Versioning of Business PartnersArchiving object: FSBP_VERSArchiving Prerequisites This chapter of the document is only valid if you have activated business partner versioning. From the business point of view you have to define the residence time. This parameter can not be maintained into the system settings. From the technical point of view there are no prerequisites to be defined.Cross-Dependencies with other system / components objects Between business partner and master data This cross dependency will be checked during the archiving of BP versions. It is possible to read and select archived BP.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 9/34
  10. 10. Best PracticeData Management Concept for SAP Bank Analyzer2.3.2.2 Original Data of Business PartnerArchiving object: CA_BUPAArchiving Prerequisites This chapter of the document is only valid if you did not activate business partner versioning, and no business partner versions were archived. Here it required to set the deletion/ archiving indicator. To be able to use the function specific to Financial Services for automatically setting the archiving indicator, proceed as follows: You are in the processing... screen for the transaction BUPA_PRE_DA. 1. If necessary, limit the number of business partners to be processed. 2. Set the value FSBP_RESID (residence time of BP in system) under Filter in the Variant for Additional Restrictions. 3. Only this filter value includes the settings made for the SAP Business Partner for Financial Services in the IMG activity Define Residence Time for Business Partners to Be Archived. 4. Set the Flag for Archiving and System Status “Can Be Archived” indicators under Set Deletion/Archiving Indicator. If BP versioning is activated, there are special regulations defined to archive the whole BP data from the system.Archiving complete business partnerTo archive the complete business partner (for all business partner versions) ensure that you archive theobjects in the following order: 1. First, archive object FSBP_VERS (Archiving of Business Partner Versions) to archive all objects from the mirror table of the business partner. 2. Then, archive object CA_BUPA (Archiving of Business Partners) to archive all objects from the original table of the business partner. 3. Do not run the relevant deletions until you have archived both objects. When you do so, make sure you run the deletions in the same order.Archiving execution Go to transaction SARA Select via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from Database tables Optional place file in Storage SystemCross-Dependencies with other system / components objects Between Master Data and the Business Partner Between Position Data and the Business PartnerThe dependencies will be checked during archiving process if you set the flag “with dependency check”during definition the archiving variant.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 10/34
  11. 11. Best PracticeData Management Concept for SAP Bank AnalyzerRecommendation of Residence Time DefinitionBest practice benchmark of definition of residence time is 15–18 months beginning from the first day of thenew fiscal year.To find out which data can be archived you can select the business partner versions data via key date. Thecomplete archiving of business partner original data is only possible if the archiving flag (field xdele) ismaintained.Recommendation of Parallelization of ArchivingSelect of archiving via business partner IDs is possible. As a range you can use 100,000 business partnerswithin one archiving job. Parallelization is depending on the available work processes on the server.2.3.3 Accounting for Financial Instruments – Merge (AFI Merge)The following chapters describe the archiving objects in AFI application.Balance Analyzer is one of two accounting scenarios in SAP Bank Analyzer and creates a complete annualfinancial statement conforming to parallel accounting standards in a heterogeneous system landscape.2.3.3.1 IntegrationBalance Analyzer is supplied with data from numerous source systems. This information is supplied first toSDL. Balance Analyzer then accesses the data contained in SDL.Balance Analyzer is linked to the other SAP Bank Analyzer applications as well as to SDL.2.3.3.2 Master Data Archiving ObjectsThe following table contains the archiving objects for master data.Archiving object ObjectBA1_B0_AO3 Accounting ObjectBA1_B0_FPO Financial Position ObjectsTable 3 Archiving Objects of AFI Master Data2.3.3.3 Flow DataThe following table contains the archiving objects for flow data.Archiving object ObjectAE* DocumentsBA1_B1_FPT Financial Position BalancesBA1_R4_055 Accounting Balances© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 11/34
  12. 12. Best PracticeData Management Concept for SAP Bank AnalyzerArchiving object ObjectBA1_R4_055 Balance ObjectsBA1_R4_055 Financial Statement ItemsBA1_B2_BPA Postings from Balance ProcessingTable 4 Archiving Objects of AFI Flow Data2.3.3.3.1 Accounting DocumentsArchiving object: AE* - generated by the systemArchiving Prerequisites From the business point of view the residence time has to be defined. This parameter can be maintained into the system settings of the IMG (Bank Analyzer Analytics Accounting: Merge Scenario Balance Analyzer After Generation Archiving Assign Residence Times for Flow Data/ Master Data) This residence time is maintained in Number of Periods for every accounting system and every legal entity. The residence time of documents must not be longer then the residence time of Master Data and Totals/ Balances From the technical point of view the archiving of other objects is not required. The posting periods for an archivable document have been (completely) closed. Accounting balances for the documents that can be archived have been calculated. Financial position balances have been calculated for the first day of the period that is not archived.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Documents and Accounting Balances Documents and Financial Position BalancesCross-dependencies will be checked during the execution of the write program.Recommendation of Residence Time DefinitionBest practice benchmark of definition of residence time is 15–18 months beginning from the first day of thenew fiscal year.To find out which data are archivable the definition of the residence time is mandatory and will be checkedduring the archiving process.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 12/34
  13. 13. Best PracticeData Management Concept for SAP Bank AnalyzerRecommendation of Parallelization of ArchivingBy definition the select option period and fiscal year it is possible to process documents each period inseparate archiving runs.Reversal of documentsReversal of documents only can be processed if the original document is stored into database of theapplication. If the original document is archived it is not possible to reverse this document automatically.2.3.3.3.2 Accounting BalancesArchiving object: BA1_R4_055Archiving of accounting balances can be executed with three categories: Archiving according the residence time Archiving of invalid data Archiving of obsolete data2.3.3.4 Archiving According to the Residence TimeArchiving Prerequisites From the business point of view the residence time has to be defined. This parameter can be maintained into the system settings of the IMG (Bank Analyzer Analytics Accounting: Merge Scenario Balance Analyzer After Generation Archiving Assign Residence Times for Flow Data/ Master Data) This residence time is maintained in Number of Periods for every accounting system and every legal entity. The residence time of documents must not be longer then the residence time of master data and totals/ balances The residence time for accounting balances must not be longer than that for master data. From the technical point of view the corresponding accounting documents have already been archived. All effected periods have been (completely) closed.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Documents and Accounting Balances Cross Dependencies will be checked during the execution of the write program.Recommendation of Residence Time DefinitionBest practice benchmark of definition of residence time is 15–18 months beginning from the first day of thenew fiscal year.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 13/34
  14. 14. Best PracticeData Management Concept for SAP Bank AnalyzerTo find out which data are archivable the definition of the residence time is mandatory and will be checkedduring the archiving process.The residence time check is no implemented on archiving mode of erroneous and obsolete data.Recommendation of Parallelization of ArchivingAt the moment it is possible to create a set of parallel work processes by execution the archiving writeprocesses via selection of period and fiscal year.Using of the FR ID additionally is not possible, because there is no technical relationship implemented.2.3.3.5 Archiving of Invalid DataArchiving Prerequisites The system does not check residence times, period closing, and dependencies related to other objects. RDB runs have to be flagged with the status invalid ( also can be maintained via table /BA1/B0_BP_BP)Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Not relevanceRecommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 3–6 months beginning from the first day of thenew fiscal period.To find out which data are archivable you can use the fields period and fiscal year.Recommendation of Parallelization of ArchivingEach archiving run can be executed with the select options Accounting (FR) ID an period and fiscal year.2.3.3.6 Archiving of Obsolete DataArchiving Prerequisites The system does not check residence times, period closing, and dependencies related to other objects. Except for the last valid run, all RDB runs for legal entities, accounting systems, periods, and fiscal years are written to an archive file.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 14/34
  15. 15. Best PracticeData Management Concept for SAP Bank Analyzer Optional place file in storage systemCross-Dependencies with other system / components objects Not relevanceRecommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 3–6 months beginning from the first day of thenew fiscal period.To find out which data are archivable you can use the fields period and fiscal year.Recommendation of Parallelization of ArchivingEach archiving run can be executed with the select options Accounting (FR) ID and period and fiscal year.2.3.4 Financial Position BalancesArchiving object: BA1_B1_FPTArchiving Prerequisites From the business point of view the residence time has to be defined. This parameter can be maintained into the system settings of the IMG (Bank Analyzer Analytics Accounting: Merge Scenario Balance Analyzer After Generation Archiving Assign Residence Times for Flow Data/ Master Data) This residence time is maintained in Number of Periods for every accounting system and every legal entity. The residence time of documents must not be longer then the residence time of Master Data and Totals/ Balances The residence time for financial position balances must not be longer than that for master data. From the technical point of view the corresponding accounting documents have already been archived. All effected periods have been (completely) closed.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Documents and Financial Position Balances Financial Position Balances and Financial Position Objects Cross Dependencies will be checked during the execution of the write program.Recommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 15–18 months beginning from the first day of thenew fiscal year.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 15/34
  16. 16. Best PracticeData Management Concept for SAP Bank AnalyzerTo find out which data are archivable the definition of the residence time is mandatory and will be checkedduring the archiving process.Recommendation of Parallelization of Archiving At the moment it is not possible to create a set of parallel work processes.2.3.4.1 Balance Objects and Financial Statement ItemsArchiving object: BA1_R4_055Archiving of Balance Objects and Financial Statement Items can be executed with three categories: Archiving according the residence time Archiving of invalid data Archiving of obsolete data2.3.4.2 Archiving According the Residence TimeArchiving Prerequisites From the business point of view the residence time has to be defined. This parameter can be maintained into the system settings of the IMG (Bank Analyzer Analytics Accounting: Merge Scenario Balance Analyzer After Generation Archiving Assign Residence Times for Flow Data/ Master Data) This residence time is maintained in Number of Periods for every accounting system and every legal entity. The residence time for balance objects must be the same as that for the accounting balances. The residence time for results data must not be longer than that for master data. All effected periods have been (completely) write protected. (Bank Analyzer Analytics Accounting: Merge Scenario Balance Analyzer Automatic Processing Further Processing Balance Processing Write Protect Data.Before you can write protect the periods, you must set the posting block in accounting.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Not relevanceRecommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 15–18 months beginning from the first day of thenew fiscal year.To find out which data are archivable the definition of the residence time is mandatory and will be checkedduring the archiving process.The residence time check is no implemented on archiving mode of erroneous and obsolete data.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 16/34
  17. 17. Best PracticeData Management Concept for SAP Bank AnalyzerRecommendation of Parallelization of ArchivingAt the moment it is not possible to create a set of parallel work processes.Using of the FR ID additionally is not possible at the moment.2.3.4.3 Archiving of Invalid DataArchiving Prerequisites The system does not check residence times, period closing, and dependencies related to other objects. Data from an erroneous financial reporting process for legal entities, accounting systems, periods, and fiscal years are written to archive files. RDB runs have to be flagged with the status invalid ( also can be maintained via table /BA1/B0_BP_BP)Archiving Execution Go to Transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Not relevanceRecommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 3–6 months beginning from the first day of thenew fiscal period.To find out which data are archivable you can use the fields period and fiscal year.Recommendation of Parallelization of ArchivingEach archiving run can be executed with the select options Accounting (FR) ID and period and fiscal year.2.3.4.4 Archiving of Obsolete DataArchiving Prerequisites The system does not check residence times, period closing, and dependencies related to other objects. Except for data from the last successfully-completed standard run, all data from all runs for legal entities, accounting systems, periods, and fiscal years are written to archive files.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Not relevance© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 17/34
  18. 18. Best PracticeData Management Concept for SAP Bank AnalyzerRecommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 3–6 months beginning from the first day of thenew fiscal period.To find out which data are archivable you can use the fields period and fiscal year.Recommendation of Parallelization of ArchivingEach archiving run can be executed with the select options Accounting (FR) ID and period and fiscal year.2.3.5 Postings from Balance ProcessingArchiving object: BA1_B2_BPAArchiving Prerequisites All effected periods have been (completely) closed. Closing will be check during archiving process.Archiving Execution Go to Transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Not relevanceRecommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 2–3 years beginning from the first day of the newfiscal year.To find out which data are archivable you can use the field fiscal year.Recommendation of Parallelization of ArchivingAt the moment it is not possible to create a set of parallel work processes.2.3.6 Financial Position ObjectsArchiving object: BA1_B0_FPOArchiving Prerequisites The master data residence times are specified in the application-specific Customizing for Master Data in Number of Months. This parameter can be maintained into the system settings of the IMG (Bank Analyzer Analytics Accounting: Merge Scenario Balance Analyzer After Generation Archiving Assign Residence Times for Master Data) The residence time of Master Data must be longer or equal then the residence time of Flow Data. The corresponding financial position balances are archived. The status of the corresponding Accounting Object has to be inactive.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 18/34
  19. 19. Best PracticeData Management Concept for SAP Bank AnalyzerArchiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Between Financial Position Objects and Accounting Objects Between Financial Position Objects and Financial Position BalancesThe dependencies will be checked during the archiving process.Recommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 24–36 months beginning from the first day of thenew fiscal year.The system automatically checked the maintained residence time and the invalidation of the correspondingAO during archiving process.Recommendation of Parallelization of ArchivingAt the moment it is not possible to create a set of parallel work processes.2.3.7 Accounting ObjectsArchiving object: BA1_B0_AO3Archiving Prerequisites The master data residence times are specified in the application-specific Customizing for Master Data in Number of Months. This parameter can be maintained into the system settings of the IMG (Bank Analyzer Analytics Accounting: Merge Scenario Balance Analyzer After Generation Archiving Assign Residence Times for Master Data) The residence time of Master Data must be longer or equal then the residence time of Flow Data. The corresponding financial position objects are archived. The corresponding balance objects and financial statement items are archived. The accounting object has been inactive since at least the residence time.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Between Accounting Objects and Financial Position Objects Between Accounting Objects and balance objects and financial statement items© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 19/34
  20. 20. Best PracticeData Management Concept for SAP Bank AnalyzerRecommendation of Residence Time DefinitionBest practice benchmarks of definition of residence time are 24–36 months beginning from the first day of thenew fiscal year.The system automatically checked the maintained residence time and the invalidation of the AO duringarchiving process.Recommendation of Parallelization of ArchivingAt the moment it is not possible to create a set of parallel work processes.2.4 Credit Exposure with Result Data Base (CRE-RDB)The following chapters describe the archiving objects in CRE Application.Credit Exposure contains an infrastructure that you can use to calculate exposure key figures such as theexposure at default and the capital requirement. You can adapt these key figures as required. By means ofthe calculation method and the settings you make in Customizing, you control the extent to which the systemcalculates key figures. This is referred to as the calculation level. You can choose one of the followingcalculation levels:... 1. Calculation Level 1 = Key figures are calculated at single-transaction level (for Basel II this means the calculation of the EAD) 2. Calculation Level 2 = Consideration of collateral instruments (for Basel II this means the calculation of the regulatory capital requirement)2.4.1 Implementation ConsiderationsIn order to meet the requirements of the regulations governing the capital charge, the following Basel IIapproaches can be used in Credit Exposure to measure credit risk: Standardized approach (simple standardized approach, comprehensive standardized approach) Internal ratings-based approach (IRB approach) - Foundation IRB approach - Advanced IRB approach2.4.2 IntegrationCredit Exposure is part of the Processes and Methods Layer in SAP Bank Analyzer. Various source systemssupply data to Credit Exposure. Rather than communicating directly with Credit Exposure or with theupstream General Calculation and Valuation Methods, these source systems first store the data in SDL. TheCredit Exposure solution can access master data and flow data in SDL that was either supplied by one of thesource systems or originally created in SDL.In Credit Exposure, you can use the results generated by the upstream General Calculation and ValuationMethods. The data is accessed using the Results Data Layer (RDL) or the Result Database (RDB), as this iswhere the results data from the General Calculation and Valuation methods is stored. You can use the resultsfrom the following methods: Account Pooling Facility Distribution Determination of the Free Line© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 20/34
  21. 21. Best PracticeData Management Concept for SAP Bank Analyzer Collateral Distribution Determination of DefaultThe results calculated in Credit Exposure are also stored in the Results Data Layer or in the Result Database.You define where results are stored for each client individually. You do so in Customizing under BankAnalyzer Processes and Methods General Calculation and Valuation Methods Storage of ResultsDefine Results Storage.You can then display the results data in reports in SAP NetWeaver Business Intelligence (BI), in theRegulatory Reporting Interface, or in the run administration function. Credit Exposure results can also beused in the runs for generating historical data, and stored in the Historical Database.2.4.3 Result Data of Credit Exposure RunsArchiving object: BA1_R4_063Archiving Prerequisites The CRE run is flagged with status AF (Archiving flag) Only CRE runs with status FINI can be flagged with the status Archiving flag (via Run administration)Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevanceRecommendation of Residence Time DefinitionCRE runs with key date on the end of a quarter or the end of the year should be stored between 15 and 18months. All other runs or invalid runs can be archived or deleted after 3 months.To find out which data can be archived you have to maintain the status of the single CRE run.Recommendation of Parallelization of ArchivingExecution of several archiving runs is possible because one archiving run only execute the archiving of onlyone CRE run.Recommendation of DeletionExecution of Deletion of Result Data of CRE runs is recommended/ only available for all runs with status notequal FINI. All result data that not needed for reporting also can be deleted.Before deletion the runs have to be flagged wit status Deletion flag via Run Administration. Deletion Job alsodeletes all entries in tables BA1_R4_RUN and BA1_R4_PACK.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 21/34
  22. 22. Best PracticeData Management Concept for SAP Bank Analyzer2.5 Credit Exposure with Result Data Layer (CRE-RDL)The following chapters describe the archiving objects in CRE application.2.5.1 Result Data LayerYou can use this component to store, display, and edit results data. This results data is based on accounting-related or risk-related analyses of financial transactions or financial instruments in SAP Bank Analyzer (BaselII, IAS Financial Reporting), or on analyses using other analysis tools. Results data is stored in the ResultsData Layer (RDL) in results data areas in the form of result types.The RDL is part of the Integrated Finance and Risk Architecture (IFRA). By means of common dimensions(for example, financial transaction ID, financial instrument ID, or legal entities) that are shared by resultswithin a results data area, the RDL provides a basis for the integration of results data. It stores data in aninfrastructure that is semantically and technically standardized, which enables standardized usage for existingand future applications that are integrated in the system.The RDL provides the following functions:Storage of results in results data areas Aggregation Versioning Archiving External interfaces User Interfaces2.5.2 Result Data of Credit Exposure RunsArchiving objects: /1BA/H*There are two archiving objects for result types that use result group versioning. The system uses onearchiving object for archiving result versions. The other archiving object is used if the result is to becompletely archived and if all versions were archived first.Archiving Prerequisites To run the Archiving Engine, you first have to create archiving objects per result type. You enter the data for aggregation in Customizing for Bank Analyzer under Results Data Layer Basic Settings Edit Technical Settings in Results Data Area. When you save, archiving objects are automatically generated. You can display the archiving objects under Results Data Layer Basic Settings Edit Data Structures in Results Data Area. This data is transferred to the Archiving Factory, where it is automatically integrated into an archiving scenario. This archiving scenario must be selected on the Archiving Engine interface if data is to be archived. Definition of the residence time each archiving scenarioArchiving Execution Go to transaction AR_ENGINE Define additional select options based on the Header table of the archiving scenario Start the Analysis process to analyze all archivable data under the technical point of view (Residence Time check) and if implemented under the business point of view (BADI Implementation) The “Write” process stores data in archive file© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 22/34
  23. 23. Best PracticeData Management Concept for SAP Bank Analyzer The “Delete” process deletes corresponding data from database tables Optional place file in storage system Monitoring possibleCross-Dependencies with other system / components objects No relevance Implementation of BADIs is possibleRecommendation of Residence Time DefinitionCRE runs with key date on the end of a quarter or the end of the year should be stored between 15 and 18months. All other runs or invalid runs can be archived or deleted after 3 months.To check which data can be archived it is mandatory to maintain the residence time.To archive invalid runs you have to maintain additionally Internal Result IDRecommendation of Parallelization of ArchivingParallelization of the archiving process can be controlled via settings of the maximum number of tasks andthe package size. These settings can be defined in customizing of the Archiving Scenario or during archivingprocess on execution the Archiving EngineRecommendation of DeletionExecution of Deletion of Result Data of CRE runs is not implemented.The Deletion flag can be maintained via Run Administration. Deletion Job only deletes all entries in tablesBA1_R4_RUN and BA1_R4_PACK not in RDL.2.5.3 Historical Database (HDB)The following chapters describe the archiving objects in the HDB application.Historical Database (HDB) is used to store the results of calculations (for example, recovery rates), and ascentral data store for the data from the various source systems. HDB can provide the calculation results andbasic information required by the reporting processes and supervisory review processes in SAP BankAnalyzer.The Basel II regulatory requirements apply to both the data upon which banks’ in-house models are based,and to the parameters that are used by these models. Particular attention must be paid to the historization ofthe parameters used in the calibration and validation processes. HDB hence stores data in a time-based way.This means that it is a central memory for information related to default data, and is optimized for time-basedevaluations. HDB provides a stable infrastructure, which ensures that histories can be created, even for longtime series.Since banks’ in-house models, and the related data requirements vary from one institution to the next, HDBhas an open architecture. You can therefore adjust the database to meet your individual requirements toensure that data is retained for all necessary parameters. HDB offers a large number of enhancements toenable future Basel II requirements to be met.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 23/34
  24. 24. Best PracticeData Management Concept for SAP Bank Analyzer2.5.3.1 Data AareasFollowing table describes the archiving objects of HDB.Archiving object ObjectBA1_R4_064 Scenario Data StorageBA1_R4_065 Review Data StorageBA1_R4_066 Historical Data StorageBA1_R4_067 Data Processing StorageTable 5 Archiving Objects of HDB2.5.3.2 Scenario Data StorageArchiving object: BA1_R4_064Archiving Prerequisites In the archiving control, you need to have already flagged RDB runs that you want to archive. From the business point of view the definition of a validity range of the RDB run has to be defined.Validity of the runsFor performance reasons, SAP recommends that you use the largest possible time period for the validity ofthe runs in months (for example, 24 months). However, using the smallest possible time period (for example,3 months) gives greater flexibility. Therefore, you need to find a balance between the need for greaterflexibility and for optimal system performance.If archiving is started for a particular time period, and then a new HDB run within this time period should bestarted, the system creates a new version for the RDB run.Archiving Execution Go to Transaction SARA or /BA1/R6_ARCH_SCEN Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevanceRecommendation of Residence Time DefinitionThere are no existing practice benchmarks and recommendations to setup a residence time.To setup one archiving scenario it is recommended to check how long the stored data are needed for internalprocesses.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 24/34
  25. 25. Best PracticeData Management Concept for SAP Bank AnalyzerFor high data volumes it is helpful to archive in short term corresponding to the defined residence time.Recommendation of Parallelization of Archiving No relevanceRecommendation of DeletionIt is possible to delete single HDB runs. The complete RDB runs only can be archived.2.5.3.3 Review Data StorageArchiving object: BA1_R4_065Archiving Prerequisites In the archiving control, you need to have already flagged the RDB runs that you want to archive. From the business point of view the definition of a validity range of the RDB run has to be defined.Archiving Execution Transaction SARA or /BA1/R6_ARCH_REV Selection via selection screen of the variant of the archiving process Write process stores data in archive file Delete process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevanceRecommendation of Residence Time DefinitionThere are no existing practice benchmarks and recommendations to setup a residence time.To setup one archiving scenario it is recommended to check how long the stored data are needed for internalprocessesFor high data volumes it is helpful to archive in short term corresponding to the defined residence time.Recommendation of Parallelization of Archiving No relevanceRecommendation of DeletionIt is possible to delete single HDB runs. The complete RDB runs only can be archived.2.5.3.4 Historical Data StorageArchiving object: BA1_R4_066Archiving Prerequisites In the archiving control, you need to have already flagged the RDB runs that you want to archive. From the business point of view the definition of a validity range of the RDB run has to be defined.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 25/34
  26. 26. Best PracticeData Management Concept for SAP Bank AnalyzerArchiving Execution Go to Transaction SARA or /BA1/R6_ARCH_HIST Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevanceRecommendation of Residence Time DefinitionThere are no existing practice benchmarks and recommendations to setup a residence time.To setup one archiving scenario it is recommended to check how long the stored data are needed for internalprocessesFor high data volumes it is helpful to archive in short term corresponding to the defined residence time.Recommendation of Parallelization of Archiving No relevanceRecommendation of DeletionIt is possible to delete single HDB runs. The complete RDB runs only can be archived.2.5.3.5 Data Processing StorageArchiving object: BA1_R4_067Archiving Prerequisites In the archiving control, you need to have already flagged the RDB runs that you want to archive. From the business point of view the definition of a validity range of the RDB run has to be defined.Archiving Execution Go to transaction SARA or /BA1/R6_ARCH_REV Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevanceRecommendation of Residence Time DefinitionThere are no existing practice benchmarks and recommendations to setup a residence time.To setup one archiving scenario it is recommended to check how long the stored data are needed for internalprocessesFor high data volumes it is helpful to archive in short term corresponding to the defined residence time.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 26/34
  27. 27. Best PracticeData Management Concept for SAP Bank AnalyzerRecommendation of Parallelization of Archiving No relevanceRecommendation of DeletionIt is possible to delete the Data Processing Storage. The deletion should be processed before each newexecution of the HDB processing.2.5.4 Other ObjectsThe following chapters describe the archiving objects of other objects.2.5.4.1 Correction Entries of Correction ServerArchiving object: BA1_FK_CORArchiving Prerequisites From the business point of view the residence time has to be defined.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevanceRecommendation of Residence Time Definition Data can be archived after 3–6 monthsTo find out which data can be archived you can use the fields Time stamp, Business date or the field Olderthan … years on the selection screen of the archiving process.Recommendation of Parallelization of Archiving It is not possible to archive data in parallel mode.Recommendation of DeletionDeletion is not possible.2.5.4.2 Data Flow Entries of Correction ServerArchiving object: BA1_FK_DFWArchiving Prerequisites From the business point of view the residence time has to be defined.Archiving Execution Go to transaction SARA© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 27/34
  28. 28. Best PracticeData Management Concept for SAP Bank Analyzer Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevance ..Recommendation of Residence Time Definition Data can be archived after 3–6 monthsTo find out which data can be archived you can use the fields Time stamp, Business date or the field Olderthan … years on the selection screen of the archiving process.Recommendation of Parallelization of Archiving No relevance ..Recommendation of DeletionDeletion is not possible.2.5.4.3 Administration Data of Processing Framework RunsArchiving object: BA1_PFW*Administration data of data export from SDL to other application will be archived with this archiving method.Archiving Prerequisites From the business point of view the definition of residence time has to be defined.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects No relevanceRecommendation of Residence Time Definition Data can be archived after 3–6 months.Recommendation of Parallelization of Archiving No relevanceRecommendation of DeletionDeletion is not possible.© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 28/34
  29. 29. Best PracticeData Management Concept for SAP Bank Analyzer2.5.4.4 Archive Administration DataArchiving object: BC_ARCHIVEArchiving Prerequisites From the business point of view the residence time has to be defined. If data are deleted it is not possible to administrate archived data within the ADK.Archiving Execution Go to transaction SARA Selection via selection screen of the variant of the archiving process The “Write” process stores data in archive file The “Delete” process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Archive Administration and Archive Files Archive Administration and Archive Info System Archive Administration and Archive ExplorerThere is no check during the archiving process. If the administration data are archived and deleted you cannot administrate archive files within ADK.Recommendation of Residence Time DefinitionArchive Administration for all archived data that have no relevance for the legal requirements of archiveddata.Administration for all archive runs of erroneous or obsolete data can be archived in short term after thearchiving of this application data. Benchmarks are between 3 and 6 months.Administration of archive runs by using residence time should be archived according the requirements of theaccess of archived data.Recommendation of Parallelization of Archiving No relevanceRecommendation of DeletionDeletion is not possible.2.5.4.5 Application LogsArchiving object: BC_SBALArchiving Prerequisites From the business point of view the residence time has to be defined according the residence time of the application dataArchiving Execution Transaction SARA© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 29/34
  30. 30. Best PracticeData Management Concept for SAP Bank Analyzer Selection via selection screen of the variant of the archiving process Write process stores data in archive file Delete process deletes corresponding data from database tables Optional place file in storage systemCross-Dependencies with other system / components objects Application Logs and Application processesRecommendation of Residence Time DefinitionThe residence time of application logs has to be defined according the residence time of the application data.If this data are not be required the residence time should be defined between 3 and 6 months.To find out which data can be archived the fields From… to can be used.Recommendation of Parallelization of Archiving No relevanceRecommendation of DeletionDeletion is not possible.2.6 House-Keeping2.7 Deletion of Cross-Application DataThere are a number of jobs that must periodically run in a live installation, for example, to delete outdatedjobs or spool objects. As of release 4.6C, you can easily schedule these jobs as follows: SAP TransactionSM36, press button Standard jobs.The list below contains the required programs, their parameters, and the recommended repeat interval whichare necessary for the house-keeping. In addition, names are suggested for the required jobs. Adhere to therecommendations, as the naming conventions enable us to check quickly and easily whether these jobs havebeen activated in your system.Please review SAP Note 16083 ‘Standard jobs, reorganization jobs’ to get detailed information regarding thejobs to be considered.Standard house-keeping jobs without application-specific reorganization programs: Job Name Program Variant Repeat- Client- Interval dependent SAP_REORG_JOBS RSBTCDEL Yes Daily No SAP_REORG_SPOOL RSPO0041/1041 Yes Daily Yes SAP_REORG_BATCHINPUT RSBDCREO Yes Daily Yes SAP_REORG_ABAPDUMPS RSSNAPDL /RSNAPJOB Yes Daily No SAP_REORG_JOBSTATISTIC RSBPSTDE Yes Monthly No© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 30/34
  31. 31. Best PracticeData Management Concept for SAP Bank Analyzer Job Name Program Variant Repeat- Client- Interval dependent SAP_COLLECTOR_FOR_ RSBPCOLL No Daily No JOBSTATISTIC SAP_COLLECTOR_FOR_ RSCOLL00 No No PERFMONITOR SAP_REORG_PRIPARAMS RSBTCPRIDEL No Monthly SAP_REORG_XMILOG RSMILOGREORG Yes Weekly No SAP_CCMS_MONI_BATCH_DP RSAL_BATCH_TOOL_ No DISPATCHING RSPO0041/1041 RSPO0041 /1041 Yes Daily RSPO1043 RSPO1043 Yes Daily Spool- consistency Batch Delete expired logs SBAL_DELETE NoTable 6 Standard House-KeepingThe deletion reports for the following data should be scheduled on a regular basis: Batch Input data table APQD RFC-Call data table ARFCSDATA ABAP Dumps table SNAP TemSe/Spool data table TST03Tables VBDATA, VBMOD and VBHDR contain information about incomplete update requests (updaterequests that have not been executed yet). Update terminations and short dumps should be analyzedregularly and in detail by system administration (SAP transaction SM13).2.8 SAP Bank Analyzer Application-Specific Reorganization ProgramsData stored in the SDL, RDB and RDL cannot be deleted but only archived. During the archiving procedurethe run administration information will not be deleted. After archiving runs with the purpose to delete the dataafterwards, e.g. for erroneous data, which must not be kept, the run administration can be deleted withadditional deletion programs.Furthermore deletion reports for other areas (e.g. bundling services) are available:© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 31/34
  32. 32. Best PracticeData Management Concept for SAP Bank AnalyzerSAP Bank Analyzer application-specific reorganization programs: Program Function/Affected table(s) Deletion of bundling data /BA1/FP_OBS_R, /BA1/RFP_OBSDB_DELETE /BA1/FP_OBS_RS (Transaction /BA1/FP_ODSDB_DELETE) /BA1/FP_OBS_O /BA1/FP_OBS_H /BA1/FP_OBS_L /BA1/RF3_DS_PACK /BA1/F3_DS_SELH (Transaction /BA1/F3_DS_PACK) /BA1/F3_DS_SELPA /BA1/RF3_GDS_DATAPACK Year end closings or accounting balances: RBANK_DELETE_RUNS BANK_WORKL_PACK BANK_PACKMAN_OBJ Balance processor packages ONLY: /BA1/RB2_MAP_BP_BAS_PACK_CLEAR BANK_WORKL_PACK BANK_PACKMAN_OBJ /BA1/R2_JOB_ADMIN_DELETE2 Administration data of credit exposure runs /BA1/R2_WRKTABS_DELETE Administration data of work tables /BA1/R2_JOB_ADMIN_DELETE Administration tables of country risk runs Administration data of HDB runs: /BA1/R4_HDB(1-3)_LAY /BA1/R6_JOB_ADMIN_DELETE /BA1/R4/KFSTRC /BA1/R4_PACK /BA1/R4_REC_HDB(1,2,3,5) /BA1/R4_RUN /BA1/R6_ESY_RECORDS_DELETE HDB: Data processing storage /BA1/R6_SCENARIO_DELETE HDB: Scenario data /BA1/R5_JOB_ADM_DELETE Cashflow-Hedge-Analysis data /BA1/RA_SCENARIO_DELETE HDB: Scenario data Data from General Methods /BA1/DE_JOB_ADMIN_DELETE /BA1/R4/KFSTRC /BA1/R4_PACK /BA1/R4_RUN /BA1/R8_JOB_ADM_DELETE Administration data of Fair Value Tests© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 32/34
  33. 33. Best PracticeData Management Concept for SAP Bank Analyzer Program Function/Affected table(s) Display/deletion of business transaction from /BA1/RB1_PBTP_DEL_WLIST parallel proc. tools WL /BA1/RB0_STAT_DELETE Delete statistics of processed objects (Transaction /BA1/B0_STAT_DELETE) BANK_SGS_REORGANIZATION_SINGLE Reorganization of single SGS structure (Transaction BANK_SGS_REORG_SING) BANK_SGS_REORGANIZATION_MASS Reorganization of multiple SGS structure (Transaction BANK_SGS_REORG_MULT)Table 7 House-Keeping SAP Bank Analyzer© 2008 SAP AG - Best_Practice_DVM_SAP_BA_V21.doc page 33/34
  34. 34. Best PracticeData Management Concept for SAP Bank AnalyzerIndex of TableTable 1 Archiving Objects SDL 7Table 2 Archiving Objects of BP 9Table 3 Archiving Objects of AFI Master Data 11Table 4 Archiving Objects of AFI Flow Data 12Table 5 Archiving Objects of HDB 24Table 6 Standard House-Keeping 31Table 7 House -Keeping SAP Bank Analyzer 33© 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_DVM_SAP_BA_V21.doc page 34/34

×