> We are a small grocery wholesaler and right now only use EDI for
> transactions 810, 820, 850, 824, 997.
> I'm looking to possibly expand EDI's usage here internally and need to
> determine, out of the hundreds of available EDI transactions, which
> ones might possibly be applicable for our usage.
>
> Anyone care to share how they use EDI transactions, including what
> transactions, as well as in what internal areas/departments.
I think you are looking at this backwards.
EDI is not a goal unto itself; it is but one means to a business end. That
business end may be a problem solution or it might be an opportunity to be
seized.
E.g, you might have an opportunity to make additional sales and profit "if
only we could enter into some kind of vendor-managed-inventory program with
target customer X"
Might ANSI EDI offer a good choice of tools to facilitate such a VMI
program? (Answer: yes). (But do you really care? Well,if VMI makes
*business* sense to you, then sure you care).
Or, you might decide .. as you apparently already have ... that printing
invoices for everyone just costs too much, and there simply must be a better
(read: less expensive) way.... and ANSI ASC X12 EDI has provided a tool -
the '810' invoice document - to facilitate the non-printing submission of
invoices to your customers.
All that said, there are in the "wholesale anything" business a group of
documents which are in quite common use: 850, 810, 856, 820, etc... but I
doubt you'd have use for, say, the 837 Health Care Claim or Encounter or the
272 Property/Casualty Loss Notification documents in your particular line of
business.
The frequency of ANSI document use is directly proportional to the frequency
of use of the corresponding paper documents: e.g., if you handle a lot of
paper/phone purchase orders, using the ANSI Purchase Order document might
offer you some benefits. But there is no sense in even thinking about using
the '850 Purchase Order" document if you don't have to process customer
purchase orders or send purchase orders to your vendors.
It seems quite often here we see posts which "forget" that ANSI EDI is a
*support* function, existing only to aid the *real* business purposes of its
users. Better I think we all remind ourselves of this a bit more often than
we do now.
Michael C. Mattias
Tal Systems Inc.
Racine WI
[EMAIL PROTECTED]
...
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/
