Hybrid: for example, the source systems on-premises and the target systems on cloud
The system copy
One to two pre-tests are required, one of which should be performed on the production system. The additional load on the production system caused by the IMIG has been negligible. Split/mirror techniques allow many actions to be moved from the production machine to another machine.
You should also create a delta list for all transports that have not yet reached the production system. Software contained in open transports is lost during the upgrade, which may seem useful for cleaning up the system, but can have dire consequences for development projects. That's why you should take a close look at delta transport lists before proceeding with the upgrade. UC4 Automated System Copy allows you to automate the above steps. If necessary, you can add additional steps without losing testing capabilities.
In terms of its architectural approach, BSC takes standards into account wherever possible. As a result, the automation tool can be installed with minimal effort, fits very well into the respective system landscape and offers a fast ROI.
With TM-TMS, an SAP add-on is offered that largely automates manual user interventions during a system copy and thus relieves the developers/customizing users. Cross-user developments are processed in one package, ensuring consistency. The entire process consists of three areas.
There is a useful product for SAP system copy - "Shortcut for SAP Systems".
When you install the Connector for LaMa, the following SAP Landscape Management operations are enabled in Google Cloud.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
This cannot be done directly in the production system, but must first be extensively tested, which in turn requires data that is as realistic as possible.