Two BW system and one OLTP system

[Former Member]

Hi All,

I have the following problem. I have 2 BW system that are a copy of each other. So I have BWP and BWP* pointing to the same R/3 source with the same tsprefix 'AB' which is used for example for the names of the transferstructures.

I cannot make a new connection from BWP* to R/3 because in RSBASIDOC an entry already exists with the tsprefix 'AB'. I cannot delete this entry because this tsprefix is used by the BWP system. (I want to change the tsprefix without having to create all the transferrules again).

So my question is how to make a source system assignment in de BWP* to the same R/3 system without losing the original transferstructures and delta administration.

Please advice.

[former_member21257]

Hi,

Unfortunately, since the TSPREFIX is same for both BWP and BWP* to connect to the R/3 system, you need to delete the source system connection and recreate it once again. You cannot have same TSPREFIX for two different BW system connected to the one R/3.

Rgds,

Colum

[Former Member]

But when I delete the source system, I have to recreate all the transfer rules. Isn't there another way to do it. Copy it from the original setup?

Tnx, Carlo

[former_member21257]

Hi,

If a source system connection is deleted, then generally all dependent objects are deleted as well (transfer rules, structures and all content dependent on this source system). However, you can

transport this content from the original system again (and this is the normal way after system copy).

Create a transport request for system copies in the originating system as follows:

1. RSA1 > Transport Connection

2. Button 'Collection mode' set to 'start manual collection'

3. Press 'Source system assignment' button (it's the one left of the

'Request BEx' button > Select the source systems you want to save

the transfer rules for

4. Button 'Grouping' set to 'Save for system copy'

5. At the left border click on 'Object Types' > Extend tree 'Source

system' LSYS > Double click on 'Select objects' > Select the

source systems you want to collect objects for > the source

system is now displayed in the right box

6. Press collecting button ('gather dependent objects') - this may

take a while > Right click on the root of the tree and select >

Transport all below

7. Expand the whole tree and check if there isn't an object which is

locked by an other open transport request (the column 'Transport

request' has to be empty)!

8. Press the transport button => A transport request is created.

Check if the request contains all ISMP and ISTS objects.

9. You can release the request!

NB: make sure you release the request BEFORE deleting the corresponding

source system connection.

Alternatively:

1. save all your transferstuctures/-rules with "save your systemcopy"

2. no RFC-destination is allowed to show to your R/3

3. delete your source system connection to R/3

4. create a new source system connection to R/3

5. import all your saved transferstructures/-rules

6. activate them -> se38 -> RS_TRANSTRU_ACTIVATE_ALL

Rgds,

Colum

[Former Member]

Hi,

If you re-transport the transferstructures than they get the original names. In my opinion the structure names are appended with the tsprefix.

Is that not going to be a problem if you retransport the transferstructures?

Regards, Carlo