BDLS in BI System

[Former Member]

Hello Friends,

I have a ECC and BW system landscape.

Previously we ad the following client

ECC-100(PROD)----

---

BIW-200(PROD)

ECC-240,200(QA)-----BIW-200(QA)

The connection between them was working fine.

Recently we did a client copy of out ECC system from Production to QA.

Now in the ECC QA we have only Client 100.So for the QA landscape its

ECC-100(QA) ---BIW-200(QA).

Problem,

In the BW QA the source system was created to the client 240 of the ECC , which is no more.

So for that we ran a BDLS in BW system for the convertion from 240 to 100..

Even after the BDLS run, the Technical name in the RSA1 for this source system has not changes to 100.

Please suggest.

Anthony

[former_member185954 · Accepted solution]

Hello Anthony,

Please carry out activities as described in the following notes:

Note 886102 - System Landscape Copy for SAP NetWeaver BW

Note 184322 - Procedure after DB copy of BW source systems

Please note theat note 886102 is the most recent note and should be referred to, however I have provided the older note to give you an idea of the changes that are done internally after system copy of the source system.

Hope that helps.

Regards,

Siddhesh

[former_member185954 · Accepted solution]

I forgot to mention the scenario that seems to be applicable to your case is C4 in Note 886102 - System Landscape Copy for SAP NetWeaver BW

[Former Member]

Hi Anthony,

You have the source systems created between ur BI QA 200 and ECC QA 240. Upon executing the BDLS in the ECC QA server the source systems in that server would have changed(ECC QA) but not the connectivity.

To establish the connectivity, you need to modify the RFC destination in the BI QA server.

1. Goto RSA1 in ur BI QA Server

2. Drill down the node SAP on the right side pane

3. Right click on the respective source system

4. Select Connection Param.

5. The RFC destination will be opened (Usually the RFC destination will be in the name of the ECC QA logical system.)

6. Goto the Logon data tab and then change the client (from 240 to 100) and the logon details.

7. Test the connection after these changes.

Hope this will resolve ur issue.

Regards,

Varadharajan M