Source System connection tables

Table T000

BW sourcesystem connection is working with the logical systemname.

 A connection between two systems with the same logical systemname will not work.

Table RSBASIDOC

Includes all connection between BW and a sourcesystem. It is not recommended to change the table manually. The important fields are the following 

SLOGSYS = logical sytemname of the sending system according to table T000

RLOGSYS = logical systemname of the receiving system according to table T000

Remark: for the myself connection SLOGSYS and RLOGSYS are the same

OBJSTAT = should be A

BIDOCTYP = generated by system in case you create a connection

TSPREFIX =  those two letters are part of the field BIDOCTYP. The prefix which identifies the sourcesystem connection are used in several sourcesystem dependent objects and therefore it is not recommended to change the entry manually.

SRCTYPE = which kind of sourcesytem

possible types 

Table RSLOGSYSDEST

If you want to use another RFC connection than the logical systemname you can use this table for mapping  

 That means in the example above the RFC connection DEV_RFC will be used for a RFC call to logical system DEV_100.

Table RSLOGSYSMAP

This table is maintained in the target system of a transport and provides a mapping for the transport of source-system-dependent objects in BW systems. It maps the source system of the BW where the transport was created to the source system of the BW where the transport is to be imported. This means that it usually maps the source-system-dependent objects of source-DEV to source-TEST or source-PROD.).

In order to maintain this table: Call transaction RSA1 --> Transport connection --> select button CONVERSION   . Or use the view maintenance  V_RSLOGSYSMAP in transaction sm30.

LOGSYSORG: Sourcesytem of the transport BW source system
LOGSYSNEW: Sourceystem of the transport BW target system
ONLYNEW: only necessary in case you need 7.X for mulitple sourcesystems

Mapping in transport Target BW System