Conclusion
TM-TMS (Transport Manager)
Fact: BDLS is a kind of "time eater" for system copies (except when using Hana). An important first step is to integrate the BDLS run into the system copy. Once the copy is effectively through, the BDLS is automatically started.
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
Planning Guide for the Connector for SAP Landscape Management
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.
Quasi tick boxes instead of time-consuming handling of programming lines, so that the use is also possible for less experienced experts who have never or only few SAP system copies created. And this after little system training.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
A non-production SAP system should also have the same repository status as the source system, regardless of the data transfer method chosen for the refresh.
The Cloud Manager feature for Google Cloud supports the following SAP Landscape Management operations at SAP system level or SAP instance level.