Test Data Migration Server

SAP Test Data Migration Server:

Overview and Implementation

Peter Keller, SAP AG

Chicago, July 24, 2008

© SAP 2008 / Page 1

SAP TDMS Reference Customers

© SAP 2008 / Page 2

SAP TDMS Reference Customers

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.

A Smoother Test Ride

© SAP 2008 / Page 3

Customer Situation and ChallengesSolution Approach and TechnologyBenefits, Best Practices & Use CasesFacts and FiguresOutlookWrap-up

Agenda:

SAP TDMS Overview

© SAP 2008 / Page 4

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,

testing, quality assurance, and training environments based on real business data

© SAP 2008 / Page 5

Challenges with Full System Copy

Interfaces need to be changed or closedUsers need to be set up or changedAuthorizations need to be adjustedSaved objects need to be copied back ( CATTS)

After each copy, settings need to be readjusted

CHALLENGES CONSEQUENCES

Production systems are becoming larger and larger

Administration of large data volumeIncreased 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.

© SAP 2008 / Page 6

Customer Situation and ChallengesSolution Approach and TechnologyBenefits, Best Practices & Use CasesFacts and FiguresOutlookWrap-up

Agenda:

SAP TDMS Overview

© SAP 2008 / Page 7

The Solution

With SAP TDMS you can:Reduce data volumeSimulate production environmentAutomate system refreshesSelectively refresh individual clientsExtract data based on business objects or org. units/timesliceScramble 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.

© SAP 2008 / Page 8

SAP TDMS for ERP: The Solution

Shell Creation - Repository and client-indep. data onlyTDMS for ERP Classic:

Master and configuration data onlyMaster and configuration data in addition to time slice of transactional dataMaster 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

Available Data Extraction Scenarios ERP

© SAP 2008 / Page 9

SAP TDMS for BI and CRM: The Solution

Shell Creation - Repository and client-independent data onlyMaster data and time slice of transactional data

Available Data Extraction Scenarios BI

Shell Creation - Repository and client-independent data onlyTDMS for CRM Classic:

Master and configuration data onlyMaster and configuration data in addition to time slice of transactional data

Available Data Extraction Scenarios for CRM

© SAP 2008 / Page 10

Technology: ArchitectureTDMS Classic

Fast, optimized data transferProven high-speed data extraction technology (Migration Workbench)Table-wise data migration via RFC (Remote Function Call) connections

Sender System SAP TDMS Receiver System

© SAP 2008 / Page 11

Solution ApproachTDMS 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 can be 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

© SAP 2008 / Page 12

Technology – TDMS ClassicProcess and System Setup

Refresh (recurrent):Source System Receiver SystemTDMS

Initial Setup Phase (one-time activity):Source System Receiver System

3. Delete Client Data1. TDMS Customizing2. Data Analysis

2. Delete Client Data1. ∆ Analysis

TDMS

3. Test Data Migration

4. Test Data Migration

© SAP 2008 / Page 13

Business Process Library - Approach

Predefined business object and process data selection scenariosMaster 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 14

SAP TDMS – BPL: 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)

© SAP 2008 / Page 15

SAP TDMS – BPL: Purchasing Process

Provides selective data of a purchasing process (master and transactional data)


Purchase Order

Material Document

Invoice

Accounting Documents

Purchase Requisition

Material

Vendor

Service Packets

Conditions

© SAP 2008 / Page 16

SAP TDMS BPLArchitecture and Components

Sender System Receiver System

DD Framework

Central-System

Scenarios / Content

Control / Monitoring

Parallel RFCDDIC

ExtractorCrawler Importer

Admin Designer

Data

File

qRFC

Data qRFC(optional)

Deleter

DD Framework

© SAP 2008 / Page 17

Business Process LibraryAvailable Business Contexts

Master DataBusiness PartnerMaterial VendorCustomerG/L AccountFixed Asset Functional LocationEquipmentInternal Order ProjectArticle (Retail)Insurance Object (FS-CD)Loans Contract (CML)Asset (CFM)Contract (IS-U)Installation (IS-U)Device (IS-U)User

Transaction DataAccounting DocumentPurchase Requisition Purchase Order Sales OrderMaterial Document Billing Document Invoice Receipt Quality NotificationMaintenance Order Allocation Table (Retail)FI-CA DocumentTransaction (CFM)

Process DataPurchase Order Sales Order Insurance Object(FS-CD) Contract (FS-CD)Loans ContractContract (IS-U)

Custom DataEmpty scenario for custom-specific objects

© SAP 2008 / Page 18

Customer Situation and ChallengesSolution Approach and TechnologyBenefits , Use Cases & Best PracticesFacts and FiguresOutlookWrap-up

Agenda:

SAP TDMS Overview

© SAP 2008 / Page 19

Benefits of SAP TDMS

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 FLEXIBILTY

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

OUTSOURCINGReduce testing expenses by outsourcing those activities to low-cost countries while keeping sensitive data anonymous thus ensuring legal compliance.

Resulting in REDUCED COST while INCREASING QUALITY in development and training activities

© SAP 2008 / Page 20

SAP TDMS – Business Case*

0

500

1000

1500

2000

2500

Year 1 Year 2 Year 3 Year 4

Future: Use of SAP TDMS

PROD QA DEV Total

0

500

1000

1500

2000

2500

Year 1 Year 2 Year 3 Year 4

PROD QA DEV Total

Current: Copy of Production

* Based on real customer data

Storage Requirements for 3-Tier Landscape

0 GB0 GB

© SAP 2008 / Page 21

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, e.g. 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 22

Typical Process Example 1: BPL

Setup of new target system via TDMS Shell CreationExecute TDTIM, TDMDC or TDTCC to build training/maintenance client with a reduced set of dataIn order to quickly provide data for training purposes or for maintenance situations, utilize BPL scenarios to selectively transfer specific

Master dataTransactional data plus dependent master data orData needed for specific 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, utilize BPL scenarios to selectively transfer specific

Master dataTransactional data plus dependent master data orBusiness Processes/Test cases

© SAP 2008 / Page 24

Customer Use CaseGlobal Insurance Company

IndustryGlobal Insurance Company

Target SystemsQuality SystemDevelopment System (Enhance development process)Test Systems (migration tests)

Customer RequirementsRefresh small amounts of quality system data from productionEnhance development process by providing new test data on development systemReduce costs for migration through creation of smaller test systems

BPL Business Scenarios usedCML (Loan)

© SAP 2008 / Page 25

Customer Use CaseInsurance for Building Sector

IndustryInsurance for building sector, Real Estate Administration

Target SystemsQuality System (Maintenance Clients for problems on production)Development System (Enhance development process)

Customer RequirementsRefresh Development systems with small amounts of data from production and QASpeed up troubleshooting in case of production problems without risking compliance

BPL Business Scenarios usedFS-CD (Insurance Object)CML (Loans)

© SAP 2008 / Page 26

Customer Use CaseInsurance Company

IndustryInsurance Company

Target SystemsQuality System (Synchronize FS-CD QS with reduced Mainframe QS)Development System (Enhance development process)

Customer RequirementsQS 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 copiedParallelization by 4 processes Total extraction and copy time: ~4h

BPL Business Scenarios used

© SAP 2008 / Page 27

Customer Use CaseInternational Heavy Industry Company

IndustryInternational Heavy Industry Company

Target SystemsQuality System Development SystemTraining Systems

Customer RequirementsBuild up a small training client with productive data for PM employee trainings

BPL Business Scenarios usedPM (Maintenance Order)SD (Sales Document)

© SAP 2008 / Page 28

Customer Use CaseTop 5 German Cooperative Bank

IndustryTop 5 German Cooperative Bank

Target SystemsQuality System Development System

Customer RequirementsTransfer consistent test data to development andquality clients to speed up IT projects

BPL Business Scenarios usedCML (Loans)BCA (Bank Contract)

© SAP 2008 / Page 29

TDMS BPL - Customer Use CaseRetailer – Home Improvement

IndustryRetailer (Home Improvement)

Target SystemsTraining Systems

Customer RequirementsBuild up a system with 10 training clients which should be refreshable over nightA very small amount (< 8GB) of consistent data had to be extracted out of a retail system (> 3TB)

BPL Business Scenarios usedIS-Retail (Article)Custom Scenario to handle complete copies of (customer) tables

© SAP 2008 / Page 30

Customer Use CaseGerman Local Power Supplier

IndustryGerman Local Power Supplier

Target SystemsDevelopment SystemQuality System

Customer RequirementsConsistent data extraction for IS-U data for problem caseson production and improvement of development quality

BPL Business Scenarios usedIS-U (Contract Account and Business Partner)

© SAP 2008 / Page 31

SAP TDMS - Best PracticesBuild Maintenance Client

Target:Create clients for maintenance/support casesProvide live data from production for analysis in test/dev environment

Requirements:specific productive data for resolving support casesCoverage 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 caseAdd customer specific objects and relationsWhen support case occurs:– Apply selection criteria for affected scenario– Extract and import test data from productionRebuild target client in regular intervals to provide up-to-date customizingand ensure consistency with TDMS Classic process types

© SAP 2008 / Page 32

SAP TDMS - Best PracticesBuild up Project or Training System

Target:Create System for use during implementation / development projectsor training sessionsReduce disk space and hardware in comparison to system copiesProvide real-life data for tests and training

Requirements:Test data for developer test or QA/Training purposesCoverage of wide range of test cases

Procedure:Build up or reuse system shell (TDMS Shell Creation)or create new client on existing systemCopy required basic data (i.e. TDTIM / TDMC / Client Copy Customizing)Define and copy suitable TDMS-BPL scenariosUse TDMS-BPL custom scenario to copy additional data (e.g. copy complete Z-tables, reduce tables by free selection criteria, etc.)

© SAP 2008 / Page 33

SAP TDMS BPL - Best PracticesRefresh Development System

Target:Provide test data for developersReduce time and costs for software logisticsImprove quality of developments

Requirements:Small amount of data requiredCoverage of specific test casesScramble 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 packagesAdd customer specific objects and relationsApply selection criteria and scrambling rules for test casesExtract and import test data from production or quality systeminto new development client

© SAP 2008 / Page 34

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.”

Dr. Klaus-Ulrich Meininger, Head of IT Systems LMH

“Using SAP Test Data Migration Server enables us to significantly improve the quality of our in-house development, because development work is no longer interrupted by repeated time-consuming transports for testing purposes.”

Alexander Angermann, SAP Basis Lead, Behr Group

© SAP 2008 / Page 35

Customer Statement Pacific Coast Building Products

“With SAP Test Data Migration Server, we’ve been able to free up our

IT resources, our infrastructure team, as well as our data backup and storage systems.”

Randy SubryanEnterprise Architect

Pacific Coast Building Products

© SAP 2008 / Page 36© SAP 2007 / Page 36

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. from doing full data copies to QAS

Errors in production systems caused by inconsistent data in QAS

Customer ExperienceHolly Corp. – Challenges prior to SAP TDMS

© SAP 2008 / Page 37© SAP 2007 / Page 37© SAP 2007 / Page 37© SAP 2007 / DSAG Jahreskongress 2007 / Page 37© SAP 2008 / GSS SAP Business ByDesign Workshop / Page 37

SAP ERP 6.0 system with IS-Oil

SAP Enterprise Portal 6.0

SAP Solution Manager 4.0

SAP Business Intelligence 7.0

SAP Process Integration 7.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 ExperienceHolly Corp. - SAP Landscape

© SAP 2008 / Page 38

Customer ExperienceHolly Corp. – SAP TDMS Environment

HEQ HEPHED

HBD HBQ

HSO

HBP

SAP SOLUTION MANAGER

(SAP TDMS Console)

ECC 6.0 Landscape

BI 7.0 Landscape

© SAP 2008 / Page 39

Customer ExperienceHolly Corp. – SAP TDMS Technical Infrastructure

Server 1 (HEP) ERP Source:Model: HP DL585

CPU: 2 x Intel Xeon 82142.2 GHz dual core 32BIT

Memory: 16 GB

Server 4 (HEQ) ERP Target:Model: HP DL380

CPU: Quad Intel Xeon 3.16 GHz, 32BITMemory: 12 GB

Server 3 (HSO)SAP Solution Manager(SAP TDMS Console)

Model: HP DL380CPU: 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 82142.2 GHz dual core 32BIT

Memory: 16 GB

Server 5 (HBQ) BI Target:Model: HP DL380

CPU: Quad Intel Xeon 3.16 GHz, 32BITMemory: 12 GB

© SAP 2008 / Page 40© SAP 2007 / Page 40

Knowledge of R3load system copy procedure critical for shell creation functionality

Ensure sufficient hardware resources for target system

Straightforward installation and operation

No business, 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 ExperienceHolly Corp. - SAP TDMS Lessons Learned

© SAP 2008 / Page 41

Customer Example - PetrobrasTechnical 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 serverCPU: 4 UltraSPARC IV 1,35 MHz (dual core) Memory: 16 GBytesCapacity: ~ 2900 SAPSHosted System: copy of PEP (source system)

Server 2:Model: 1 system board of a Sun MicroSystems Enterprise 25K serverCPU: 4 UltraSPARC IV 1,35 MHz (dual core) Memory: 16 GBytesCapacity: ~ 2900 SAPSHosted System: copy of PEP (target system) + GPD (TDMS console)

© SAP 2008 / Page 42


When the CLUSTER_FILL task started (writing on cluster export table in the source system), an extra system board was added to server 1, doubling its size

Server 1:Model: 2 system boards of a Sun MicroSystems Enterprise 25K serverCPU: 8 UltraSPARC IV 1,35 MHz (dual core) Memory: 32 GBytesCapacity: ~ 5800 SAPSHosted System: copy of PEP (source system)

Server 2:Model: 1 system board of a Sun MicroSystems Enterprise 25K serverCPU: 4 UltraSPARC IV 1,35 MHz (dual core) Memory: 16 GBytesCapacity: ~ 2900 SAPSHosted System: copy of PEP (target system) + GPD (TDMS console)

© SAP 2008 / Page 43


When the MT_DATA_LOAD task started (writing on data tables in the target system), the extra system board was moved from server 1 to server 2

Server 1:Model: 1 system board of a Sun MicroSystems Enterprise 25K serverCPU: 4 UltraSPARC IV 1,35 MHz (dual core) Memory: 16 GBytesCapacity: ~ 2900 SAPSHosted System: copy of PEP (source system)

Server 2:Model: 2 system boards of a Sun MicroSystems Enterprise 25K serverCPU: 8 UltraSPARC IV 1,35 MHz (dual core) Memory: 32 GBytesCapacity: ~ 5800 SAPSHosted System: copy of PEP (target system) + GPD (TDMS console)

© SAP 2008 / Page 44

Customer Example - PetrobrasData 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 45

Customer Example - PetrobrasFirst 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 week copy

Result system: PEP’, renamed to PEH afterwards, 1.3 TB database size

© SAP 2008 / Page 46

Customer Example - PetrobrasSecond Copy

Source system: PEH, 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, 900 GB database size

© SAP 2008 / Page 47

Customer Example - PetrobrasTDMS System Landscape

PEDPEQ

PEP

Development

QualityAssurance

Production

PPP

Pre-production

PEH

Test

Acceptance

© SAP 2008 / Page 48

Customer Example - PetrobrasKey Lessons Learned

Straightforward installation and operation

No business, 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, trim or scramble HR data in transparent fields

© SAP 2008 / Page 49

Customer Example - PetrobrasSummary

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 50

Customer Situation and ChallengesSolution Approach and TechnologyBenefits, Use Cases & Best PracticesFacts and FiguresOutlookWrap-up

Agenda:

SAP TDMS Overview

© SAP 2008 / Page 51

Facts and Figures

System RecommendationSAP WebAS 6.20, 6.40 or 7.00Minimum 4000 SAPS, 20 GB hard drive

Supported ReleasesERP: 4.6C, 4.7, ERP 5.0, ERP 6.0BI: 3.5, 7.0CRM: 4.0

PricingPrice is dependent on size of production databaseLicense covers one PRD system and n non-PRD systems

Knowledge Transfer/TrainingTZTDM3 (offered by SAP Education)

ImplementationImplementation Services offered by SAP Consulting

Service and SupportSAP Standard and Premium Maintenance

© SAP 2008 / Page 52

Excerpt of Existing SAP TDMS Customers

Schaeffler KG Edeka AG Bekaert N.V. EMI Group Plc. nordIT GmbH Worldbank

Behr GmbH & Co. KG Provinzial NordWest Holding

GB Gas Holdings Limited

Anheuser-Busch Companies, Inc.

Pacific Coast Building Products

R.J. Reynolds Tobacco Company

Endress & Hauser Solvay SA Vodafone Group Plc. Microsoft Corporation REWE Homebase Limited

Heidelberger Druckmaschinen

SPAR Österr. Warenhandels AG

British Nuclear Fuels Plc.

Nippon Paper Industries Co., Ltd.

Allgemeines Krankenhaus Wien Nordson Corporation

Burberry Limited Telekom Austria AG Astellas Solectron Corporation J. Crew Group Inc. IGT

Kommunalkredit Austria AG

The Coca-Cola Company Service Birmingham Ltd. Disney Worldwide

Services, Inc.EADS Deutschland

GmbH Federal Prison Industries

Degussa AG Smithfield Foods Kao Corporation Holly Corp. Johnson & Johnson Petrobras

KLA-Tencor Corporation

Oesterreichische Kontrollbank

Holcim Group Support Ltd.

Stadtwerke Düsseldorf AG

Ulta Salon, Cosmetics & Fragrance

School Board of Polk County

Eon AG EMI WalMart Mars AstraZeneca T-Mobile USA, Inc.

E.I. DuPont de Nemours & Co., Inc.

Bundesamt für Bauten und Logistik

Pick 'n Pay Retailers (Pty) Ltd. Baldor Electric Company Wincor Nixdorf

International GmbHPuget Sound Energy,

Inc.

W.W. Grainger, Inc. Jumbo Markt AG Air Liquide Goodrich Corporation Autodesk, Inc. UPM-Kymmene Oyj

ISE Innomotive Systems Europe GmbH

Migros-Genossenschafts-Bund

City Power Johannesburg (Pty) Ltd. CenterPoint Energy, Inc. Cemex Central, S.A. de

C.V.Agilent Technologies,

Inc.

Kimberly Clark Pirelli & C. S.p.A. First Energy Diageo Plc. Yell Ltd. BOC Group Plc.

VNG Verbundnetz Gas AG Electricity Supply Board

ADC Telecommunications,

Inc.Mahindra Mahindra Effem Services

IncorporatedPratt & Whitney Canada

Inc.

Weidmüller Coles Husky Energy Inc. Forest Laboratories, Inc. Weyerhaeuser Respironics, Inc.

Leopold Kostal GmbH & Co. KG

Saskatchewan Power Corporation

Eastman Chemical Company

Honeywell International, Inc. Zentraldienst der Polizei Nortel Networks Limited

Otafuku Sauce Co., Ltd.

Kyocera Mita Corporation

Co-Operative Bulk Handling Ltd. Genentech, Inc. Horiba, Ltd. Linde AG

SAP Reference Program

© SAP 2008 / Page 53

SAP TDMS – Pricing ModelAs of October 2007

Price depends on DB size of productive system:

Standard DB and maintenance fees as well as standard regional uplifts applyLicense covers one productive system and n non- productive systemsMaterial Number: 7002944

Note:Fees are not prorated and apply for each productive system

DB size in GB Price in USD0 - 299 51,000300 - 499 72,000500 - 999 109,5001,000 - 1,999 156,0002,000 - 3,999 156,0004,000 + n times 1,000

156,000 + n times 30,000

© SAP 2008 / Page 54


Agenda:

SAP TDMS Overview

© SAP 2008 / Page 55

SAP Test Data Migration Server

Road Map(Conceptual Timeline)

Last Updated: April 2008

This document contains intended strategies, developments and/or functionality 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 2008 / Page 56

SAP TDMS Road MapConceptual Timeline

This document contains intended strategies, developments and/or functionality 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.

HCM-specific Scenarios- TDHC1 – PA only(Personnel Administration)

- TDHC2 – OM & PA(Organizational Management& Personnel Administration)

Supports 4.7 and higher

Enhancements to BPL

TDMS 3.0 TDMS 3.0Ext. Set 1+2

Supported Releases

4.6C, 4.7, ERP04, ERP6.0

Available Scenarios

- TDSHL - TDTCC- TDMDC - TDDEL- TDTIM

TDMS Workbench- Data Scrambling- Custom Scenarios

Business Process Library (BPL)

QIII/2008 2010QII/2008QI/2008

TDMS for SRM

TDMS for SCM

Enhancements to BPL

Execution Manager

TDMS 3.0Ext. Set 3

TDMS for BW

- TDBTM

TDMS for CRM

- TDCMC- TDCTM

Enhancements to BPL

TDMS 4.0

© SAP 2008 / Page 57

Legal Disclaimer

This presentation outlines our general product direction and should not be relied upon 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, eitherexpressed or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose.SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or gross negligence.

© SAP 2008 / Page 58

SAP TDMS – Latest Offerings

TDMS BI (Currently in Ramp up)

Solution similar to TDMS for ERP solutionSupports release BW 3.5 and BI 7.0Possible to reuse settings from TDMS for ERP implementationData reduction based on time characteristicsFilters PSA data completelySignificant reduction in InfoCube and ODS data

TDMS CRM (Currently in Ramp up)

Solution similar to TDMS for ERP solutionSupports release CRM 4.0Time based reduction and Master data scenario availableEnsures consistency in core business processes such as sales, service, marketing etc. Ensures consistency of document flowSupports integration scenarios for mobile clients

© SAP 2008 / Page 59

Architecture & Solution Approach –TDMS BI

BI Architecture

Data! Data!

Data!

Data!

© SAP 2008 / Page 60


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 61


Solution ApproachUse the existing DMIS infrastructureIdentify the large transactional tables and reduce themPSA data is temporary and hence not transferredAll Master Data is transferred in fullReduction 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. 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 62

SAP TDMS for HCMOverview

Workforce Planning & AnalyticsWorkforce Cost Planning & SimulationWorkforce PlanningWorkforce BenchmarkingWorkforce Process Analytics & MeasurementTalent Management Analytics & Measurement

Workforce Process ManagementEmployee AdministrationOrganizational ManagementGlobal Employee ManagementTime and AttendanceTravel ManagementPayrollBenefits Management

End-User ServiceDeliveryManager Self-ServicesEmployee Self-ServicesEmployee InteractionCenterBusiness RolesOffice-IntegrationDuet

Workforce DeploymentProject Resource PlanningResource and ProgramManagementCall Center StaffingRetail Scheduling

Talent Management RecruitingCareer ManagementSuccession ManagementPerformance ManagementCompensation ManagementEnterprise LearningIncentive Commission Management

© SAP 2008 / Page 63© SAP 2007 / Page 63

SAP TDMS for HCMArchitecture – Data Scrambling

Scrambled Data

Production System

HR original

Data

TDMS Server

Test System

(Cluster)

HR scrambled Data

RFC

RFC

Control System

© SAP 2008 / Page 64© SAP 2007 / Page 64

SAP TDMS for HCMProcess Tree

© SAP 2008 / Page 65© SAP 2007 / Page 65

TDMS for HCMData Selection for PA

Selection via PNPCE

Adhoc-Query

© SAP 2008 / Page 66© SAP 2007 / Page 66


© SAP 2008 / Page 67© SAP 2007 / Page 67

TDMS for HCMData Selection for PA – Custom tables

© SAP 2008 / Page 68© SAP 2007 / Page 68


© SAP 2008 / Page 69© SAP 2007 / Page 69

TDMS for HCMData Selection for PD

© SAP 2008 / Page 70© SAP 2007 / Page 70

TDMS for HCMData Selection for PD and PA

Personell Data selected as well

Either mini selection (IT0000 – IT0003) or comprehensive selection possible

© SAP 2008 / Page 71© SAP 2007 / Page 71

TDMS for HCMData Selection for PD and PA

Target area per userand object type

possible

© SAP 2008 / Page 72

Complete scrambling of personnel dataContent dependencies are taken into accountGrouping of content absolutely freely possibleProvisioning of business content per country (recommendations)

TDMS for HCM

Scrambling

© SAP 2008 / Page 73© SAP 2007 / Page 73

Scrambling – Groups

© SAP 2008 / Page 74© SAP 2007 / Page 74

Scrambling – Sets

© SAP 2008 / Page 75© SAP 2007 / Page 75

Scrambling – Fields

© SAP 2008 / Page 76© SAP 2007 / Page 76

Scrambling – Fields

© SAP 2008 / Page 77

Target number range customizable per user if desiredOption to set maximum number of objects per userOption to exclude objects and infotypes of a table from transferOption to exclude specific employees from transfer by flexibly possible via specific criteriaFlexible setting which cluster/tables should be taken into account (e.g. customer-specific cluster/tables)

TDMS for HCM

Customizing

© SAP 2008 / Page 78© SAP 2007 / Page 78

TDMS for HCMCustomizing

© SAP 2008 / Page 79

In general, existing HCM authorizations are checkedFor performance reasons, comprehensive authorization checks can be reduced

No authorization checkAuthorization check only on object levelComplete authorization check

In addition, individual activities can be assigned to specific activity groups depending on customer situation

TDMS for HCM

Authorization Concept

© SAP 2008 / Page 80© SAP 2007 / Page 80

TDMS for HCMExample for Authorization Group

Can be defined customer-specific

Asssignment to activity group Is done via specific authorization object

© SAP 2008 / Page 81

The SAP TDMS Vision

Solution Manager

SAP TDMS

Non-Productive Landscape

SAP R/3 SAP CRM/SRM

SAP APOSAP BW

Productive Landscape

© SAP 2008 / Page 82

SAP TDMS Services 1/2

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 TDMS Training Class

This course will prepare you to implement and configure standardfunctionality of SAP TDMS

SAP Education Course TZTDM3

© SAP 2008 / Page 83

SAP TDMS Services 2/2

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, scrambling, 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 TDMS Set-up & Configuration Consulting

Remote initial set-up using a landscape provided by customer

Documentation of set-up

SAP TDMS Proof of Concept / Evaluation Offering

© SAP 2008 / Page 84


Agenda:

SAP TDMS Overview

© SAP 2008 / Page 85

7 Key Points to Take Home

SAP TDMS helps customers to reduce storage requirements for non-production systemsSAP TDMS enables the transfer of current test data into development environmentsSAP TDMS improves efficiency and quality of in-house developmentsSAP TDMS provides an easy way to refresh clientsSAP TDMS supports independent project schedulesSAP TDMS enables customers to simulate new business scenariosSAP TDMS is a tool every SAP customer should have

© SAP 2008 / Page 86

Resources

SAP Test Data Migration Server Websitewww.sap.com/tdms

SAP Service Marketplace Webpage on TDMShttp://service.sap.com/customdev-tdms

System Landscape Optimizationhttp://service.sap.com/slo

© SAP 2008 / Page 87

SAP TDMS

© SAP 2008 / Page 88

Your Turn!

Peter KellerSolution Management

SAP [email protected]+49 6227/7-44919

© SAP 2008 / Page 89© SAP 2007 / Page 89© SAP 2007 / Page 89© SAP 2007 / Page 89

Thank you for your attentionQUESTIONS?

© SAP 2008 / Page 90

Copyright 2008 SAP AGAll rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, 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. All other product and service names mentioned and associated logos displayed 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. 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. 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

© SAP 2008 / Page 91

Copyright 2008 SAP AGAll Rights ReservedWeitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, 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. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. A., aber nicht ausschließlich, 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.SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.Alle Rechte vorbehalten.

© SAP 2008 / Page 92

SAP TDMS – BPL: Article Master

Main Business Objects

Article (IS-R)

Listing Data

Purchase Information

Layout

Provides selective Article Master data with depending objects

© SAP 2008 / Page 93

SAP TDMS – BPL: ExampleSales Order


Sales Order

Sales Document

Customer

Materials

Conditions

Provides selective Sales Order data with depending objects (including master data)