Tdms Presentation
-
Upload
slawomir-pindel -
Category
Documents
-
view
116 -
download
3
Transcript of Tdms Presentation
Customer Situation and RequirementsSolution Approach – TechnologyValue to the Customer
System DemoVersion TDMS 05 – Facts and Figures
Future PlansWrap-up
© SAP AG 2006, 2
Providing Test Data — Pain Points
The need to test and validate your custom developments early on with real business data?
Multiple parallel IT projects affecting different organizational units with diverse project timelines?
Scrambling real business data in non-productive systems?
Large and quickly growing SAP systems, causing increasing infrastructure and maintenance expenses?
Is your company facing …
<Place a picture from the SMART
Image Library here that relates to your solution or target
industry>
SAP Test Data Migration Server (TDMS) can help
© SAP AG 2006, 3
Providing Test Data — Current Situation
RESULTCHALLENGE
Extensive authorization checks neededSensitive data available in test system
Repository objects lose their history by copying production to test systems
Information on transport paths from development to production system is being lost
Objects must be transported into Q/A, tested, sent back to development, corr., …
New development testing can only be performed in the Q/A System
Transports need to be closed, released, re-imported after refresh
Developments need to be stopped (before system rebuild)
Interfaces (change/shut down)
Create new users or block existing ones
Assign new authorizations
Copy saved objects back into the system ( CATTS)Logical System Change (trans. BDLS)
After every copy, settings need to be readjusted
Administration of large data volume
Storage space is expensiveProduction systems constantly becoming larger
© SAP AG 2006, 4
Solution Approach: SAP Test Data Migration Server —Key Features
SAP Test Data Migration Server is the data extraction tool that populates your development and test systems with SAP business data from your live production environment
Consider implementing a solution that helps you to create lean and consistent development and test environments based on real business data
With SAP Test Data Migration Server (TDMS) software you can:
Reduce data volume in test systems
Apply ready-to-use reduction scenarios
Simulate production environment by using real business data
Reduce post-processing work by keeping administrative data in target system unchanged (interfaces, users, authorizations, etc.)
Perform selective refreshes of individual clients in target system (multi-client systems)
Scramble sensitive data according to your needs
Change client and logical system name during transfer
© SAP AG 2006, 5
Why Invest to Gain Current Test Data?
Application failures
40% Operator errors40%
HW, OS failures, disasters
20%
Source: Gartner Group
Unplanned Downtime Planned Downtime System and infrastructure maintenance
Patches, upgrades, transports
...
Reduce causes of production downtimes throughearly development testing using real production data!
Customer Situation and RequirementsSolution Approach – TechnologyValue to the Customer
System DemoVersion TDMS 05 – Facts and Figures
Future PlansWrap-up
© SAP AG 2006, 7
Solution Approach — Method of Resolution
Non-productionlandscape
Productionlandscape
Test Data Migration
Server
© SAP AG 2006, 8
TDMS Carves Out the Business Data and Sends a Reduced Copy to Another System
Client-specific migrationBusiness data is client-specificA single TDMS run migrates one source to one target client
ReductionOnly a few tables need to be reduced since 10-20% of client-specific tables contain 80-90% of client dataAll other tables (master data, customizing data, custom-made “Z” tables) are migrated entirely
Fast Data TransferUses Migration Workbench as proven technical basisMigrates data table-wise via RFC connections
© SAP AG 2006, 9
Data Reduction Background
Data volume reductionReduce a small number of tables, since they hold > 80% of the production data volumeAll other tables (master and configuration data) are transferred 1:1Customer-individual tables are transferred 1:1, or can be reduced, e.g., via time criteriaSome tables are excluded from transfer by default, e.g., change documents, etc. (customizable)
* Estimate based on project experience
7% Config. Data *
3 % Admin-Data*
80% Transaction Data *
10% Master Data *
Client DB
© SAP AG 2006, 10
Data Reduction Scenarios
Master Data and Configuration (MD/C) ScenarioOnly master and configuration data without transaction data
Time-Based (TIM) Scenario All master and configuration data, and a reduced set of transaction data based on a time limit
Individual custom-developed scenarioData selection based on organizational or other criteria
Choose the data set to be extracted from your production environment
Source
SAP TDMS Setup
TestSystem
SAP TDMS
© SAP AG 2006, 11
Transferred Data
Scenario: “Time-Based Reduction”
Day of MigrationFrom Defined Date
Bus
ines
s P
roce
sses
Business Process I
Process begins and ends within migration period
Process begins before and ends within the migration period
Business Process III
beyond date limit
TimeMigration Period
Business Process II
Process begins within migration period and ends after
Past
© SAP AG 2006, 12
System Setup
Initial Setup phase only once:
TDMS
Productive system Non-productive systems
3. Client data deletion4. Test data
migration
1. Customize TDMS
2. Analyze data
2. Client data deletion
3. Test data migration
Refresh multiple times:
Productive system
TDMS
Non-productive systems
1. Analyze data
© SAP AG 2006, 14
Migration Strategies: Different Source Systems
Production System with closed DatabasePro: ConsistencyCon: Downtime required
Production System with open DatabasePro : No downtime requiredCon : Inconsistencies
Snapshot of Production StoragePro : Consistency, no downtime requiredCon : Additional hardware, additional license fees for snapshot solution
Copy of Production SystemPro : Consistency, no downtime requiredCon : Additional hardware cost
Quality Assurance SystemPro : ConsistencyCon : Downtime required
© SAP AG 2006, 15
Technology/Architecture — “Snapshot/Cloning”
C
TDMSProd Target
Extract
P'
write SnapshotP
Prod'
Customer Situation and RequirementsSolution Approach – TechnologyValue to the Customer
System DemoVersion TDMS 05 – Facts and Figures
Future PlansWrap-up
© SAP AG 2006, 17
Value to the Customer
Improve quality of customer developments by improving test data quality
Saves disk space by reducing data volume in non-productive systems
Stabilization of non-productive systems by not touching administrative data
Architecture of TDMS does not depend on releases of productive system and can theoretically be used with all R/3 and ERP systems
Benefits
Customers with large systems (size of database)
Customers who do their own development and need “actual data” to do testing in the development system
Customers who need to make data anonymous when they “leave”a productive system
Customers who need to refresh clients in non-productive systems selectively
Target Audience
With TDMS, companies are able to create small and consistent non-productive systems as an extract of their live system
© SAP AG 2006, 18
TDMS Reduces the Overall Storage Usage
Example of a three system landscape
0
500
1000
1500
2000
2500
Year 1 Year 2 Year 3 Year 4
PROD QA DEV Total
Current: Copy of Production
0
500
1000
1500
2000
2500
Year 1 Year 2 Year 3 Year 4
Future: Use of SAP TDMS
PROD QA DEV Total
Customer Situation and RequirementsSolution Approach – TechnologyValue to the Customer
System DemoVersion TDMS 05 – Facts and Figures
Future PlansWrap-up
© SAP AG 2006, 21
Version TDMS 05 — Facts and Figures
RequirementsSAP WebAS 6.20 or 6.40Minimum 4 CPU, 4 GB RAM, ca. 20 GB DB
System environments managedSAP R/3 4.6C SAP R/3 4.7mySAP ERP 2004 ECC 5.0
PricingPrice depends on size of database of production systemPrice for one production and nnon-production installations
ImplementationTraining offered for TDMS implementation and configuration (TZTDM3)Implementation services offered by SAP Consulting
Service and SupportSAP Standard + Premium maintenance applies
© SAP AG 2006, 22
Implementation Services by SAP Consulting
Base Offering – Initial Set Up
Custom-specific functional enhancement (e.g., data scrambling, customer-specific tables, conceptual design etc.)
Scoping Workshop: Workshop with customer (on-site) to analyze and validate custom-specific demand and define project scope
Duration and price depending on scope
Project Scope
Duration
Pricing
Deliverable
Expert Offering – Custom-Specific AdaptationsDeliverable
Project Scope
Duration/Pricing
Fully functional non-production system
Kick-Off Workshop with customer (on-site) to discuss technical details and project set up
Initial set up of non-production system: Configuration of SAP Test Data Migration Server according to selected set of data →customer validation
Know-how transfer to enable customer to set up and refresh their non-production system with SAP Test Data Migration Server
12 consulting days
Fixed price
Customer Situation and RequirementsSolution Approach – TechnologyValue to the Customer
System DemoVersion TDMS 05 – Facts and Figures
Future PlansWrap-up
© SAP AG 2006, 24
SAP TDMS: Structure
P01
D01
T01
S01MD/C
P01/401-D01/401
90009 Initial Setup 10/01/2003TIME
P01/401-T01/401
TIMEP01/401-S01/401
Project Packages
Tim
e
9000x Initial Setup xx/xx/xxxx
9000x Refresh of… xx/xx/xxxx
9000x Refresh of… xx/xx/xxxx
Tim
e
9000x Initial Setup xx/xx/xxxx
9000x Refresh of… xx/xx/xxxx
9000x Refresh of… xx/xx/xxxx
Tim
e
P01
(ER
P Eu
rope
)
Subprojects
9000x Refresh of… xx/xx/xxxx
9000x Refresh of… xx/xx/xxxx
ERP Europe
Customer Situation and RequirementsSolution Approach – TechnologyValue to the Customer
System DemoVersion TDMS 05 – Facts and Figures
Future PlansWrap-up
© SAP AG 2006, 27
Future Plans – TDMS 06
Extend the two existing scenarios (TIM and MDC) to mySAP Business Suite components to higher mySAP ERP releases
Extend functionality of TDMS migration engine User interface to maintain existing and create new scenarios User interface for “scrambling data”Build up systems “Repository only”
Performance optimizationSpeed up overall migration process
Include Storage Snapshot creation in migration process
Enable customers, consultants, and partners to create their own scenarios
Training for TDMS developers
Timeline Ramp Up planned for October 2006
Customer Situation and RequirementsSolution Approach – TechnologyValue to the Customer
System DemoVersion TDMS 05 – Facts and Figures
Future PlansWrap-up
© SAP AG 2006, 29
Resources
SAP Global Web Site:
SAP Service Marketplace: http://service.sap.com/customdev-tdms *
http://service.sap.com/slo *
* Requires login credentials to the SAP Service Marketplace
© SAP AG 2006, 30
7 Key Points to Take Home
Saves disk space of non-production systems
Provides current test data to the development environment
Focuses on consistency of reduced data
TCO reduction by transfer of data between different OS/DB
Individual refresh of non-productive clients possible
Data scrambling — a functionality of TDMS — becomes more and more important for customers
Version 05 is just the beginning — extended functionality will be available in future releases
© SAP AG 2006, 31
Your Turn!
Q&A
THANK YOU FOR YOUR ATTENTION
Ralf DebusSolution Manager SAP AGTel.: (+49) 6227-7-41105Mail: [email protected]
© SAP AG 2006, 33
Value proposition: Storage Reduction
Current situation:
Full copy of productive systems to non productive systems means today to copy the whole database n times storage of production
Future situation – use of TDMS:
Only productive systems will grow. Non productive systems stay at a constant database size based on the reduction scenario TDMS use
Value of TDMS usage:
Cost savings for hardware (storage)
Cost savings for less administrative effort
© SAP AG 2006, 34
Value proposition: Productive Data in Development Systems
Current situation:
Development systems contain only ‘garbage’ data. Developers can’t test their developments and must transport developments to Q-systems to test them.
Future situation – use of TDMS:
Development systems will become a small test client, so that developers can do testing in development systems
Value of TDMS usage:
Better quality of developments due to ‘good’ data for tests in an early stage of development
Cost savings due to less transports in Q-systems for test purposes
© SAP AG 2006, 35
Value proposition: Reduce Time for System Adaptation
Current situation:
After a full copy of a system a system must be adapted to the requirements of the target system. Interfaces (RFC’s), users, authorizations, printers, faxes, … must be changed. Often customers have scripts to support this activities, but it takes usually between 2 – 5 days.
Future situation – use of TDMS:
All administrative data will stay as they are. No RFC’s, users and so on are changed. The Non-Productive-System remains unchanged regarding administrative objects.
Value of TDMS usage:
The time for system adaptation can be reduced by 50%.
© SAP AG 2006, 36
Value proposition: Stable Non-Productive-Landscape
Current situation:
When a system is copied via ‘System Copy’ or DB copy, everything is taken from productive. That means all Interfaces are taken as they are and still ‘point’ to a productive landscape until they are manually changed.
Future situation – use of TDMS:
Since systems are kept as they are and only business data is transferred it cannot happen, that non-productive systems are linked to a productive landscape.
Value of TDMS usage:
Minimize risk to produce uncontrolled system postings in productive systems
© SAP AG 2006, 37
Copyright 2006 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. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks 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. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as 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 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.