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.
Installation, Planning & Component information (TDMS)
*Setting up the TDMS Server – The standard way of setting up the TDMS server is to install the software on new SAP system. Refer to http://service.sap.com/tdms & download standard Installation manual for TDMS also refer SAP Note 877860 – Installation procedure, which also provide additional information with regards to the installation of TDMS.</p><p>Setting up the Receiver System – For a successful TDMS project or data transfer, the Repositories of the sender system & the receiver system must be absolutely alike. This may be achieved by using a test system that has been created from a recent copy of the production system.</p><p>Preparation of the Receiver Client – TDMS enable you to either use an existing client as the receiver client or create a new client using profile SAP_UCSV (client-dependent customizing, users, authorization profiles & variants). This is necessary because data related to users & variants are not transferred from the sender system to the receiver system, but this data is needed for working with the new client.</p><p> <strong>TDMS components information – </strong>Every system in TDMS project (Central/Control, Receiver & Sender) should have following Add-ons installed and on same patch level. </p><p>Package Description</p><p>DMIS 2006_1_700, DMIS_CNT 2006_1_700, DMIS_EXT 2007_1_700, DMIS_HR 2008_1_700 (DMIS_HR is installed only on HCM systems)</p><p>Preparation</p><ol><li>Create RFC communication or system type users in Central, Receiver & Sender </li><li>Assign necessary roles, authorizations to these RFC users and the dialog users who are involved in the TDMS run as per SAP note 889988.</li><li>Prepare hardware of target system (e.g. sufficient disk space)</li><li>Make sure the system details for the sender, control and receiver systems are readily available (R3 logins, OS logins for <sid>adm and root).</li><li>Create DB statistics in your source & target databases.</li><li>Check the System settings as per SAP note 890797</li><li>Make sure there is enough space available in Table space in the target system</li><li>Make sure Archive mode is switched off before starting the activities in a TDMS package else excessive generation of logs in oraarch directory will make it 100 % full.*</li></ol>