cancel
Showing results for 
Search instead for 
Did you mean: 

Changing a Source System

Former Member
0 Kudos

All,

I have a weird one. I am on BW 3.5. I have a standard landscape - D - Q - P. I do not have a sandbox. My BWD box has for a source system an R/3 Dev box. Recently, the R/3 team created a new client for their development - different than the one that BWD is hooked to. Basis tells me they can make this new client a source system for BWD very easily, but that doesn't help me. All of my transfer rules that touch R/3 point to the old client number. Is there any automated process that will 'redirect' all my transfer rules from the old client to the new one so I don't have to recreate all of them by hand?

Thanks.

Dave

Accepted Solutions (1)

Accepted Solutions (1)

former_member181964
Active Contributor
0 Kudos

Hi,

First you ask ABAPer what is teh new client, I hope for customization they might have created, so actaul data may be posted in your old ECC client, so it this is the case then don't change the source system. FIrst take clarity from ABAPer generaly Data will be there in which client?.

Thanks

Reddy

Former Member
0 Kudos

Data is in the new client.

former_member181964
Active Contributor
0 Kudos

Hi,

in this case you need to rework i.e. DataSource mappings and Inpfopackages ect..

Thanks

Reddy

Former Member
0 Kudos

Hi,

You can try the Tcode BDLS to avoid the manual changes . Before that RFC connection need to be maintained between the new client and BW. Replicate the DataSources in RSA1.Then run the tcode BDLS .Enter the old logical system name and the new logical system name and execute with the first option 'Conversion of Client-dependent and client-indepedent tables. If you get any message saying that 'partner profile deactivated' , then activate all the partner profiles. Finally verify your transfer rules.

Also ,have a look at OSS notes 886102 and it will give all the information.

Hope it solves your issue.

Thanks

Former Member
0 Kudos

I am trying to redirect BW-BI 7 to a different source system R3/ECC client

*Maintained remote RFC to new client

*Ran BDLS with old system as DEV35 and new system as DEV15 and chose client independent and dependent

But in RSA1, I still have dozens of datasources tied to DEV35 instead of DEV15.

I certainly don't/can't go through every one and change the source and it is uncomfortable as it deletes the mappings and on select of source it seems to add them back, but there has to be a better way?

What step am I missing after running BDLS.

I have also looked at Note 886102 and it does not appear to address this scenario.

        • BW 7.00 SUPPORT PACK 20, ABAP AND BASIS SUPPORT PACK 18***

Advise is much appreciated, respect

Lee Lewis

Edited by: Lee Lewis on Dec 30, 2009 9:18 PM

Former Member
0 Kudos

Hi,

Please check below whether you missed any steps.

1 . Assume that DEV35 and DEV15 transports are synchronized

2. Make sure RFC connection between (BW> DEV15 and DEV15> BW) established.

3. Replicate data sources from DEV15 to BW -> Source system via RSA1

4. Make sure all users will be locked out.

5. Make sure there are no active jobs during this activity. (Note: It may take 1hr)

6. Run BDLS transaction (as per OSS notes 121163).

7. Enter old logical system i.e. DEV35 and target logical system i.e. DEV15

8. Choose option 'Client Dependent and Independent table'.

9. De-select *Test run *Check existence.

Execute.

10. If you notice any partner profiles deactivated message at the bottom of BDLS report, reactivate all partner profiles in the SAP BW system.

11. verify source system dependant objects .

12. Data can be extracted by running info packages .

Thanks.

Answers (2)

Answers (2)

Former Member
0 Kudos

hi

I do not agree at all with the previous posts.

Normally you could do this with the assistance of your basis.

Ask them about the possible scenario with a BDLS, you might have some mapping inactive after that but this worth it if you have a lot of dev.

BDLS is a way to switch a source system in BW by converting the logical systems, be careful and aware of such manipulations, your basis before changing a client should have informed you, so work in close collaboration.

bye

Boujema

Former Member
0 Kudos

Hi David,

I have faced a similiar situation in my previous project and we had to do all the mappings and dataflow with the new client of the source system. It is a large chunk of rework. I am afraid there is no other way!

Regards,

VA