Finance | Project Operations, Human Resources, ...

Voucher Is already used !

(0) Share

Report

Posted on by Kareem Taima

Hi,

I'm facing this error for the first time,

I tracked it down and I found it's used in Transfer with 8546.Untitled1.png the same voucher number..

but I couldn't find out why it's giving me this error and what's the relation?

I need to know what's the solution to avoid any future issues like this

thank you

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello Kareem Taima,

You mentioned that this issue is related to a transfer journal in inventory is that right?

If this is the case, please check the number sequence that is assigned to this journal.

It looks as if this number sequence is used also elsewhere for example for another journal type.

A result of such an 'overlap' is the error message that you see.

What you can do to avoid this in the future is setting up a new and unique number sequence that you use with this journal - and only with this one.

Best regards,

Ludwig

Was this reply helpful? Yes No
Suggested answer

Satish Panwar 14,673 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi Kareem,

There is a parameter in AX (GL > parameters > Duplicate vouchers), that checks if duplicate vouchers are allowed or not. Based on message above, it looks like it's turned on in your environment and that's why you get error above. The error is actually good and is typically best practice to not accept duplicate voucher. This will allow you to trace transaction easily.

What you need to do is, go to the number sequence that's being used in posting above and see what sequence it uses. Also check what's the setup behind transfer order number sequence. Then determine which one you want to retain and which one you want to change. You obviously can't use the number above as it's already used in your transaction so if you want to use above number sequence, then you have to increase the next number on existing number sequence (once you find what next number you can use).

Make the change on number sequence and then try to resume/post the transaction again.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi-

I see this and similar response to how to work around this issue, but it's not clear to me how to prevent this issue. Is it something we have to have workarounds for in the department?

Thanks

Jeannette

Was this reply helpful? Yes No
SouravDam 11,732 on at

Like (0)

Report
Copy link

Link copied!

Hello JeannetteC,

This seems an old thread.

Appreciate if you kindly create a new thread on this topic to discuss.

Best regards,
Sourav Dam

Was this reply helpful? Yes No