Invoice created in SUS vs created in ECC

[Former Member]

Hi Gurus,

I think I know the answer to this one, but I'm going to ask anyway...

If we have a PO & GR for 100 units, and a supplier mails/email/faxes an invoice to AP for 10 units, and a MIRO invoice is created, and then they create an invoice in SUS for 100 units, the SUS invoice will error out when the IDoc is created in ECC. Is there any way for this to create some kind of notification? The supplier made a mistake in this case, but unless someone is monitoring IDocs, how would anyone know that this happened?

I'm guessing this would have to be a custom solution, but is that how others have addressed the issue of inbound Idocs that fail?

Thanks,
Seth

[ivy_li · Accepted solution]

Hi,

In MM-SUS scenario, normally invoice will be created by suppliers in SUS system and sent back to ECC.

You can send invoice from ECC to SUS only if it is in the ERS process.
Vendor must be ERS enabled & in the PO the ERS option must be selected,
then it is possible to create the ERS invoice during the ERS run with transaction MRRL.

If you create a non-ERS invoice in ECC, it will not be updated to SUS and hence SUS will have no idea of the already invoiced quantity.

ECC non-ERS invoices will not be updated back to SUS.
SUS system has no idea of the remaining un-invoiced quantity of PO.

If you allow this procedure to be used, you might consider

to make use of BADI BBP_SUS_QUAN_PROPOSE (method SET__QUANTITY_INV) in

SUS when creating Invoice to perform a remote function call to ECC to

check the remaining un-invoiced quantity of the PO, and issue an error

to supplier if necessary.

BR,
Ivy

[Former Member · Accepted solution]

Hi Ivy,

Thanks for the response. I was aware of most of what you said and my main concern was if the supplier submit an invoice to AP and also creates one in SUS, the system won't stop them. And we can't expect AP to monitor this when they receive an invoice.

But that BADI looks like it will do the trick. So if we have a GR of 100 units, and the supplier submits a paper invoice for 40, forgets, and then creates a SUS invoice for 100, it will give them an error.

Thanks,
Seth

[ivy_li · Accepted solution]

Hi Seth,

Your understanding is correct.
This is one restriction of SUS system, and we could only use this BADI to trigger error to remind supplier of this.

BR,
Ivy

[Former Member · Accepted solution]

Thanks, Ivy. So may restrictions on SUS!!

You don't happen to know of any documents that describe how the "Check Payment Status" button works? It doesn't work with our ERS invoices, and we think it has something to do with the fact that we put a custom value in the reference field of the invoice on the ECC side...

Thanks,
Seth

[ivy_li · Accepted solution]

Hi Seth,

Yes, I have to admit that SUS has many restrictions, and we also have notes to list the restrictions.

For 'check payment status' button, what is the problem?
Did you check note 1410435 & 1947162?

BR,
Ivy

[Former Member · Accepted solution]

We're using MRER, not MRRL to generate ERS invoices. Our settings put the Delivery Note from the GR into Reference field in the invoice (instead of the invoice number). It APPEARS that SUS compares the value in the External Reference Number to the ECC Reference field to determine whether payment has been made. So they'll never match up.

We figured that we could just remap the fields in XI, so that our ECC reference field get put into the SUS External Reference Number. Two problems with this. One, it doesn't work. Two, if the reference value is greater than 10 characters, SUS strips the first ten characters off of the value and puts the rest in the External Reference field. So if the value is "1234567890ABC" only "ABC" is entered.

And that raises another, tangentially related, question - why is the reference field in the webpage limited to 10 characters, when the underlying field have a 16 char limit?

Any thoughts?

Thanks,
Seth