In Navision 3.70 (HU) we experience the phenomenon, that sometimes a number of the number series of “Posted sales invoice” is skipped - for no apparent reason. And I was not able to replicate it on purpose yet. Has anybody experienced that same problem (that in the posted sales invoices one number is missing) and does anybody know how to solve it? It is quite a big problem, since in Hungary one is not allowed to have a gap in the posted invoices (sales and purchase). Thanks in advance for any hint.
Create a sales order. Deliberately create some sort of error that will not allow it to post (eg. Set Blocked on an item). Post. You ewill get an error message. The posted number seq has now increased. There are more solutions. I had the same problem on a couple of installs in Hungary, and eventually had to modify the code to resolve this.
Hi David, thanks for the info - I was indeed able to replicate the problem. You talked about “there are more solutions” - any chance of sharing the most effective with us (e.g. coding)? Thanks.
Hi guys, We have more than 40 installations here in Hungary and I think phenomenon is not a problem but a question of setup. After you correct and post erroneus invoice, gap will be solved. If you have any quastions please let me know! [:)] Greetings from Bp
Evaluation is like this: *Post an invoice/order. *In codeunit 80 “Posting No.” is assigned. *An error occurs. *“Posting No.” remains. *You correct the error and post again. *Codeunit 80 will not assign another “Posting No.” - it will use the allready-assigned one; result: no gap. If you on the other hand try to delete the invoice/order after “Posting No.” has been assigned, standard-Navision will create and emtpy posted-invoice to prevent a gap in the number-sequence. So - this should not be a problem…?
It shouldn’t, but users can get around this. I agree with Tibor, that traing is the real solution. Other than that you can modify the code to not commit the increment of invoice number, but this will make the system slow. The mods I did, were not so much to controll the number, but to warn the user when they were making mistakes.
We are having the same issue over here, no gaps allowed in invoice no. sequence and we prefered in older Navision versions to desactivate the COMMIT at the end of the section where the posting no. get’s assiged. Right now, with 3.70 and the Open/Release that requieres another COMMIT, I also agree that training and error resolution will solve the problem more easily. Saludos Nils
Looking back, the code I did was in 3.56 OS/2 and in financials 1.10 things have changed a lot since then.
This Issue is resolved in IN 3.70 Upgrade to the latest version Guys
In Italy cu80 and 90 have been localized to avoid gap in invoice number, they remove the initial commit. There are also two additional tables to avoid locking all the users during invoice posting: No. Series Line Sales No. Series Line Purchase Elena
quote:
This Issue is resolved in IN 3.70 Upgrade to the latest version Guys
Life is so easy - do you work for MBS? [:D]
Sorry guys to disappoint you… but this issue is NOT resolved in 3.70 (at least 3.70HU incl. HF1-5, an I have not read anything useful in the other HF)[:(][:(]
quote:
Originally posted by elbi
In Italy cu80 and 90 have been localized to avoid gap in invoice number, they remove the initial commit. There are also two additional tables to avoid locking all the users during invoice posting: No. Series Line Sales No. Series Line Purchase Elena
Hello Ms Elena, can you please explain your tips more detail? Thank you very much. Regards Tirta
I have a situation where the system is generating phantom cheques in the middle of auto cheque runs. Baffling and nobody at MBS has yet been able to offer an explanation