Bad Ship To address in AR Group

Yahoo Archive
1
Never mind. I did a quick crystal report that compared the Invoice Detail
Ship to Num to the Customer Ship To Num and it was evident which Invoice had
the problem.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Scott Litzau
Sent: Monday, January 23, 2012 2:49 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Bad Ship To address in AR Group





Tony,

Did you ever figure this out? We are having the exact same issue today and
trying to determine which Invoice it is.

Scott

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Tony Hughes
Sent: Tuesday, November 01, 2011 10:50 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Bad Ship To address in AR Group

I have an AR invoice group with something like 300 different invoices in it.

Printing the invoices step fails and the System Monitor says the cause is
"ShipTo Record Not Found". And of course it does not tell you which one was
not found, or which shipment, or even which invoice is affected...
I've had this problem before, but the group was small, maybe 4-5 invoices
and it was easy to figure out.

Anyone know how to figure this out? I have SQL back end and can query if
that makes it easier.
Thanks.

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
2
I have an AR invoice group with something like 300 different invoices in it.
Printing the invoices step fails and the System Monitor says the cause is "ShipTo Record Not Found". And of course it does not tell you which one was not found, or which shipment, or even which invoice is affected...
I've had this problem before, but the group was small, maybe 4-5 invoices and it was easy to figure out.

Anyone know how to figure this out? I have SQL back end and can query if that makes it easier.
Thanks.
3
Tony,



Did you ever figure this out? We are having the exact same issue today and
trying to determine which Invoice it is.



Scott



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Tony Hughes
Sent: Tuesday, November 01, 2011 10:50 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Bad Ship To address in AR Group





I have an AR invoice group with something like 300 different invoices in it.

Printing the invoices step fails and the System Monitor says the cause is
"ShipTo Record Not Found". And of course it does not tell you which one was
not found, or which shipment, or even which invoice is affected...
I've had this problem before, but the group was small, maybe 4-5 invoices
and it was easy to figure out.

Anyone know how to figure this out? I have SQL back end and can query if
that makes it easier.
Thanks.





[Non-text portions of this message have been removed]
4
Hello Scott,

Look at the error message in the Vantage Log file. It should tell you detail info about the error.

The path should be something like this -

\\your-erp-server\EPICOR\mfgsys803\Server\logs

Good luck,
Hanh

--- In vantage@yahoogroups.com, "Scott Litzau" <scott.litzau@...> wrote:
>
> Tony,
>
>
>
> Did you ever figure this out? We are having the exact same issue today and
> trying to determine which Invoice it is.
>
>
>
> Scott
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> Tony Hughes
> Sent: Tuesday, November 01, 2011 10:50 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Bad Ship To address in AR Group
>
>
>
>
>
> I have an AR invoice group with something like 300 different invoices in it.
>
> Printing the invoices step fails and the System Monitor says the cause is
> "ShipTo Record Not Found". And of course it does not tell you which one was
> not found, or which shipment, or even which invoice is affected...
> I've had this problem before, but the group was small, maybe 4-5 invoices
> and it was easy to figure out.
>
> Anyone know how to figure this out? I have SQL back end and can query if
> that makes it easier.
> Thanks.
>
>
>
>
>
> [Non-text portions of this message have been removed]
>