1 Preconditions

1.1 DisclaimerThe following is a special simplified procedure for the system copy scenario B3 of note 886102:Copy a single BW system of the group; the source system is not copied. You want to refresh anexisting non-productive BW system by copying the source-system-independent objects from theproductive BW system [PRD to NPS, refresh].

It can only be applied under the conditions described below, which must be carefully checked. Forthis reason, this procedure is only published for use by experienced consultants. If theconditions are not met, this procedure must not be applied, if not severe problems with theusage of the source system dependent BW objects shall occur in the copied system. Instead,follow the procedure B3 as described in note 886102 itself. SAP rejects any reliability forproblems, which occur if the below procedure is followed even though the conditions are not met.

1.2 CheckIn the following, the original BW system of the copy is assumed to be the productive BW system(PRD), named BWPRD500, the system to be replaced by the copy is the quality BW system(NPS), named BWQAS300.

Compare the field TSPREFIX in table RSBASIDOC of NPS and PRD. Any equivalent SAP orERP source system (including the BW itself) must have the same TSPREFIX in both NPS andPRD. Two source systems A of PRD and B of NPS are equivalent, if the source systemdependent objects, which are assigned to source system A, shall be assigned to source system Bin course of the copy. An “SAP-source system” is a system with SRCTYPE = ‘M’, ‘D’ or ‘3’.

1.3 ExampleNPS:RLOGSYS SLOGSYS TSPREFIX SRCTYPEBWQAS300 R3QCLNT800 NA 3BWQAS300 R3QCLNT600 NB 3BWQAS300 R3QCLNT500 NC 3BWQAS300 BWQAS300 MA MBWQAS300 PC_FILE OA F

PRD:RLOGSYS SLOGSYS TSPREFIX SRCTYPEBWPRD500 R3PCLNT800 NA 3BWPRD500 R3PCLNT600 NC 3BWPRD500 R3PCLNT500 NB 3BWPRD500 BWPRD500 MA MBWPRD500 PC_FILE OB F

Comparison:SRCTYPE SLOGSYS(NPS) SLOGSYS(PRD) TSPREFIX(NPS) TSPREFIX(PRD) result3 R3QCLNT800 R3PCLNT800 NA NA Ok3 R3QCLNT600 R3PCLNT600 NB NC mismatch3 R3QCLNT500 R3PCLNT500 NC NB mismatchM BWQAS300 BWPRD500 MA MA OkF PC_FILE PC_FILE OA OB irrelevant

Because of the mismatch of TSPREFIX of source systems R3QCLNT600 / R3PCLNT600 andR3QCLNT500 / R3PCLNT500, the below procedure could not be applied in this example. Instead,the procedure described in note 886102 must be followed.

If the clients 600 and 500 would not exist in this example, the below procedure could be followed.The PC_FILE is not a SAP source system (SRCTYPE <> ‘M’, ‘D’ or ‘3’), thus the mismatch isirrelevant for this check.

2 Procedure

Perform necessary generic post-system copy activities, i.e. DB SIDrename, TMS configuration (SE06,STMS).

Please refer to existing SAP technical documentation formore information. Some important resources are listed inthe appendix.

1. Log into the SAP BW client in thenewly refreshed SAP BW system.Run transaction BDLS first to convertthe SAP BW myself logical systemname. In our example, BWPRD500is the logical system name of the DBthat was copied, and it is renamed toBWQAS300 (example logical systemnames only). BDLS convertsoccurrences of the value for logicalsystem name in various tables.Accept the other default selections,except de-select “test run” and“check existence…” Please note thatif you have equal logical names forPRD and NPS systems, do notperform this step or the othersfollowing. These procedures are onlyapplicable for cases where the logicalsystem naming convention includesunique names. Cf. note 184447.

2. Again in the SAP BW client of thenewly refreshed SAP BW system, intransaction BLDS, convert the logicalsystem name of the source system.In our example, we convertR3PCLNT800 to R3QCLNT800(again, this is run in the SAP BWsystem, in the SAP BW client).Accept the other default selections,except de-select “test run” and “checkexistence…”

3. In the SAP BW system (BW client), intransaction SM59 create a newinterface destination for the myselfsource system. In our example, theSAP BW QA system’s logical systemname is BWQAS300, and thereforean interface destination BWQAS300 iscreated, with the destination from theprevious myself source system,BWPRD500 as the template. Theinterface destination for BWPRD500is then deleted, in order to avoidconfusion at some later point.

4. In the SAP BW system (SAP BWclient), in transaction SM59 create anew interface destination for thesource system interface destination.In our example, the source system isan SAP R/3 QA system, and thereforean interface destination R3QCLNT800is created, with the destination fromthe previous source systemR3PCLNT800 as the template. Theinterface destination for R3PCLNT800is then deleted, in order to avoidconfusion at some later point. Besure to maintain the logon/securitytab, and you need to know theextraction user and its password forthe source system to which you are(re)connecting.

5. If the source system is an SAP sourcesystem, there is an interfacedestination created during sourcesystem creation for the dialogconnection. In our example, thisdestination is calledR3QCLNT800_DIALOG. In the SAPBW system (SAP BW client), intransaction SM59 create a newinterface destination for the sourcesystem dialog interface destination. Inour example, the source system is aSAP R/3 QA system, and therefore aninterface destinationR3QCLNT800_DIALOG is created,with the destination from the previoussource systemR3PCLNT800_DIALOG as thetemplate. The interface destinationfor R3PCLNT800_DIALOG is thendeleted, in order to avoid confusion atsome later point. Note the specificsettings required in the logon/securitytab (logon screen).

6. In the SAP BW system (SAP BWclient), transaction SE16, maintaintable RSSYSLOGDEST. This tableholds the relationship between sourcesystem logical system name andSM59 interface destination. In ourexample, BWPRD500 is changed toBWQAS300, and R3PCLNT800 ischanged to R3QCLNT800.

7. In the SAP BW system (SAP BWclient), transaction WE20, activate thepartner profiles for the logical systemsfor the SAP BW myself logical and thesource system logical system.Highlight the logical system name,under partner type LS. Go to theclassification tab, and change the “I”to an “A”, to activate the profile, asBDLS deactivated them. In ourexample, the partner profiles forlogical systems R3QCLNT800 andBWQAS300 were activated.

8. In the SAP BW system (SAP BWclient), administrator workbench(RSA1) > Modeling > SourceSystems, highlight, right mouse click(RMC), context menu – chooserename. Rename the text of the BWmyself logical system and the sourcesystem logical system. This is purelya cosmetic change, but again mayhelp to avoid confusion later. To beclear, this refers to the short text labelattached to the technical name in theadmin workbench view of the sourcesystems.

9. In the SAP BW system (SAP BWclient), administrator workbench(RSA1) > modeling > SourceSystems: Highlight the sourcesystem, and from the context menu,choose restore. In our example wewill attempt to restore the connectionto the SAP R/3 QA source systemR3QCLNT800. In order to proceed,you must know the password for boththe extraction user in the sourcesystem and also the equivalent user inthe SAP BW system (system user,like “BWREMOTE” or somethingsimilar). Be ready to log onto theclient for the source systemconnection. IMPORTANT NOTE: thedialog makes an RFC call into thesource system, where you must log inwith a user with admin privileges(basis administrator authorizations),but *note* the client “000” is thedefault! You must enter the specificclient you are (re)connecting as thesource system, overwrite the “000”s!

10. When you log on to the sourcesystem via RFC, there is a dialog thatsays “user already exists”, “continue”,choose “continue”. Next is the dialogfor the RFC destination, choose“check”. Here, make any necessarychange if there is any difference in theclient number for the newly refreshedSAP BW system (than the previousSAP BW system to which this sourcesystem was connected). Testconnection, save, green arrow backcontinues the RFC dialog. This takesyou back to the SAP BW system.There is a dialog that says “ReplicateMetadata?”, choose only activate.Please note in the next step, it isexpected that this will result in atermination with an error.

11. The error that is to be expected, whenmaking the first attempt at(re)connection of the source system.The reason for the failure is that thepartner profiles do not have thecorrect partner profile receiver portdefinition. The initial attempt at(re)connect of the source systemgenerates a new TRFC receiver portfor the source system (in our example,R3QCLNT800), which we can use tofix the configuration of the partnerprofiles for the logical system.

12. In the SAP BW system (SAP BWclient), transaction WE20, againmaintain the partner profiles for thelogical systems, but this time, double-click on the Outbound Parameter“Message Type” RSRQST.

13. In the Outbound Parametersmaintenance screen, under the tabOutbound Parameters, click the dropdown icon to select the TRFC port ofthe source system to which you are(re)connecting. This action does nothave to be performed for the partnerprofile for the SAP BW myself logicalsystem, only for partner profiles ofrelevant source systems.

14. Once again, in the SAP BW system(SAP BW client), administratorworkbench (RSA1) > modeling >Source Systems: Highlight the sourcesystem, and from the context menu,choose restore. Attempt at(re)connection results in a dialog thatsays “Connection cannot be used.”Choose Delete: The text in the dialogis the key “The connection is restoredafter it has been deleted successfully”.After this, the same dialog for RFClogon to the source system client towhich you are connecting must berepeated, with the same dialogs aboutthe user existing and the same checkof the RFC destination once again.This time, when prompted toReplicate Metadata, choose ReplicateAs Well. Please see the previousnotes in step 9 about the default clientin the RFC dialog in the sourcesystem; you must specify the exactclient to which the connection shouldbe established.

15. The connection process should endat “Analyze Application Log”. If youchoose “continue”, the defaults willtake you to the log for the activity.Success in (re)establishing theconnection will result in green lights inthe application log.

16. You are now able to performInfoPackage data loads now for thesource system, and the deltamechanisms should continue withoutinterruption, no re-initializationsrequired. Please note that dataconsistency is not maintained,however – the only way to ensureconsistent data between sourcesystem and SAP BW InfoProviders isto delete data from the InfoProviderand re-initialize delta for theDataSource in question.

3 Appendix: Additional Resources

http://service.sap.com/BW > Services & Implementation > Migration

o On this page there is a link to the latest migration document, as well as aspecial Product Availability Matrix. You can link to a document such as,for example, “Heterogeneous and Homogenous System Copy for SAPSystems Based on SAP Web Application Server ABAP 6.40 SR1”.

http://service.sap.com/osdbmigration (SAP migrations homepage)

http://service.sap.com/instguides > Choose SAP NetWeaver > Release 04 >Installation.

o The example guide listed above is located here as well. Also see SAPNote 771209 “NW04: Homogeneous and Heterogeneous System Copy(supplementary SAP note)“ for any supplements to the guide.

SAP Notes:

Please refer to the note-list within note 886102.