RE: Duplicate AP invoice entry -- MAPICS-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: Duplicate AP invoice entry
From: Konrad Underkofler <kdunderk@xxxxxxxxxxxxx>
Date: Fri, 12 Jul 2002 15:24:18 -0400
List-archive: <http://archive.midrange.com/mapics-l/>
List-help: <mailto:mapics-l-request@midrange.com?subject=help>
List-id: MAPICS ERP System Discussion <mapics-l.midrange.com>
List-post: <mailto:mapics-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/mapics-l>,<mailto:mapics-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/mapics-l>,<mailto:mapics-l-request@midrange.com?subject=unsubscribe>

Keith,

As I seem to recall the duplicate invoice entry
is only applicable to live items, those not fully
in history. So if it had transitioned from OPNPAY
files to APHST files it would not check. We have the
same issue if the check reconciles fast.

If it had not reconciled, I would look into the
invoice sequence number to see if it was different.
I believe invoice sequence is set during data entry.

Given the timeframe, I would check the invoice sequence
issue first.

Regards

Konrad

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Duplicate AP invoice entry , Keith Schwarz

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.