Automation of homogeneous SAP system copies
Multicloud: the systems involved with different hyperscalers
Users do not have to deal with individual tables, but can access a database of business entities. This means that they do not select tables, but business objects such as employees or documents. To do this, however, the tools must contain the object dependencies for SAP's complex data model. Even companies that offer the setup of test systems as a service rarely do this for any SAP dataset. In addition, users can define objects themselves to accommodate customizing and in-house developments.
Strategy as of NetWeaver 2007: Prerequisite: in the case of a Unicode conversion, conversion must be performed during export. If the target database can be built with unsorted unloaded data, all packages are automatically unloaded unsorted. R3load ensures that tables that must always be unloaded sorted are unloaded sorted.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Differentiation between homogeneous and heterogeneous SAP system copy
An alternative to this is a refresh using a client copy. The test environment will then be missing audit documents, among other things, but the development objects will remain untouched. The client copy only works from a running SAP system, but it burdens the system with database queries and transfers data more slowly than a system copy. The affected client is not available during the copy process. Since there are no options within the client to select what all should be copied, the runtime is often unacceptable.
The maturity and performance of automation tools for SAP system copying have evolved over a period of more than 15 years. The first tools for SAP system copy creation came from the mainframe environment.
If you have used "Shortcut for SAP Systems" to save system-specific tables before the system refresh, several manual steps can be omitted - the data can be restored by restoring the data saved before the system copy.
SAPinst/R3load - SAP standard method for ABAP systems - as of SAP Web AS Release 6.10 - OS and DB independent - for homogeneous and heterogeneous copies - for Unicode conversions.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
In connection with Unicode must be differentiated between the system copy of a Unicode system and the Unicode conversion.