Save time, money and nerves with "Systemcopy as a Service
Key solution steps
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
With TM-TMS, an SAP add-on is offered that largely automates manual user interventions during a system copy and thus relieves the developers/customizing users. Cross-user developments are processed in one package, ensuring consistency. The entire process consists of three areas.
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
Test data is important for companies to eliminate risks in ongoing operations and to optimize systems or processes. But collecting this data can be challenging in times of Big Data and increased data protection, as well as due to complex IT structures.
Normally, therefore, the target system is created using a copy of the production system. The advantages here are: After the initial setup, data is already available, and users receive a completely identical test environment. However, the disadvantages of this procedure are the high memory requirements, the lack of anonymization of the data and the long runtime of the copy process.
Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.
If the current system runs on Windows Server and SQL Server or Oracle, the target system must now run on Linux and SAP Hana.
On cloud: all involved source/target systems on hyperscalers such as Microsoft Azure or Amazon Web Services.