Select and Transfer a Time Slice of Data for Testing with SAP Test Data Migration Server 3.0

  • by Manfred Gonschor, Consultant at ENERGY4U GmbH, Germany
  • January 15, 2009
The new SAP Test Data Migration Server (TDMS) is an automated solution for creating test systems that can be a real alternative to full-system copies. It can pare down the size of your test system in a variety of ways, the most popular of which is to copy only a time slice of your production data to populate your test system. This article gives you an idea of the capabilities of TDMS, provides a detailed walkthrough of how to use it to create a reduced-size test system, describes its technology and process types, and gives you some hints on how to get it running in your landscape. Learn how TDMS’s new technology can save you time, money, and memory in your non-production systems and benefit your organization.
Key Concept

Test Data Migration Server (TDMS) replaces the client-specific data of a client in a non-production system with current test data. For the extraction of new test data from a production system, for example, TDMS uses various rules to lessen the volume of data. This enables you to include, for instance, only the previous three periods of transactional data in the test data refresh. In addition, all cross-client configurations, such as interfaces and repository objects, as well as all user-related data will remain as they are in the non-production system to avoid time-consuming adjustments after a refresh.

Today’s production system databases are growing rapidly — not only in hardware requirements, but also in the creation of non-production systems — as current test data becomes more expensive and technically challenging. Even if you can still perform full-system copies or remote client copies, the manual effort required to refresh such a system, including all of the post-processing steps, demands an easier, more automated solution to create test systems. TDMS addresses exactly these issues. It has become an appealing product for providing current test data in non-production environments.

This article gives you an overview of TDMS, as well as a detailed walkthrough of how to use it to set up a test system with a reduced volume of data. I often receive feedback in training classes and implementation projects that the “getting started” portion of TDMS would be a lot easier if a walkthrough describing the first data transfer with TDMS were available.

As an introduction, I would first like to give you an idea of the capabilities of TDMS and how you might benefit from using it. After that, I’ll describe the technology and the process types of TDMS, as well as give you some hints on how to get TDMS running in your landscape. In the main part of this article, I’ll follow a TDMS instance for a time-based reduction of data volume in the non-production system, the process type chosen for most TDMS data transfers. (This process type transfers customizing, master, and application data; the other available process types are explained in this article, too.) This article is based on TDMS 3.0 Service Pack 8.

Manfred Gonschor

Manfred Gonschor works as a consultant for ENERGY4U GmbH. He graduated from the Berufsakademie Mannheim, Baden-Württemberg, Germany, with studies in business information technologies. He was part of the System Landscape Optimization (SLO) consulting team at SAP Germany from 2005 to 2008 with a focus on SLO Analytic Services and TDMS. In the past few years, Manfred ran numerous TDMS implementation projects and conducted official training classes around the globe.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.