cancel
Showing results for 
Search instead for 
Did you mean: 

"Sender partner does not match with PO vendor" - Invoice IDoc posting issue

Former Member
0 Kudos

Hi SNC Experts,

We are currently trying to implement invoice collaboration feature in SNC->PI->ECC. But after we successfully created an invoice in SNC and receives an invoice idoc in ECC, we are getting this idoc posting issues(ECC) having "Sender partner does not match with PO vendor" error found in the idoc logs.

Any suggestions/tips in fixing the specified issue above?

Thanks!

-Walter Rogando

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Walter,

in We20 tcode can you check which type of partner profile(LS/LI) you have created.If it is LS same LS profile need to maintain in OBCD or LI.And compare the Supplier code and supplier BP in Po also.

Thanks&Regards,

Vishnu

Former Member
0 Kudos

Hello,

Below is the steps to be executed:

1- WE20 settings for ME based output profile

2- OBCA (Company code to Logical system)

3- OBCD (Do not forger to enter your Tax Key)

4- OBCE for Logical System

5- If you would like to create the invoice as an pre document then check the OSS notes için 501524 & 1109900

Regards,

Selim Batur

Answers (2)

Answers (2)

former_member213836
Active Participant
0 Kudos

1. Check PO Header Partner tab in ECC and  validate  that you dont have different invoicing party maintained there.

2. Ensure that EDI parameters are maintained correctly for the invoice as suggested by Selim

3. In OBCE, ensure that you enter correct Invoice and Credit memo document type

4. Check your Invoice IDoc Segment E1EDKA1 and validate that Partner is entered in 10 digits including leading zeroes.

Regards,

Niranjan

Former Member
0 Kudos

Hi Walter Rogando,

Did you created the sender partner profile in ECC system?. Please check the partner profile in WE20 transaction.

Regards,

Mahesh KHM

Former Member
0 Kudos

Hi, Sender Partner profile already maintained in ECC upon checking WE20. not sure what other reason is causing the error.

Thanks!

-Walter Rogando