SAP system clone and copy
Reliable and fast rework after SAP® system copies
For some time now, SAP customers have been supported in system copying by very powerful automation tools that can be used as needed. In addition to this area of activity, additional automation tools are also available, for example up to the creation of sandboxes, which provide valuable services.
By using the automation solution, errors that typically occur with manual process steps - just like additional costs due to repetition - can be avoided. To date, the IT team has created 88 SAP system copies. "If we had wanted to do this with SAP board resources, we would not have been able to pay for it as a medium-sized company," Rudi Scharf knows.
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.
For a long time, manual procedures dominated, supported by SAP (guidelines), in particular by predefined procedures and a large number of checklists. In many places, this was supplemented by scripts created in-house, which, however, only automated partial tasks/processes of an SAP system copy.
"Shortcut for SAP Systems" provides an automated solution for many of the tasks involved in copying SAP systems by enabling the backup and restore of any table.
Rework, a transaction checklist: SU01 Adjust DDIC PW, SM66 Check server instance distribution, SE38 BTCTRNS1 (schedule all jobs out), SM38 Suspend jobs, SICK SAP Consistency check, SM28 Installation rework, SE06 Installastion check, SLICENSE License check, RZ10 Delete profiles, create and import OS level, RZ04, SM63 Create operation modes (optional), SMLG Delete SAP logon groups, SE14 Delete table contents: from system specific tables (emails, monitoring), SE38 RSBTCDEL (delete background jobs), SE16N Match table entries (optional), RZ12 Maintain server groups, SM61 Job server groups, create servers, SM59 Delete RFC connections, , SCC4 / SE03 Edit system: Assign system type, create and name SALE logical system, SCC4 client setting, rename to current SYSNAME, convert BDLS original system, generate SGEN ABAP Load, set up SA36 standard jobs, regenerate STRUST certificates, set/adjust SE61 logon screen, DB02 database connection, maintain PW.
Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.