Automation of homogeneous SAP system copies
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
Database: For some databases (MS SQL Server) there is the possibility to copy the database files and reattach them on the target system. For the following SAP installation you only have to specify that no SAP loads should be used, but that the database is already there!
Packages that have not been explicitly assigned a special DDLORA file receive the DDL file specified via the "ddlFile=" parameter. The default is DDLORA.TPL.
Test and training system: data anomyization, migration of master data, migration of user data / passwords
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place. Nevertheless, once created copy jobs can be reused, which minimizes the maintenance effort and a certain susceptibility to errors. This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
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.
An SAP system copy usually includes both the copy of the database and the copy of the file systems that contain the SAP system. There are several ways to create a system copy of an SAP system, depending on the type of database and operating system used.
Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.
In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules.
The process of creating system copies for updates can be broken down into different activities, as shown in Table 1.