Hello all,
I have been notified by our purchaser that he is getting an error:
Line 0 of the receipt, which you are attempting to invoice, has already been invoiced.
I googled this error but did not find a solution. We have not invoiced any of this order.
Is that an exact wording of error message?
Because LineNo = 0 only while you move to new line and haven’t entered anything yet in any column. As soon as you start filling in the data, LineNo is set to “normal” current value (most often a multiple of 10’000).
Even if you already have some lines completed and focus is on next empty line – for which the LineNo = 0 – when you try to post, Navision ignores that empty line and posting goes on…
This error is probably form the GetReceivedLines function. do you receive goods tot he Purchase order, and then consolidate the lines onto one big invoice and post there? If so that is where to look. Maybe he did the get lines function twice.
It is a new issue that we havent had before and only occurs on this PO. We only invoice what the vendor gives us an invoice for at a time, so we consolidate receipts and then invoice multiples.
My purchaser has notified me that they were able to invoice 3 out of 4 of those lines individually.
And yes that is the exact wording of the error which is why I am a bit confused.
I am not sure how I can help more. I have told you what the error means, if you don’t want to believe me, then you need to look for another solution.
Okay, I looked and did not see anything that appeared unusual regarding the code for gettinglines.
However, we figured out a workaround and was able to invoice it.
My new question would be, is there a way to manually change qty invoiced? (and in turn change qty received not invoiced)
Hi,
It is not possible and i strongly recommend not to interfere any data in the posted transaction. Its better to use reversal features like credit memo for making corrections.
Thanks…
In this case - definitely right! You may gain what you want for now. But later on you most likely will have problems whith this.
The thing to do here is to resolve the issue, find out why it happened and make sure it doesn’t happen again. Hacking the database is never an alternative to user training.
Dan if you are not able to diagnose this (and its a very common user error) then get your partner in to show you what went wrong, otherwise you could cause serious damage to your system.