Purchase Invoice xxxxxxxx already exists

(0) Share

Report

Posted on by Alicja_

241

Hello,

When posting purchase orders and purchase invoices, we keep running into issue: "Purchase Invoice PPIxxxxxx already exists"

There is no such invoice, only a PPI number in the PO header was reserved at some point. Once I remove the number from PO or PI header, we are able to post that document. Issue is that it is happening with all documents. Not sure if that is a bug in BC or how to resolve this.

Please help!

thank you!!

Categories:

Other

Purchasing

All responses (11)

Answers (0)

Suggested answer

MahGah 15,419 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

You need to use configuration package and then take that exact PO to Excel and edit and upload back. This is the only way I know. But be careful with configuration package since if you make a mistake then it is not reversible.

www.youtube.com/watch
bcconsultant14 44 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

Has a resolution been discovered on this? I'm working on BC v20 and I have the same posting error.

Tried to post a purchase invoice when the No. Series has been exhausted. I extended the No. Series but the number BC tried to post to is being used somewhere, presumably held up but won't post.

In BC Cloud, how would I edit the table header to remove that bad P-RCPT number?
FredaSun 20 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

Hi Alicja,

The PPI number in the Purchase Header table is grey for me, do you know how I can edit that?

Thanks,

Freda
Surabhi Dobhal 80 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

Hey all,

I need urgent help, which is a similar issue.

I'm getting and error while converting from Purchase requisition (PR) to Purchase quote (PQ).

The Purchase Line already exists. Identification fields and values: Document Type='Quote',Document No.='PUS17541',Line No.='10000'"

The thing is that;

when I'm checking the No. series for PQ; last No used is showing as "PUS17540".

and this error rarly comes, not always we're facing this. Currently we're suggesting them to create another PR but we want permanent solution.
Suggested answer

Praveen V 10 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

Hi Alicija,

I know its a very late reply, but I came across similar issue. You have already posted an Invoice with Vendors Invoice number and now you have not updated the latest vendor invoice number in Purchase header, pls check the Vendor Invoice No in Purchase Header and update it with the latest one.
Suggested answer

Renato Fajdiga 1,849 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

usually I would suggest to not fill manually this field because in posting routine BC/NAV will fill that field automatically.
Alicja_ 241 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

so the reason this is happening is due to the transactions that were imported for the beginning entries...
Alicja_ 241 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

Hi,

Here is an example, the item was received already, now trying to Invoice:

I have no invoices with Vendor Invoice Number = ABS0024 also I do not have any other Purchase Orders with that number

there is no Purchase Invoice there:

what is happening..?
Suggested answer

Renato Fajdiga 1,849 on at

Like (0)

Report

RE: Purchase Invoice xxxxxxxx already exists

Hi,

usually in posting/checking codeunits system writes Posting No. in field Posting No. on table Purchase Header. If you try to post the purchase invoice, and you get error message sometimes Posting No. value stays in that field. That is some issue why sometimes my customers have the same problem.

I tested your case on my BC OnPrem Cumulative Update 2 and can't reproduce the error.

Best regards,

Renato.
Alicja_ 241 on at

Like (1)

Report

RE: Purchase Invoice xxxxxxxx already exists

Hi Renato,

Thank you for the message!

I went to - PO - Help - About this page - Table Fields - Find field 'Posting No.' - to verify the PPI number from the error

Then I went to Purch Inv Header table to verify that that PI is not there (in each case I had, there was no such a PPI number

Then I went to Purchase Header table and removed that PPI number from the Posting No field

That seems to resolve the issue. That is why our assumption is that at some point the Posting number is being reserved, if so that is causing a lot of issues..