cancel
Showing results for 
Search instead for 
Did you mean: 

File2Idoc - Error [EDI: Partner profile inbound not available]

Former Member
0 Kudos

Hi All,

I am executing file to Idoc Scenario, It is picking the file from sender & delivering to Idoc as well (fields) in R/3 system and showing chequered flag SXMB_MONI.

But If go to WE02 in R/3 : It is showing that Partner Profile not availbe , I have already mentioned in We20 - R/3 system.

EDI: Partner profile inbound not available

Diagnosis

An inbound partner profile could not be found with the following key:

I checked in Idoc - Control Segments - > It is shwoing Wrong recipient Partner No & Type

Recipient Information :-

Partner No - CLNT_300 Expecting 100008

Partner Type - LS Expecting LI

Where are to maintain these entries ?

Please do the needful.

Regards,

~Anshul

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Anshul,

Have a look on below threads..

Regds,

Pinangshuk.

Answers (2)

Answers (2)

Former Member
0 Kudos

This blog should be your solution:

/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload

Divyesh Vasani

Former Member
0 Kudos

Hi,

By default XI will send the logical system name with LS....if you need to send as different one like LI/KU/...

need to use the party with identifiers where you need to configure the values for LI and the partner No...

and the sender partner nubmer and logical system name...

Search SDN if still need more details...

HTH

Rajesh

Former Member
0 Kudos

Rajesh,

Thank you very much !

After using Party with identifiers for (LS-KU). Now it is showing error in R3/ WE02 system :-

Function module not allowed: IDOC_INPUT_DELVRY

Message no. B1252

Diagnosis

The function module IDOC_INPUT_DELVRY and the application object type which were determined are not valid for this IDoc.

Is there any another alternative or idea apart from it ?

Thanks,

Anshul

former_member208856
Active Contributor
0 Kudos

Check your IDoc message type & process code used for posting the same in R/3 system.

This error is due to Process code used for posting for this IDoc message.

Use correct process code for this message type.

Former Member
0 Kudos

Sandeep,

I am using simple Idoc Delivery:-

Idoc:DELINF.DELVRY05 Messgae Type u2013 DELINF Process Code -- DELV

But I am getting error in R/3 - WE02

I checked in all entries in We20

EDI: Partner profile inbound not available

Message no. E0337

Diagnosis

An inbound partner profile could not be found with the following key:

/PEVCLNT100/LS//DELINF////

This involves the key fields of table EDP21:

-SNDPRN partner number of sender

-SNDPRT partner type of sender

-SNDPFC partner function of sender

-MESTYP logical message type

-MESCOD logical message code

-MESFCT logical message function

-TEST test flag

Thanks,

Anshul

Former Member
0 Kudos

By Myself....