Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
SAP system clone and copy
In order to have up-to-date data and exactly the same software versions on an SAP test system for meaningful tests as are active on the production system, the production systems are regularly copied completely to the test system. However, many settings in the test system must be retained, because a test system should not act like a production system and, for example, send documents to customers and suppliers or trigger something in production.
To build a target system that can be used for testing, development and training purposes, there are two different approaches: Users can reinstall an SAP system and import all transports and support packages that have also made it into the production system to date. However, when their number reaches the hundreds and thousands, the effort becomes disproportionately high. In addition, the data still has to be imported from the production system, for example via a client copy.
A note box in which data of all kinds can be quickly filed and retrieved. This is what Scribble Papers promises. At first, the program looks very spartan. But once a small structure is in place, you realise the great flexibility of this little helper.
Purpose of the SAP system copy
Provide your QA, test and training systems with current production data at the push of a button. Including all preparatory and finishing work - Without interfering with or changing your SAP environment - Without time-consuming pre-planning - With minimum lead time - With consistent copy quality.
In terms of its architectural approach, BSC takes standards into account wherever possible. As a result, the automation tool can be installed with minimal effort, fits very well into the respective system landscape and offers a fast ROI.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
Procedure: - Identify the largest or longest running tables in the system that determine the total system copy time - Perform an initial copy of these tables at source system production time - Record the changes to these tables - Copy the delta using RFC, at source system production time - Use the standard procedure to copy all non-IMIG tables (downtime).
On www.sap-corner.de you will also find useful information about SAP basis.
In these cases, a single client or the entire SAP system is duplicated.