SAP system copy On-premises: all involved source/target systems in the company's own data centers

Direkt zum Seiteninhalt
On-premises: all involved source/target systems in the company's own data centers
Copy only specific data
As a rule, the SAP basis has to fulfill: to provide SAP system copies as quickly as possible for the increased usage purposes. The performance of modern tools has developed rapidly. An assessment of the current situation.

Heterogeneous system copy: As the name suggests, the operating system and/or database on the source and target systems are different. One takes thus in the context of the copy a platform change. This procedure is currently gaining in relevance, as it is required for the migration from SAP ERP to S/4HANA. If the current system runs on Windows Server and SQL Server or Oracle, the target system must now run on Linux and SAP Hana.
TM-TMS (Transport Manager)
The solution does not use software agents. The use of standard protocols for the interaction of tool (client/server) and source system and tool with target system has proven itself, exclusively for the purpose of system copy creation. Whereby the use of a single point of management and control has also proven its worth.

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.

With "Shortcut for SAP Systems", tasks in the area of SAP system copying are simplified and can also be automated via the command line interface.

The solution does not use software agents.

Due to the very high repeatability of the nevertheless complex process, it is advisable to automate it to a large extent.
SAP Corner
Zurück zum Seiteninhalt