Earl,
You were right to stress the _should_.
>>>Sounds like an understandable programming oversight...
Actually, I like to call it a piece of junk.
>>>There are ways to prevent this...
>>> use a different sequence of numbers for each process,
Earlier in the thread others were talking about not using ODBC, instead
using flat files and the ERP system's import processes because you wouldn't
want to overlook the critical internal processes that may need to occur.
That's why I brought this up. We ARE using the system's tools, and this is
how well they work. THIS IS AN EXCEPTION TO THE RULE - I DIDN'T INTEND FOR
THIS TO DISPROVE WHAT ANYONE ELSE WAS SAYING, IT WAS MERELY COMICAL.
In other words, this is a closed process, which we have no control over. No
changing sequence numbers.
>>> get people out of order entry when importing,
Heh. This is our current "solution". You can probably guess how well that
works. Ever asked a bunch of people to please not use something every day at
time X,Y, and Z? :)
>>> make sure that both processes cannot 'grab' the same order number...
With all due respect, isn't that like saying, "Doctor, just stop the
bleeding and get his spinal column reattached to his brain stem." We don't
have the source- our accounting system just does it. This would require
SERIOUS reverse engineering and then a bunch of hacks if even possible.
Travis-
-----Original Message-----
From: Earl Wertheimer [mailto:[EMAIL PROTECTED]
Sent: Friday, September 08, 2006 2:48 PM
To: Travis Truax; [email protected]
Subject: RE: [EDI-L] ERP EDI raw data import/export concerns
Travis
> Our accounting package's "documented interface" with it's built-in
integrity
> checks- likes to unpredictably (yet frequently) steal lines from imported
EDI
> POs and place them on manually entered POs our sales people may be
entering.
Sounds like an understandable programming oversight...
If this happens as EDI orders are being imported, it's because both the
import
process and the manual entry are using the same unique order number...
There are ways to prevent this... use a different sequence of numbers for
each
process, get people out of order entry when importing, make sure that both
processes cannot 'grab' the same order number...
This _should_ be easy to fix...
Earl Wertheimer
[EMAIL PROTECTED]
http://www.spe-edi.com
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
