Showing posts with label RSBASIDOC. Show all posts
Showing posts with label RSBASIDOC. Show all posts

Thursday, May 7, 2015

What systems are connected to my BW?

Recently for purposes of one SAP BW upgrade project I needed to find out what systems are connected into particular BW. Easy way is to run t-code RSA1 and loot at Modeling -> Source systems. Of source I needed to have more technical information about the sources. Also I wanted to have a central source of this information so I dig into the system to find out what table stores this information. It is RSBASIDOC – Assignment of source systems to BIW systems incl. IDoc type. The table as all about source system connections, status of particular connection, what kind of IDOC Basic type is used for the connection, prefix used for particular source system, etc.

Let’s have a closer look at all its fields:

SLOGSYS      log.name of system connected to the particular BW system

RLOGSYS      log. name of receiver; identifies BW system into which SLOGSYS is connected to

OBJSTAT      Object Status; wheatear connection is active (ACT) or inactive (INA)

BIDOCTYP    IDoc Basic type used for the connection

TSIDOC3X    Transfer structure 3.x number state for a source system; not used in BW 7.x

TSPREFIX     Transfer structure prefix for a source system; 2 chars used in field BIDOCTYP; it identifies the source system connection for source system dependent objects

SRCTYPE      Type of the source system: 3 = SAP R/3 from version 3.0D onwards; B= External system, data staging done by BAPI; M = used for connection of BW itself (myBW); D = SAP BW system; F = External system based on File; G = DB Connect type of source system; S = UD Connect type of source system; I = Web Service type of source system

SAPREL        Release of SAP System (version of SAP Basis component)

TSTPNM       User who changed it last

TIMESTMP    Time Stamp of the last change (in format YYYYMMDDhhmmss)

SBWBCRL     Release of SAP Sending System

RBWBCRL     Release of SAP Receiver System


So to answer my question from the title of this blog spot: go to the RSBASIDOC table and look at values of SLOGSYS field.


Monday, June 2, 2014

Logical system name has been changed for this system

This is again very common error very often seen in newly installed or copied BW systems. Similarly as it with “You can only work in client 001” error message.

Issue here is that BW’s myself system is not properly customized. It is within table RSBASIDOC which carries assignment of source systems to BW systems and IDoc types that are used for connection between the  systems.

Here’s full error message:


Logical system name has been changed for this system Message no. R3206

Diagnosis
The logical system name of this system is EH6CLNT800. However, this system was originally created with the logical system name T90CLNT090. It is not permitted to change the logical system name, as connections to other systems will be damaged beyond repair.

System Response
The transaction is canceled.

Procedure
Change the name of the logical system (table T000) for client  back to T90CLNT090. This enables you to continue working with the system.

Note: If you really want to change the logical name, read the information in SAP Note 886102.


To solve this it is necessary to adjust data in table RSBASIDOC. Basically error is triggered by FM RSA_LOGICAL_SYSTEM_BIW_GET. While the FM is checking system type of myself (field SRCTYPE = 'M' in the same table) there was an error.  Logical system name of the system which corresponds to myself in the table RSBASIDOC is not the same as BW logical system in table T100-LOGSYS.

How to correct this:

You can use FM RSAP_BIW_DISCONNECT which removes old/invalid value of myself BW system from the RSBASIDOC table. Afterwards you can use RSAP_BIW_CONNECT to get the table RSBASIDOC populated with proper logical name. If those FM do not help do deletion directly of M entry from the table RSBASIDOC. Then run FM RSA_LOGICAL_SYSTEM_BIW_GET which recreates new/valid entry for the same.