Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Voucher*** already exi...
Microsoft Dynamics AX (Archived)

Voucher*** already exist as of date-error while posting purchase receipt

(0) ShareShare
ReportReport
Posted on by NDingankar22 487

Dear All,

Greetings

Hope you are fine.

I am new to AX and working on some support project.

I need your help in solving the below critical issue

My client is unable to post receipt of ANY PO in system. The error message is recievs is "Posting is cancelled, Voucher XXXX used on the date and some exceptions in FOrmLetterService run method is thrown

1.When he sets the GL paramets-Allow Duplicates-The product receipt is working fine. Can someone tell me what is the implication of changing this setup on PO( as the earlier setup was " Reject Duplicates");

2.  I tried finding the exact number sequence(AP -Purchase receipt made changes as freeing the Status list etc) but no luck still the same error message

3.I than went to Inventory number sequence and there changed few number sequence (* as per the format-only those-found 2) but no free status list. But however the voucher XXX was the  value in the "NEXT field" of number sequence . I changed to some other value and the error disappered. 

May i know what the next field should be example Number sequence-TST001-continuous-is ticked(checked)-Starting number is 16000 and last number is 16999. next is 16200. I made it 16300(any guidelines) to make the out the next number??

Please help as i am still in learning phase of AX tech. I need answers as what implications would GL parameters and Next (in number sequence) would have

I have tried all solution but it aint working. AX is weird..all of sudden the error comes out of blue with so much exception that a normal person will get headache seeing the exception infolog

*This post is locked for comments

  • Suggested answer
    Satish Panwar Profile Picture
    Satish Panwar 14,645 on at
    RE: Voucher*** already exist as of date-error while posting purchase receipt

    Thank you for kind words. Please know that there is not a way to change posted voucher numbers. Let them be as is. If you think this may cause issue during Audit, just record the incident in your internal system and attach appropriate documentation with it (Note down all vouchers that got duplicated along with dates / screenshots etc). Apart from it just try to fix the on-going problem and you should be good.

    Thanks,

    Satish Panwar

    Please help verify answer(s) if they guide you in right direction so other community members can also benefit from your question with verified answer.

  • NDingankar22 Profile Picture
    NDingankar22 487 on at
    RE: Voucher*** already exist as of date-error while posting purchase receipt

    Hi All,

    Thank you so much for giving me some lead. May god bless you all . INdeed this community is life saver for people like me.

    I will try to check the Number Sequences and see if the error goes. Ax is weird. I tried again few PO and it worked without doing anything. However will test tomorrow again in LIVE

    Alternatively, the client posted some PO in system with  GL parameters-->Accept duplicates"(earlier the setup was  "Reject Duplicates")

    As Satish mentioned above the drawback that we may get the multiple voucher numbers , the client is asking as how to go ahead with these 6 PO's which were receipted using the " Accept Duplicates" parameters. What would be the drawback and implications.

    Kindly suggest how to rectify this PO's which were recipted with " Accet Duplicates" parameters

    Thanking you all again

    Regards

  • Suggested answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,253 Super User 2024 Season 2 on at
    RE: Voucher*** already exist as of date-error while posting purchase receipt

    Hi,

    In addition: It might be possible that there are multiple number sequences setup which do generate the same numbers. In that case, you can also get duplicate voucher numbers. Using the number sequence form, you can check the format of each number sequence which is in use if there are any overlaps.

    Usually, voucher and invoice numbers should be sequential, so check if you are allowed to skip numbers before you will disable the continuous setting or when you want to change the next.

  • Suggested answer
    Richard Wehmeyer Profile Picture
    Richard Wehmeyer 1,002 on at
    RE: Voucher*** already exist as of date-error while posting purchase receipt

    For a GL voucher I do not see why it is restricted to 16000 to 16999.  It seems you would run out of numbers in the sequence very fast.

    We have run into this problem when a number sequence set to continuous is being used in multiple companies.  You don't want to do that.

    Alternatively if someone assigned a new number sequence similar to a previous sequence you can get this effect. 

    Check GL > Setup > Journals > Journal names.  It is possible to specify old or erroneous voucher sequences to journal names.

  • Suggested answer
    Satish Panwar Profile Picture
    Satish Panwar 14,645 on at
    RE: Voucher*** already exist as of date-error while posting purchase receipt

    Hi,

    Allow duplicates will let the system record the same voucher number again. The downside is if you research tomorrow using voucher numbers, you will get multiple records. Preference is to keep this check box cleared so there are no duplicates in the system.

    What you need to do is find out what's causing the duplicates. If this happens frequently, check if the continuous check box is marked and if that can be removed. In some cases continuous creates the issue when number doesn't get cleaned up OR if someone changes the number sequence without understanding what would be the impact.

    Changing the value in NEXT is fine, it just means that you don't have regular number sequence in the system and you just skipped a few. Unless there is regulatory requirements to have continuous number sequence, it's ok to advance to next value to resolve immediate problem while you try to identify the root cause and fix it permanently. It may not happen again.

    Next column in short holds the value -> what is going to be your next number for the number sequence.

    Thanks,

    Satish Panwar

    Please help verify answer(s) if they guide you in right direction so other community members can also benefit from your question with verified answer.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans