You want to migrate an SAP NetWeaver BI system from another database platform to IBM DB2 for Linux, UNIX, and Windows (in the following referred to as DB6) or you want to perform a Unicode migration of an SAP NetWeaver BI system running on DB6.
You are not sure whether all relevant corrections for SAP BI migrations to DB6 are implemented in your system.

Other terms

BI system copy migration DB6

Reason and Prerequisites

You want to make sure that all corrections and features relevant for heterogeneous system copies with DB6 as target database platform are available in your system before you start the migration.
Especially you want to ensure that the DB6 DDL for InfoCube, DataStore object and PSA tables and indexes is created correctly by report SMIGR_CREATE_DDL.

Solution

Import the transport attached to this note into your system. The transport contains the program DB6_CHECK_BI_MIGR_NOTES. The program determines the support package level for SAP BASIS and SAP BI installed in your system and scans the correction workbench for implemented SAP Notes. It compares the support package level and the implemented notes against the corrections and features available for SAP BI migrations to DB6.
The output lists the SAP BASIS notes that are missing and that should beimplemented as well as the SAP BI notes that are missing and that should be implemented. The note number, title, the support package in which the note is implemented and the importance of the note is shown.
You should always implement SAP Notes that are displayed with importance “high” or “very high”beforeyou start the migration.
The current version 1.01 of the program handles all relevant SAP Notes that are available until July 2009.

Related:

1. SAP System Installation ProblemsSymptom Customer is having an error or problem when trying...
2. System Landscape Copy for SAP NetWeaver BWSymptom You want to copy a productive SAP solution landscape...

Customer is having an error or problem when trying to install or copy
a SAP system (R/3, NetWeaver, ECC, CRM, BW, APO, EP etc.)

Other terms

R3load, SAPInst, R3SETUP, Installation, System Copy, troubleshooting
Homogeneous, Heterogeneous, OS/DB Migration

Reason and Prerequisites

During SAP System installation or system copy, an error occured and the
process has been interrupted, then the customer wants to open a message
in order to receive support from SAP.
This note describes what input SAP Support needs in order to provide
adequate support for a problem related to installations and and system
copy or migrations.

Solution

Dear Customer,
SAP requires the following information to be able to process your
enquiry efficiently and accurately.
Please check the details of your problem message to ensure they are
comprehensive. The following guidelines will gives you an indication
of what is needed:

=======================================================================

Contents:
1. Type of Installation / System Copy
2. Logs files required
3. Media used
4. Procedure used
5. How to send the required information to SAP
6. Remote connection

=======================================================================

=======================================================================
1. Type of Installation / System Copy
=======================================================================
It’s very important for the troubleshooting that indicate us what kind
of installation you are performing
For example: SAP NetWeaver Web AS, mySAP ECC 5.0, SAP BW 3.5 or an Homogeneous System Copy for SAP R/3 Release 4.6D, etc.
Also please indicate:
o Operating System
o Database Version and patch level
o kernel patch level

=======================================================================
2. Logs files required
=======================================================================
The installation log files are the most important input to detect the
source and reasons of your installation/migration problem, these files
are absolutely required by the SAP Support to process your case.
o For system based on SAP WebAS 6.20 or higher, please provide us
the following files:
- sapinst*.log
- sapinst_dev*.log
- keydb.xml
- control.xml
- summary.html
If following files are present on installation directory, please also send it to us:
- java.log, java*.log
- jload.log, jload.java.log
- callSdmViaSapinst.log, CallSdmViaSapinst*.log
- All the files with structure SAP*.log
For oracle based installations:
- ora*.log, ora_sql_results.log
- Save the information present on the log window (view log button)
into a text file
If the error should be in the R3load import phase of theinstallation, please add the following logfiles as well:
- all .log files , i.e. SAPAPPL0.log
- all .TSK files, i.e. SAPAPPL0.TSK
o As of installation release NW 7.00 SR3 sapinst offers to
automatically create an archive SUPPORT.SAR when it aborts.
Please attach this file to the message as it includes all important logfiles.
If the file should be too large to attach you may split it up into smaller files or you may ask the message processor to create an upload link for you (SAPMATS).
o For system based on SAP Release 4.6D or lower releases (3.x or 4.x)
please read the SAP Note 331082 and provide us all the required log
files.
o If the source/target operating system is Linux, we will require the
output forSAPSYSINFOscript as per SAP Note 618104
=======================================================================
3. Media used
=======================================================================
If you’re using a CD or DVD, please indicate the Mat.Number, otherwise
indicate the SAR/CAR file and the location from where you obtain it.
=======================================================================
4. Procedure used
=======================================================================
Some installations are performed using special procedures, we need to
know the guide and/or SAP Notes used during your installation in order
to follow up the exact procedure that you’re doing.
Please indicate also what attempts you have made to correct the problem
and which SAP Notes have consulted.
=======================================================================
5. How to send the required information to SAP
=======================================================================
Once you have ALL the mentioned files,please compress them using SAPCAR or WINZIP, afterwards select one of follwing options to send it to SAP:
- As Attachment (recommended) : the procedure to attach any file to customer messages is mentioned on SAP Note 541726
- Via FTP to SAPServX : if you have access to the SAPServX you can upload the file as indicated on SAP Note 40024
- Ask to SAP Support for a SAPMats container to send the files, in SAP Note 560499 you will find your local support office phone number, please contact us.

=======================================================================
6. Remote Connection
=======================================================================
During the message processing a remote connection to the affected server could be required by SAP. Please establish a remote connection and if required, open it, saving the logon data in the secure area as indicated in SAP Note 508140
Q: What kind of remote connection is required ?
A: For Unix-based systems a Telnet or ssh connection is required. You
can set up the telnet connection following SAP Note 37001. For ssh connections please refer to note # 1275351.
For Windows-based systems you can set up one of follwing sessions:
- Windows Terminal Server (recommended) (see SAP Note 605795)
- Netviewer (see SAP Note 1036616)
- PcAnywhere (see SAP Note 100740)
- Citrix (see SAP Note 701588)
- NetMeeting (see SAP Note 356635)
If it should be that you want SAP Support to reproduce an issue by runnning ’sapinst’ directly, it is also possible to set up an SAPINST GUI connection as per note # 707848.
=======================================================================
This valuable information will allow SAP Active Global Support to process your message efficiently and provide adequate support for the problem that you’re facing.
Thanks in advance for your collaboration in this matter

Related:

1. DB6: Check notes needed for SAP BI system copy to Db6Symptom You want to migrate an SAP NetWeaver BI system...
2. System Landscape Copy for SAP NetWeaver BWSymptom You want to copy a productive SAP solution landscape...

You want to copy a productive SAP solution landscape to create a non-productive system landscape for testing, quality assurance or other purposes. This copy scenario is referred to as “PRD to NPS”. Or you want to copy your productive landscape to a new productive landscape to change some property of the systems, like hardware, operating system or database. This copy scenario is referred to as “PRD to PRD”.
Since an SAP solution landscape often consists of multiple components that may or may not be based on NetWeaver, additional component-specific steps that are not described in the general System Copy Guide for SAP Web AS (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Web Application Server (ABAP or JAVA)) are required..
You can subscribe to this Note by adding an e-mail address to your profile. Go to -> http://service.sap.com -> MyProfile (in the header)
-> My personal data -> e-mail. To subscribe to this Note, click on the Subscribe link in the top line of the display. If the Note is changed, you will get an e-mail notification.

Other terms

System Copy, System Refresh, SAP BW

Reason and Prerequisites

In case you are still in the process of defining your SAP BW system landscape, please read note 184447 and its attachements first, which will give you background information on logical system naming in BW landscapes.
The common procedure for the system copy of an SAP Solution landscape is described in the SAP Best Practice “SAP System Landscape Copy for SAP NetWeaver and SAP Solutions”. Please see SAP Note 885343 for more information on that document.
This Note contains supplemental information for copying SAP BW 2.x, 3.x and SAP NetWeaver BW 7.x (formerly known as SAP NetWeaver BI). BW is used as an umbrella term for SAP BW and SAP NetWeaver BW. NetWeaver AS (application server) is used as an umbrella term for Web AS and NetWeaver AS.
The Best Practice document and this Note have a common structure. The procedure described in the Best Practice is divided into several phases and steps that need to be executed for the system copy. This Note only lists the steps of the main document requiring BW-specific information and leaves out the steps that do not need additional actions in a BW system.
When copying an SAP BW system or another SAP solution connected to the BW system, you should work in parallel with the Best Practice and this Note to perform the required system copy steps.
Phase 1: Preliminary Tasks
The Solution part of this Note provides BW-specific enhancements to the steps 1.1 and 1.2. The latter step describes 10 copy scenarios, from which you should choose the one closest to your scenario.Phase 2: Preparations in Target Environment
Only 1 of the 10 copy scenarios requires BW-specific preparations in the target environment before the copy.Phase 3: Preparations in Source (Original) Environment
No BW-specific preparations are required in the source (original) environment before the copy.Phase 4: Copy Process
No BW-specific action is required.Phase 5: Final Activities in Source (Original) Environment
No final BW-specific activities are required in the source (original) environment after the copy.Phase 6: Final Activities in Target Environment
All 10 copy scenarios require final BW-specific activities in the target environment after the copy.

Note: In contrast to the Best Practice, this Note uses the term “source system” for the systems that load data to a BW system. The term “original system” is used for the system that is the source of the database copy.

Solution

This section describes the specific steps to be executed in each phase as given in the Best Practice.
Phase 1: Preliminary Tasks
Step 1.1: Get required documentation
To copy an SAP BW system landscape, you need the following documentation:
Newest version of this SAP NoteSAP Best Practice “System Landscape Copy for SAP NetWeaver and SAP Solutions”, see SAP Note 885343.System Copy Guide for SAP Systems Based on SAP NetWeaver 7.x or the System Copy Guide for SAP Web AS (”Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Web Application Server”) for the underlying Web AS release of your BW 2.x or 3.x systemThe following additional SAP Notes:121163 BDLS: Converting logical system names369758 BDLS: New functionality and better performance524554 Storing destinations in the BW environment184447 Building a BW-system landscapeFor Netweaver 7.0 (2004s) BI systems:961551 70SP09: BDLS: DTPs are not converted929045 Correction: No PSA-userobj conversion in BDLS931029 Transformations are not taken into account (BDLS)981248 Correction: Backup for system copy only for old objects1000062 70SP13: Conversion of the logical system name1048947 Corr:Source syst names,pseudo D versions for transformations1055483 Renaming system in RDA tables (BDLS)1059278 70SP15: Error in transaction BDLS1070378 Correction: Hard-coded source system in DataSource program1097357 7.0 Support Package 16: Transaction BDLS terminates1107155 70SP17: Transport after system copy1122853 P17: BDLS does not convert staus manager tables1135964 70SP17: BDLS with transport connection1139924 BI7.0(SP18): System names converted incorrectly1142908 70SP18: BDLS does not convert pseudo D versions1146596 Correction: DataSources remain after source system deleted1148403 70SP18: BDLS after early replication1149141 70SP18: BDLS: log improvements1156599 Correction: 3.x DataSources are not collected1168471 Correction:Collecting transformations using emulated DS1169659 Correction: Process variants not entered by BDLS1180016 P19:BDLS conversion of PSA text table of status manager1224597 P19:BDLS:DataSource not converted1227247 APD: Analysis processes ignored in transaction BDLS1330317 InfoPackages for DSs missing when collecting for system copyDetails about database-specific preparation and post-processing for heterogeneous system copies can be found in the following SAP Notes:771209 NW04: System copy (supplementary note)777024 BW3.0 and BW3.1 System Copy (supplementary note)

Step 1.2: Define a clear copy strategy

The following components belong to a SAP BW system landscape. Unless you are only refreshing an existing landscape copy, these components must be installed and configured in the target landscape:
BW server (SAP NetWeaver AS9
The BW server can be copied using a NetWeaver AS copy procedure. Alternatively you can reload the required data into the BW system after copying the systems serving as BW data sources.J2EE (as of BW 3.5)

Usually the above components have dependencies on the systems or solutions listed below. To ensure a consistent target landscape, consider copying these components together with the BW landscape. In this case you also need to execute the copy procedure specific to these components.
One or more source systems (SAP systems such as ERP, CRM, SEM, APO, other BW systems, or non-SAP systems) can be linked to a BW system.The BW system can be source system to one or more other systems (i. e. other BW, SEM or APO systems).

Keep data consistency between BW and all connected systems in mind. Check whether there are additional dependencies that need to be taken into consideration.

Copy Scenarios

Several copy scenarios are possible in a BW environment. Find the scenario that is closest to yours in the below list. This scenario specifies which steps need to be executed.
Scenario group A: You want to copy the whole system group, i.e. a BW system and all its connected source systems.
Scenario A1: You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group). You want to replace a productive system group [PRD to PRD].Scenario A2: You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group). You want to create a new non-productive system group or refresh an existing non-productive system group [PRD to NPS, installation or refresh]. If the whole system group is refreshed, the installation and refresh scenario do not differ, since all the systems are overwritten.

Scenario group B: You want to copy the BW system only; the source systems are not copied.
Scenario B1: You want to copy a single BW system of the group; the source system is not copied. You want to replace a productive BW system [PRD to PRD].Scenario B2: You want to copy a single BW system of the group; the source system is not copied. You want to create a new non-productive copy [PRD to NPS, installation].Scenario B3: You want to copy a single BW system of the group; the source system is not copied. You want to refresh an existing non-productive BW system by copying the source-system-independent objects from the productive BW system [PRD to NPS, refresh].Scenario B4: You want to copy a single BW client of the group; the source system is not copied. You want to create a new non-productive client [PRD to NPS, installation, client].

Scenario group C: You want to copy the source system only; the BW system is not copied.
Scenario C1: You want to copy a single source system of a BW system; the BW system is not copied. You want to replace a productive source system of a BW system [PRD to PRD].Scenario C2: You want to copy a single source system of a BW system; the BW system is not copied. You want to create a new non-productive source system (of an existing non-productive BW system) by copying the productive source system [PRD to NPS, installation].Scenario C3: You want to copy a single source system of a BW system; the BW system is not copied. You want to refresh an existing non-productive source system (of a non-productive BW system) by copying the productive source system [PRD to NPS, refresh].Scenario C4: You want to copy a single source system client of a BW system; the BW system is not copied. You want to create a new non-productive source system client (of an existing non-productive BW system) [PRD to NPS, installation, client] or refresh an existing source system client [PRD to NPS, refresh, client].

In the following descriptions, look for the copy phases that are valid for your scenario.
=====================================================================
Scenario A1
You want to copy the entire system infrastructure connected by the BW source system connections (the entire system group). You want to replace a productive system group [PRD to PRD].
Phase 3: Preparations in Source (Original) Environment
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 BCTRANS1.
Phase 6: Final Activities in Target Environment
Step 6.4: Correct RFC destinations
Modify the RFC destinations. Change the hosts in the appropriate RFC destinations so that they refer to the correct system. See Note 524554.
Since SAP does not support the renaming of productive systems, step 6.7 “Execute Transaction BDLS if you want to rename a system” is omitted here.
Step 6.8: Perform BW-specific adaptations
The following steps are necessary when 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.If you are using a BW Accelerator, refer to SAP Note 1146983 for further instructions.

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.
=====================================================================
Scenario A2
You want to copy the entire system infrastructure connected by the BW source system connections (the entire system group). You want to create a new non-productive system group or refresh an existing non-productive system group [PRD to NPS, installation or refresh]. If the whole system group is refreshed, the installation and refresh scenario do not differ since all systems are overwritten.
Phase 3: Preparations in Source (Original) Environment
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 BCTRANS1.
Phase 5: Final Activities in Source (Original) Environment
Step 5.4: Restart productive operation in the original 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 but it should be done before restarting and enabling the other background jobs, e.g. by executing report BCTRANS2.
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_UPDATEIf 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.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.
=====================================================================
Scenario B1
You want to copy a single BW system of the group; the source system is not copied. You want to replace a productive BW system [PRD to PRD].
Phase 3: Preparations in Source (Original) Environment
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 BCTRANS1.
Phase 6: Final Activities in Target Environment
Step 6.4: Correct RFC destinations
Modify the RFC destinations. Change the hosts in the appropriate RFC destinations so that they refer to the correct system. See Note 524554.
Since SAP does not support the renaming of productive systems, step 6.7 “Execute Transaction BDLS if you want to rename a system” is omitted here.
Step 6.8: Perform BW-specific adaptations
The following steps are necessary if the host has been changed:
Adjust the table RSLOGSYSDEST for the RFC destinations of the SAP source systems and the myself system. This table contains the relationship between the logical system names and RFC destinations.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.If you are using a BW Accelerator, refer to SAP Note 1146983 for further instructions.

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.
=====================================================================
Scenario B2
You want to copy a single BW system of the group; the source system is not copied. You want to create a new non-productive copy [PRD to NPS, installation].
Phase 3: Preparations in Source (Original) Environment
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 BCTRANS1.
Phase 5: Final Activities in Source (Original) Environment
Step 5.4: Restart productive operation in the original 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 but it should be done before restarting and enabling the other background jobs, e.g. by executing report BCTRANS2.
Phase 6: Final Activities in Target Environment
Step 6.4: Delete source system assignments in the target BW after the copy
Directly after the copy, there is a connection between the target BW system and the source systems of the original BW system. Delete the source system connections of the target BW system without changing the source system connections in the original SAP source system.
In the target BW, change the contents of the “target host” field in all RFC destinations for SAP source systems to a non-existent address (transaction SM59). Caution: This step is very important, as otherwise the original source system will be changed!
Delete ALL SAP source systems in the RSA1 source system tree of the target BW system. Caution: This step deletes all transfer rules and PSA tables of these source systems, and the data is lost. A message is generated stating that the source system cannot be accessed (since you deleted the host of the RFC connection). Choose “Ignore”.
Delete all obsolete RFC destinations pointing to the original environment.
Step 6.7: Rename the target BW system and convert the logical system names
If you want to rename the copied system, execute transaction BDLS. 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
Perform the following steps if the logical system name has been changed:
Reset generation flag for ODS activation programs. Call transaction RSSGPCLA and select program class RSDRO_ACTIVATE. Click #set status# and #OK#. Repeat for program class RSDRO_EXTRACT and RSDRO_UPDATE

Perform the following steps if the host has been changed:
Adjust the table RSLOGSYSDEST for the RFC destinations of the SAP source systems and the myself system. This table contains the relationship between the logical system names and RFC destinations.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.If you are using a BW Accelerator, refer to SAP Note 1146983 for further instructions.

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.
=====================================================================
Scenario B3
You want to copy a single BW system of the group; the source system is not copied. You want to refresh an existing non-productive BW system by copying the source-system-independent objects from the productive BW system [PRD to NPS, refresh].
Remark:As a consultant, you may also read note 1333302, which describes a simplified copy scenario for special system landscapes.
Phase 2: Preparations in Target Environment
Step 2.1: Save source-system-dependent objects
Create a special transport with the source-system-dependent objects (transfer structures, InfoPackages, …) in the transport connection of the target BW system to be overwritten (transport collector -> grouping: system copy) for each SAP source system. In the area “Source System Assignments”, select the source systems for which you want to collect the source-system-dependent objects. Select all collected objects, even if some are not selected by default.
Caution: We recommend that you have a look at the object list of the transport to make sure that it contains all necessary objects. If this transport is inconsistent, the source-system-dependent objects are lost when the target BW system is overwritten. Do not forget to release the transport before the copy.
Remark: This transport request can also be created in the copied BW system after replacement by the productive BW (before step 6.4).
If the source system of the productive BW and the source system of the target BW deliver the very same datasources, this does not make a difference. However…
… if the source system of the target BW delivers additional datasources, the corresponding transformations would be lost.
… if the source system of the productive BW delivers additional datasources, this would lead to import errors later.
Step 2.3: Delete source-system-assignments in the target BW system before the copy
In the target BW system to be overwritten, delete all SAP source systems in the Administrator Workbench / Data Warehousing Workbench (RSA1). DO NOT delete the myself system!
This step is necessary to delete all source-system-dependent objects from the source system (the objects of the old source system connection would interfere with the new source system connection, which will be created after the copy).
Phase 3: Preparations in Source (Original) Environment
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 BCTRANS1.
Phase 5: Final Activities in Source (Original) Environment
Step 5.4: Restart productive operation in the original 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 but it should be done before restarting and enabling the other background jobs, e.g. by executing report BCTRANS2.
Phase 6: Final Activities in Target Environment
Step 6.4: Delete source system assignments in the target BW system after the copy
Directly after the copy, there is a connection between the target BW system and the source systems of the original BW system. Delete the source system connections of the target BW system without changing the source system connections in the original SAP source system.
In the target BW system, change the contents of the “target host” field in all RFC destinations for SAP source systems to a non-existent address (transaction SM59). Caution: This step is very important, as otherwise the original source system is changed!
Delete ALL SAP source systems in the RSA1 source system tree of the target BW system. Caution: This step deletes all transfer rules and PSA tables of these source systems, and the data is lost. A message is generated stating that the source system cannot be accessed (since you deleted the host of the RFC connection). Choose “Ignore”.
Delete all obsolete RFC destinations pointing to the original environment.
Step 6.7: Rename the target BW system and convert the logical system names
Assign the name assigned to it before it was overwritten with the productive BW system (logical system name, table T000) to the target BW system. Use transaction BDLS to convert the logical system name in all the relevant tables. 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
Connect the source systems that were connected to the target BW system before it was overwritten. Use the Administrator Workbench / Data Warehousing Workbench (RSA1), right mouse click on Source Systems and choose Create. In NetWeaver 7.x (2004s or higher) systems, do NOT replicate the DataSources.
Perform the following steps if the logical system name has been changed:
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 select program class RSDRO_ACTIVATE. Click #set status# and #OK#. Repeat for program class RSDRO_EXTRACT and RSDRO_UPDATE.

Perform the following steps if the host has been changed:
Adjust the table RSLOGSYSDEST for the RFC destinations of the SAP source systems and the myself system. This table contains the relationship between the logical system names and RFC destinations.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.If you are using a BW Accelerator, refer to SAP Note 1146983 for further instructions.

Step 6.9: Import the transport with the source-system-dependent objects
Import the transport request created before the system copy.
Do not forget to adjust RSLOGSYSMAP. This table is maintained in the target system of a transport and provides a mapping for the transport of source-system-dependent objects in BW systems. This means that it maps the source-system-dependent objects of R/3DEV to R/3PROD.
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.
=====================================================================
Scenario B4
You want to copy a single BW client of the group; the source system is not copied. You want to create a new non-productive client [PRD to NPS, installation, client].
Phase 3: Preparations in Source (Original) Environment
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 BCTRANS1.
Phase 5: Final Activities in Source (Original) Environment
Step 5.4: Restart productive operation in the original 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 but it should be done before restarting and enabling the other background jobs, e.g. by executing report BCTRANS2.
Phase 6: Final Activities in Target Environment
Step 6.7: Rename the target client and convert the logical system names
Assign a new name to the target BW client (logical system name, table T000). Use transaction BDLS to convert the logical system name in all the relevant tables. No other activities (for example, execution of Administrator Workbench / Data Warehousing Workbench (RSA1)) can be performed in the system during conversion!
Ensure that you select the (non-default) option “Conversion of client-specific tables (e.g. after a client copy)” in transaction BDLS. You must not convert client-independent tables under any circumstances! If you cannot select this option, you are using an obsolete version of transaction BDLS. Get the latest patch for the transaction!
Read Notes 121163 and 369758 for details about transaction BDLS.
Step 6.8: Perform BW-specific adaptations
The newly created client is not a BW client, i.e it cannot be used to start the Administrator Workbench / DataWarehousing Workbench (RSA1) and load data. It is not connected to any BW source system and, as a result, no BW-specific activities are necessary in this step.
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.
=====================================================================
Scenario C1
You want to copy a single source system of a BW system; the BW system is not copied. You want to replace a productive source system of a BW system [PRD to PRD].
Phase 6: Final Activities in Target Environment
Step 6.4: Correct RFC destinations
Modify the RFC destinations in the copied source system and all connected BW systems. Change the hosts in the appropriate RFC destinations so that they refer to the correct system. See Note 524554.
Since SAP does not support the renaming of productive systems, step 6.7 “Execute Transaction BDLS if you want to rename a system” is omitted here.
=====================================================================
Scenario C2
You want to copy a single source system of a BW system; the BW system is not copied. You want to create a new non-productive source system (of an existing non-productive BW system) by copying the productive source system [PRD to NPS, installation].
Phase 6: Final Activities in Target Environment
Step 6.4: Delete copied source system assignments
Directly after the copy, there is a connection between the copied SAP source system and the original (productive) BW. Delete the source system connections of the copied SAP source system without changing the source system connections between the original BW system and the SAP source system connection.
Check table RSBASIDOC in the newly copied target SAP source system to determine all existing source system connections.
If the table is empty, you do not have to execute function module RSAP_BIW_DISCONNECTIf entries exist, note down these entries: fields RLOGSYS and SLOGSYS.

Note: Do not delete the RFC destination between the target SAP source system and the productive BW system! The system needs the destination during the deletion to obtain metadata information from the productive BW system (only a read access).
Execute function module RSAP_BIW_DISCONNECT in the copied target SAP source system using the following parameters:
I_BIW_LOGSYS = I_OLTP_LOGSYS = I_FORCE_DELETE = ‘X’

This step deletes all obsolete BW connections. Repeat this step for all entries in table RSBASIDOC.
Caution: DO NOT enter a value in the field “RFC target sys”. This would cause the function module to run in the system specified there!
Step 6.7: Rename the target SAP source system and convert the logical system names
If you want to rename the copied system, execute transaction BDLS. You cannot perform any other activities in the system during conversion!
Read Notes 121163 and 369758 for details about transaction BDLS.
=====================================================================
Scenario C3
You want to copy a single source system of a BW system; the BW system is not copied. You want to refresh an existing non-productive source system (of a non-productive BW system) by copying the productive source system [PRD to NPS, refresh].
Phase 6: Final Activities in Target Environment
Step 6.4: Delete copied source system assignments
Directly after the copy, there is a connection between the copied SAP source system and the original (productive) BW. Delete the source system connections of the copied SAP source system without changing the source system connections between the original BW and SAP source system connection by executing following procedure:
Check table RSBASIDOC in the newly copied target SAP source system to determine all existing source system connections.
If the table is empty, you do not have to execute function module RSAP_BIW_DISCONNECT.If entries exist, note down all these entries: fields RLOGSYS and SLOGSYS.

Note: Do not delete the RFC destination between the target SAP source system and the productive BW system! The system needs the destination during the deletion to obtain metadata information from the productive BW system (only a read access).
Execute function module RSAP_BIW_DISCONNECT in the copied target SAP source system using the following parameters:
I_BIW_LOGSYS = I_OLTP_LOGSYS = I_FORCE_DELETE = ‘X’

This step deletes all obsolete BW connections. Repeat this step for all entries in table RSBASIDOC.
Caution: DO NOT enter a value in the field “RFC target sys”. This would cause the function module to run in the system specified there!
In the copied source system: Delete all obsolete RFC destinations pointing to the original environment.
Step 6.7: Rename the target SAP source system and convert the logical system names
Assign the name assigned to the overwritten SAP source system (logical system name, table T000) to the target SAP source system. Use transaction BDLS to convert the logical system name in all the relevant tables. No other activities 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
Restore the source system connection in the BW system connected to the overwritten SAP source system
Start the Administrator Workbench / Data Warehousing Workbench (RSA1), right mouse click on the source system, and choose Restore.
Repair the delta queue
In the BW system: Execute report RSSM_OLTP_INIT_DELTA_UPDATE for each datasource, which has an active init request. Provide the field ‘ALWAYS’ with value ‘X’.
This will push the init / delta information of the BW into the source system, thus allows to continue loading delta or to do a new init.
=====================================================================
Scenario C4
You want to copy a single source system client of a BW system; the BW system is not copied. You want to create a new non-productive source system client (of an existing non-productive BW system) [PRD to NPS, installation, client] or refresh an existing source system client [PRD to NPS, refresh, client].
Phase 6: Final Activities in Target Environment
Step 6.7: Rename the target SAP source system and convert the logical system names
Assign the name assigned to the overwritten SAP source system client (logical system name, table T000) to the target SAP source system client. If the client created by the copy is a new client, choose a new name. Use transaction BDLS to convert the logical system name in all the relevant tables. No other activities can be performed in the system during conversion.
Ensure that you select the (non-default) option “Conversion of client-specific tables (e.g. after a client copy)” in transaction BDLS. You must not convert client-independent tables under any circumstances! If you cannot select this option, you are using an obsolete version of transaction BDLS. Get the current patch for the transaction!
Read Notes 121163 and 369758 for details about transaction BDLS.

Related:

1. SAPBINews NetWeaver BI 7.00 ABAP Support Package 20Symptom Support Package 20 for BI Release 7.00 Other terms...
2. NW 7.01 SPS 04 Patch 3 note for BI JavaSymptom Support Package 04Patch 3of the BI Java component for...
3. NetWeaver 7.0/7.10: System copy (supplementary note)Symptom This note contains additions to the guidelines. Other terms...
4. BI 7.X precalculation service – First Customer ShipmentSymptom This note is intended to help how to upgrade...
5. BI 7.X precalculation service – SP901Symptom This note is intended to help how to upgrade...
6. SAP System Installation ProblemsSymptom Customer is having an error or problem when trying...
7. NW 7.01 SPS 04 Patch 4 note for BI JavaSymptom Support Package 04Patch 4of the BI Java component for...
8. SAPBINews NW7.0 BI ABAP Support Package 21Symptom Support Package 21 for BI Release 7.00 Other terms...