Source System Activation Error

[Former Member]

Hi,

We Upgraded BW3.1 to BI7.0, we did successfully on Development. but when in QA when I was trying to activate RFC by going to RSA1 and right click and activate it is showing errors like

Source system XXX300 is inactive RSAR 5

BI unknown in source system RSAR 8

BI IDoc type ZSBB025 is not the same as source system IDoc type RSAR 371

The following errors occurred in the source system: RSAR 374

EDI: Partner profile not available E0 332

Entry in inbound table not found E0 414

Entry in outbound table not found E0 400

Entry in outbound table not found E0 400

Am I missing anything ?

Thanks,

Chander

[Former Member]

Chander,

right click on Source System, click on check. you will promt you with error messages. if you click on Question i.e. help icon. it will give you what need to be done.

All the best.

Regards,

Nagesh Ganisetti.

[Former Member]

Hi

Any updates??

Hope it Helps

Chetan

@CP..

[Former Member]

we try to do by going SE37 RSAP_BIW_DISCONNECT and removed the entry for RSBASIDOC. then try to create one using SE37 RSAP_BIW_CONNECT but it not creating and says IDOC already exists. one field I am confused while creating is I_STEXT( name of OLTP System).

Any help from here

[Former Member]

It seems that the error arises due to some system copy in the landscape - either a "refresh" that overwrote QA BI system from another system, or a "refresh" that overwrote the SAP source system.

Please see the how to paper "How to System Copy in an SAP BI System Landscape" for more information about this matter. It is available on SDN or service marketplace alias "BI" > SAP NetWeaver 2004 (although it is valid for all releases).

Best Regards -

Ron Silberstein, SAP NetWeaver RIG

[Former Member]

Hi

As a part of sanity check did you perform rituals as below -

Below deletes the BW-specific information in the source system that does not have a connection to the BW System.

1. Log on to the source system in question

2. Call Transaction SE37

3. Enter function module name 'RSAP_BIW_DISCONNECT'

4. Select the 'Sngl. test' function.

5. Enter the name of the BIW system for the import parameter 'I_BIW_LOGSYS' that matches the one prior to the new installation

6. Enter the name of the source system for the import parameter 'I_OLTP_LOGSYS'

7. Choose the function 'Execute'

and then

Transaction SE37 - function module RSAP_BIW_CONNECT - Single Test. Parameter:

I_LANGU <language of the destination to BW>

I_SLOGSYS <OLTP Source system (SLOGSYS from RSBASIDOC in BW)>

I_LOGSYS <BW system (RLOGSYS from RSBASIDOC in BW)>

I_STEXT <name of the OLTP system>

I_BASIC_IDOC <BIDOCTYP from RSBASIDOC in BW>

I_SAPRL <SAPREL from RSBASIDOC in BW>

I_RESTORE

I_TSPREFIX <TSPREFIX from RSBASIDOC in BW>

I_PREFIXE <35 times second byte of TSPREFIX from RSBASIDOC in BW

(Example TSPREFIX = 'BA', then

I_PREFIXE = 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA')>

Hope it Helps

Chetan

@CP..

[Former Member]

Thanks Chetan

Recreated IDOC in R3 Source System and assign partner profile using the we20.

Chander

[Former Member]

Welcome Chander,

Thanks for reverting back with the feedback.

Chetan

@CP..

[Former Member]

Hi

Please accord the following notes with your Basis team.

<b>325525

325470</b>

Quite Imperative to check your <b>Table - RSBASIDOC</b> ,that should be good to analyse your problem.

If IDOC is not created create it in <b>Transaction- WE30/WE20</b>

Hope it Helps

Chetan

@CP..