BI unknown in source system ?

[Former Member]

Hello,

I have R/3 system which is connected to my BI server

via RFC.

When i go to transaction RSA1 in BI server ,and when i select source systems,but client in that system is in active mode.when i try to activate it ,it gives the following error.

BI unknown in source system

BI IDOC type ZSBB003 is not the same as source system IDOC type

EDI: partner profile not available

Entry in inbound table not found.

Entry in outbound table not found

I have also checked RFC connection using remote login from R/3 to BI and vice-versa it is perfectly fine.

can anyone resolve the above issue?

Regards,

Rachel

[Former Member]

Can you check if the RFC system users have the profiles S_BI-WHM_RFC in BW system & S_BI-WX_RFC in R3 system.

[Former Member]

Hello Rachel,

Could you please let me know on how did you resolve the issue 'BI unknown in source system'?

Thank you,

Nikee

[Former Member]

Hi Nikee,

In my case, the logical system of R/3 system was incorrect. hence I was getting the error BI unknown in source system.

with the help of below forum I was able to chage my logical system name.

**********************************************

Hi Rachel,

BDLS creates an ABAP program SBDLS* which includes all the tables possibly including logical system names as of the domain behind the table fields. This program firstly

lives in runtime only and is checked by syntax checker.

Now, sometimes tables have inconsistencies associated with them and you

will get this dump when a syntax check is performed on them.

So please check this and regenerate the culprit tables.

So please redo the steps for BDLS and check. There are

probably some tables which could be determined by you (syntax

check - in case program has already been saved only)

An easy way to check this is to run RBDLS2LS program (old BDLS) and

afterwards performing a syntax check on generated RBDLS*** (RBDLS<(>

<<)>(>

<<(><<)>)>ClientName>) program.

Known tables which caused such dumps in the past are:

DFKKCOLFILE_P_W

DFKKKO

DFKKMKO

DFKKREP06

DFKKREP06_S

DFKKREP07

DFKKREV06

DFKKREV07

Simply reactivate the tables you find out in SE11.

Another thing which has lead to this dump in the past is

in your R/3-System the value ' x ' is

additionally added to the value of your current release in the basis

release table SVERS.

The table RSBASIDOC takes the release value from the table SVERS.

If you change value 'x' to your release in both tables (SVERS and

RSBASIDOC) and

and activate again your source system connection. This could solve the

dump too.

I hope, this helps-if not, pls open a message with SAP.(component: BC-MID-ALE)

b.rgds, Bernhard