cancel
Showing results for 
Search instead for 
Did you mean: 

source system conection problems( PRDClient 100)

Former Member
0 Kudos

for BW Development.

Result of the destination check: User is locked. Please notify the person responsib le RSAR 375

for BW production

BW unknown in source system RSAR 8

The BW IDoc type ZSBB005 is not the same as the 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

I am kindly request you to provide me solution in this regard.

thanks & regards

subba reddy.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

hi subba,

1. EDI: Partner profile not available E0 332

On BW Type Transaction WE20. Partner Profiles

Click on 'Partner Profile' and then 'Partner Type LS’. Click on your Source system profile to verify settings. If Source System does not exist; click on 'Partner Type LS' then Create. In your Outbound, Parameter should be ‘RSRQST’. Double click it. Outbound Options Tab Receiver Port: select RFC from above step #3. Packet Size: 1. Output Mode: 'Transfer IDocs Immediately. IDoc Type: RSRQST. Syntax Check: 'X' Post Processing Tab Type: 'US' User: Remote User (RFC_R3) Language: EN

ii. if receivers port is not available go to WE21 -> create port

R3 setting : we20

outbound :RSINFO,RSSEND

inbound :RSRQST

BW setting : we20

outbound :RSRQST

inbound : RSINFO,RSSEND

2. Entry in inbound table not found E0 414

i. In your Inbound Parameters should be 'RSINFO'. Double click. Inbound Options Tab Process Code: 'RSIN'. Syntax Check: 'X' Process By Function Module: 'Trigger Immediately > Post Processing Tab Type: 'US' User: Remote User (RFC_R3) Language: EN

ii. In your Inbound Parameters should be 'RSSEND'. Double click. Inbound Options Tab Process Code: 'RSDR'. Syntax Check: 'X' Process By Function Module: 'Trigger Immediately Post Processing Tab Type: 'US' User: Remote User (RFC_R3) Language: EN

3. Entry in outbound table not found E0 400

Entry in outbound table not found E0 400

enter : RSRQST

Click on 'Partner Profile' and then 'Partner Type LS' . Click on your Source system profile to verify settings. If Source System does not exist:

Click on 'Partner Type LS' then Create. In your Outbound Parameters should be 'RSINFO'. Double click.

Outbound Options Tab Receiver Port: select RFC from above step #3. Packet Size: 1. Output Mode: 'Transfer IDocs Immediately. IDoc Type: RSINFO. Syntax Check: 'X' Post Processing Tab Type: 'US' User: Remote User (RFC_BW) Language : EN In your Outbound Parameters should be 'RSSEND'. Double click. Outbound Options Tab Receiver Port : select RFC from above step #3. Same as RSINFO. Packet Size: 1. Output Mode: 'Transfer IDocs Immediately. IDoc Type: Basic IDoc Type (ZSBAXXX) that was checked or created in Step #5. Syntax Check: 'X

Post Processing Tab Type: 'US' User: Remote User (RFC_BW) Language: EN In your Inbound Parameter should be ‘RSRQST’. Double click. Inbound Options Tab Process Code: 'RSRQ'. Syntax Check: 'X' Process By Function Module: 'Trigger Immediately Post Processing Tab Type: 'US' User: Remote User (RFC_BW) Language: EN

regards

sangram sutar

Former Member
0 Kudos

Hi Subba,

It sounds like there is more than one problem.

The first thing that you will have to check is that the system user used for the RFC connection (on BW and on R3) is not locked (TCode SU01 in BW and in R3).

Your best option is to then do a repair on the source system connection. This should automatically correct the inbound and outbound ports. Just remember that if you do the repair, both the BW and R3 clients needs to be opened for changes (Tcode SCC4). The Basis team will have to help with this.

Hope this is helpful

Adelle

Former Member
0 Kudos

Hi,

Tran we20 configure Partner profile

Rgds,

San!