Dear members,
We have a received purchase order. When the received is converted to invoice, it has to go through the workflow. In the workflow it throws up this error during posting “Posting has been cancelled. Voucher xxxx-xxxxx is already used as at date xx/xx/xxxx. 36 30 20 started.” Workflow has just two steps. First step is approval. Once approved, post invoice. During the second step, it throws up this error. I have traced that particular voucher number that shows up in the error to Stock and warehouse management parameters → Number sequence → Invoice costing voucher. Now how to go from here. What are the steps to be taken so that the workflow lets the invoice to post?
In that particular stock and warehouse management parameter number sequence, I have edited and increased the next number by 1 (Like for ex: If it shows 31802, I manually entered 31803). But didn’t work. (Not sure if it’s the right method). Continuous is unchecked.
If any screenshot is required, please let me know.
Thanks.
Send a screenshot. When you increased the number sequence, did the error message reference the number you had just changed it to, or was it still complaining about the old number?
You are right, Jacob. The error message that popped up referenced the latest number that I changed to. But we have got the solution.
Let me give the solution. This is applicable for all types of errors Voucher number xxxx already used errors in whichever posting it may happen.
When this occurs, we have to go to the parameters as mentioned above and look & find the number sequence under “Number sequence”. Either in the same parameters or in some other module parameters, this same number sequence format should be mapped to another number sequence code. Now check the next number on both. We can ignore the number sequence that whichever is already used. Take the other sequence and edit the format (under segment, we can change add either one extra # under alphanumeric or a “hyphen” under constant etc.). Then we should be able to post.
Thanks.
That still sounds like something isn’t working. I wonder if the number sequence got stuck somehow.
The solution was given like the above mentioned to the client. From their side, they changed the format of one of the number sequence and posted successfully. So if this type of error message pops up, mostly there is another number sequence with the same format set up which clashes with this sequence. There were some other solutions given in dynamics MS site, but I guess in this scenario, this solution worked.