DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
Verification of source system status and infrastructure - analysis of software versions, database disk layout, system status, etc.
SAP software plays a central role in the IT landscape of Rehau, a provider of polymer-based solutions for construction, automotive and industry. Currently, the IT department provides over 120 SAP systems centrally in the sense of "shared service hosting". The IT team must regularly copy the SAP productive environment in order to be able to carry out testing and development work on the "real" system without manipulating the productive systems. Rehau recently opted for the 'Automated System Copy for SAP' solution. The tool from Automic, a specialist in business automation, allows SAP system copies to be created almost fully automatically.
Table splitting reduces the risk of losing a lot of time during export in case of an error. When restarting, the complete table does not have to be exported again, but only a subset. Simultaneous processing of a table by several R3load processes can reduce the total runtime for this table.
Update more efficiently
The task of a system copy created for updates is a carefully integrated system that takes on a specific role in an SAP system landscape. That is why customizing the SAP database of the target system differs significantly from customizing the database of the production system. In a system copy-based update, the database of the target system is completely overwritten with the contents of the production system. Therefore, all SAP-specific customization of the target system must be performed after the update with the system copy. The pre- and post-processing is often performed manually while the target system is running. Specific SAP transactions are used to customize the system. Execution can take a long time and is a source of human error. To automate most transactions, UC4 Automated System Copy for SAP can also be used. Before the update, UC4 Automated System Copy takes care of downloading the required content for the SAP customization from the target system and after the update is complete, uploading the content back to the system.
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).
Tools such as "Shortcut for SAP Systems" supplement missing functions in the area of SAP system copy.
The website www.sap-corner.de offers many useful information about SAP basis.
By automating complex SAP system copies that require a great deal of manual effort, the throughput times and costs of an SAP system copy can be massively reduced.
Unsorted unloading: - By default, R3load sorts table data by primary key before export.