In the newly copied systems, subsequent technical actions and post-installation steps must be performed - most importantly to prevent the target environment from interfering with the production systems. This includes changing system connections and other cleanup activities, but also renaming and reconfiguring to meet the requirements of the target landscape. Installation of additional components that are not copied is usually done in this phase as well. Generic 6.1 - Execute follow-up activities on OS and DB level - Please note that during installation of the target system with SWPM.
6.2 - Prevent any unintentional actions on target system - Lock system ( > tp locksys) this can be done before starting the system
- Disable system connections (using a SQL statement RFCOPTIONS of table RFCDES, RFCSYSACL and RFCTRUST)
- Maintain connections ( > SM59, SMT1, SMT2)
6.3 - Start target system 6.4 - Adjust system connections - using a SQL statement RFCOPTIONS of table RFCDES, RFCSYSACL and RFCTRUST
6.5 - Execute follow-up activities from [System Copy Guide] - Set number of background processes to 0
- Restart system
6.6 - Process pending messages Not required if queues were empty in the source system 6.7 - Convert logical system names - Create new logical system name
- Convert Logical System Name (BDLS)
6.8 - Do solution-specific adjustments - Any other product, or customer specific actions (???)
- Delete old logical system names
6.9 - Import saved information from step 2.1 - Import Users (from previous SCC8)
- Adapt TMS
- Check batch jobs (RSBTCTRANS)
- Adapt printers (from earlier step)
- Logon groups
- External Commands
6.10 - Register queues If the message queues were not already enabled during step 6.6, the queues must now be registered to allow message processing in the target environment. - Register inbound and outbound queues, monitor and correct
6.11 - Install new SAP license 6.12 - Install and configure additional components 6.13 - Check and adjust integration to other components 6.14 - Load or initialize data in additional components - SAP Content Server Repositories
6.15 - Check operability and data consistency 6.16 - Release target landscape for operations - You should consider a syncronised release of all systems
- Tp locksys or group unlock of users
BW Specific Phase 6: Final Activities in Target Environment Step 6.4: Correct RFC destinations Delete or modify the RFC destinations that point to the original systems. Ensure that an RFC destination exists with the new logical name (which will be assigned in step 6.7) in every connected BW or SAP source system. Change the hosts in the appropriate RFC destinations so that they refer to the correct system. See Note 524554. Step 6.7: Execute Transaction BDLS if you want to rename a system If you want to rename one or more of the copied systems, execute transaction BDLS both in the client you wish to rename and in all connected SAP source systems. No other activities (for example, execution of Administrator Workbench / Data Warehousing Workbench (RSA1)) can be performed in the system during conversion! Read Notes 121163 and 369758 for details about transaction BDLS. Step 6.8: Perform BW-specific adaptations The following steps are necessary if the logical system name has been changed: Execute the following task on the BW system and the SAP source systems. Reactivate all partner profiles that contain the new logical system name after renaming. Execute transaction WE20 to reactivate the partner profiles. Choose "Partner type LS (logical system)", enter the logical system name of the partner on tab "classification", change the partner status from "I" (inactive) to "A" (active), and save. Execute the following tasks on the BW system: Update logical system descriptions in RSA1. For each SAP source system that was converted using BDLS, change the description to match the new logical system name. Reset generation flag for ODS activation programs. Call transaction RSSGPCLA and highlight program class RSDRO_ACTIVATE. Click #set status# and #OK#. Repeat for program class RSDRO_EXTRACT and RSDRO_UPDATE Not required - If you are using a BW Accelerator, refer to SAP Note 1146983 for further instructions. Execute the following step if the host has been changed: If you are using BI Planning, adjust the server name of the BI Enqueue Server in the administration transaction RSPLSE. For details see Note 996238. Reset RFC destination for process chain transport postprocessing. Use transaction RSTPRFC to correct the host. Step 6.9: Copying BWREQARCH archives In case request information were already archived with BWREQARCH in the original system, then after the copy the archives files must be copied to a place, where they are accessible for the target system. The best solution for this would be an "XCOPY" on OS level. With this action several serious problems can be avoided, such as the problems from the KBA 1812238. Step 6.16: Restart productive operation in the target BW system SAP NetWeaver 7.0: Restart daemons for real-time data acquisition in transaction RSRDA. SAP NetWeaver 7.2: Execute report RS_SYSTEM_SHUTDOWN to restart process chains and real-time data acquisition. This has to be done after unlocking the RFC users and after configuring the number of background work processes. CRM Specific 6.8 - Do solution-specific adjustments - Use the report ZSCAN_LOGSYS to check if there are still tables containing the logical name of the source system. For more information see SAP note 564435.
- Adjust the settings in the tables CRMCONSUM and CRMRFCPAR in the copied connected backend system.
6.9 - Import saved information from step 2.1 - Adjust the connection to backend systems in transaction SMOEAC
- Restore CRM middleware parameters in table SMOFPARSFA
6.14 - Load or initialize data in additional components For ecommerce and mobile scenarios please recheck SAP Note 886104 - System Landscape Copy for SAP CRM APO Specific 6.2 - Prevent accidental start of processes on target system If a homogeneous system copy was performed via the database restore method the liveCache connections in the target system direct to the liveCache of the source system. To prevent that jobs running in the target system change data in the liveCache of the source system you should: - Disable the batch jobs in the target system before starting the target SCM system
- Apply note 1015489 in order to reset the SAP system ID (SID) in liveCache. (The liveCache stores the SID of the application server from which the first call arrives. All subsequent calls are accepted only if they are triggered from the same SAP system, i.e. provide the same SID.)
If SWPM is used to perform a heterogeneous system copy it deletes the liveCache connections during database migration. Therefore, the target system cannot access accidently the source liveCache. Note 1015489 has not to be applied in that case because the SID information is not migrated into the target system via SWPM. 6.3 - Start target system Start the SCM server and the corresponding SAP ERP Backend System in the target environment. Ensure that in the target SCM system no users are logged in, no batch jobs are running or planned and that the CIF queues are stopped, i.e. no application data should be modified. 6.4 - Adjust system connections The following configurations establish communication between the core ERP system and the SCM server, APO liveCache and APO Optimizer. In the new system environment, use transaction SM59 to check the destination entries and maintain them as follows: ERP Connections a) Backend System/Component systems (hostname/Logon data) b) SCM Server (hostname) for each production client Note: If you are going to convert logical system names in step 6.7, the names of the RFC destinations need to be adapted as well (since the SCM communication model relies on identical names). TCP/IP Connections RFC Destination Type T to APO Optimizer: OPTSERVER_CMT01 CTM Optimizer 01 (Capable-To-Match) OPTSERVER_DPS01 DPS Optimizer 01 (Detailed Prod Scheduling) OPTSERVER_SNP01 SNP Optimizer 01 (Supply Network Planning) OPTSERVER_ND101 ND Optimizer 01 (Network Design) OPTSERVER_SEQ01 SEQ Optimizer 01 (Sequencing) OPTSERVER_VRS01 VRS Optimizer 01 (Transportation Planning and Vehicle scheduling) Additionally check and maintain the Gateway destination data within these RFC destinations above. Adapt connections to liveCache (only when using external liveCache): In the target SCM system, establish or change the liveCache connections (table DBCON) via transaction LC10 as follows: a) In the initial screen of the transaction, enter LCA, then choose the key "liveCache:Create/change connection" respectively "Integration" (Ctrl+F4) with newer releases. Enter the name of the liveCache server of the target system there, then save. b) Repeat the same procedure for the liveCache connection LDA, if this connection is set up. (The connection LDA is only required for the APO application ATP.) c) As of SCM 5. 0, repeat the same procedure for the liveCache connection LEA, which is used for the lock server. 6.7 - Convert Logical System Names Transaction BDLS must be run for the following logical system names: In the SAP R/3 backend system: a) Logical system for SCM b) Logical system for OLTP In the SAP SCM system: a) Logical system for SCM b) Logical system for OLTP Transaction BDLS must be started for every client on the backend systems. On the SCM server you can check the logical system names using path SPRO-> IMG-> Basis-> Distribution (ALE)-> Sending and Receiving Systems -> Logical Systems-> Assign Client to Logical Systems Note: After converting logical system names, the names of corresponding RFC destinations need to be adapted as well (since the SCM communication model relies on identical names). 6.8 - Do solution-specific adjustments Before you release the system to the users, it is important to do the following steps. More details on each of these steps are given below. 1) Check, if you need to change the logical system name in /SAPPAPO/ORDMAP to the target system. 2) If you need to rename the user 'SAPR3' to 'SAPEL1' (for example) after you did the Homogeneous liveCache copy please run the steps outlined in point 2 below. 3) Adapt the logical system names in the report variants /SAPAPO/CIFSTOPQUEUES, /SAPAPO/CIFSTARTQUEUES 4) Check variants of BW Reports RSIMPCURR, RSIMPCUST - if required. 5) Maintaining the Business System Group on SAP SCM Server 6) Maintaining the Business System on SAP SCM Server 7) Customizing the Optimizer Destination entries 8) Set SCM Target System on SAP R/3 OLTP System 9) Adapt table CIFRFCDES 10) Perform adaptations for F&R SCM 5. 0 11) For SCM 5. 1, reset the SCM system name in liveCache 12) Run report for additional update after system copy - Adaption of logical system in liveCache table /SAPAPO/ORDMAP:
- As of release SCM 7.0 SP12, SCM 7.01 SP09, SCM 7.02 SP05 and higher:
- Use report /SAPAPO/OM_ORDMAP_CONV_LOGSYS to adapt the logical system.
- Up to release SCM 5.1, SCM 7.0 SP11, SCM 7.01 SP08, SCM 7.02 SP04:
- when using an external liveCache:
- To adapt the liveCache table /sapapo/ordmap, you need to open a command prompt on the liveCache server and start xquery. Alternatively you could use SQL Studio.
Enter: username/password/system name (sapr3/../LC-Target) Command: select LOGSYS, count(*) from "SAPR3"."/SAPAPO/ORDMAP" group by logsys For each LOGSYS that is displayed, the same mapping / changes have to be done as in BDLS. For example <APO-SOURCE>M001 => <APO-TARGET>M001 Command: update "SAPR3"."/SAPAPO/ORDMAP" set logsys='<APOTARGET>M001'where logsys='<APO-SOURCE>M001' This will change the logical system name in /sapapo/ordmap to the target system. - Applicable only if SAP HANA is NOT the APO database:
- If required, and you want to rename the user 'SAPR3' to 'SAPEL1' after you did the Homogeneous liveCache copy, you must complete the following steps:
Stop liveCache in the LC10 transaction; Start liveCache with the command line in sm49, tool 'dbmcli': -d EL1 -n <LC-server> -u control,<control> db_warm run the SQL statement as 'SUPERDBA' user & check that 'SAPEL1' user is listed: select * from domain.users If yes, run the SQL statement in sm49, tool 'dbmcli': -d EL1 -n <LC-server> -u control,<control> -uSQL superdba,admin sql_execute DROP USER SAPEL1 run the SQL statement & check that 'SAPEL1' user is NOT listed: select * from domain.users run the SQL statement in sm49, tool 'dbmcli': -d EL1 -n <LC-server> -u control,<control> -uSQL superdba,admin sql_execute rename user SAPR3 to SAPEL1 (link: http://www.sapdb.org/7.4/htmhelp/48/f0dab7225811d3a97d00a0c9449261/content.htm) run the SQL statement in sm49, tool 'dbmcli': -d EL1 -n <LC-server> -u control,<control> -uSQL sapel1,sap sql_execute select * from domain.users Run the SQL statement as SAPEL1 user: sql_execute select * from tables where owner='SAPEL1' Run the SQL statement as SAPEL1 user: select LOGSYS, count(*) from "SAPEL1"."/SAPAPO/ORDMAP" group by logsys reset the LCA, LDA and LEA connection to the Standard liveCache user SAPEL1 ( pwd 'sap' ) To make sure that the lcinit script works with the correct user 'SAPEL1' you should run the commands to check the liveCache user in the upc container: In a dbmcli session (e.g. in transaction LC10 ) > sql_execute user-type=SAP select user from dual Should return this user. When an error returns ( unkowen user/password ), then no user is set. To set the 'SAPEL1' user run: dbmcli -d EL1 -n <LC-server> -u control,<control> user_sap sapel1,sap (please see the note 616555 for more details ) in a dbmcli session. This sets the new user in the upc container. After that the above command should return sapel1. Restart the liveCache in transaction LC10. - If you use the reports /SAPAPO/RCIFQUEUECHECK,/SAPAPO/RCIFINQUEUECHECK for queue monitoring and reports for stopping or starting of outbound queues and /SAPAPO/CIFSTOPQUEUES, /SAPAPO/CIFSTARTQUEUES it is important that you adapt the logical system names in the report variants.
- If the BW reports RSIMPCURR, RSIMPCUST are used, it is important that you check the variants of these reports.
- SAP SCM Server: Maintaining the Business System Group (BSG).
This step is a prerequisite for the successful integration of a multiple system infrastructure. The BSG is maintained in the Implementation Guide APO - Implementation Guide-> Advanced Planner and Optimizer (APO)-> Basis Settings-> Integration-> Business System Group. Alternatively you can call transaction /SAPAPO/C1 or C2 Check the distribution definitions and BSG assignments: Table /sapapo/cifdistr You can find these via: SPRO -> APO -> Basis Settings -> Integration -> Publication -> Maintain distribution Definition -> Business System Groups -> Maintain ... delete the old entries as required: Do not rename the Business System Group, because, for example, material master-tables are stored with the Name of the BSG. Since the logical systems, which are assigned to the BSG, are changed by BDLS (step 6.7), there is no need to modify the name of the BSG. - SAP SCM Server: Maintaining the 'Business System'
The Business System is defined in IMG: Extended Warehouse Management -> Interfaces -> ERP Integration -> General Settings -> 'Define Own Business System' or 'Define Business System'. Do not rename the Business System, because it is stored in some transaction data like EWM deliveries. There is no report available for a conversion of the transaction data. Since the logical system, which is assigned to the business system, is changed by BDLS (step 6.7), there is no need to modify the Business System name. This restriction is mainly applicable to EWM or SNC. - Customizing the Optimizer Destination Entries:
1. Log on to the SAP SCM server. 2. Call transaction SIMGH. 3. Expand the SAP APO Customizing tree: - APO Implementation Guide-> Advanced Planner and Optimizer (APO)-> Basic Settings-> Optimization -> Basic Functions Then call the function "Maintain Master Data for Optimization Server". Please check and maintain if necessary the Optimization Server Master Data regarding the existing and active RFC destinations (TCP/IP Connections above). - SAP R/3 OLTP System: Set APO Target System
To enable the successful setup of communication between R/3 and APO, the appropriate target system for this data channel must be installed in the definition of the RFC destination. Install a valid operation mode at the same time. For executing that function call transaction CFC1 or call the following CIF menu: For releases 4.6B on: From release 4. 6B, the CIF menu is called up via the SAP menu (SAP Easy Access). Choose SAP Menu-> Logistics-> Central Functions-> Supply Chain Planning Interface-> Core Interface Advanced Planner and Optimizer. Then choose Settings-> Target Systems. The screen Change View "Target Systems and Operation Modes: Overview" appears. Maintain the APO Release. This table controls the downward compatibility of the APO Core Interface. As a result, different SAP APO release levels can be addressed using the R/3 Plug-in version PI 99. For executing that function call transaction NDV2 or choose the following path in the SAP menu: As of Release 4.6B: Logistics-> Central Functions-> Supply Chain Planning Interface-> Core Interface Advanced Planner and Optimizer-> Settings-> APO Releases. Adjust the Advanced Planner and Optimizer R/3 Plugin Check the Advanced Planner and Optimizer R/3 Plugin within the OLTP system and import it if necessary. See the Plug-in documentation in the SAP Service Marketplace at the following address: http://service.sap.com/r3-plug-in. However your Plugin should already be installed in the system after the copy. - If logical system names were converted in step 6.7 and the names of RFC destinations had been changed, you may also need to change RFC destinations that are maintained for specific applications in table CIFRFCDES.
In SAP R/3, use transaction CFC7. In SCM, use transaction SM30 to maintain the view /SAPAPO/V_CIFRDS. - For an F&R SCM 5.0 system, follow the actions outlined in SAP note 862955.
- Relevant only for homogeneous system copy via restore method and for SCM 5.1 or higher:
See SAP note 1015489 to reset the APO system name in liveCache. - Run the 'report for additional update after system copy' as described in SAP note 1030857. This report will do the following adjustments:
When you call transaction /n/SAPAPO/RRP and select a planning version, product number, and location, you see a link to the old system in the list of product numbers. The external keys of account assignment objects (entries in the SSEXT field of the /SAPAPO/ACCKEY table) still reference the old system. 6.12 - Install and configure additional components - liveCache Start
- when using an external liveCache:
- Start the liveCache via Transaction LC10 in the target system (to do this, press the button "Start liveCache" in the liveCache administration).
After that, both the SCM database and the liveCache in the target system contain the same data as the source system. | 
