Increasingly, ad hoc requests are coming from IT or SAP Basis to provide an SAP system copy as quickly as possible, for example of an SAP ERP, BW or HCM system. This often leads to special challenges due to a lack of resources or capacities.
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
Copy only specific data
A major risk to the availability of the entire SAP environment arises when system copies are not transferred to the QA system for reasons of time and resources. Development and test work then takes place on a QA system that does not correspond to the production system. The disruption of the production system - sooner or later - is then already pre-programmed.
A note box in which data of all kinds can be quickly filed and retrieved. This is what Scribble Papers promises. At first, the program looks very spartan. But once a small structure is in place, you realise the great flexibility of this little helper.
Regular updating reduces operational risk and improves the quality of the multi-level system landscape. To update the non-productive systems of an SAP landscape, the data must be cloned from the productive system. This is time-consuming and requires very complex rework.
With "Shortcut for SAP Systems" any tables can be saved and restored. This is especially useful in the context of an SAP system copy - quite a few tables are system-specific and must exist unchanged in the system after a system copy.Shortcut for SAP Systems uses R3trans - a utility from SAP that is essentially used in the Transport Management System (TMS) environment. With "Shortcut for SAP Systems" it is now also available outside the TMS and enables completely new and diverse application possibilities. Among others in the environment of a system copy. R3trans works database independent. I.e. even in the case of a system refresh from an SAP system with an Oracle DB to a system with HANA, the backup and restore process works!
These tables are saved and later imported back into the newly built system: TBDLST, TBDLS, RFCDES, RFCATTRIB, RFCCMC, RFCDOC, RFCSYSACL, RFCTRUST, EDP12, EDP13, EDP21, EDIPOI, EDIPO2, EDIPOA, EDIPOD, EDIPOF, EDIPOI, EDIPORT, EDIPOX, EDIPOXH, TBD00T, TBD05, TBD06, TBDBR, TBDBRF, RFCATTRIB, RFCCMC, RFCDES, RFCDOC, RFCSYSACL, RFCTRUST.
In the case of BSC, sophisticated mechanisms make it possible to exclude configuration errors, since relevant parameter settings are made automatically and according to predefined rules.