Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

AP invoice journal allowing multiple invoices w/ same voucher numb

502 views
Skip to first unread message

sonia

unread,
Nov 12, 2007, 4:31:01 AM11/12/07
to
Using a general journal, AX user can book multiple invoices with same voucher
number for the same vendor. However, when this is done in Accounts Payable,
the system issues the error message:

“There can be only one vendor transaction per voucher…”

Please have a feature in AX, where the user would have the option, say a
checkbox to tell the system that a validation should be the same as that in
general journal when booking multiple invoices or it is some sort of a
tighter validation as in the present design.


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=d9553f9b-d7ec-4c11-9eda-9fd4a8117352&dg=microsoft.public.axapta

glibs

unread,
Dec 17, 2007, 5:41:35 PM12/17/07
to

> Using a general journal, AX user can book multiple invoices with same
> voucher
> number for the same vendor.

In 4.0 sp2 it is not allowed. I have just tested.

Here is error text.

Warning Message (01:37:14) There can be only one vendor transaction per
voucher.
Warning Message (01:37:14) There can be only one vendor transaction per
voucher.
Warning Message (01:37:14) Journal has not been posted.
Error Message (01:37:14) Update has been canceled because of an error.

Africa@discussions.microsoft.com South Africa

unread,
Jul 22, 2008, 3:21:02 AM7/22/08
to
Hi all

We have the exact same error even in general journals , what do you
recommend? We are using general journals for multiple customers/vendors for
data migration and experiencing the same error in general journals. We are
running Dynamics AX 4.0 SP 2

0 new messages