cancel
Showing results for 
Search instead for 
Did you mean: 

Entry in outbound table not found: Error Status 37 for IDoc

Former Member
0 Kudos

Hi

I am trying to post an IDoc from R/3 into XI but in we19 i get this error. "Status Error: 37 Entry in outbound table not found:\"

But i have maintained parter profile for R/3 in we20. For Sender R/3 LS i have made an entry for outbound message type.

In we 19 for the Sender i am giving Partner no as LS of R/3 and Receiver i an giving the partner no as LS of XI and for the receiver port i have created a port in we21 for XI.

Regards

Monika

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

You need to provide outbound param for your XI LS partner ,by the way what is the type of idoc msg you are trying to trigger?

Rajesh

Former Member
0 Kudos

Hi

In we 19

Receiver

Port: A port created in R/3 referencing RFC dest pointing to XI.

Partner no: LS of XI (CLNT100)

Partner Type: LS

Sender

Partner no: LS of R/3 (RD1CLNT500)

Partner Type: LS

Message Type is DESADV

Basic DELVRY05

and i am sending blank idoc for testing.

Regards

Monika

Former Member
0 Kudos

>

> Hi

>

> In we 19

> Receiver

> Port: A port created in R/3 referencing RFC dest pointing to XI.

> Partner no: LS of XI (CLNT100)

> Partner Type: LS >

Did you configure Outbound params for partner CLNT100 with your message type and port configuration?

Rajesh

Former Member
0 Kudos

No i configured only inbound for CLNT100, as the idoc is inbound for XI. I have not done the IR and ID configurations as yet..

Former Member
0 Kudos

Well i gave outbound params also but no rescue..

former_member181962
Active Contributor
0 Kudos

Hi Monika,

I doubt if this has got something to do with the Empty idoc.

Try to find an existing IDOC in WE02 for your IDOC Type and use that in WE19.

Regards,

Ravi Kanth Talagana

Former Member
0 Kudos

Hi

I cannot use an existing idoc as it a fresh system with no idocs. I filled some dummy data it does not work with that too.

Answers (2)

Answers (2)

Cortex2k
Active Participant
0 Kudos

Hi Monika

Please check one againg in WE20 that the IDOC type settings are correct under Outbound Parameters. Normally this type of error is caused by incorrect setup in WE20 as you wrote yourself.

Best regards,

Chris

Former Member
0 Kudos

Hi Chris

I have set the IDoc DESADV in outbound of Sending R/3. moreover the detailed error states

No partner profile (outbound parameter) could be found using the following key:

/CLNT100/LS//DESADV///X/

Here CLNT100 is LS of XI

Former Member
0 Kudos

Guys this works with giving Message Type DESADV in we19. It asks for Basic type in which there is only DELVRY06, and sending that ..it works.

Somehow i feel there was no association between DELVRY05 and DESADV. But while importing it in XI it shows DESADV.DELVRY05

Regards

Monika

Former Member
0 Kudos

Hi,

did you maintain the entries in your distribution model via BD64?

Also please check data you use in WE19! IDoc status 37 indicates usage of incorrect data in IDoc header...

Regards,

Kai

Former Member
0 Kudos

Hi Kai

I am not using BD64 for triggering the IDoc ..am using we19 to do that.