Phase 3: Preparations on Source Environment

Perform general   and technical preparations in the source systems in accordance with your   selected copy strategy. The amount of actions required here depends on the   copy scenario chosen. The copy scenario also determines the impact (and most   of all the downtime) imposed on the source landscape.

Generic

3.1 - Prepare   source systems

3.2 - Save   configuration information

Not required but   is always good to have - Prepare SMQR, SMQS, SM59, BD54 as images or text   files.

3.3 - Stop   productive operation in source systems

Applicable for   scenario “Minimum Risk” - Before shutting down the source systems in a later   step, stop any user or batch job activity to allow for the communication   queues to empty and for additional preparations to be taken.

• Locking the production        systems for user access. - tp locksys
• Disconnect all users
• Stopping and disabling all        batch jobs. This can be done using report BTCTRNS1.

3.4 - Complete   message processing in source landscape

Required with SAP   XI/PI/PO for all messages in status “scheduled for outbound processing”

3.5 - Disable   communication between source systems

• You can save screenshots of the transactions SMQR, SMQS, SM59 as images or text files.
• Outbound queues can be        locked by creating a stopmark. This can be done with transaction SMQ1 or report RSTRFCQ1.
• Unregister the outbound destinations
• Lock the inbound queues
• Deregister the inbound queues
• Disable the RFC destinations and connections to other systems
  • To change RFC destinations pointing to other productive systems, use transaction SM59. For example, you can change the host name by adding a string like  syscopy or a prefix like “#”.

3.6 - Shutdown source landscape  (Optional depending   on restore and roll forward method)

Shut down the source systems to provide a stable and consistent state for copying.

3.7 - Backup the source landscape  (Optional depending   on restore and roll forward method)

3.8 - Prepare any other systems outside the source landscape

BW   Specific

Phase 3:   Preparations in Source (Original) Environment

Step 3.2: Empty   the delta queue of the connected SAP source systems

Execute all delta infopackages two times, to clean up the delta queue in the source system.   This is needed, because BDLS cannot rename the still available LUW-s in the   qRFC queue.

Step 3.3: Stop   productive operation in the original BW system

SAP NetWeaver 7.0:   Stop all daemons for real-time data acquisition in transaction RSRDA.

SAP NetWeaver 7.2:   Execute report RS_SYSTEM_SHUTDOWN to stop process chains and real-time data   acquisition.

This has to be done before locking the RFC users and before stopping and disabling the other   background jobs, e.g. by executing report BTCTRNS1.

CRM   Specific

3.6 - Shutdown   source landscape

When shutting down   the source landscape, make sure that also all external CRM landscape   components are shut down. Make sure that e.g. no CRM Internet Sales servers   are running during the copy and no Mobile Client users are trying to connect   to the CRM server.

APO   Specific

3.1 - Prepare   source systems

You should check   the data consistency between APO DB and the liveCache (known as internal   consistency) and the data consistency between the APO DB and the R/3 system   (known as external consistency). Please refer to SAP note 425825 for R/3 and   APO.

Ensure that all   open, pending issues that have been identified in the Core Interface (CIF)   queues have been resolved.

Notes:

Locks all users including NON DIALOG users

When copying a landscape including an SAP XI system, all messages with status scheduled for   outbound processing must be processed before doing the copy!

This step can be   completed using a sql script