Sie sind auf Seite 1von 45

Testing SAP

Leuker kunnen we het niet maken,

wel makkelijker!

SAP Quality Center / SAP Loadrunner


Oscar Trompé
Software Solution Partners

( )
( ) Cooperation
( )

Endorsed Business
Solutions (EBS)

Powered by NetWeaver
Open Market
(700 PbNW)
Implement, upgrade and go-live

SAP solutions from HP Software


Project Final Go Live Continuous

Blueprint Realization
Prep Preparation and Support Improvement
Cost-effective risk
Blueprint Realization
Go Live
and Support
mitigation of
Quality and upgrades


Deliver the Business Value:
The Challenge



Project Quality

Operational Costs

IT projects are delivered over-budget

IT projects fail to meet objectives Gartner
AFX News Limited
ROUNDUP - Tokyo Stock Exchange suffers worst-
ever system crash
11.01.2005, 03:08 AM

TOKYO (AFX) - The Tokyo Stock Exchange was forced to suspend trading in all shares today in
its worst-ever computer system glitch.

TSE managing director Tomio Amano blamed the glitch on a defect in software for processing
data from securities companies which was introduced in October.

IT failure causes US$100 million loss for Mizuho Securities

System shutdown loses billions in market cap
TSE CEO resigns
Change is a Fundamental Principle – Testing is a necessity

There are many changes in the solution life cycle

- and every change requires testing

Test effort
Business inspired changes
Mergers and Acquisitions
Continuous Improvements
Functional Upgrades

IT inspired changes
Technical Upgrades
Support Packages
Business inspired IT inspired
Notes changes
Full Integration into the SAP Solution Manager Application
Management Platform

SAP Solution Manager adapter for SAP Quality Center is more than just an
interface between Quality Center and SAP Solution Manager – it is a full
integration of people, processes and data

SAP Quality Center by HP

SAP Quality Center by HP
extends SAP Solution
Manager with its testing
Perfectly integrates with the
other functional areas
Knowledge Test
Management Management

Mgmt. Monitoring


Knowledge Service
Transfer OPTIMIZE Desk

Change Service
Management Delivery
Detailed Capabilities

The SAP Quality Center by HP integration mitigates

risk, saves time and lowers cost

Automated Testing of
Web Interfaces
Enhanced Control
High Usability
Efficient Collaboration
SAP Quality Center
How to Create Automated Test Scripts?

Current Approach:


Record & Replay

TAO Approach:

Drag & Drop

Business Process Level

SAP Test Acceleration and Optimization – At a Glance

To fundamentally change the testing paradigm from

manual testing to “Testing by Composition” thereby
Why? significantly reducing the costs and risks for all system
Key Benefits
change events like upgrades etc
Lower risk due to better
testing coverage and
Comprehensive End to End Business Process Testing
Solution that (1) accelerates testing of your business
What? processes and (2) is fully aligned with ASAP and Solution Improved testing ROI
Mgr. Runs on top of SAP QC by HP suite from cycles

Install the solution and build test cases using (1) Bulk Increased capacity to
Generated components or (2) Components generated on absorb and manage
demand. Once created, these highly reusable components change
How? are easily composed to form test cases. These
components are maintained and managed in the QC
framework Tighter Integration with
QC and Solutions

Jump start today through TAO implementation services
Building a Test Factory

Step 1 - PoC (Proof of Concept) Step 2 - Pilot project Step 3 – Test Factory
Industrialized testing & test
Solution evaluation Create automated regression on demand service
Automated scripting process Automated script creation &
Define/streamline test execution on demand
Test automation maintenance
industrialized process for
Comparison against current testing testing
approach Create testing strategy
Return on investment analysis Calculate metrics

T0 T0 + 12-15 weeks
T0 +1-3 weeks
Step 2
What Is Automated Load Testing?

Emulates production workloads on an IT system

Simulated Internet/ Web Server App. Server Database

Users WAN

• Replaces real users with thousands of “virtual” users

• Generates accurate, measurable and repeatable load on the
system from a single point of control
• Pinpoints bottlenecks in the system
SAP Loadrunner
SAP R/3 Transaction & Layer Breakdown

Voor de inzet van Mercury Na de inzet van Mercury

Diagnostics Diagnostics

Beide testen zijn onder gelijkwaardige omstandigheden uitgevoerd

SAP Test Data Migration
Providing Test Data - Pain points

Is your company facing …

The need to test and validate your custom
<Place a picture developments early on with real business data?
from the SMART
Image Library here Multiple parallel IT projects affecting different
that relates to your organizational units with diverse project timelines?
solution or target
industry> Scrambling real business data in non-productive

Large and quickly growing SAP systems, causing

increasing infrastructure and maintenance expenses?

SAP Test Data Migration Server (TDMS)

can help
Providing Test Data – Current Situation


Production systems constantly Administration of large data volume

becoming larger Storage space is expensive
Interfaces (change/shut down)

Create new users or block existing ones

After every copy, settings need to Assign new authorizations
be readjusted
Copy saved objects back into the system
Logical System Change (BDLS)

Developments need to be stopped Transports must be closed, released, import

(before system rebuild) after refresh

New development testing can only Objects must be transported into Q/A, tested,
be performed in the Q/A System go back to development, correction, …

Information on transport paths

Repository objects loose their history by
from development to production copying production to test systems
system is being lost
Sensitive data available in test
Extensive authorization checks needed
Providing Test Data – With TDMS you can …

Reduce data volume on test systems when

copying from production
Retain administrative objects and data in the
target system (interfaces, user, authorizations,
Preserve consistent business processes
within target system and across system
Refresh selective target system clients (esp. in
complex multi-client systems)
Enable ability to repeat functions in user-
defined intervals without costly consulting
Consider implementing a solution that helps you
to create
Avoidlean and consistent
the execution development
of transaction and
BDLS after
test environments
refreshing a testbased
systemon real business data
Do it better!
Improve the quality of your development and
training activities.
Why invest to gain current Test Data?

Unplanned Downtime Planned Downtime

System and infrastructure
HW, OS failures,
disasters maintenance
20% Application
Patches, upgrades, transports
Operator 40% ...
Source: Gartner Group

Reduce Causes for Production Downtimes by

early development testing on real production data!
TDMS carves out the business data and sends a reduced copy to
another system

Client-specific Migration
Business data is client-specific
A single TDMS run migrates
one source to one target client

Reduction Fast Data Transfer

Only a few tables need to be Uses Migration Workbench as
reduced since 10 -20% of client- proven technical basis
specific tables contain 80 – 90% Migrates data table-wise via RFC
of client data connections
All other tables (master data,
customizing data, custom-made
„Z“ tables) are migrated entirely
SAP TDMS – Solution Approach

Client DB Assumption

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

20% of client-dependent tables
Data volume reduction

80% Transaction Data * 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
10% Master Data * entirely or can be reduced via e.g. time criteria
Some tables are excluded from transfer by
7% Config. Data *
3 % Admin- Data* – E.g. change documents, user tables, etc.
* Estimate based on project experience
Two reduction scenarios

Master Data & Customizing (MDC)

Only master and customizing data is migrated
All transactional data is left out

Time-Based (TIM)
All master and customizing data is migrated
Operational rule: date in the past
All transactional data from a specified point in time until today is
TDMS contains mechanisms to include additional business
objects (SAP R/3 standard) that are located prior to the selected
date to improve consistency
Operational Rule: Time Based – Consistency

Process begins in
Data volume transferred in migration period
period of time
being migrated
Business Process II and it ends
Business processes

Process starts
Business Process I and end in period
being migrated

Process starts
before period
i c al being migrated
ri t Business Process III
C and ends within
migration period

Migration Period

Past Day of Migration

Consistency with regard to TDMS means that customers can

reproduce and continue business processes that are
included in the selected period of time.

Numerous business processes require the availability of

related information like sales and distribution documents
for material documents that are exterior to the chosen
selection date. TDMS identifies and transfers them.

Highlights for the achievement of consistency by using

TDMS for building up non-production systems are sales and
HIGHLIGHTS distribution documents, sales and distribution chains,
purchasing documents, manufactoring orders, process
relations and status objects.

Consistency of business processes within a selected period of time

is achieved by transferring dependent objects as well.
Achievement of Consistency

Invoice Invoice … D Document Flow


Delivery… Delivery …


Order …

Maximum five steps in the document flow are processed for tracing dependencies
of objects
System setup

Initial Setup phase only once:

Productive system 1. Customize TDMS Non-productive systems

TDMS 3. Client
4. Test data data deletion
2. Analyze data migration

Refresh multiple times:

Productive system Non-productive systems

2. Client data
3. Test data
1. Analyze data migration
User Interface guides through the configuration
Migration Strategies: Different source systems

Production System with closed Database

Plus: consistency
Minus: downtime required

Production System with open Database

Plus: no downtime required
Minus: inconsistencies

Snapshot of Production Storage

Plus: consistency, no downtime required
Minus: additional hardware, additional license fees for snapshot solution

Copy of Production System

Plus: consistency, no downtime required
Minus: additional hardware cost

Quality Assurance System

Plus: consistency
Minus: Downtime required
Technology / Architecture – “Snapshot/Cloning”

Prod Prod’ TDMS Target


write Snapshot

Everybody wants to save money.
Reduce your operational and infrastructure
TDMS reduces the overall storage usage

Example of a three system landscape

Current: Copy of Production Future: Use of SAP TDMS

2500 2500

2000 2000

1500 1500

1000 1000

500 500

0 0
Year 1 Year 2 Year 3 Year 4 Year 1 Year 2 Year 3 Year 4


Storage usage drives the Infrastructure Costs

Cost drivers that depend on the database size:

Hard disks
Sizing of RAID or Storage System
Sizing of database server (CPU, Memory)
Archive media for database backups (Tapes, disks, …)
Hardware Service and Support fees
Exchange of defective hard disks and archive media
Administration effort
Maintenance windows
Server center (power, cooling, space, …)

TDMS can save you money

If you want to compute the return-on-investment of TDMS consider

the following savings with TDMS:

Less infrastructure costs

Less effort for providing current test data

Shorter development cycles, less transports

Less malfunctions and downtime in production due to better

quality of custom developments based on availability of current test
Success at Our Customers

“ Thanks to SAP Test Data Migration Server we

were 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
In a Nutshell:
Facts, Figures, and Roadmap of TDMS
Facts and Figures

System Recommendation
– SAP WebAS 6.20, 6.40 or 7.00
– Minimum 4000 SAPS (20 GB hard drive)

Supported Releases*
– SAP R/3 4.6C
– SAP R/3 4.7
– SAP ERP 2004 (ECC 5.0)
– SAP ERP 6.0 (ECC 6.0)
(* including all industry solutions)
– Price is dependent on size of production database
– License covers one production system and n non-
production systems
Knowledge Transfer/Training
– TZTDM3 (offered by SAP Education)

– Implementation Services offered by SAP Consulting

Service and Support

– SAP Standard and Premium Maintenance
Implementation Services by SAP Consulting

Base Offering – Initial Set Up

Deliverable Fully functional non-production system

Project Scope 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
Know-how transfer to enable customer to set up and refresh their
non-production system with SAP Test Data Migration Server
Duration 12 consulting days
Pricing Fixed price

Expert Offering – Custom-Specific Adaptations

Deliverable Custom-specific functional enhancement (e.g. data scrambling,
customer-specific tables, conceptual design etc.)
Project Scope Scoping Workshop: Workshop with customer (on-site) to analyze
and validate custom-specific demand and define project scope
Duration/ Duration and price depending on scope
SAP TDMS Roadmap 2007+

TDMS 2005 TDMS 2006 TDMS 3.0 Feature Pack

• Two scenarios: • Enhanced UI • HR-specific features • SRM solution

• TDMDC • Support of ERP 6.0 • BW solution • SCM solution
• TDTIM (ECC6.0) • CRM solution • Extended business
• Additional scenarios: • Business process library process library
• Shell Creation • Streamlined UI
• TDTCC • Performance improvements
• TDMS Workbench
• Data scrambling
• Custom scenarios

April ’06 April ’07 April ’08 April ’09

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 TDMS – Customer Expectations/Vision

Production Non-Production
Landscape Solution Manager Landscape




45 11 October 2007 HP Software - Change and Configuration Center