cancel
Showing results for 
Search instead for 
Did you mean: 

EDI: Partner profile not available, Message E0332 for /0000000000/LI/

Former Member
0 Kudos

Dear,

We have a scenario running in which Customer/Company code/ Purchasing organization 90006/6000/6000 buys materials from Vendor/Company code/Sales organization 90002/1100/1100.

A Purchase order creates an automatic Sales order via EDI, this works fine.

Now we want to optimize the process further by using an Output type ZD04 (copy of RD04) by which the Billing document of 90002/1100/1100 automatically triggers an Invoice Receipt (MIRO) at 90006/6000.

This gives me the trouble in that I can’t get the outgoing IDOC processed correctly.

I get the following error message:

EDI: Partner profile not available

Message no. E0332

Diagnosis

A partner profile could not be found with the following key:

/0000000000/LI/

This involves the key fields of the table EDPP1:

-PARNUM partner number
-PARTYP partner type

Procedure

Please check the EDI partner profiles.

Before you come up with your clues (which are very welcome by the way;), you should know that so far, I have already done the following:

  • Created Vendor 90002 in Company code/Purchasing organization 6000
  • Created Customer 90006 in Company code/Sales area 1100/1100-90-01;
  • Field KNVV-EIKTO is set to 90002 for Customer 90006 in Sales area 1100-90-01
  • OVV9 (customizing): Sales organization 1100 is assigned Customer 90002, Sales organization 6000 is assigned Customer 90006
  • Output type ZD04 is created as a copy of RD04; Access sequence 0005, Transmission medium 6-EDI, Partner role BP
  • An Output condition record is maintained for ZD04 for Sales organization 1100 and the relevant Billing type
  • WEL1 (customizing): Logical address 60000000090002 created which comprises of Company code 6000 and Vendor 90002
  • WE20: Outbound: Partner number 90006/Partner type KU/Partner role BP: Message type INVOIC, Message code MM, IDOC Basic type INVOIC1, Message control: V3-ZD04-SD08
  • WE20: Inbound: Partner number 90002/Partner type LI/Partner role <blank>: Message type INVOIC, Message code MM, Process code INVL
  • WE42 (customizing): Process code INVL; Message type INVOIC, Message code MM, Identification IDOC_INPUT_INVOIC_MRM
  • OBCA (customizing): Partner type LI, Partner number 90002, Company code name ‘Company 90006’, Company code 6000
  • (I also did further customizing of OBCB, OBCD and OBCE but for my problem this is not relevant)

Also bear in mind that we are on SAP_APPL 605/0004 and I went through a whole lot of (outdated) SAP Notes already.

Again, thanks for your clues, helpful ones will be rewarded!

Kind regards,

Bart

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member

Hi

In WEL1, the Assignment has to be verified

PO Intercompany process

Logical Address:  < Delivering Company code code> <IC  Paying C.code-customer>

Destination Setting:

Company code: < Paying C.code>

Vendor:              <IC  Delivering C.code-Vendor>

In transaction WE41, Assign the process code SD09 with  Function Module IDOC_OUTPUT_INVOIC for the outbound IDOC and the error will be resolved.

sundancer
Explorer
0 Kudos

Dear all,

As said, WEL1 and WE41 have to be filled correctly.

BR,

Sébastien

Former Member
0 Kudos

Dear Bart

We have the same problem. Could you tell us how it was solved?

Regards.

Carlos

Shiva_Ram
Active Contributor
0 Kudos

I went through a whole lot of (outdated) SAP Notes already.

I am sure you could have gone through as your explanation is very detailed. However let me refer this OSS Note 31126 - Intercompany billing - posting to vendor account using EDI     

The step WE20 partner 90002, in the note output code is mentioned as FI whereas in your case it is MM and process code as INVL (instead of INVF). Does this cause this error message.

Regards,

Former Member
0 Kudos

Hi Shiva,

Thanks for your reply.

Yes, I went through SAP Note 31126 as well;

Since we want a MIRO Invoice (hence Logistics Invoice Verification), we need MM/INVL as the Note states, and as I wrote, I have already set that, so that does not cause the error I would say.

Kind regards,

Bart