Re: what is meaning of ** in edi data stream

Standardized edi?
Currently working in a part of the insurance industry, and boy does it
seem not very standardized (some is and some is not). And some is by design
to not be fully automated (you can get your response file from our
web portal - (very unfriendly). Be thankful for a standard transaction set.
jim

----- Original Message ----- From: "Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, August 04, 2011 3:49 PM
Subject: Re: what is meaning of ** in edi data stream

Hello,

On 8/4/2011 1:08 PM, Steve Richter wrote:

EDI is kind of interesting. A lot of noise when I search the web for EDI
specs. Like every site I clicked on is looking to sell something.

Is there a site from which I can download the official EDI spec? Two I am
working with now are the 945 and 846.

There's more than one "official EDI spec". I'm guessing (from the
examples in your messages) that you are working with ASC X12 documents
-- which are the dominant type in the USA.

The standards body responsible for those has a page, here:
http://www.x12.org/

I suspect that they will sell you the standards documentation (rather
than providing it as a free download) if you contact them. Indeed, a
quick Google finds that they have an online store:
http://store.x12.org/

However, the international standard for EDI (recommended by the United
Nations) is EDIFACT. It's the dominant standard worldwide.
http://live.unece.org/trade/untdid/texts/unredi.htm

There are a few other "EDI standards" out there besides these two, but
these two are the dominant ones.

Within each EDI standard, almost everything is optional... so just
because two of your trading partners might be using the same standard
and transaction set doesn't necessarily mean that their documents will
be similar! (But this is just me griping...)

And what is the great value of an EDI translator? I was able to parse the
846 ( inventory snapshot ) pretty quickly with RPG procedures. I can see
using a translator when sending a properly formatted document.

I agree, but... not everyone has your (or my) skills as a programmer.

Plus, what you find is that you need a separate "map" for almost every
trading partner, since they tend to all use slightly different optional
elements. (At least, that's what I found.) So having software that
lets you just create a map, rather than coding a whole program, can be
advantageous.

Of course, that depends heavily on how many different documents you use
from how many different trading partners.

Plus, when you buy the package, there's typically a database in the
package (used by the software) that describes the EDI standards, so you
don't have to buy the official docs from ASC X12/EDIFACT. :-)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.