You want to copy a productive SAP solution landscape to create a non-productive system landscape for testing, quality assurance or other purposes. Or you want to copy your productive landscape onto a new productive landscape to change some property of the systems like hardware, operating system or database.
This section describes the specific steps to execute in each phase as given in the Best Practice.
Phase 1: Preliminary Tasks
Step 1.1: Get required documentation
For copying an SAP SCM system landscape you need the following documentation:
The newest version of this SAP or the respective SAP for your current release of SAP SCM
The SAP Best Practice "System Landscape Copy for SAP NetWeaver and mySAP Solutions",
The System Copy Guide for SAP WebAS ("Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Web Application Server") for the underlying WebAS release of your SCM solution
The following SAP
457425 Homogenous liveCache copy using backup/restore
129352 Homogeneous system copy with MaxDB
Refer to www.service.sap.com - alias scm --> mySAP SCM Technology --> Information on SCM 4.1 and prior releases you will find here --> Installation, Upgrade, Migration, System Copy, Client Dependencies
Step 1.2: Determine a clear copy strategy
A specific SCM solution with mySAP SCM may consist of different application components like APO, SNC (former ICH) (since SCM 4.0), EM (since SCM 4.0), F&R (since SCM 4.1) and EWM (since SCM 5.0). These application components use different technical components which are relevant for the system copy procedure.
Technical components which are used by SAP SCM are
SCM server (SAP WebAS 6.xx)
Depending on the overlying application component, the ABAP stack or the ABAP and JAVA stack of SAP WebAS are used. The SCM Server can be copied using a WebAS copy procedure.
The liveCache is usually copied using a database restore method. For heterogeneous system copy, an export of liveCache to the SCM database is applied.
SCM APO Optimizer
The APO Optimizer should be implemented as per the guidelines in the following SAP:
603828 APO 4.0: Importing an optimizer version
703774 SCM 4.1: Importing an APO Optimizer version
IGS und Geocoding
These components are just installed in the target landscape and do not need to be copied since they do not store application data of their own.
An APO solution uses the SCM server (ABAP stack), liveCache and Optimizer (optional).
SNC (former ICH) and EWM use the ABAP stack of an SCM server.
EM and F&R use the ABAP and JAVA stack of an SCM server (WebAS).
Unless you are doing just a refresh of an already existing landscape, the above technical components must be installed and configured in the target landscape according to their usage by the application components.
Usually, the above components have dependencies to other systems or solutions. To get a consistent target landscape, consider copying these components together with the SCM landscape. In that case you also need to execute the copy procedure specific to these components.
Backend System (SAP ERP, SAP R/3 or other)
To retain consistency of backend system and SCM Server, both should be copied together.
One or more OLTP systems can be linked to an SCM system.
In this case you need to consider data consistency between SCM and all connected OLTP systems. You should compile a detailed list of all connected RFC connections and Registered queues for example, R/3, CRM, SCM, BW and not forgetting any third party systems such as Legacy.
Please check whether you have additional dependencies that need to be regarded.
Attention when using data extraction via BW functionality from other systems:
When using data extraction via BW functionality to load data into the SCM system, consider that it may be required to additionally apply the system copy activities for a BW system according to 886102 to the SCM system. Specifically when using DP or SNP, data extraction is commonly used in SCM to load data from a source system, for example from a BW system.
Please note that when applying 886102 to the SCM system, you need to consider your SCM system being the 'BW system' while the source system for the extracts can be a BW system.
Phase 2: Preparations on Target Environment
Step 2.1: Save important information/data of components of the target landscape.
Save especially all SCM related information like logical systems etc. as outlined in the Best Practice.
Phase 3: Preparations on Source Environment
Step 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).
Ensure that all open, pending issues that have been identified in the Core Interface (CIF) queues have been resolved.
Phase 4: Copy Process
Step 4.2: Install SCM components
First start SAPInst to install the SCM system. This process will also start the installation and set up of liveCache in combination with SAP SCM Advanced Planner and Optimizer.
The installation procedure and the post-installation activities for the liveCache are described in the standard R/3 System Installation Guide for APO. This is available at www.service.sap.com/instguides -> mySAP Business Suite Solutions -> mySAP SCM ->
To complete the SAP Optimizer installation you have to perform the Post-Installation Steps as described in the APO Installation Guide above:
Adjustment Procedure for APO Optimizer:
1. Create a user on the SAP SCM server.
2. Make a setup check for the RFC destination
3. Customize the Optimizer destination entries
4. Set Optimizer network properties on the liveCache server
5. Test the Optimizer connections
Testing the Optimizer Server Connection
1. Log on to the SAP SCM application server.
2. Call transaction SM59. The Display and maintain RFC destination screen appears.
3. To display the complete destination list, open the TCP/IP node.
4. Double-clicking your destination . The RFC destination screen appears.
5. To see whether the connection to the server is correct, choose Test connection.
6. Leave the screen.
7. Repeat the test for all remaining Optimizer destinations that have been installed.
Step 6.13: Check and adjust integration to other components
Integrating the Advanced Planner and Optimizer (APO) and CRM
When a sales order is entered in the CRM Online Application, it may be necessary to know whether the products are available and to pass on requirements to materials planning. For this purpose, a product availability check is carried out for the sales order. This function is carried out by the SAP SCM System.
The Integration of CRM and APO-ATP is described in detail in the CRM/APO integration guide in the Installation/Upgrade Guides in the SAP Service Marketplace.
Step 6.15: Check data consistency
1) Check the internal data consistence between liveCache and the APO system.
The internal data consistency (between the APO-DB and the liveCache) can be checked and restored with the help of transaction /sapapo/om17.
2) Check the external data consistence with transaction /sapapo/ccr between APO system and the R/3 system.