I like your comment, Leah:
>>EDI does not drive the content (what you're calling design) of the ASN,
>>business does. Although, once in a while we do get to be backseat drivers!
But in small operations such as ours, there's no "application people" to talk
with... it's just a few Jacks, or a single one in some cases. The logical
distinctions still exist, but in practice they matter very little to us. We're
responsible for the design of the process, as well as everything else. (Except
for the actual execution of the process, at least!)
95% of our EDI problems come from gaps in the application side. Mapping data is
pretty easy when there's actually something to map it to & from. Just
connecting dots and converting a few dots to stars.
Travis-
[Non-text portions of this message have been removed]
------------------------------------
...
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:
[email protected]
[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/
