Skip to Content

Definition of TDMS

Due to the limitations of available tools, most companies simply create a complete copy of the productive system,  including the entire data repository and all administrative settings whether or not this information is required for testing purposes. This method duplicates the productive environment, so it’s both time-consuming and expensive in terms of infrastructure resources. Your nonproduction environments like development, testing, and training require specific data. SAP Test Data Migration Server addresses this need by allowing you to select just the amount of data you need.

SAP Test Data Migration Server uses rules to create an extract of your data that is approximately 30% the size of the complete data set, but still contains exactly the data that is necessary to keep the business objects and processes consistent. You can reduce data sets in several ways. You can create a system shell that contains only cross-client data and client-specific user and address data, but nothing else. You can set up a system that contains only master data and customizing information. Or you can create a nonproduction system that contains master data, customizing information,

and application data starting with a defined from date. In this last scenario, some essential data may fall outside of the defined time period, but the nonproduction system still requires it. To handle this situation, SAP Test Data Migration Server, configured and implemented on systems running the SAP ERP application, includes rules that logically link data, ensuring that all relevant information is transferred and that the consistency of the involved business processes and data is maintained even beyond the defined time period. You can also reduce data sets based on organizational structure,

such as company code or plant. And with the workbench, you can create completely new ways to reduce data sets or custom scrambling routines for sensitive data.

With SAP TDMS you can:

·         Reduce data volume

·         Simulate production environment

·         Automate system refreshes

·         Selectively refresh individual clients

·         Extract data based on business objects or organizational units/timeslice

·         Scramble sensitive data

Contents of Document

The contents of the document explains in full how to create a new system using TDMS Shell Creation.

Checklist

Description

Source

Target

DDIC Client 000

Server Name

Root

Transport #

SMIGR_CREATE _DDL

SOFTWARE

TDMS 4.0

TDMS 4.0 Notes

Post Activities

The following command creates control and template files that will be adapted/modified in the shell package by TDMS. This will run for some minutes

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPGCapture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

The script starts the migration monitor and runs the export. Depending of the speed and load of the source system this can several hours. Note: If you do the export on a running system make sure no TMS imports are being imported that contain DDIC changes. Otherwise you may have trouble later when running a TDTIM package because of different DDIC structures. At best don’t do any imports at all as long as the export is running or even better stop the system.

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

Capture.JPG

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Billy Warring

    Thank you for this detailed doco, I was going to start working on a Shell creation for a second landscape; saved me one very large nightmare with 6 systems (3 Dev/3 QAs).  While I think I will have to do this one day when the DBs become larger in size, but as we can afford the space now I will look into deleting the client specific data and time slice in the last month’s worth.  😀

    (0) 
  2. Vicky Dev

    Its an excellent doc. Marius, are you accessing your email. I have sent you an email and also a linkedin msg. not sure if you got a chance to go through, but I would love to be in touch with you, to seek your help further in my work, ofcourse only if you are available to share your knowledge.

    (0) 
  3. D I

    This is a very well laid out guide with screenshots.   Do these steps still apply in current patch level (DMIS SP11/DMIS_CNT SP11)?  I ask because in reading the current TDMS guide, I don’t see any information in it related to many of the steps outlined here.  We are new to this, so I’m trying to do our first shell system creation and have been getting hung up at various points.  If these steps are appropriate to Sp11, I’ll be more than happy to proceed with them.
     

    (0) 

Leave a Reply