Shutting Down the Target System
SAP Landscape Copies
To meet ever-changing business requirements, a production system must be continuously developed and adapted after the initial installation. To do this, you need development, consolidation, and quality assurance (QA) systems that can provide the appropriate updates to the production system as SAP transports.
You can manage your SAP system landscape in Google Cloud with SAP Landscape Management, Enterprise Edition (SAP Landscape Management) by installing the Google Cloud Connector for SAP Landscape Management (Connector for LaMa). Google Cloud provides the Connector for LaMa free of charge. You must purchase all required licenses for SAP Landscape Management from SAP.
Multicloud: the systems involved with different hyperscalers
The steps to be taken before shutting down the target SAP system can be summarized as follows: Well before performing the upgrade, inform the target system users - especially project managers, developers, and testers - about the planned maintenance work via e-mail, SAP system messages, and/or a message at the system logon. Using the SAP transport system requires careful preparation so that software development projects can be completed as far as possible. Shortly before the start of the update, inform users again that maintenance work on the system is imminent and that they should log off from the target system. After logging users off and locking them out, download system-specific content from the target system database for customization (including security settings, Remote Function Call (RFC) targets, and operating modes).
The website www.sap-corner.de offers many useful information about SAP basis.
An alternative to this is a refresh using a client copy. The test environment will then be missing audit documents, among other things, but the development objects will remain untouched. The client copy only works from a running SAP system, but it burdens the system with database queries and transfers data more slowly than a system copy. The affected client is not available during the copy process. Since there are no options within the client to select what all should be copied, the runtime is often unacceptable.
With "Shortcut for SAP Systems", tasks in the area of SAP system copy are simplified and made possible.
Because the reliability is limited by the misuse of the backup system and the storage network is additionally burdened, users should keep the runtime of this refresh variant as short as possible.
However, it is important to regularly schedule and monitor the creation of system copies to ensure that a working copy of the system is available in the event of an emergency.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.