SAP TDMS - Implementation Guide

SAP Test Data Migration Server: Overview and ImplementationPeter Keller, SAP AG Chicago, July 24, 2008 SAP TDMS Reference Customers © SAP 2008 / Page 1 SAP TDMS Reference Customers A Smoother Test Ride Network Computing, India - July 15, 2008 “…We were undergoing a situation where data was growing at about 500 GB per year and the need to develop, test and roll out applications was becoming more and more urgent.“… …“We didn’t have a method to cut this data or use it partially for the development and quality assurance environments.” says Dheeraj Sinha, Head of the company’s Corporate Management Services. This posed several challenges for Apollo Tyres, including unwanted production system downtime due to whole data transfer to DEV and Q/A each time something needed to be developed and tested. To tackle the problem, Apollo Tyres implemented SAP’s Test Data Migration Server (TDMS) solution, which is used for creating and refreshing non-production systems with a reduced but consistent data set. As a result, response times in development have increased, and the development team’s ability to reconfigure and tweak the data has improved. “The solution, implemented directly by SAP, “was a quick and smooth process without any roadblocks,” says Nagaraj Bhargava, Vice President of Marketing, for SAP India. © SAP 2008 / Page 2 Best Practices & Use Cases Facts and Figures Outlook Wrap-up © SAP 2008 / Page 3 .Agenda: SAP TDMS Overview Customer Situation and Challenges Solution Approach and Technology Benefits. Customer Situation and Challenges Is Your Company Facing… Large and quickly growing SAP systems? The need to test and validate in-house developments? The challenge to scramble sensitive data? Multiple parallel IT projects? Demand to simulate new business scenarios? Consider implementing a solution that helps you to create lean and consistent development. quality assurance. testing. and training environments based on real business data © SAP 2008 / Page 4 . tested. corrected in DEV system. settings need to be readjusted Developments need to be stopped (before system rebuild) New developments can only be tested in Q/A system Data in non production system is completely replaced by production data Sensitive data in test systems © SAP 2008 / Page 5 . and transported again to Q/A. etc.Challenges with Full System Copy CHALLENGES Production systems are becoming larger and larger CONSEQUENCES Administration of large data volume Increased storage expenses Interfaces need to be changed or closed Users need to be set up or changed Authorizations need to be adjusted Saved objects need to be copied back ( CATTS) Transports need to be closed. Repository Objects loose their transport history when copied from production Need to implement complex authorization concept After each copy. released and reimported Objects need to be transported to Q/A system. Agenda: SAP TDMS Overview Customer Situation and Challenges Solution Approach and Technology Benefits. Best Practices & Use Cases Facts and Figures Outlook Wrap-up © SAP 2008 / Page 6 . and training systems with SAP business data from your live productive environment. © SAP 2008 / Page 7 . units/timeslice Scramble sensitive data SAP Test Data Migration Server is a high-speed data extraction tool that populates your development.The Solution With SAP TDMS you can: Reduce data volume Simulate production environment Automate system refreshes Selectively refresh individual clients Extract data based on business objects or org. quality assurance. test. data only TDMS for ERP Classic: Master and configuration data only Master and configuration data in addition to time slice of transactional data Master and configuration data in addition to time slice of transactional data for specific company code(s) TDMS Business Process Library (BPL) .Predefined business objects and process data © SAP 2008 / Page 8 .Repository and client-indep.SAP TDMS for ERP: The Solution Available Data Extraction Scenarios ERP Shell Creation . SAP TDMS for BI and CRM: The Solution Available Data Extraction Scenarios BI Shell Creation .Repository and client-independent data only Master data and time slice of transactional data Available Data Extraction Scenarios for CRM Shell Creation .Repository and client-independent data only TDMS for CRM Classic: Master and configuration data only Master and configuration data in addition to time slice of transactional data © SAP 2008 / Page 9 . optimized data transfer Proven high-speed data extraction technology (Migration Workbench) Table-wise data migration via RFC (Remote Function Call) connections © SAP 2008 / Page 10 .Technology: Architecture TDMS Classic Sender System SAP TDMS Receiver System Fast. Solution Approach TDMS Classic Assumption 80 . etc. user tables. (customizable) 10% Master Data * 7% Config. change documents.g. Data * 3 % Admin.Data* * Estimate based on project experience © SAP 2008 / Page 11 . only few tables need to be reduced All other tables (master and configuration data) are migrated entirely Customer-individual tables are transferred entirely or can be reduced via e.g. time criteria Some tables are excluded from transfer by default: E.90% of the production data is stored in 10 20% of client-dependent tables Data volume reduction 80% Transaction Data * Client DB In order to reduce the overall volume. Test Data Migration 2. Data Analysis 1.Technology – TDMS Classic Process and System Setup Initial Setup Phase (one-time activity): Source System TDMS Receiver System 4. TDMS Customizing 3. Delete Client Data Refresh (recurrent): Source System TDMS Receiver System 3. ∆ Analysis © SAP 2008 / Page 12 2. Delete Client Data . Test Data Migration 1. Approach Predefined business object and process data selection scenarios Master data only Selective transactional data with dependent master data Complete business processes / test cases Covers key areas in ERP and industry solutions Data extraction based on built-in relationship knowledge Simple integration of customer data und customer development Optional scrambling of sensitive data during extraction (customizable) © SAP 2008 / Page 13 .Business Process Library . SAP TDMS – BPL: Accounting Document Provides selective Accounting Document data with depending objects (including master data) Main Business Objects: Accounting Document Vendor Customer G/L Account Open & Balanced Posts © SAP 2008 / Page 14 . SAP TDMS – BPL: Purchasing Process Provides selective data of a purchasing process (master and transactional data) Main Business Objects: Purchase Order Material Document Invoice Accounting Documents Purchase Requisition Material Vendor Service Packets Conditions © SAP 2008 / Page 15 . SAP TDMS BPL Sender System Architecture and Components Receiver System Data DDIC Data Parallel RFC qRFC qRFC (optional) Crawler Extractor File Importer Deleter DD Framework DD Framework Central-System Control / Monitoring Admin Designer Scenarios / Content © SAP 2008 / Page 16 . Business Process Library Available Business Contexts Master Data Business Partner Material Vendor Customer G/L Account Fixed Asset Functional Location Equipment Internal Order Project Article (Retail) Insurance Object (FS-CD) Loans Contract (CML) Asset (CFM) Contract (IS-U) Installation (IS-U) Device (IS-U) User Transaction Data Accounting Document Purchase Requisition Purchase Order Sales Order Material Document Billing Document Invoice Receipt Quality Notification Maintenance Order Allocation Table (Retail) FI-CA Document Transaction (CFM) Process Data Purchase Order Sales Order Insurance Object (FS-CD) Contract (FS-CD) Loans Contract Contract (IS-U) Custom Data Empty scenario for custom-specific objects © SAP 2008 / Page 17 . Agenda: SAP TDMS Overview Customer Situation and Challenges Solution Approach and Technology Benefits . Use Cases & Best Practices Facts and Figures Outlook Wrap-up © SAP 2008 / Page 18 . test. quality assurance and training systems Improve quality of development and training activities by using business-relevant and up-to-date test data Increase development efficiency by reducing the administrative efforts and time required to manage your development and test systems HIGHER FLEXIBILTY Support independent project schedules by selectively refreshing single clients of your development. Resulting in REDUCED COST while INCREASING QUALITY in development and training activities © SAP 2008 / Page 19 .Benefits of SAP TDMS REDUCED INFRASTRUCTURE EXPENDITURES IMPROVED QUALITY INCREASED EFFICIENCY Reduce your disk space by decreasing the data volume in your development. test and quality assurance systems DECISION SUPPORT Effectively simulate new business situations in your test environments using up-to-date data before taking critical business decisions OUTSOURCING Reduce testing expenses by outsourcing those activities to low-cost countries while keeping sensitive data anonymous thus ensuring legal compliance. SAP TDMS – Business Case* Storage Requirements for 3-Tier Landscape Current: Copy of Production Future: Use of SAP TDMS 2500 2000 1500 1000 500 0 GB 0 2500 2000 1500 1000 500 0 GB 0 Year 1 Year 2 Year 3 Year 4 Year 1 Year 2 Year 3 Year 4 PROD QA DEV Total PROD QA DEV Total * Based on real customer data © SAP 2008 / Page 20 . for resetting purposes Create initial master shell and place in transport path to be used as starting point for target system build © SAP 2008 / Page 21 . e.Use Cases .General Typical SAP TDMS Use Cases: Create separate TDMS client in development environment Create a slim test system with a reduced set of data for upgrade testing purposes Business Process Library: quickly populate maintenance systems with small data sets based on business objects Create multiple TDMS clients with differing data volumes in DEV as master clients to supply test or training systems recurringly.g. utilize BPL scenarios to selectively transfer specific Master data Transactional data plus dependent master data or Data needed for specific business processes/test cases © SAP 2008 / Page 22 . TDMDC or TDTCC to build training/maintenance client with a reduced set of data In order to quickly provide data for training purposes or for maintenance situations.Typical Process Example 1: BPL Setup of new target system via TDMS Shell Creation Execute TDTIM. utilize BPL scenarios to selectively transfer specific Master data Transactional data plus dependent master data or Business Processes/Test cases © SAP 2008 / Page 23 .Typical Process Example: BPL Setup of new target client via client copy (customizing only) In order to quickly provide data for training purposes or for maintenance situations. Customer Use Case Global Insurance Company Industry Global Insurance Company Target Systems Quality System Development System (Enhance development process) Test Systems (migration tests) Customer Requirements Refresh small amounts of quality system data from production Enhance development process by providing new test data on development system Reduce costs for migration through creation of smaller test systems BPL Business Scenarios used © SAP 2008 / Page 24 CML (Loan) . Customer Use Case Industry Insurance for Building Sector Insurance for building sector. Real Estate Administration Target Systems Quality System (Maintenance Clients for problems on production) Development System (Enhance development process) Customer Requirements Refresh Development systems with small amounts of data from production and QA Speed up troubleshooting in case of production problems without risking compliance BPL Business Scenarios used FS-CD (Insurance Object) CML (Loans) © SAP 2008 / Page 25 . Customer Use Case Insurance Company Industry Insurance Company Target Systems Quality System (Synchronize FS-CD QS with reduced Mainframe QS) Development System (Enhance development process) Customer Requirements QS for FS-CD had to be synchronized with already reduced main frame insurance system (IBM z/OS) 9.000 Insurance Objects including dependencies had to be copied Parallelization by 4 processes Total extraction and copy time: ~4h © SAP 2008 / Page 26 BPL Business Scenarios used . Customer Use Case Industry International Heavy Industry Company International Heavy Industry Company Target Systems Quality System Development System Training Systems Customer Requirements Build up a small training client with productive data for PM employee trainings BPL Business Scenarios used PM (Maintenance Order) © SAP 2008 / Page SD (Sales Document) 27 . Customer Use Case Industry Top 5 German Cooperative Bank Top 5 German Cooperative Bank Target Systems Quality System Development System Customer Requirements Transfer consistent test data to development and quality clients to speed up IT projects BPL Business Scenarios used CML (Loans) BCA (Bank Contract) © SAP 2008 / Page 28 . Customer Use Case Retailer – Home Improvement Industry Retailer (Home Improvement) Target Systems Training Systems Customer Requirements Build up a system with 10 training clients which should be refreshable over night A very small amount (< 8GB) of consistent data had to be extracted out of a retail system (> 3TB) BPL Business Scenarios used IS-Retail (Article) Custom Scenario to handle complete copies of (customer) tables © SAP 2008 / Page 29 .TDMS BPL . Customer Use Case Industry German Local Power Supplier German Local Power Supplier Target Systems Development System Quality System Customer Requirements Consistent data extraction for IS-U data for problem cases on production and improvement of development quality BPL Business Scenarios used IS-U (Contract Account and Business Partner) © SAP 2008 / Page 30 . SAP TDMS .Best Practices Build Maintenance Client Target: Create clients for maintenance/support cases Provide live data from production for analysis in test/dev environment Requirements: specific productive data for resolving support cases Coverage of a predefined scope of support scenarios Procedure: Build up new client in existing QA system (client copy customizing from production) Create or copy suitable TDMS-BPL packages for each support case Add customer specific objects and relations When support case occurs: – Apply selection criteria for affected scenario – Extract and import test data from production Rebuild target client in regular intervals to provide up-to-date customizing and ensure consistency with TDMS Classic process types © SAP 2008 / Page 31 . copy complete Z-tables. etc.g.Best Practices Build up Project or Training System Target: Create System for use during implementation / development projects or training sessions Reduce disk space and hardware in comparison to system copies Provide real-life data for tests and training Requirements: Test data for developer test or QA/Training purposes Coverage of wide range of test cases Procedure: Build up or reuse system shell (TDMS Shell Creation) or create new client on existing system Copy required basic data (i.SAP TDMS .e. TDTIM / TDMC / Client Copy Customizing) Define and copy suitable TDMS-BPL scenarios Use TDMS-BPL custom scenario to copy additional data (e.) © SAP 2008 / Page 32 . reduce tables by free selection criteria. Best Practices Refresh Development System Target: Provide test data for developers Reduce time and costs for software logistics Improve quality of developments Requirements: Small amount of data required Coverage of specific test cases Scramble personal data (e.g. names and addresses) Procedure: Build up new client in existing development system (client copy customizing & users) Create or copy suitable TDMS-BPL packages Add customer specific objects and relations Apply selection criteria and scrambling rules for test cases Extract and import test data from production or quality system into new development client © SAP 2008 / Page 33 .SAP TDMS BPL . ” Alexander Angermann. Head of IT Systems LMH “Using SAP Test Data Migration Server enables us to significantly improve the quality of our inhouse development. Behr Group © SAP 2008 / Page 34 . SAP Basis Lead.” Dr.Success at Our Customers “ “Thanks to SAP Test Data Migration Server we are able to massively reduce the amount of data in our non-production systems by 70% and more. Klaus-Ulrich Meininger. because development work is no longer interrupted by repeated timeconsuming transports for testing purposes. ” Randy Subryan Enterprise Architect Pacific Coast Building Products © SAP 2008 / Page 35 . as well as our data backup and storage systems.Customer Statement Pacific Coast Building Products “With SAP Test Data Migration Server. our infrastructure team. we’ve been able to free up our IT resources. – Challenges prior to SAP TDMS . from doing full data copies to QAS Errors in production systems caused by inconsistent data in QAS Customer Experience © SAP 2007 / Page 36 © SAP 2008 / Page 36 Holly Corp.Functional and development teams need good data to perform their quality assurance tests QAS system with obsolete business data The size of the production system kept Holly Corp. 0 SAP Solution Manager 4.0 SAP Business Intelligence 7.0 SAP Process Integration 7. .SAP Landscape © SAP 2007 / GSS SAP Business ByDesign Page 37 / Page 37 © SAP 2008 / Page 37 2008 DSAG Jahreskongress 2007 / Workshop Page 37 .SAP ERP 6.0 system with IS-Oil SAP Enterprise Portal 6.0 Go-live with SAP in May 2007 ERP DB size: 600 GB with growth rate of 50 GB per month BI DB size: 300 GB with growth rate of 27 GB per month Customer Experience Holly Corp. Customer Experience Holly Corp.0 Landscape HED HEQ HEP SAP SOLUTION MANAGER (SAP TDMS Console) HSO HBD HBQ BI 7.0 Landscape HBP © SAP 2008 / Page 38 . – SAP TDMS Environment ECC 6. 32BIT Memory: 12 GB .Customer Experience Server 1 (HEP) ERP Source: Model: HP DL585 CPU: 2 x Intel Xeon 8214 2. – SAP TDMS Technical Infrastructure Server 4 (HEQ) ERP Target: Model: HP DL380 CPU: Quad Intel Xeon 3.16 GHz.2 GHz dual core 32BIT Memory: 16 GB © SAP 2008 / Page 39 Server 5 (HBQ) BI Target: Model: HP DL380 CPU: Quad Intel Xeon 3.2 GHz dual core 32BIT Memory: 16 GB Holly Corp. 32BIT Memory: 12 GB Server 3 (HSO) SAP Solution Manager (SAP TDMS Console) Model: HP DL380 CPU: 2 x Intel Xeon 8214 2.2 GHz dual core 32BIT Memory: 8 GB Server 2 (HBP) BI Source: Model: HP DL585 CPU: 2 x Intel Xeon 8214 2.16 GHz. configuration or ABAP skills needed SAP TDMS consultant onsite during the first copy was very helpful Time needed during the copy depends heavily on database size and on TDMS knowledge/experience Customer Experience © SAP 2007 / Page 40 © SAP 2008 / Page 40 Holly Corp. .Knowledge of R3load system copy procedure critical for shell creation functionality Ensure sufficient hardware resources for target system Straightforward installation and operation No business.SAP TDMS Lessons Learned . Customer Example .35 MHz (dual core) Capacity: ~ 2900 SAPS Hosted System: copy of PEP (source system) Memory: 16 GBytes Server 2: Model: 1 system board of a Sun MicroSystems Enterprise 25K server CPU: 4 UltraSPARC IV 1.Petrobras Technical Infrastructure – Step 1 The project started with two servers having the same configuration: Server 1: Model: 1 system board of a Sun MicroSystems Enterprise 25K server CPU: 4 UltraSPARC IV 1.35 MHz (dual core) Capacity: ~ 2900 SAPS Hosted System: copy of PEP (target system) + GPD (TDMS console) Memory: 16 GBytes © SAP 2008 / Page 41 . 35 MHz (dual core) Capacity: ~ 2900 SAPS Hosted System: copy of PEP (target system) + GPD (TDMS console) © SAP 2008 / Page 42 Memory: 16 GBytes .35 MHz (dual core) Capacity: ~ 5800 SAPS Hosted System: copy of PEP (source system) Memory: 32 GBytes Server 2: Model: 1 system board of a Sun MicroSystems Enterprise 25K server CPU: 4 UltraSPARC IV 1.Petrobras Technical Infrastructure – Step 2 When the CLUSTER_FILL task started (writing on cluster export table in the source system).Customer Example . an extra system board was added to server 1. doubling its size Server 1: Model: 2 system boards of a Sun MicroSystems Enterprise 25K server CPU: 8 UltraSPARC IV 1. Customer Example . the extra system board was moved from server 1 to server 2 Server 1: Model: 1 system board of a Sun MicroSystems Enterprise 25K server CPU: 4 UltraSPARC IV 1.35 MHz (dual core) Capacity: ~ 5800 SAPS Hosted System: copy of PEP (target system) + GPD (TDMS console) © SAP 2008 / Page 43 Memory: 32 GBytes .Petrobras Technical Infrastructure – Step 3 When the MT_DATA_LOAD task started (writing on data tables in the target system).35 MHz (dual core) Capacity: ~ 2900 SAPS Hosted System: copy of PEP (source system) Memory: 16 GBytes Server 2: Model: 2 system boards of a Sun MicroSystems Enterprise 25K server CPU: 8 UltraSPARC IV 1. Customer Example .Petrobras Data Copy Throughput Instant data throughput varies during the copy process according to the size of the table and the number of parallel processes used in it Some tables had copy throughput of up to 8 GBytes per hour per process The average of copy throughput for individual tables was 5 GBytes per hour per process As up to 15 process parallels processes were used. the average copy throughput was around 75 GBytes/hour with peaks of 120 GBytes/hour © SAP 2008 / Page 44 . Customer Example . 1 week copy Result system: PEP’.3 TB database size © SAP 2008 / Page 45 . renamed to PEH afterwards.Petrobras First Copy Source system: a copy of PEP. 5 TB database size TDMS scenario: time-based scenario with all master + 5 months transactional data People involved: 1 Basis + 1 SAP consultant Timing: 1 week preparation. 1. Customer Example . 900 GB database size © SAP 2008 / Page 46 . 1.3 TB DB size TDMS scenario: time-based with all master + 1 month transactional data People involved: 1 Basis Timing: 3 days Result system: PPP.Petrobras Second Copy Source system: PEH. Petrobras TDMS System Landscape Quality Assurance PEQ PED Test Development Preproduction Production PPP PEP PEH Acceptance © SAP 2008 / Page 47 .Customer Example . configuration or ABAP skills needed The fact that Petrobras had an SAP TDMS consultant onsite during the first copy was very helpful Database reorganization needed at the end of the process to save disk space Time needed during the copy depends heavily on database size and on TDMS knowledge/experience TDMS does not delete.Petrobras Key Lessons Learned Straightforward installation and operation No business. trim or scramble HR data in transparent fields © SAP 2008 / Page 48 .Customer Example . Petrobras Summary TDMS is a simple to use tool that delivers what it promises Petrobras was able to create two new systems in its R/3 landscape that highly improved the quality of data which configuration and development teams have available to use in their test process Petrobras Basis team will use TDMS as an alternative to client copy and homogeneous system copy processes © SAP 2008 / Page 49 .Customer Example . Use Cases & Best Practices Facts and Figures Outlook Wrap-up © SAP 2008 / Page 50 .Agenda: SAP TDMS Overview Customer Situation and Challenges Solution Approach and Technology Benefits. 6C.0 CRM: 4.40 or 7. 7.00 Minimum 4000 SAPS. 4.0 BI: 3.7.0. 6. 20 GB hard drive Supported Releases ERP: 4.5.Facts and Figures System Recommendation SAP WebAS 6. ERP 5.0 Pricing Price is dependent on size of production database License covers one PRD system and n non-PRD systems Knowledge Transfer/Training TZTDM3 (offered by SAP Education) Implementation Implementation Services offered by SAP Consulting Service and Support SAP Standard and Premium Maintenance © SAP 2008 / Page 51 .20. ERP 6. Microsoft Corporation Nippon Paper Industries Co. Edeka AG Provinzial NordWest Holding Solvay SA SPAR Österr. BOC Group Plc.W.. Anheuser-Busch Companies. Inc. Inc. Inc. S. Inc. Ltd. Inc. Cemex Central. Grainger.. Ltd. Inc. SAP Reference Program © SAP 2008 / Page 52 . W. Diageo Plc. Reynolds Tobacco Company Homebase Limited Nordson Corporation IGT Federal Prison Industries Petrobras School Board of Polk County T-Mobile USA.I. Genentech. KG Endress & Hauser Heidelberger Druckmaschinen Burberry Limited Kommunalkredit Austria AG Degussa AG KLA-Tencor Corporation Eon AG E. WalMart Pick 'n Pay Retailers (Pty) Ltd. Nortel Networks Limited Linde AG Coles Saskatchewan Power Corporation Kyocera Mita Corporation Forest Laboratories. Inc.A.. ISE Innomotive Systems Europe GmbH Kimberly Clark VNG Verbundnetz Gas AG Weidmüller Leopold Kostal GmbH & Co. British Nuclear Fuels Plc. KG Otafuku Sauce Co. Inc. Air Liquide City Power Johannesburg (Pty) Ltd. Mahindra Mahindra nordIT GmbH Pacific Coast Building Products REWE Allgemeines Krankenhaus Wien J.p.Excerpt of Existing SAP TDMS Customers Schaeffler KG Behr GmbH & Co. GB Gas Holdings Limited Vodafone Group Plc.A.V. Stadtwerke Düsseldorf AG Mars Baldor Electric Company Goodrich Corporation CenterPoint Energy. Kao Corporation Holcim Group Support Ltd. UPM-Kymmene Oyj Agilent Technologies. Inc. S. First Energy ADC Telecommunications. Inc. Solectron Corporation Disney Worldwide Services. Cosmetics & Fragrance AstraZeneca Wincor Nixdorf International GmbH Autodesk. EADS Deutschland GmbH Johnson & Johnson Ulta Salon. Worldbank R. Holly Corp. EMI Group Plc. Honeywell International. Electricity Supply Board Bekaert N. Inc. Puget Sound Energy. Husky Energy Inc. Eastman Chemical Company Co-Operative Bulk Handling Ltd. Respironics. Astellas Service Birmingham Ltd. Ltd. Inc. Yell Ltd. Crew Group Inc. Warenhandels AG Telekom Austria AG The Coca-Cola Company Smithfield Foods Oesterreichische Kontrollbank EMI Bundesamt für Bauten und Logistik Jumbo Markt AG MigrosGenossenschafts-Bund Pirelli & C. Inc. DuPont de Nemours & Co. de C.V. Effem Services Incorporated Weyerhaeuser Zentraldienst der Polizei Horiba. Inc.J. Pratt & Whitney Canada Inc. 000 + n times 1.000 156.999 1.000 .000 .SAP TDMS – Pricing Model As of October 2007 Price depends on DB size of productive system: DB size in GB 0 .000 + n times 30.000 Price in USD 51.000 156.500 156.499 500 .productive systems Material Number: 7002944 © SAP 2008 / Page 53 .1.999 4.999 2.000 Note: Fees are not prorated and apply for each productive system Standard DB and maintenance fees as well as standard regional uplifts apply License covers one productive system and n non.000 109.000 72.299 300 .3. Agenda: SAP TDMS Overview Customer Situation and Challenges Solution Approach and Technology Benefits. Use Cases & Best Practices Facts and Figures Outlook Wrap-up © SAP 2008 / Page 54 . SAP Test Data Migration Server (Conceptual Timeline) Last Updated: April 2008 Road Map © SAP 2008 / Page 55 . developments and/or functionality and is not intended to be binding upon SAP to any particular course of business. Please note that this document is subject to change and may be changed by SAP at any time without notice. product strategy and/or development.This document contains intended strategies. 0 TDMS 3.0 Available Scenarios .0 Ext.TDMDC . 4. product strategy and/or development.0 Supported Releases 4.TDBTM TDMS for CRM .0 TDMS for BW .6C.TDSHL .TDHC2 – OM & PA (Organizational Management & Personnel Administration) Supports 4. Set 1+2 TDMS 3.TDCTM Enhancements to BPL HCM-specific Scenarios .TDTCC .7.TDDEL Ext. Set 3 TDMS 4. developments and/or functionality and is not intended to be binding upon SAP to any particular course of business. Please note that this document is subject to change and maySAP 2008 / by SAP at any time without notice.SAP TDMS Road Map Conceptual Timeline TDMS 3.TDCMC . ERP6.TDTIM TDMS Workbench . © be changed Page 56 . ERP04.Custom Scenarios Business Process Library (BPL) QI/2008 QII/2008 QIII/2008 2010 This document contains intended strategies.7 and higher Enhancements to BPL TDMS for SRM TDMS for SCM Enhancements to BPL Execution Manager .TDHC1 – PA only (Personnel Administration) .Data Scrambling . Legal Disclaimer This presentation outlines our general product direction and should not be relied upon in making a purchase decision. © SAP 2008 / Page 57 . either expressed or implied. fitness for a particular purpose. This presentation is not subject to your license agreement or any other agreement with SAP. except if such damages were caused by SAP intentionally or gross negligence. the implied warranties of merchantability. including but not limited to. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This document is provided without a warranty of any kind. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. SAP assumes no responsibility for errors or omissions in this document. Ensures consistency of document flow Supports integration scenarios for mobile clients © SAP 2008 / Page 58 .SAP TDMS – Latest Offerings TDMS BI (Currently in Ramp up) Solution similar to TDMS for ERP solution Supports release BW 3.0 Possible to reuse settings from TDMS for ERP implementation Data reduction based on time characteristics Filters PSA data completely Significant reduction in InfoCube and ODS data TDMS CRM (Currently in Ramp up) Solution similar to TDMS for ERP solution Supports release CRM 4.0 Time based reduction and Master data scenario available Ensures consistency in core business processes such as sales.5 and BI 7. service. marketing etc. Architecture & Solution Approach – TDMS BI BI Architecture Data! Data! Data! Data! © SAP 2008 / Page 59 . Architecture & Solution Approach – TDMS BI BI Data model The following is the structure of an InfoCube InfoCubes are reduced based on the time dimension All other objects in BW could be handled similar to the TDMS ERP Solution © SAP 2008 / Page 60 . Change log and new data could be optionally transferred InfoCube tables are reduced based on time dimension All InfoCube and ODS objects irrespective of the functional area are reduced Customer created InfoCube and ODS objects are reduced as well © SAP 2008 / Page 61 .Architecture & Solution Approach – TDMS BI Solution Approach Use the existing DMIS infrastructure Identify the large transactional tables and reduce them PSA data is temporary and hence not transferred All Master Data is transferred in full Reduction is achieved in ODS and InfoCube tables – – – – – ODS tables are similar to transparent tables in ERP & reduced similarly Only Active data in ODS is transferred. SAP TDMS for HCM Overview Talent Management Recruiting Career Management Succession Management Performance Management Compensation Management Enterprise Learning Incentive Commission Management Workforce Planning & Analytics Workforce Cost Planning & Simulation Workforce Planning Workforce Benchmarking Workforce Process Analytics & Measurement Talent Management Analytics & Measurement Workforce Deployment Project Resource Planning Resource and Program Management Call Center Staffing Retail Scheduling Workforce Process Management Employee Administration Organizational Management Global Employee Management Time and Attendance Travel Management Payroll Benefits Management End-User Service Delivery Manager Self-Services Employee SelfServices Employee Interaction Center Business Roles Office-Integration Duet © SAP 2008 / Page 62 SAP TDMS for HCM Architecture – Data Scrambling Control System Production System TDMS Server HR original Data Scrambled Data (Cluster) Test System RF C © SAP 2007 / Page 63 © SAP 2008 / Page 63 RF C HR scrambled Data SAP TDMS for HCM Process Tree © SAP 2007 / Page 64 © SAP 2008 / Page 64 TDMS for HCM Data Selection for PA Selection via PNPCE Adhoc-Query © SAP 2007 / Page 65 © SAP 2008 / Page 65 . TDMS for HCM Data Selection for PA © SAP 2007 / Page 66 © SAP 2008 / Page 66 . TDMS for HCM Data Selection for PA – Custom tables © SAP 2007 / Page 67 © SAP 2008 / Page 67 . TDMS for HCM Data Selection for PA © SAP 2007 / Page 68 © SAP 2008 / Page 68 . TDMS for HCM Data Selection for PD © SAP 2007 / Page 69 © SAP 2008 / Page 69 . TDMS for HCM Personell Data selected as well Either mini selection (IT0000 – IT0003) or comprehensive selection possible Data Selection for PD and PA © SAP 2007 / Page 70 © SAP 2008 / Page 70 . TDMS for HCM Data Selection for PD and PA Target area per user and object type possible © SAP 2007 / Page 71 © SAP 2008 / Page 71 . TDMS for HCM Scrambling Complete scrambling of personnel data Content dependencies are taken into account Grouping of content absolutely freely possible Provisioning of business content per country (recommendations) © SAP 2008 / Page 72 . Scrambling – Groups © SAP 2007 / Page 73 © SAP 2008 / Page 73 . Scrambling – Sets © SAP 2007 / Page 74 © SAP 2008 / Page 74 . Scrambling – Fields © SAP 2007 / Page 75 © SAP 2008 / Page 75 . Scrambling – Fields © SAP 2007 / Page 76 © SAP 2008 / Page 76 . g. customer-specific cluster/tables) © SAP 2008 / Page 77 .TDMS for HCM Customizing Target number range customizable per user if desired Option to set maximum number of objects per user Option to exclude objects and infotypes of a table from transfer Option to exclude specific employees from transfer by flexibly possible via specific criteria Flexible setting which cluster/tables should be taken into account (e. TDMS for HCM Customizing © SAP 2007 / Page 78 © SAP 2008 / Page 78 . TDMS for HCM Authorization Concept In general. comprehensive authorization checks can be reduced No authorization check Authorization check only on object level Complete authorization check In addition. individual activities can be assigned to specific activity groups depending on customer situation © SAP 2008 / Page 79 . existing HCM authorizations are checked For performance reasons. TDMS for HCM Example for Authorization Group Can be defined customer-specific Asssignment to activity group Is done via specific authorization object © SAP 2007 / Page 80 © SAP 2008 / Page 80 . The SAP TDMS Vision Productive Landscape Solution Manager Non-Productive Landscape SAP TDMS SAP R/3 SAP BW © SAP 2008 / Page 81 SAP CRM/SRM SAP APO . SAP TDMS Services 1/2 SAP TDMS Training Class This course will prepare you to implement and configure standard functionality of SAP TDMS SAP Education Course TZTDM3 SAP TDMS Basic Offering Provides overview of SAP TDMS for licensee Assists licensee with the initial set-up of SAP TDMS Provides knowledge transfer in the use of SAP TDMS to licensee’s SAP TDMS resources Provides support for issues that arise for the duration of the project © SAP 2008 / Page 82 . and unique data reduction rules Provide knowledge transfer in the use of SAP TDMS to licensee’s SAP TDMS resource(s) based on customer-specific requirements Provide support for issues that arise for the duration of the project © SAP 2008 / Page 83 . scrambling.SAP TDMS Services 2/2 SAP TDMS Proof of Concept / Evaluation Offering Remote initial set-up using a landscape provided by customer Documentation of set-up SAP TDMS Set-up & Configuration Consulting Provide overview of SAP TDMS for licensee Assist licensee with the initial set-up of SAP TDMS Implementation of customer-specific requirements such as shell creation. Use Cases & Best Practices Facts and Figures Outlook Wrap-up © SAP 2008 / Page 84 .Agenda: SAP TDMS Overview Customer Situation and Challenges Solution Approach and Technology Benefits. 7 Key Points to Take Home SAP TDMS helps customers to reduce storage requirements for non-production systems SAP TDMS enables the transfer of current test data into development environments SAP TDMS improves efficiency and quality of in-house developments SAP TDMS provides an easy way to refresh clients SAP TDMS supports independent project schedules SAP TDMS enables customers to simulate new business scenarios SAP TDMS is a tool every SAP customer should have © SAP 2008 / Page 85 Resources SAP Test Data Migration Server Website www.sap.com/tdms SAP Service Marketplace Webpage on TDMS http://service.sap.com/customdev-tdms System Landscape Optimization http://service.sap.com/slo © SAP 2008 / Page 86 SAP TDMS © SAP 2008 / Page 87 [email protected] +49 6227/7-44919 © SAP 2008 / Page 88 .Your Turn! Peter Keller Solution Management SAP AG p. Thank you for your attention QUESTIONS? © SAP 2007 / Page 89 © SAP 2008 / Page 89 . National product specifications may vary. xApps. indirect. xApp. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages © SAP 2008 / Page 90 . developments. Duet. SAP. This limitation shall not apply in cases of intent or gross negligence. SAP NetWeaver. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. text. special. This document contains only intended strategies. fitness for a particular purpose. This document is provided without a warranty of any kind. either express or implied. Business ByDesign. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. SAP does not warrant the accuracy or completeness of the information. product strategy. SAP assumes no responsibility for errors or omissions in this document. The information contained herein may be changed without prior notice. SAP shall have no liability for damages of any kind including without limitation direct. or other items contained within this material. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. mySAP. The statutory liability for personal injury and defective products is not affected. or consequential damages that may result from the use of these materials. or non-infringement. links. graphics.Copyright 2008 SAP AG All rights reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. R/3. Data contained in this document serves informational purposes only.com. including but not limited to the implied warranties of merchantability. and/or development. PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. ByDesign. mySAP. weder ausdrücklich noch stillschweigend. R/3. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.Copyright 2008 SAP AG All Rights Reserved Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. einschließlich und ohne Einschränkung für direkte.. Die Informationen. xApp. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. SAP NetWeaver. die Eigentum anderer Softwarehersteller sind. Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend. Duet. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Texte. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. A. unterliegen nicht dem Einfluss von SAP. mySAP. Links oder anderer in diesen Materialien enthaltenen Elemente. indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Grafiken. SAP übernimmt keine Haftung für Schäden jeglicher Art. xApps. Dieses Dokument enthält nur vorgesehene Strategien. ByDesign. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. -entwicklung einzuschlagen. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen. SAP. PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Produkte können länderspezifische Unterschiede aufweisen. Business ByDesign. auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen. hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen. Diese Publikation wird ohne jegliche Gewähr. Dies gilt u. © SAP 2008 / Page 91 . zu welchem Zweck und in welcher Form auch immer. einen bestimmten Geschäftsweg. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. aber nicht ausschließlich. bereitgestellt. Alle Rechte vorbehalten.com. mySAP. eine Produktstrategie bzw. spezielle. SAP TDMS – BPL: Article Master Provides selective Article Master data with depending objects Main Business Objects Article (IS-R) Listing Data Purchase Information Layout © SAP 2008 / Page 92 . SAP TDMS – BPL: Example Sales Order Provides selective Sales Order data with depending objects (including master data) Main Business Objects: Sales Order Sales Document Customer Materials Conditions © SAP 2008 / Page 93 .