• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Sap test data migration server for banking solutions
 

Sap test data migration server for banking solutions

on

  • 1,689 views

 

Statistics

Views

Total Views
1,689
Views on SlideShare
1,689
Embed Views
0

Actions

Likes
0
Downloads
72
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Sap test data migration server for banking solutions Sap test data migration server for banking solutions Document Transcript

    • Best Practice SAP Test Data Migration Server for Banking Solutions Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS customer published DATE VERSION June 10 2009 3.0 SOLUTION MANAGEMENT PHASE SAP SOLUTION Operations & Optimizations SAP for Banking TOPIC AREA SOLUTION MANAGER AREA SAP Solution Management Change ManagementBP_TDMS_V30.doc – 10.06.2009
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsTable of Contents1 Management Summary 3 1.1 Goal of Using this SAP Product 4 1.2 Alternative Practices 5 1.3 Staff and Skills Requirements 6 1.4 System Requirements 6 1.5 Duration and Timing 72 Best Practice 9 2.1 Preliminary Tasks 9 2.1.1 Test Management 9 2.1.2 Solution Landscape 10 2.2 General Procedure for TDMS 12 2.2.1 Preparing the System Landscape 12 2.2.1.1 Set up TDMS server 12 2.2.1.2 Set up receiver system 12 2.2.1.3 Set up sender system 12 2.2.1.4 Set up RFC connections 13 2.2.2 Set up a non-production system 13 2.2.2.1 Procedure for master data & customizing 13 2.2.2.2 Time-based reduction of master and transaction data 13 2.2.2.3 Data selection by business processes or business objects (BPL) 14 2.2.2.4 Scrambling procedure for master and transaction data 15 2.3 TDMS for SAP Banking Services Deposits Management 16 2.3.1 Introduction of TDMS scenario 16 2.3.2 Deposit Management data model 17 2.3.3 Reduction of master and transaction data 18 2.3.3.1 Selection based on external account 19 2.3.3.2 Selection based on business partner account holder 19 2.3.3.3 Selection based on the product 19 2.3.3.4 Additional selection for business partner 19 2.3.3.5 Tables of master and transaction data for reduction 20 2.3.4 Scrambling for master and transaction data 213 Further Information 22 3.1 Background Information and References 22 3.2 Troubleshooting 22Index of Figures 23Index of Tables 23© 2009 SAP AG page 2/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions1 Management SummaryThis Best Practice document introduces SAP Test Data Migration Server (SAP TDMS) as technicalsolution provided by SAP to manage main challenges for banking customers to test their productivesolution. These challenges are caused by the typical situation of customer with banking solution: Enormous high data volume (e.g. Account Management und Bank Analyzer), because the banking solutions are build and used for mass volume retail banking and enterprise wide analysis on single transaction level. Productive systems can easily reach sizes of 1 to 5 terabyte. Need for test of productive data in test environment to ensure that new functionality or support packages as well as upgraded solutions will work smoothly. This demand is usually combined with the need for selective data transfer methods in order to reduce resource requirement (less cost for test landscape). Security and access sensitive customer data need to be anonyms before provided as test data in non productive environments.The SAP TDMS solution is part of SAP recommendation in the SAP Solution Operation Standard for TestManagement which contains SAP best-practice approaches for End-to-End (E2E) test management. Aspart of the test management standard the Test Data Migration Server provides the technical infrastructureto transfer test data out of the production environment into test and other non-production systems withsignificantly reduced data volume. This is shown in the figure below for a three system landscape.Especially the size of the QA and test environment will be reduced significantly in comparison to a systemcopy.Figure 1: Current vs. futureA high level explanation of TDMS is given in the document in order to introduce the basic functions andprinciples. For more detailed information links to the TDMS information sources and SAP servicesofferings are provided in chapter 3 Further Information.© 2009 SAP AG page 3/24
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsFor SAP Deposit Management as part of banking services the SAP Test Data Migration Server scenario isdeveloped by SAP System Landscape Optimization development for the specific contract type accounts.As basis of the scenario the Deposits Management data model with central master and transaction data isexplained. The scenario description focuses on the specific data selection variants, tables relevant forreduced data transfer and the used scrambling functionality. The necessary system landscape is alsodescribed including the recommended usage of SAP Solution Manager as TDMS server.1.1 Goal of Using this SAP ProductSAP TDMS is used for creating and refreshing non-production systems (test systems, training systems,quality assurance systems, development systems) with a reduced dataset. Note that it is not meant to beused for creating production systems.SAP TDMS operates at client level, that is, the selected data from a client in the sender system is copiedto a client in an existing system (non-production system). The rationale behind SAP TDMS is as follows:Approximately 80 % of the data volume of a typical database is contained in less than 10 % of the tables.The biggest tables are normally transaction data tables.Figure 2: SRC system – test systemThis means that small non-production systems for different purposes can be created by including onlythose parts of the data that is really required for the test of new or existing functionality.Use the Test Data Migration Server for SAP Banking Services to be able to easily extract test data fromthe production environment with high data quality to assure effective testing of changes and duringimplementation projects or the upgrade of the solution. With the setup of selective data extraction by© 2009 SAP AG page 4/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutionsaccount number, product or business partner test data transfer can be exactly aligned to the relevant testscenarios. Security critical data can be scrambled during extraction.To summarize the advantages of TDMS Saves disk space of non-production systems Provides test data from the current productive system (testing on real production data) Selective data extraction to achieve a reduced data volume on the test systems TCO reduction by transfer of data between different OS/DB Individual refresh of non-productive clients possible Provides a framework to scramble secure and sensitive data to security standardsSAP System Landscape Optimization (SLO) development provides a SAP Banking Service scenario forDeposit Management that focuses on contract type account. This scenario is based on SAP BankingServices release 6.0 (FSAPPL 200). This service provides the banking specific content for data transferwith SAP TDMS.For further information and service request see TDMS information area at SAP Service Marketplace:http://service.sap.de/tdms.1.2 Alternative PracticesFor providing test data different practices are used. Some of them are listed below with a shortassessment. All of them lack in providing efficient data transfer of production data for test cases forsolution operation.Data transfer to test environment provided by client/system copyTransfers of data via client/system copy will transfer complete master and transaction data of a SAPsolution, but also transfer the current set of coding and configuration (e.g. SAP Customizing) from sourcesystem.Disadvantages: no data reduction for testing on productive data raise similar hardware cost in test environment as in production not suitable for single transaction tests time consuming procedure plain data transfer causes security issues on customer dataManual test data creationTest data will be created manually following detailed instructions. In order to simulate the variances ofproductive data a wide range of data has to be created. This scenario applies especially when solutionsare setup initially during implementation projects before migrated test data are available.Disadvantages: High effort on data creation Not real productive data used for testingData transfer via custom programsCustomer can build up own program similar to migration programs.© 2009 SAP AG page 5/24
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsDisadvantages: Programs have to be build and tested High efforts for deeply structured data models as SAP BankingSAP Mass Data Generator toolThe tool is provided by SAP Active Global Support to build up mass data and early performance testingpossibilities. The tool is limited to replicate template data, which means the same account or businesspartner is multiplied. The SAP Mass Data Generator is not suitable for functional testing.1.3 Staff and Skills RequirementsBased on the experiences with other SAP Banking implementation the TDMS server should be in theresponsibility of the basis team. Independent from the responsibilities of the test data migration server youneed at least the following skills to support the test data migration server appropriately. SAP basis person with advanced knowledge in the area of SAP basis/system copy and client copy Developer for customer specific enhancements e.g. additional selection criteria SAP Banking consultant who is familiar with the customizing of the banking services system, who can validate if the transferred data will work on the receiver system and who can verify the customizing settingsFor build up TDMS specific knowledge and skills SAP provides trainings to up skill project and operationsteam (access via http://www.sap.com/education). Search there for the TDMS courses. Training ID Title Course Type TDMS10 SAP Test Data Migration Server 3.0 3 days, Instructor-led Classroom OTDMS3 Online Knowledge Product SAP Test Data Migration E-Learning, ~ 4:30 hours Server (TDMS) 3.0Table 1: Current SAP Education offering for TDMS1.4 System RequirementsThe system infrastructure for a data transfer using SAP TDMS requires the following system roles: A sender system (client) from which the data supply for the non-production system is taken (usually the production system). The TDMS server, which includes: - A central system (client) on which the settings and customizing for the setup of the non-production system are stored - A control system (client) from which almost all activities for SAP TDMS are triggered and monitored A receiver system (client) (the non-production system to be filled)The systems should meet the following technical requirements:TDMS Server: SAP system with Web AS 6.20, 6.40 or NetWeaver 7.00 and SAP ABA can act as TDMSServer. The technical restriction can easily be solved with SAP Solution Manager 7.0 (SAP_BASIS =701),© 2009 SAP AG page 6/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutionsbecause SAP Solution Manager runs on NetWeaver 7.00. As central system in the customer solutionlandscape SAP Solution Manager would be an appropriate system for the test data migration server.Sender and Receiver System: SAP system with Web AS 6.20, 6.40 or NetWeaver 7.00 could act assender and receiver systems. This would apply for SAP Transaction Banking versionsTRBK 3.0 / TRBK4.0. As the SAP Banking Services 5.0/6.0 (FSAPPL =100/200) solution is based on SAP NetWeaver 7.10and currently (status Q2/2009) no general availability for NetWeaver 7.10 systems is released, usage ofTDMS is limited to a project solution for SAP NetWeaver 7.1 system with a limited SAP product supportuntil it will be released.Requirements for technical settings are described in SAP Note 890797.1.5 Duration and TimingThe planning of test management should be already part of implementation project or a solution operationstandard implementation. One central step of an implementation project is testing. For the preparation ofthe test cases appropriate test data has to be setup (phase Test Planning System Setup). If the projectsare not first implementations (normally upgrade and enhancement projects) the TDMS server isrecommended be implemented before the start of the test phase to setup capability to transfer data out ofproductive environment.Figure 3: Test managem ent phases for projects© 2009 SAP AG page 7/24
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsFor an initial implementation of TDMS server and test data transfer for the relevant SAP application thefollowing effort estimation is given as a rough guideline: Setup of TDMS in system landscape (TDMS installation, implementing SAP notes, etc.) will take approximately less than a week. For enabling the test data transfer for the relevant SAP application additional activities are needed. SAP System Landscape Optimization consulting provides services for setup existing TDMS scenarios on demand.The project specific effort might vary significantly depending on customer situation and demand as well asproject participation.© 2009 SAP AG page 8/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions2 Best Practice2.1 Preliminary Tasks2.1.1 Test ManagementThe implemented banking solution at each SAP customer is unique. Therefore, it must be testedthoroughly before going live or before applying change to the productive environment. Such testingincludes tests of individual functions, integration tests between SAP and non-SAP applications, scenariotests in which entire business processes are executed from end to end, performance and acceptancetests. Most of the errors which can occur in the Banking application will be immediately visible tocustomers, which is the main reason for the high quality assurance standards at our Banking customers toprevent any disruption of the application.The Test Management part of SAP Standards for Solution Operations describes the SAP standard for testmanagement (access via http://service.sap.de/supportstandards • Media Library • Test Management). Thisstandard provides SAP best-practice approach for End-to-End (E2E) Test Management. Forrecommendations of implementing this standard see Run SAP Roadmap at http://service.sap.com/runsap.For efficient implementation of SAP TDMS for Banking the test management for the customer specificsolution landscape should be defined clearly. Central aspects are mentioned below as introduction of theSAP standard for solution operation.Test strategyThe definition of a company specific test strategy is the most important activity before per-forming any testactivities. The test strategy describes the approach for test management. It provides guidance and should(as a minimum) describe the following aspects: roles and responsibilities, test information management /test documentation, tools used to support the scoping, planning, execution and analysis of tests, companyprocedure to manage change, test types that have to be considered in various change scenarios, generalstart and exit criteria by test type.Test conceptReview of the test strategy in the context of the planned test project. Dependent on the type of change thesuitable test types and test approach must be determined and documented in a test concept.Test objectivesThe goal of the test activities should be described via a transparent set of test objectives. Requirements toenable the start of test activities, quality goals as well as test exit criteria should be formulated to guidetest preparation and management of expectations.The definition and the objectives of the planned tests will have a major impact on the required data fortesting, which can be provided by test tools.Test toolsExecute selection of available test tools which are appropriate for scoping, planning, execution andanalysis of the planned test activities and implementation and roll out to involved persons.© 2009 SAP AG page 9/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions2.1.2 Solution landscapeThe system infrastructure for a data transfer using SAP TDMS requires the following system roles:A sender system (client) from which the data supply for the non-production system is taken. Usually theproduction system or a system copy of the productive environment is used as the sender system.However there are other options as well. For more details, see the TDMS Operations Guide on SAPService Marketplace under: http://service.sap.de/tdms. The TDMS server includes: - A central system (client) on which the settings and customizing for the setup of the non-production system are stored - A control system (client) from which almost all activities for SAP TDMS are triggered and monitoredAny of the systems – except the receiver system – can be used as the control system. However westrongly recommend that you implement the TDMS server separately for example on SAP SolutionManager. More details about which types of SAP systems can be used as the central system and controlsystem for SAP TDMS are provided in the TDMS Operations Guide on SAP Service Marketplace under:http://service.sap.de/tdms. A receiver system (client); the non-production system to be filled. This may be either a system shell or a full copy of the production system. For more details, see the TDMS solution operation guide. Central Sender Receiver Control TDMS Server = RFCFigure 4: System overview for TDMS scenarioThe sender system and the receiver system must be on the same release level. The TDMS software mustbe installed on all systems that are part of the given TDMS landscape. The systems are linked by RFC© 2009 SAP AG page 10/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutionsconnections. For more information about how to configure these connections, see the TDMS OperationsGuide.As recommendation for the SAP Banking scenario the TDMS Server could be setup on a SAP SolutionManager 7.0 (SAP_BASIS =701). For productive SAP solutions the SAP Solution Manager is setupalready as central system in the customer solution landscape. SAP Solution Manager would therefore bean appropriate system for the SAP Test Data Migration Server as well. And the technical requirement on aTDMS server (SAP system with Web AS 6.20, 6.40 or NetWeaver 7.00 and SAP ABA) are fulfilled as SAPSolution Manager 7.0 based on NetWeaver 7.00. Central Sender Receiver Control TDMS Server = RFCFigure 5: Recommended TDMS scenario for banking with SAP Solution Manager 7.0 as TDMS serverThe described SAP TDMS scenario for Banking Service Deposit Management is setup on a SAP BankingService release 6.0 (FSAPPL 200). As the SAP Banking Services 5.0 or 6.0 (FSAPPL = 100 or 200)solution is based on SAP NetWeaver 7.10 and SAP Solution Manager is used as TDMS server.The TDMS software must be installed on all systems that are part of the given TDMS landscape. Forfurther details see TDMS Operations Guide on SAP Service Marketplace under:http://service.sap.de/tdms. In the scenario described here TDMS add-on can be installed on TDMSServer. As sender and receiver are based on SAP Base Release 7.10, TDMS will be shipped on a projectbase separately and has to be imported into both systems.The systems are linked by RFC connections. For more information about how to configure theseconnections, see the related SAP documentation.© 2009 SAP AG page 11/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions2.2 General Procedure for TDMSThe following chapters will introduce you in the setup of the TDMS server.2.2.1 Preparing the system landscape2.2.1.1 Set up TDMS serverThe standard way of setting up the TDMS server is to install the TDMS software in an empty SAP system.Alternatively, an existing system (e. g. SAP Solution Manager System) may be used.SAP Notes 970531 and 970532 describe the installation procedure and provide additional information withregard to the installation of SAP TDMS.2.2.1.2 Set up receiver systemWith SAP TDMS, you transfer the required parts of the client-dependent data from the sender system tothe receiver system. For this to work properly, it is very important that the receiver system has the samedata dictionary (DDIC) and cross-client customizing as the sender system. You have the following optionsfor setting up the receiver system: If you have a suitable test system (or other recent copy of the production system), you can use this system – provided that its DDIC and cross-client customizing are the same as in the sender system. Install the TDMS software and use the deletion functions that come with SAP TDMS to get rid of obsolete client-dependent data. You can make a full copy of the production system, install the SAP TDMS software, and then delete all data except the DDIC and the cross-client information from this system copy. The required functions for doing the deletion come with SAP TDMS and are accessible from the process tree. Then you do a data reorganization to free up the disk space.You can create a system shell using one of the related process types that come with SAP TDMS: Bycombining steps from the standard system copy process with the reduction logic provided by SAP TDMS,this package makes it possible to copy only the data needed for a system shell – rather than first copyingthe complete client and then deleting the data that is not needed in the system shell.With SAP TDMS, you can either use an existing client as the receiver client, or create a new client to beused as the receiver client. If you want to use a new client, set it up by means of the client copy tool;profile SAP_UCSV (client-dependent customizing, users, authorization profiles and variants). This isnecessary because data related to users and variants are not transferred from the sender system to thereceiver system, but this data is needed for working with the new client.The receiver system must be available from the beginning of a TDMS project, and the SAP TDMSsoftware must be installed.2.2.1.3 Set up sender systemGenerally, the sender system must be an SAP system with the relevant components and will beconnected with the TDMS server and the receiver system by means of RFC (remote function call).The sender system must be available from the beginning of a TDMS project, and the SAP TDMS softwaremust be installed.© 2009 SAP AG page 12/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions2.2.1.4 Set up RFC connectionsAll participating systems in a subproject must be linked by RFC connections. More information what has tobe considered during the set up of these connections is provided in the TDMS Operations Guide.2.2.2 Set up a non-production systemWhen you have installed TDMS in all participating systems as described before and made the relevantpreparations (described in detail in the TDMS Operations Guide), you can set up your first project in theTDMS server: Getting started with SAP TDMS with definition of a project, subprojects and packageassignment. When you have completed all preparations, you can start executing the activities for yourpackage in the process tree.2.2.2.1 Procedure for master data & customizingThe following drawing provides an overview of the data transfer process for master data and customizingdata which is transferred to the receiver system. These data will be transferred without reductions ofentries. Sender system TDMS Test system DDIC DDIC FUNCTION READ DATA FUNCTION WRITE DATA for mass transfer Code generator data CONVERT_DATA Customi data for mass transfer zing and Master System- Customi Application Customi data and zig and System- Userdata Master tables and and zing Master data Userdata dataFigure 6: Procedure for master data and customizing transfer2.2.2.2 Time-based reduction of master and transaction dataThe drawing provides an overview of the data transfer process for the time-based reduction in the contextof SAP TDMS. For a short explanation of the central procedures in this process, see the followingsections.© 2009 SAP AG page 13/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions sender system TDMS NPS system DDIC DDIC CONVERT_DATA FUNCTION READ_DATA. for conv. objects FUNCTION WRITE DATA with reduction criteria FUNCTION READ DATA for mass transfer Code generator data data CONVERT_DATA for mass transfer ~200 large ~12.000 ~30% of tables other tables sender dataFigure 7: Procedure for master data and customizing transferSystem analysisIn this phase system evaluation of the largest tables has to take place to identify the most critical tables interms of database growth. This evaluation is required to identify the tables which are relevant for reduction(selective data transfer) to get a non-production system that is as small as possible, but contains all datayou require. In addition, you define the rules for the data reduction (selection groups). Finally the settingsare confirmed so that they become effective for the data transfer.Preparations in the receiver systemTo make the receiver system ready for the data transfer, all client-dependent data have to be removed. Inthis phase the necessary preparations are made and the TDMS functions that delete the client-specificdata from the receiver system are started.2.2.2.3 Data selection by business processes or business objects (BPL)Similar to the data transfer process for the time-based reduction also data selection based on businessprocesses or business objects is possible using the Business Process Library (BPL) This process appliesespecially for the transfer of test data for specific test scenarios, e.g. for objects that need to be testedfrequently.Setup phaseIn this phase the selection objects for the data transfer and the related settings are defined.Deletion phaseIn this optional phase existing data from the tables in the receiver client can be deleted.© 2009 SAP AG page 14/24
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsExtraction phaseIn this phase the selected data from the sender system are copied to the receiver system either via directimport via RFC (which is the default setting) or via flat files in the file system. The flat files will then beimported to the receiver system.2.2.2.4 Scrambling procedure for master and transaction dataAs described in the beginning of the document it is also possible to apply scrambling rules during the datatransfer to ensure that sensitive data (like customers’ personal data or confidential financial information) ismade anonymous and is not accessible to bank internal and external users of the non-production system. Sender TDMS Receiver DDIC DDIC Container Container Data Scrambling Example Data Scrambling Pers-ID Name Salary Pers-ID Name Salary Pers-ID Name Salary Pers-ID Name Salary 0001 Mueller 10.000 € 0001 Mueller 10.000 € 0001 Mister X 32000 € 0001 Mister X 32000 € 0002 Mayer 1.800€ 0002 Mayer 1.800€ 0002 Mister Y 6.400€ 0002 Mister Y 6.400€Figure 8: Scrambling execution: system architecture and exampleSAP TDMS provides a workbench to create rules for data scrambling to make test data anonymous. Theshipment does not contain any out-of-the-box scrambling functionality but provides the technical platformto implement scrambling scenarios.Scrambling rules may be either field-related (referring to a single field) or event-related (referring to two ormore fields which are related).© 2009 SAP AG page 15/24
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsFigure 9: Field related rules – example customer IDFigure 10: Event related rules – example address2.3 TDMS for SAP Banking Services Deposits Management2.3.1 Introduction of TDMS scenarioThe available SAP TDMS scenario for SAP Deposits Management on banking services is build forcontract type accounts. Within the scenario critical data base tables for the database size can betransferred with substantial reductions of data ranges based on test case oriented efficient selectioncriteria.© 2009 SAP AG page 16/24
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsTo implement the banking specific SAP TDMS scenario a test data migration system landscapeoptimization consulting service can be ordered.Not in the scope of the best practice paper are other contract types as loans, cards and master contracts.Also not in focus can be custom development based enhancements of data model (e.g. Z* table). Bothadjustments for data selection and reduced transfer are possible but need enhancement in alignment withSAP TDMS product management or consulting.2.3.2 Deposit Management data modelThe data model of Deposit Management contains different types of data objects and their related tables.These central tables will be used for reduced TDMS data transfer as described later.The central master data object is the contract in the SAP Deposits Management scenario. It is used for thedifferent contract types like current accounts, saving accounts and cards. The table BCA_CONTRACTstores the internal contract ID as key and the assignment to a specific product and product version asmain attributes. The table BCA_CN_LINK contains all the relations to further contract components and torelated business partners and organizational units.The SAP Banking Services contract type account has one central master data table(BCA_CNSP_ACCOUNT) that link the account specific external ID (bank country and key and externalaccount ID, IBAN) to the internal contract ID from BCA_CONTRACT. Various additional contractcomponents are specific for the contract type accounts. One example of these components is the contractcomponent Contract Events, which characterize the specific account with processing relevant information.This information is stored in master data table BCA_CN_EVENT.The central transaction data objects of the SAP Banking Services contract type account are paymentitems and prenotes. These objects are stored in the following data tables: BCA_ BCA_PAYMITEM andBCA_PRENOTE, which have the internal contract ID as key field. These tables contain normally thehighest data volume in a productive DM system, because of the posted daily transactions. Similar to thesetables are other transaction data objects like the GL transfer item, settlement and statement information.The SAP Banking Services data model is not only containing own data objects. It reuses so called SAPcross-application object like SAP Business Partner and SAP Organizational Management. These objectsare linked via the central link table BCA_CN_LINK. The business partner is linked via the partner GUIDthat point to the central entry in master data table BUT000. All business partner tables are related to thistable as well like the data objects addresses and contact information (email and telephone numbers). Theorganizations units are linked via the organizational unit ID that point to the central entry in master datatable HRP1000. All organizational data tables are related to this table.© 2009 SAP AG page 17/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions Contract Specialization Payment Items Account BCA_PAYMITEM BCA_CNSP_ACCT External account ID Prenotes BCA_PRENOTE Contract Central Table: BCA_CONTRACT Internal contract ID General Leger Transfer Assignment to product BCA_GL_PAYMITEM Various Transactions Data for contract (Settlements, Assignment Table: Statements, GL transfer,..) Contract Parts to a Contract BCA* BCA_CN_LINK Event-Controlled Bank Statement BCA_BCAS_EVBST Business Partner (BP) Organization Units Central table: BUT000 Central table: HRP1000 Contract Events BCA_CN_EVENT Other BP Data Other Org Data Legacy Data Transfer BUT100: Roles HRP1001: Relations BCA_INV_DETAILS BUT021_FS: Address HRP1905: Banking Assignment …. ADR*: Address Data Various other Contract …… elements (Limits, Account Closing,..) BCA_CN*… BCA_CN_* Color Data Object / Category DM Contract (Type independent data model DM Account master data (type specific contract data) DM Account transaction data Cross-Application master data object: Business Partner Cross-Application master data object: Organizational MgmtFigure 11: Overview on DM data model introducing central object with table and relations2.3.3 Reduction of master and transaction dataFocus of the SAP TDMS scenario for Deposits Management on banking services is the reduction of thecentral master and transaction tables demanding the highest disk space. To reduce the required diskspace data out of the tables should be transferred based on test case oriented selections.With the current TDMS scenario for DM SAP provides 3 types of alternative selection criterias: Deposit Management accounts© 2009 SAP AG page 18/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions Business partner account holder Deposit Management product/product versionBased on the input the relevant contracts and/or business partner are selected in a first step. In a secondstep all related data from critical tables which were identified in advance are selected for data reduction.2.3.3.1 Selection based on external accountThe selection based on the external account ID uses the external account ID and will select all necessarykey information from the relevant related tables, like contracts, events, payments and so on.As selection criteria we offer: Bank country Bank key External account IDThe relevant table for selection of contracts is: BCA_CNSP_ACCT: Mapping external account ID to internal contract ID2.3.3.2 Selection based on business partner account holderThe selection based on business partners in role account holder uses the business partner ID as selectioncriteria and selects all necessary key information from the related tables, like contracts, events,payments…As selection criteria are offered: Business partner IDThe relevant tables for selection of contracts are: BUT000: Mapping external business partner ID to internal business partner ID BCA_CN_LINK: Assignment of internal business partner ID to internal contract ID2.3.3.3 Selection based on the productThe selection based on the product uses the product as selection criteria and will select all necessary keyinformation from the related tables, like contracts, events, and payments.As selection criteria are offered: External product ID Product versionThe relevant tables for selection of contracts are: FSPR_PRODUCT_Y: Mapping external product ID to internal product ID BCA_CONTRACT: Assignment of internal product ID and version to internal contract ID2.3.3.4 Additional selection for business partnerThe business partner is not only used in roles with assignment to a DM account. They could be used aswell in other scenarios that could be interesting for testing. Therefore the business partners will beselected via assigned roles. The SAP scenario contains the selection of all business partners based onassigned roles with a range including all BP roles and excluding the banking specific roles (BCA*). Basedon this selection the business partner data will be transferred to the receiver system.© 2009 SAP AG page 19/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions2.3.3.5 Tables of master and transaction data for reductionThe following table lists the data tables that were already identified as critical for data reduction in the SAPTDMS DM scenario. Table ID Table description Account transaction data BCA_PAYMITEM Payment Items BCA_PAYMITEM_NT Payment Notes of a Payment Item BCA_PRENOTE DB Tables - Prenotes BCA_GL_PAYMITEM GL: Additional Payment Item Data BCA_GL_BALCN GL: Balances in FI for Each Account for Balance Sheet Prep. BCA96 Account Settlement Detail Data BCA_TRANSFIG Value Date Transaction Figures BCA_BANO_DUE Bank Statement Agreement Flow Data (Due Date...) BCA_BCAS_DUE Bank Statement Agreement Flow Data (Due Date...) Account master data BCA_CONTRACT Assignment Table: Contract Anchor BCA_CNSP_ACCT Assignment Table: Account Contract Specialization BCA_CN_LINK Assignment Table: Contract Parts to a Contract BCA_CN_BP_EVT Master Data: Business Processes BCA_CN_EVENT Contract Events BCA_BCAS_EVBST Event-Controlled Bank Statement BCA_CN_PER_ACBAL Time Periods for Account Settlement BCA_CRRV_DATES Credit Standing Check: Dates BCA_INV_DETAILS Detail Information on Inventory/Legacy Data Transfer BCA_COUNTER Counter Reading Business partner master data BUT000 BP: General data I BUT001 BP: General data II© 2009 SAP AG page 20/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions Table ID Table description BUT020 BP: Addresses BUT021 BP: Address usages BUT021_FS Time-Dependent Address Usages BUT100 BP: Roles ADRC Addresses (Business Address Services)Table 2: List of DM tables for reduction of transaction and master dataAll other data base tables are transferred with the complete table content. With this approach the criticaltables in regards to the database size are reduced efficiently but complete test data sets are available withshort transfer times.2.3.4 Scrambling for master and transaction dataAs bank accounts contain security critical data, data scrambling can be one part of the SAP scenario forDeposit Management. Sensitive data that could be used to identify business partners by name addressand contact data details should be scrambled.Also the transaction texts should be considered to be relevant for data scrambling. Table ID Table description Scrambling relevant BCA_PAYMITEM Payment Items Texts BCA_PRENOTE Prenotes Items Texts Name (different field for the different BP types: BUT000 BP: General data I Person, Group, Organization) Addresses (Business Address Address Details (Street, House Number, City, ADRC Services) Postal Code) Details on contact data (Email addresses, ADR* Contact Data telephone numbers, fax numbers)Table 3: List of DM tables and relevant information for scrambling of transaction and master dataThe relevant fields of the tables can be scrambled completely. This does not consider a specific handlingof parts of the field content.© 2009 SAP AG page 21/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions3 Further Information3.1 Background Information and ReferencesGeneral TDMS information is provided to customers via SAP Service Marketplace in a special TDMSinformation area (Access via quick link: http://servcie.sap.com/tdms ).For implementation information go to • Media Library • Guides. There you find the central TDMS guides: Master guide: SAP Test Data Migration Server 3.0 Operations guide: SAP Test Data Migration Server 3.0 Security guide: SAP Test Data Migration Server 3.0For latest information regarding releases and support packages please check the following SAP Notes: SAP Note: 1231203 TDMS release strategy (Add-on: DMIS, DMIS_CNT, DMIS_EXT...) SAP Note: 1244346 Support Packages for TDMS (Add-on DMIS, DMIS_CNT, ...)There will also the link to SAP consulting for System Landscape Optimization (SLO) which is offeringvarious TDMS services. (Access via link: SAP SLO Consulting)3.2 TroubleshootingGeneral TDMS information is given to customers via SAP Service Marketplace, TDMS area (Access viaquick link: http://servcie.sap.com/tdms ).Ongoing discussing on TDMS usage could be found in SAP Developer Network; access viawww.sdn.sap.com and usage of content search.Additional help by SAP product support can be requested via creation of a support message for SAPcomponent XX-PROJ-DMS-TDM. The message can be created in SAP Service Marketplace (access viahttp://service.sap.com/support) or by forwarding a service desk message from your SAP SolutionManager.© 2009 SAP AG page 22/24
    • Best PracticeSAP Test Data Migration Server for Banking SolutionsIndex of FiguresFigure 1: Current vs. future 3Figure 2: SRC system – test system 4Figure 3: Test management phases for projects 7Figure 4: System overview for TDMS scenario 10Figure 5: Recommended TDMS scenario for banking with SAP Solution Manager 7.0 as TDMS server 11Figure 6: Procedure for master data and customizing transfer 13Figure 7: Procedure for master data and customizing transfer 14Figure 8: Scrambling execution: system architecture and example 15Figure 9: Field related rules – example customer ID 16Figure 10: Event related rules – example address 16Figure 11: Overview on DM data model introducing central object with table and relations 18Index of TablesTable 1: Current SAP Education offering for TDMS 6Table 2: List of DM tables for reduction of transaction and master data 21Table 3: List of DM tables and relevant information for scrambling of transaction and master data 21© 2009 SAP AG page 23/24
    • Best PracticeSAP Test Data Migration Server for Banking Solutions© Copyright 2009 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 SAPAG. 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 softwarevendors.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 ofIBM Corporation.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 ofCitrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered tradem ark 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 astheir respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over theworld. All other product and service names mentioned are the trademarks of their respective companies. Data contained in thisdocument serves informational 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 anyform or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding uponSAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to changeand may be 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 anykind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose,or non-infringement.SAP shall have no liability for dam ages of any kind including without limitation direct, special, indirect, or consequential dam ages 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 provideany warranty whatsoever relating to third-party Web pages.© 2009 SAP AG page 24/24