Downtime
Scenario with system copies for updating
In order to be able to work with the most up-to-date data possible on the development and quality assurance systems, it is necessary to bring an up-to-date production status onto these systems. This is often done via a complete system copy (production system -> development system, production system -> quality assurance system) and is very error-prone and user-intensive in ad-hoc configuration (especially if each developer/customizing user is responsible for saving the transports and importing them again after the copy). Every SAP system copy then carries the risk of losing the development status achieved and can lead to inconsistencies in programs and customizing, and any damage repair is usually very time-consuming.
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.
The target system
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.
Especially in complex environments, SAP system copies regularly represent a critical challenge in terms of time and expertise and thus become a real cost factor in the long run. This is because system copies must be scheduled at an early stage, are complex, time-consuming and resource-intensive, require specific knowledge, tie up important employee capacities due to the large number of manual interventions, and are error-prone.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
To ensure that these processes run smoothly at all times, adaptations and further developments must be comprehensively tested in a non-production SAP system using current production data.
This means that they do not select tables, but business objects such as employees or documents.