SAP system copy Easy integration also in the system copy of systems of older releases possible! - SAP Basis

Direkt zum Seiteninhalt
Easy integration also in the system copy of systems of older releases possible!
On-premises: all involved source/target systems in the company's own data centers
Basically, a distinction is made between the initial setup and refresh of a non-productive SAP system. In the past, the cost of a refresh, i.e., updating the environment with new data, often corresponded to the cost of the initial setup. This also restricted the availability of the productive system, which is hardly tolerable for companies that operate internationally and in different time zones.

One of the most common methods of creating an SAP system copy is to use SAP's own tool "BR*Tools". This tool provides the ability to create a backup of the database, which can then be used to restore the system. It can also be used to export certain data from the database and import it into another system.
Re-import backup transports (exports), set up locally in 000 client for isolated systems (sandbox)
After shutting down the target system, the technical system copy for upgrade 1 can be created at the infrastructure level. To automate the creation of the technical system copy for upgrade, HP System Copy can be used for the following steps.

SAP offers its own solution for this: With the Test Data Migration Server (TDMS), individual tables can be selected and written indirectly, via a third SAP system, from the source to the target system via Remote Function Call (RFC). However, the selection of business objects is not possible in the standard system. The tables to be copied can only be determined on the basis of the date. The content restriction applies from a certain point in time. At least the SAP tool can be used to reduce the runtime of an extraction of test data compared to the system copy or client copy.

Use "Shortcut for SAP Systems" to make a required SAP system copy easier and faster.

SAPinst/Jload: - SAP standard method for Java systems - OS and DB independent - for homogeneous and heterogeneous system copies.

Incremental Migration (IMIG): - OS- and DB- independent - for homogeneous and heterogeneous system copies - for Unicode conversions - for ABAP systems as of 4.0B.
Zurück zum Seiteninhalt