EDI: Partner profile inbound not available

[Former Member]

Hi Gurus,

I am facing an error while posting invoice from SRM. I am in standalone scenario. I am getting following error in we02 for message type BBPIV and BBPCO.

EDI: Partner profile inbound not available

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

/SR8CLNT300/LS//BBPCO////

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

Same error is coming with BBPIV.

I successfully created a distribution model and generated partner profile in SRM system and then generated partner profiled in EH4. But inbound parameted BBPIV and BBPCO are not created.

When I try to create Partner profile for BBPIV and BBPCO, I get an error, process code Co01 and Iv01 don;t exist in table TEDE2

Regards

Kapil

[Former Member · Accepted solution]

For the error of BBPIV and BBPCO please refer the notes 330401

[Former Member · Accepted solution]

Thanks Joseph. My problem is solved.

Maintain process code co01 and iv01 in transaction we42 and then regenerate the partner profiles using BD64 in backend system.

Thanks

Kapil

[Former Member · Accepted solution]

EDI: Partner profile inbound not available

Message no. E0 337

Diagnosis

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

/INFO_CDT/LS//MATMAS/MAT/DPT//

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

Procedure

Please check the inbound partner profiles.

how can solve this problem pls help me any one

[former_member183819]

Hi Kapil

check we20,we21

we21- ports would have created automatically when you generate a partner profile.

in we20

partner type ls

check your backend logical system and corresponding messages are existing or not.

double check scc4 - client - your logical system is correct or not both systems.

br

muthu