Reliable and fast rework after SAP® system copies
Food for thought for another productive system: until when must the system be identical, keyword: transaction log
This means that the time required to create an SAP system copy - be it for providing a system copy for training purposes, be it for testing purposes or whatever - is drastically minimized. Instead of several days, only hours are required for system copying.
Unsorted unloading: - By default, R3load sorts table data by primary key before export. This requires time and resources in the source system. Under certain conditions, this sorting can be omitted.
Save time, money and nerves with "Systemcopy as a Service
In this context, generated jobs adapt to changes, even if, for example, a DB change, a release change or other changes have taken place. Nevertheless, once created copy jobs can be reused, which minimizes the maintenance effort and a certain susceptibility to errors. This is also the case when switching from one Any DB to another or when moving from an Any DB to Hana.
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.
A solution such as "Shortcut for SAP Systems" offers an automatable solution for many of the activities involved in an SAP system copy.
Some copies are short-term (ad hoc) in nature, while others are intended for long-term use.
Additional backup: server profiles, RFC connection passwords.