Top Banner
ALM116 SAP Test Data Migration Server High-Quality Testing Requires High-Quality Test Data Peter Keller Speaker for SAP TechED US Nilguen Atasoy Speaker for SAP TechED EMEA Solution Management System Landscape Optimization Active Global Support SAP America, Inc October 19, 2010 © 2010 SAP AG. All rights reserved. / Page 2 Disclaimer This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. 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 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. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.
21
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • 1ALM116

    SAP Test Data Migration Server

    High-Quality Testing Requires High-Quality Test Data

    Peter Keller Speaker for SAP TechED USNilguen Atasoy Speaker for SAP TechED EMEA

    Solution Management

    System Landscape Optimization

    Active Global Support

    SAP America, Inc

    October 19, 2010

    2010 SAP AG. All rights reserved. / Page 2

    Disclaimer

    This presentation outlines our general product direction and should not be relied on in making a

    purchase decision. This presentation is not subject to your license agreement or any other

    agreement with SAP. 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

    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. This document is provided

    without a warranty of any kind, either express or implied, including but not limited to, the implied

    warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP

    assumes no responsibility for errors or omissions in this document, except if such damages

    were caused by SAP intentionally or grossly negligent.

  • 2 2010 SAP AG. All rights reserved. / Page 3

    SAP TDMS 1200+ Shipments to Date

    2010 SAP AG. All rights reserved. / Page 4

    SAP TDMS Reference Customers

  • 3 2010 SAP AG. All rights reserved. / Page 5

    1. Customer Situation and Challenges

    2. Solution Approach and Technology

    3. Benefits & Use Cases

    4. Facts and Figures

    5. Outlook

    6. Questions & Answers

    Agenda

    SAP TDMS Overview

    2010 SAP AG. All rights reserved. / Page 6

    1. Customer Situation and Challenges

    2. Solution Approach and Technology

    3. Benefits & Use Cases

    4. Facts and Figures

    5. Outlook

    6. Questions & Answers

    Agenda

    SAP TDMS Overview

  • 4 2010 SAP AG. All rights reserved. / Page 7

    Customer Situation and Challenges

    Are you 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, testing, quality assurance, and training

    environments based on real business data

    2010 SAP AG. All rights reserved. / Page 8

    Challenges with Full System Copy

    Challenges Consequences

    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)

    After each copy, settings need to be readjusted

    Production systems are becoming larger and

    larger

    Administration of large data volume

    Increased storage expenses

    Developments need to be stopped (before

    system rebuild)

    Transports need to be closed, released and

    reimported

    Data in non production system is completely

    replaced by production data

    Repository Objects loose their transport

    history when copied from production

    Sensitive data in test systems Need to implement complex authorization

    concept

    New developments can only be tested in Q/A

    system

    Objects need to be transported to Q/A

    system, tested, corrected in DEV system,

    and transported again to Q/A, etc.

  • 5 2010 SAP AG. All rights reserved. / Page 9

    1. Customer Situation and Challenges

    2. Solution Approach and Technology

    3. Benefits & Use Cases

    4. Facts and Figures

    5. Project Experience: Kraft Foods

    6. Questions & Answers

    Agenda

    SAP TDMS Overview

    2010 SAP AG. All rights reserved. / Page 10

    The Solution - SAP TDMS

    With SAP TDMS you can:

    Reduce data volume

    Simulate production environment

    Automate system refreshes

    Selectively refresh individual clients

    Extract data based on business objects, time slice, or a

    combination of organizational unit and time slice

    Scramble sensitive data

    SAP Test Data Migration Server is a high-speed data extraction tool that

    populates your development, test, quality assurance, and training systems

    with SAP business data from your live productive environment.

  • 6 2010 SAP AG. All rights reserved. / Page 11

    SAP TDMS Functionality for ERP

    TDMS Shell Creation - Repository and client-indep. 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

    TDMS for HCM

    Personnel Administration (PA) data only

    Combination of Personnel Administration (PA) and Organizational Management (OM) data

    Payroll comparison functionality

    Data Extraction Scenarios for ERP

    2010 SAP AG. All rights reserved. / Page 12

    SAP TDMS Functionality for BW and CRM

    Shell Creation - Repository and client-independent data only

    Master data and time slice of transactional data

    Data Extraction Scenarios for BW

    Shell Creation - Repository and client-dependent data only

    TDMS for CRM Classic:

    Master and configuration data only

    Master and configuration data in addition to time slice

    of transactional data

    Data Extraction Scenarios for CRM

  • 7 2010 SAP AG. All rights reserved. / Page 13

    SAP TDMS - High-Level Architecture

    Sender System SAP TDMS Receiver System

    2010 SAP AG. All rights reserved. / Page 14

    Solution Approach - TDMS Classic

    Assumption

    80 - 90% of the production data is stored in 10 - 20% of

    client-dependent tables

    Data volume reduction

    In order to reduce the overall volume, only few tables need

    to be reduced

    All other tables (master and configuration data) are

    migrated entirely

    Customer-individual tables are transferred entirely or canbe reduced via e.g. time criteria

    Some tables are excluded from transfer by default: E.g. change documents, user tables, etc.

    (customizable)

    * Estimate based on project experience

    7% Config. Data *

    3 % Admin- Data*

    80% Transaction Data *

    10% Master Data *

    Client DB

  • 8 2010 SAP AG. All rights reserved. / Page 15

    Master Data:

    Business Partner

    Material

    Vendor

    Customer

    G/L Account

    Fixed Asset

    Functional Location

    Equipment

    Internal Order

    Project

    Article (Retail)

    Insurance Object (FS-CD)

    Contract (FS-CD)

    Loans Contract (CML)

    Asset (CFM)

    User

    Cost Center

    Work Center

    Purchasing Information Record

    Material BOM

    SAP TDMS Business Process Libraray (BPL)

    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)

    CO Document

    Custom Data: Empty scenario for

    custom-specific objects

    Process Data: Purchase Order

    Sales Order

    Insurance Object(FS-CD)

    Contract (FS-CD)

    Loans Contract

    Contract (IS-U)

    Installation (IS-U)

    Device (IS-U)

    Production Order

    Process Order

    Asset (CFM)

    Bank Account (BCA)

    Business Partner (IS-U)

    2010 SAP AG. All rights reserved. / Page 16

    Example for Business Process Library

    Accounting Document

    Main Business Objects:

    Accounting Document

    Vendor

    Customer

    G/L Account

    Open & Balanced Posts

    Provides selective Accounting Document data

    with depending objects (including master data)

  • 9 2010 SAP AG. All rights reserved. / Page 17

    SAP TDMS for HCM:

    Architecture Data Scrambling

    IMPORTANT:

    1. Sensitive Data does NOT leave PRD

    2. TDMS for HCM can scramble data in cluster tables

    HR scrambled Data

    Production System

    HR original Data

    Scrambling

    TDMS

    Server

    Test System

    (Cluster)

    HR scrambled Data

    Control System

    2010 SAP AG. All rights reserved. / Page 18

    SAP TDMS for HCM

    Fully Integrated in SAP TDMS

    Transfer of Repository Objects

    and Client-Independent Tables

    (Shell Creation)

    Transfer of Master Data

    (non HCM) and Customizing Data

    (TDMDC, TDTIM or TDTCC)

    Transfer of HCM Data

    (TDMS for HCM)

  • 10

    2010 SAP AG. All rights reserved. / Page 19

    Scrambling:

    ANY HCM data can be scrambled (also data in cluster tables)

    Content dependencies are taken into account

    Grouping of content absolutely freely possible

    Scrambling templates available for 20+ countries

    Customizing:

    Option to customize specific target number range per user

    Option to exclude specific employees from transfer

    Option to set maximum number of objects per user

    Option to exclude objects and info types of a table from transfer

    Option to include customer-specific info types/tables

    Authorizations:

    Standard SAP HCM authorizations are active

    Capability to assign activities to activity groups

    SAP TDMS for HCM - Details

    2010 SAP AG. All rights reserved. / Page 20

    1. Customer Situation and Challenges

    2. Solution Approach and Technology

    3. Benefits & Use Cases

    4. Facts and Figures

    5. Outlook

    6. Questions & Answers

    Agenda

    SAP TDMS Overview

  • 11

    2010 SAP AG. All rights reserved. / Page 21

    SAP TDMS Value Drivers

    REDUCED

    INFRASTRUCTURE

    EXPENDITURES

    Reduce your disk space by decreasing the data volume in your

    development, test, quality assurance and training systems

    IMPROVED

    QUALITY

    Improve quality of development and training activities by using

    business-relevant and up-to-date test data

    INCREASED

    EFFICIENCY

    Increase development efficiency by reducing the administrative efforts

    and time required to manage your development and test systems

    HIGHER

    FLEXIBILITY

    Support independent project schedules by selectively refreshing single

    clients of 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.

    2010 SAP AG. All rights reserved. / Page 22

    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

    Allow HCM business users to transfer specific employee data

    and scramble (anonymize) the data before transfer

    Create multiple TDMS clients with differing data volumes in

    DEV as master clients to supply test or training systems

    recurringly, e.g. for resetting purposes

    Create initial master shell and place in transport path to be

    used as starting point for target system build

    Use Cases General

  • 12

    2010 SAP AG. All rights reserved. / Page 23

    1. Customer Situation and Challenges

    2. Solution Approach and Technology

    3. Benefits & Use Cases

    4. Facts and Figures

    5. Outlook

    6. Questions & Answers

    Agenda

    SAP TDMS Overview

    2010 SAP AG. All rights reserved. / Page 24

    SAP TDMS Facts and Figures

    System Recommendations

    SAP WebAS 6.20, 6.40 or 7.00

    Minimum 4000 SAPS, 20 GB hard drive

    Supported Releases

    ERP: 4.6C, 4.7, 5.0, 6.0

    BW: 3.5, 7.0

    CRM: 4.0, 5.0, 6.0, 7.0

    Pricing

    Price is dependent on size of production database

    License covers one PRD system and n non-PRD systems

    Knowledge Transfer/Training

    TDMS10 (offered by SAP Education)

    Implementation

    Implementation Services offered by SAP Consulting

    Service and Support

    SAP Standard and Premium Maintenance

  • 13

    2010 SAP AG. All rights reserved. / Page 25

    1. Customer Situation and Challenges

    2. Solution Approach and Technology

    3. Benefits & Use Cases

    4. Facts and Figures

    5. Outlook

    6. Questions & Answers

    Agenda

    SAP TDMS Overview

    2010 SAP AG. All rights reserved. / Page 26

    Outlook

    SAP TDMS Road Map

    20082007

    Next TDMSTDMS 3.0

    Supported SAP Solutions with

    TDMS Classic:

    ERP, BW, CRM, HCM

    IS-Specific TDMS Functionality:

    Apparel Footwear Solution (AFS),

    Discrete Industries & Mill Products

    (DIMP), Healthcare, Retail

    Business Process Library (BPL)

    Data Scrambling Workbench

    Additional supported SAP Solutions

    with TDMS Classic: SCM, SRM, GTS

    IS-Specific TDMS Functionality

    Oil & Gas, Public Sector (Funds Management),

    Retail (Store Solution), Utilities

    Unified Data Scrambling Functionality

    HCM-specific Enhancements

    Solution Manager Integration

    Unified User Interface

    Process Automation

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

  • 14

    2010 SAP AG. All rights reserved. / Page 27

    Employee Administration

    Organizational Management

    Global Employee Management

    Time and Attendance

    Travel Management

    Payroll

    Benefits Management

    CATS Cross-Application Time Sheet

    Workforce Cost Planning & Simulation

    E-Recruiting

    HR Processes & Forms

    New Selection of Objects

    SAP TDMS for HCM

    Solution Coverage - Roadmap

    Available since TDMS 3.0

    Planned for next TDMS

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

    2010 SAP AG. All rights reserved. / Page 28

    Planned for Next SAP TDMS

    Main Control Center

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

  • 15

    2010 SAP AG. All rights reserved. / Page 29

    Planned for Next SAP TDMS

    Project View - Main Screen

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

    2010 SAP AG. All rights reserved. / Page 30

    Planned for Next SAP TDMS

    Project View Details

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

  • 16

    2010 SAP AG. All rights reserved. / Page 31

    Planned for Next SAP TDMS

    Data Migration Landscape

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

    2010 SAP AG. All rights reserved. / Page 32

    Planned for Next SAP TDMS

    TDMS for HCM: eRecruiting

    Transfer of eRecruiting objects (Candidate, Applicant, Candidacy, ) and their relationships

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

  • 17

    2010 SAP AG. All rights reserved. / Page 33

    Planned for Next SAP TDMS

    TDMS for HCM: HR Processes & Forms

    Transfer of HR Processes & Forms data for personnel #s

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

    2010 SAP AG. All rights reserved. / Page 34

    Define HCM objects (Personnel Numbers, PD-Objects, Relations) based on complex

    business criteria

    Example:

    Select 20 trainees from a particular Company Code. They should all be born after Jan

    01,1992, should have a particular wage type and should have entered the company after Sept

    01, 2008. In addition, they should have a particular absence in 2010

    Selections can be defined in a separate transaction by HR administrators instead of

    TDMS for HCM user

    The list of objects and relations obtained from such a selection can be used in

    multiple transfers

    Standard SAP HCM authorizations are active for selection of objects plus additional

    authorization checks to control access to transaction

    Planned for Next SAP TDMS

    TDMS for HCM: New Selection of Objects (1/2)

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

  • 18

    2010 SAP AG. All rights reserved. / Page 35

    Planned for Next SAP TDMS

    TDMS for HCM: New Selection of Objects (2/2)

    This presentation and SAPs strategy and possible future developments are subject to change by SAP at any time for any reason w ithout notice. This document is provided w ithout a w arranty of any kind either expressed or implied, including but not limited to, the implied w arranties of mechantability, f itness for a particular purpose , or non-infringement.

    2010 SAP AG. All rights reserved. / Page 36

    1. Customer Situation and Challenges

    2. Solution Approach and Technology

    3. Benefits & Use Cases

    4. Facts and Figures

    5. Outlook

    6. Questions & Answers

    Agenda

    SAP TDMS Overview

  • 19

    2010 SAP AG. All rights reserved. / Page 37

    Questions?

    2010 SAP AG. All rights reserved. / Page 38

    Thank you!

  • 20

    2010 SAP AG. All rights reserved. / Page 39

    Contact Information

    Peter Keller

    Solution Management

    SAP America, Inc.

    +1 (610) 618-6847

    [email protected]

    ContactFeedback

    Please complete your session evaluation.

    Be courteous deposit your trash, and do not take the handouts for the following session.

  • 21

    2010 SAP AG. All rights reserved. / Page 41

    No 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

    IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

    Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

    Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

    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 Citrix Systems, Inc.

    HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute 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 by Netscape.

    SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer 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 other countries.

    Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.

    All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document 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 any form 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 document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and 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 the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

    SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may 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 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.

    2010 SAP AG. All Rights Reserved