I don't remember if that version had a problem with last...Epicor may be able to tell you. I know that 406A had a bug where if two miscellaneous header charges with the same ID were added to an order only the first one printed. I believe 408 may have fixed that but added the bug where the header miscellaneous charges were multiplied by the number of order lines; if your order had 10 lines and you had one miscellaneous charge, it would print and add the miscellaneous charge in 10 times! Epicor released a one-off in 409 that fixed that one. The report data def changed in 409 so I don't think the one-off version will work on 407.
--- In vantage@yahoogroups.com, Keith Walter <keithfwalter@...> wrote:
>
> We are on 407. Definatly seems buggy...
> ÂÂ
> Keith Walter
> Vantage Coordinator
> Norgren Automation Solutions, Saline Division
> keith.walter@...
>
>
>
>
> ________________________________
> From: snielsen28 <snielsen.hipco@...>
> To: vantage@yahoogroups.com
> Sent: Wed, September 1, 2010 3:26:31 PM
> Subject: [Vantage] Re: Sales Order Header Misc Charge Frequency
>
> ÂÂ
> What version are you on? There have been a few different bugs concerning
> miscellaneous charges on order ack...Last one I know of that appeared in
> 8.03.408 was fixed with a one-off I applied on our 8.03.409A version.
>
> --- In vantage@yahoogroups.com, Keith Walter <keithfwalter@> wrote:
> >
> > We are trying to use Misc Charges on SO headers. It give you an option for
> > Frequency (First, Last, Every). When I select LAST, I assume that
> > in Invoice Entry, when you "Get Shipments", it should only add the Misc
> > Charge when the last open line ships. This is not happening. It is adding the
> >
> > Misc Charge EVERY time we invoice a line. Has anyone else seen this work or
> >not
> >
> > work? Why is this happening?
> >
> > Thanks,
> > ÂÂ
> > Keith Walter
> > Vantage Coordinator
> > Norgren Automation Solutions, Saline Division
> > keith.walter@
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>