- Open Access
- Authors : Harminder Singh
- Paper ID : IJERTV9IS110245
- Volume & Issue : Volume 09, Issue 11 (November 2020)
- Published (First Online): 03-12-2020
- ISSN (Online) : 2278-0181
- Publisher Name : IJERT
- License: This work is licensed under a Creative Commons Attribution 4.0 International License
SAP Test Data Migration Servers
Harminder Singh SAP Basis Lead/Architect
1340 Noah Rd, North Brunswick NJ-08902, USA
AbstractSAP Test Data Migration Server (TDMS) provide us with the small, easy-to-maintain non-production environment using extracts of business data to minimize infrastructure and maintenance expenses while maximizing the effectiveness and accuracy of your test and training systems. SAP TDMS ensures full data consistency and less transactional data during the execution of the migration projects from the production to non- production system. SAP TDMS provides new migration solution which help with the system refreshes and cover the migration strategy end to end. SAP TDMS is a fast method of data extraction which populates your quality and training systems with real SAP business data. Also, this tool provides the functionality to scramble the sensitive data copied from production.
Have you ever wondered if you could have a tool which could select customized data from your production server for purposes such as testing? The answer to this is SAP's TEST DATA MIGRATION SERVER (TDMS). TDMS operates at
client level and creates non-production clients. The selected data from a client in the sender system is copied to a client in existing non-production system. The idea is not to have the entire system copy, rather have the data which is more critical and required. Approximately 80 % of the data volume of a typical database is contained in less than 10 % of the tables. Transaction data tables are usually the largest tables in the database. Thus, smaller non-production systems with only the required data can be created. Using TDMS you are not only saving the storage space but this can help you to run the queries faster and which can help in the performance of the system with less transactional data.
II. SAP TDMS ARCHITECTURE
A. SAP TDMS LANDSCAPE
The landscape of TDMS involves three different systems- Sender, Receiver and the server on which TDMS is installed. TDMS server has two systems basically one is called as control system and central system. Central system is the system where we perform and setup the receiver system configuration and control system is the triggering and monitoring system for the migration activities to carry out. The receiver system is the non-productive system to which production data is copied with less transactions data and data will be scrambled. SAP best practices says to have three systems on different servers for the better performance. All three system are connected with remote function call. SAP TDMS is a flexible tool which help you to integrate most of the SAP products to copy data from production to non-
production and some of the example are SAP ERP, SAP BW, SAP CRM and SAP MDG etc.
III. SAP TDMS EXECUTION STEPS OR PROCESS FLOW
Before you start learning or understand the process, lets check the DOs and DONTs in TDMS. Make sure the version of source and target system both are on the same version, lets say production system is SAP ERP system and release is ECC EHP7 then we have to make sure target system is on the same release to carry the system refresh. Also make sure the version of DMIS components which brings SAP TDMS functionality in source, target and central system are on same version. Now lets discuss the process flow or how we carry out the extraction of the data. There are three layers or levels of the settings to work in TDMS. These are Project, Sub-project and Package.
Project: A collection of any number of subprojects. Normally the sub-projects which are related in some way are grouped into a project.
Subproject: The combination of the sender client, the receiver client and the RFC connection between them.
Package: A package is created for every transfer. A new package has to be created for every initial setup or refresh, for a given combination of sender and receiver systems. A separate subproject is created for every client whose data is going to be transferred to a non-production environment by means of SAP TDMS. We can create project, subproject and packages in SAP TDMS using transaction TDMS in 4.0 release whereas in version of TDMS 3.0 it is CNV_MBT_TDMS.
Once the package is created a process tree is created which has number of steps involved in it.
Figure1: Diagrammatic view of SAP TDMS architecture.
A. TDMS capabilities and What we can achieve.
With TDMS, there are different ways of selecting data from the production server, these ways or reduction scenarios are called process types.
Few of them are listed below:
SHELL CREATION-TIME-BASED REDUCTION-TIME-BASED REDUCTION AND REDUCTION BY COMPANY CODE-REDUCTION BY DELETION OF ALL CLIENT- DEPENDENT DATA FROM A CLIENT SYSTEM-EXTRACT DATA BASED ON A BUSINESS PROCESS LIBRARY-TRANSFER OF MASTER AND CUSTOMIZING DATA AND MINIMAL TRANSACTION DATAPackage SettingsSystem AnalysisData TransferPost Processing