SAP SYSTEM COPY - in a nutshell
Solution Description
Regular updating reduces operational risk and improves the quality of the multi-level system landscape. To update the non-productive systems of an SAP landscape, the data must be cloned from the productive system. This is time-consuming and requires very complex rework.
With Automated System Copy for SAP, an SAP system copy can be scheduled and executed in a parallel mode, which has the advantage of reducing manual intervention to a minimum. In addition, daily work can continue as normal. Rehau had already been using the software provider's Business Automation platform for cross-platform scheduling of complex job chains since 2004. The existing installation was expanded to include the module for creating SAP system copies.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
The Refresh
SAP SE is a software company that uses the proprietary programming language ABAP. SAP® landscapes include not only production but also Quality Assurance (QA) systems as well as test and other staging systems. For appropriate and consistent testing and acceptance of changes in programs and processes, SAP recommends the "homogeneous system copy" approach to provide non-production systems with up-to-date data.
The solution does not use software agents. The use of standard protocols for the interaction of tool (client/server) and source system and tool with target system has proven itself, exclusively for the purpose of system copy creation. Whereby the use of a single point of management and control has also proven its worth.
The tool "Shortcut for SAP Systems" is excellently suited to complete an SAP system copy easier and faster.
The groups are defined in the same file where the order of the packages is defined.
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.
For the Unicode conversion of a 4.5 TB system (2.7 TB data) a downtime of 16 hours was achieved (including the follow-up work such as reconfiguration, updating DB statistics, generating reports, creating backups, testing the system).