184322 - Procedure after DB copy of BW source systems

Symptom

CAUTION: THIS NOTE WAS REPLACED. FOR MORE UP-TO-DATE, COMPREHENSIVE INFORMATION, SEE NOTE 886102.


You replaced a source system of a Business Information Warehouse with another system using a database copy or a client copy.
For example: You refreshed the OLTP consolidation system using a copy of the OLTP production system.
You want to restore the BW source system connection that was lost as a result.
See Note 325525. This note helps you choose the correct procedure for your scenario.

Other Terms

Database copy, source system, BW, client copy

Reason and Prerequisites

This note assumes that the connection worked before you copied the system. Overwriting the source system does not affect BW. Therefore, this note does not describe any repairs that you may have to carry out in BW. It assumes that the connection is configured correctly in the BW system.

Solution

Carry out the following steps immediately after the copy:

1. In the source system: Go to Transaction SE16 - table RSBASIDOC.

a) If entries exist:

                       Note down all these entries: fields RLOGSYS and SLOGSYS.
                       Go to Transaction SE37 - function module RSAP_BIW_DISCONNECT - Single Test. Parameter I_BIW_LOGSYS = <RLOGSYS>, I_OLTP_LOGSYS = <SLOGSYS>, I_FORCE_DELETE = 'X'.
                       DO NOT enter a value in the "RFC target sys" field. If you do, this causes the function module to run in the system specified there.
                       Repeat this for all entries in table RSBASIDOC.
                       This step deletes all obsolete BW connections.

b) If no entries exist:

                       Skip step 1.

2. In the source system: Go to Transaction SM30 - table T000. Make sure that the client to be repaired has the logical name that it had before the copy. The BW system identifies the source system by this name.

3. If you renamed the system, execute Transaction BDLS in the source system to reset all relevant tables to the new logical system name. To do this, see Notes 121163 and 369758.

              Check the destinations in all connected BWs as described in Note 524554.

4. For BW as of Release 2.0A:

                       In the Business Information Warehouse: Go to the Administrator Workbench, the source system tree and select the "Restore" function from the context menu of the source system.
                       When you restore the connection, you must ensure that the two relevant systems can be changed.

5. For BW up to Release 1.2B:

a) In the Business Information Warehouse: Go to Transaction SM59 - destination <logical name of the source system>. Take a note of the user who is entered here.

b) In the source system: Go to Transaction SU01. Make sure that the user you just noted down exists and has the S_BI-WX_RFC profile.

c) In the Business Information Warehouse: Go to Transaction SM30 - table T000. Make a note of the logical system of the BW client.

d) In the source system: Go to Transaction SM59 - destination <logical name of BW>. Make sure that this destination exists. Test this by testing both the connection and the authorization.

e) In the Business Information Warehouse: Go to Transaction SE16 - table RSBASIDOC. Find entry SLOGSYS <name of source system (see point 2)>, RLOGSYS <name of BW>. Make a note of the entries of tables BIDOCTYP, SAPREL and TSPREFIX.

f) In the source system: Go to Transaction SE37 - function module RSAP_BIW_CONNECT - Single Test. Parameter:

                       I_LANGU        <language of the destination to BW>
                       I_SLOGSYS      <OLTP Source system (SLOGSYS from RSBASIDOC in BW)>
                       I_LOGSYS       <BW system (RLOGSYS from RSBASIDOC in BW)>
                       I_STEXT        <name of the OLTP system>
                       I_BASIC_IDOC   <BIDOCTYP from RSBASIDOC in BW>
                       I_SAPRL        <SAPREL from RSBASIDOC in BW>
                       I_RESTORE
                       I_TSPREFIX     <TSPREFIX from RSBASIDOC in BW>
                       I_PREFIXE <35 times second byte of TSPREFIX from RSBASIDOC in BW
                                      (Example TSPREFIX = 'BA', then
                                       I_PREFIXE = 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA')>

g) In the BW System: Go to the Administrator Workbench - InfoSource tree. Activate all transfer structures to the source system.

If all these steps were successful, you can load data from the copied system again.

UKRepairs in the Code