Copy only specific data
Job logic instead of customizing
On the other hand, such a tool must ensure that traceability or transparency is always available. What happens in the smallest detail during an SAP system copy creation must be visible in whatever form in order to be able to track down possible errors, but also, for example, to optimize the actual copying process or to accelerate it even further, for example by using log files and more.
The suite idea has established itself here as well as in many other software areas. And for good reasons. In addition, such automation tools are moving even more strongly in the direction of the IT topic of system management.
DB-specific methods: - for DB-homogeneous system copies - no Unicode conversion possible!
A system copy can be created either with SAP transactions (R3trans, from R4.6C SAPinst) or at file and database level. Costs and effort increase with the size of the system and the requirements for availability and data protection. In addition, administrative rework is often necessary, starting with the system name and extending to printers and interfaces.
With "Shortcut for SAP Systems" you can sustainably relieve your administrators of time-consuming routine activities of an SAP system copy.
Against the background of constantly changing business processes, the SAP production systems that serve as the basis for these processes must also be continuously adapted and further developed.