RFC Connection from R/3 to BW fails

[Former Member]

Hi,

I'm getting the following problem. We just upgraded our R.3 system from 4.7 to SAP ECC 6.0. I've just tested the connection from BW to DEV and that's fine. I can connect from BW to DEV and customize extractors etc., no problem.

However, when I try to load data into BW via an infopackage I get no data. The monitor itself doesn't display any messages. It looks like it is still running but in SM37 and AL08 in R/3 there is no RFCUSER active.

Please note that the pre-upgrade DEV was sapdv5 with system number 00

Post-upgrade DEV is sapdv3 with system number 20. In SM59, under the BW connection the settings for Target Host are set to sapdv3 and system number 20. When I test the BW connection I get the following message:

Logon Connection Error

Error Details Error when opening an RFC connection

Error Details ERROR: service 'sapgw20' unknown

Error Details LOCATION: SAP-Gateway on host sapdv5 / sapgw00

Error Details DETAIL: NiHsLGetServNo: service name cached as unknown

Error Details COMPONENT: NI (network interface)

Error Details COUNTER: 466

Error Details MODULE: nixxhsl.cpp

Error Details LINE: 776

Error Details RETURN CODE: -3

Error Details SUBRC: 0

Error Details RELEASE: 700

Error Details TIME: Wed Nov 7 14:02:15 2007

Error Details VERSION: 38

I'm not experienced in BASIS but it looks like it's confuding sapdv3 and sapdv5.

Is that correct? How can I solve my problem?

thanks

Michalis

[Former Member]

Hi Michail,

After upgrade your R3 system from 4.7 to ECC6.0, did you change your logical system name in BW? did you check the status of RFCUSER in R3? did you check the table RSBASIDOC entries in BW?

After upgrade please check the RFCUSER in R/3 system, to do that you have to go to SU01 transaction code and give your RFCUSER and display the status if it is not there ask the basis person to create a RFCUSER with sufficient profiles, you must know the password for that. Once you done that in R/3 come into BW system and change the logical system name by applying BDLS transaction code and you have to know the password of BW_USER background user in BW system. Try to restore the source system, while restoring the source system check the authorization connections and test connections. once every thing is OK then you can activate the source system and replicate your datasources and try to load the data.

Hope it helps

(assign the points if you satisfied)

Thanks,

Babu

[Former Member]

Hi Babu, our BASIS team has already resolved the issue. Thanks for your response.

cheers

Michalis

[Former Member]

RESLOVED

[Former Member]

Correction:

Pre-upgrade R/3 DEV was sapdv2

Post-upgrade R/3 DEV is sapdv5

BI DEV has always been on sapdv3

hope it makes sense now

Michalis