SAP system copy Possibility of manual intervention in case of delta import - SAP Basis

Direkt zum Seiteninhalt
Possibility of manual intervention in case of delta import
SAP SYSTEM COPY - in a nutshell
Security-conscious companies usually keep their mission-critical IT infrastructures redundant anyway. Storage systems are usually secured in disk arrays by multi-level raid, spatially separated from each other and networked by a storage area network (SAN). Connected to this are at least two computers, also spatially separated. One of these acts as a backup system.

SAP recommends that you always update enterprise software in your production system using the SAP transport system and never make changes directly in the production system. In addition, SAP suggests that you validate change transports through a QA system that is approximately identical to the production system and has up-to-date transaction data. Outdated data can affect the validity of change transport tests, which can lead to errors and failures in the production system. However, end-user transaction data is received only from the production system. Such data must therefore be passed regularly throughout the SAP transport chain to ensure that your non-production systems have up-to-date and valid transaction data. This can usually be accomplished by passing a system copy of the production system, created for updates, to the QA system. To reduce the number of test cycles, it is also advisable to update your development system occasionally.
Ways of SAP system copy: export / import
The tools we use can be easily operated either in the cloud or on premise. For this, the SAP systems to be copied must allow access at operating system level. The typical cloud infrastructures, such as AWS or Azure, are not a hurdle for this service.

On www.sap-corner.de you will also find useful information about SAP basis.

Especially in complex environments, SAP system copies regularly represent a critical challenge in terms of time and expertise and thus become a real cost factor in the long run. This is because system copies must be scheduled at an early stage, are complex, time-consuming and resource-intensive, require specific knowledge, tie up important employee capacities due to the large number of manual interventions, and are error-prone.

"Shortcut for SAP Systems" can considerably simplify and shorten a number of activities within the scope of a system copy or a system refresh. By using this application in conjunction with the information on system-specific tables from the PCA tool, the system-specific data can be backed up and restored after the system copy / system refresh. As a result, many of the activities mentioned here regarding data backup / restore can be performed much more easily; the creation of screenshots and the subsequent manual restoration of the state documented in this way can then be completely eliminated.

In principle, the task proves to be simple: All files belonging to the clean configuration and implementation of the SAP environment must be transferred from the productive systems to the quality assurance system in the correct order and in the correct directories.

To automate most transactions, UC4 Automated System Copy for SAP can also be used.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
SAP BASIS
Zurück zum Seiteninhalt