cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Invoices in Business Network failing incorrectly

Velu_V
Explorer
0 Kudos
500

Hi Experts,

We are implementing Ariba Invoice Management solution for a Non-SAP ERP, as part of this, after the realm baseline, we started creating test transactions from Ariba Invoice Management (AIM) to network (Non-PO Invoices) and were able to validate only for a couple of invoices that it all went fine (from AIM to Network). But after those couple of non-po invoices any non-po invoice we create is getting rejected at Network with the error - "Invoice could not be created from InvoiceDetailRequest. Reason = Duplicate invoice number." We tried creating multiple combinations, by replicating the same data as the ones that were successful by changing quantity and amount and copying the existing Non-PO invoices from AIM, but all invoices seems to be getting this error, although there is no duplicate of invoices here, all the invoices have different Invoice Numbers. 

We are trying to raise a support request on this, i want to check in this group if anyone has encountered this error during implementation or support and what steps have been taken to resolve this.

Please note, we don't have CIG in place here, we are creating the invoices from AIM and validating the statuses in Business Network.

Any help on this would be much appreciated.

Thanks,
Velu

Accepted Solutions (1)

Accepted Solutions (1)

Mridul
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello @Velu_V , 

Based on my understanding, i have seen this error generally in two scenarios:
1) The invoice was rejected because there is another invoice already identified by the same payloadID. Each document in SAP Business Network must have their unique payloadID, they cannot share the same payloadID
2) The invoice got stuck in Ariba Buying & Invoicing with no entity reference number

I guess this would require support team to review logs and trace so i think SR with support is the right option to get this fixed.

Answers (0)