Downtime
SAP system update and database update
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
Transaction IMIG comes with extensive online documentation. It describes the preparations, the general procedure in the form of a quick guide, the individual steps in detail, typical error situations and the problem-solving procedure.
Easy integration also in the system copy of systems of older releases possible!
Fact: BDLS is a kind of "time eater" for system copies (except when using Hana). An important first step is to integrate the BDLS run into the system copy. Once the copy is effectively through, the BDLS is automatically started.
Often, the development and test systems of an SAP landscape are far removed from the status of the productive systems used on a daily basis: Outdated developments, customizing settings and master data reduce the quality and trustworthiness of test and emergency scenarios. It also becomes increasingly difficult to make reliable statements about the behavior of the production system after changes in customizing.
With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.
In addition, such automation tools are moving even more strongly in the direction of the IT topic of system management.
Large or complex tables with an extremely long runtime can lead to a very long total runtime, even if a separate package has already been defined for the table.