Skip to Content
0
Former Member
Oct 03, 2011 at 07:44 AM

Restore BW connection by via R3load

48 Views

Hi,

We regularly refresh our staging (mostly R3) from production which is used as source system in our staging BW system. Prior to the refresh the BW connection is running ok. But every after refresh, I'm getting tired of manually restoring the BW connection (RSA1>Restore - this is based on SAP Note 886102 scenario C3)). I'm planning to automate the process by backing up the tables related to the following before the refresh:

a) RFC connections - we already got this working

b) ALE settings (i.e. partner profiles, ports, idoc types, etc.). So far I have identified EDIMSG, EDIPORT, EDPP1, EDP13, EDP21.

c) BW settings. So far I have identified RSBASIDOC.

I'm going to use R3load to backup/restore the tables.

My question is:

1). Has anyone tried this process before?

2) If yes, are the tables listed above are correct? I did a trace and there are other tables listed but I have to dig thru what those other tables are for - which might take a while, so I'm trying my luck here.

3.) If restoring the tables won't work, can I use RSAP_BIW_CONNECTION instead of RSA1>Restore? We can use startrfc to kickoff the function module as part of our script.

Additional info that might help you understand my landscape:

- we don't run BDLS after the refresh because the logical name of Prod and staging are the same.

- BW system is running on Netweaver 7.0 abap stack only.

Thanks in advance for your help.

Regards,

Pip