sometimes in AX duplicate voucher created for journals, and system shows info as voucher %1 is already in used as of date %2.
Here number seq is of continous type and for more info since some wrong entries were created we have deleted those journals and the number seq are also deleted but since its of type continous it can be reused.
apart from this we have that voucher problem,
Any permanent way to avoid such problem in AX 2009 or any fixes are there for these continous type number sequence issues.
If you delete the journal how can it be in use? Seems to me as though you have not deleted the journal correctly. If it is continuous then it is autonumbered, so how are you “reusing” it when the next number would already have been set once the line was saved?
I think the details was not quite enough ,the problem was not trying to use the deleted journal, but that journal would have voucher having the number sequence attached to it, so that also will be deleted along with that journal deletion, now since voucher number sequence is continuous type then those number sequence are reusuable at any time once they have been freed from the list of that number sequence group. But if they are not freed we cannot use those voucher number sequence.
So is there anything we can do to release those number sequence from the list which are not freed , present in number sequence form under basic.
In AX, Basic --.> Number sequence, on which there is list button where it shows the status of number sequence, suppose if any number sequence deleted from system it shows whats that current status. If the status shown as “freed” then it means that number sequence deleted before is now ready for using again…
If I understand correctly, yes, when the number sequence is continuous, the deleted number goes to the NumberSequenceList table.
So, when Ax have to create the next number, first it checks, whether the number sequence is of continous type, if yes, it checks in NumberSequenceList table to pick the next number. If the number sequence is not of continous type, it creates the next number as on NumberSequence form.
So, for your case, I think, its enough to remove the continous check on the number sequence.
And, regarding, the vouchers, I think, on parameters, u have an option, to make the voucher duplicate or not…
I face the same problem. In my case, the voucher got posted. Next time when i create a new journal, the same voucher is alloted. It doesnt happens all the time to the user. The problem is i couldnt simulate the same thing in test environment.
Regarding setup, number sequence should be checked continuous. I have not allowed duplicates vouchers in the parameters setup. Is there any other way to solve the problem.
Here same problem: No duplication of vouchers allowed, number sequence is continuous and needs to be continuous, but system loads in journal line a vouchernumber which is already used and posted. It’s not possible to simulate, but more or less once every 2 months it happens (especially in Payment Journals). I suppose it is a bug which is difficult to simulate, but it happens too much to just accept it.
Do you have another number sequence (that is also used for journals) that generates numbers that have the same format as the number sequence you have problems with?
In the same company I don’t have another number sequence of the same format. I do have the same format in other companies in the same database. But the error which is generated refers to a voucher in the same company, mostly a number which is used and posted one or two weeks before. It seems as if that number is by accident released to be re-used, but the posting is blocked because of check on duplicate vouchers.
It’s only in Payment journals (for customers as wel as vendors) that this happens.
Thanks for the tip. I checked it but the DataAreaID is filled correctly in the original voucher. It’s also not the case that it is re-used over and over again. But next time I will check this immediately after it happens, maybe it could have something to do with this.
Even i checked the Dataareaid, it is filled correctly. I have unchecked the cleanup for the number sequence. It is still continuous. Till now i dint face the problem again. May be u can try it out. Will let you know if i face the problem again… Thanks
As Manish mentioned earlier in the discussion, you should uncheck the continuous box in the setup for that number sequence. A continuous voucher sequence will cause problems when you delete journal lines that have been posted.