|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: looking for unix utilities to deal with edi files(X12 837 format)
Mr. McTeigue,
I hear and respect your perspective, and your ability to program an EDI
translator from scratch.
I don't think it is necessarily an either-or proposition, that is home-made
EDI or off-the-shelf EDI. I have been very fortunate to work in IT
departments with scripting jockeys and EDI translators.
Here is some humor, if you have look for it:
It takes a villiage to build an EDI...
Gary
----- Original Message -----
From: "Paul McTeigue" <
To: <
Sent: Tuesday, July 15, 2003 7:40 PM
Subject: RE: [EDI-L] looking for unix utilities to deal with edi files(X12
837 format)
>
> >> Anyone who really knows EC selects the best tool available in the tool
> >> chest to solve the problem that requires addressing.
>
> Which is why those religious arguments against developing EDI software
> are so annoying. I have programmed from scratch an EDI translator
> and also re-sell two other commercial ones. Whichever solution is best
> is the one that gets implemented.
>
> Paul McTeigue
> www.icefan.ca
>
>
>
> -----Original Message-----
> From: EDI [mailto:
> Sent: July 15, 2003 9:49 PM
> To:
> Subject: RE: [EDI-L] looking for unix utilities to deal with edi files(X12
> 837 format)
>
>
> Frankly, I do think that the point is that Perl is very useful and
> powerful. Purchased software is limited only to the functions it was
> created for.
>
> If I really had ".nothing better to do with my time." I would probably
> spend endless hours at the TLE Mapping Workbench attempting to get it
> to perform functions that it was not designed to perform.
>
> In the not so distant past I had a lot of better things to do with my
> time, but instead I was being required to spend inordinate amounts of
> time debugging Harbinger / Peregrine / Inovis / software.
>
> The only cursing at my place of employment is due to fact that our
> commercial translator software version will no longer be supported at
> the end of this year and upgrading to the latest version is not in the
> budget. Yes, the manager is unhappy, but not because Perl is no longer
> supported.
>
> Because I have not identified myself and have a point of view about the
> purpose of mapping software and programming languages I am accused of
> lacking business etiquette? Yes, I failed to attend that business
> etiquette class. Of course, anyone who sells EC Solutions would not
> argue for someone to obtain their own ability to make software. I
> believe that I understand your point of view but do not understand how
> accusations would attract me to ever use your solutions.
>
> Anyone who really knows EC selects the best tool available in the tool
> chest to solve the problem that requires addressing.
>
>
>
>
>
>
>
>
> --- wrote:
> > Quite frankly getting into a discusion with someone who doesn't even
> > identify
> > himself in a professional mailing list is probably not time well
> > spent.
> > While 'I_know_EC" may know a little about EC, I would suspect he
> > doesn't know
> > business etiquette. Of course, anyone who really knows EC wouldn't
> > argue for
> > make versus buy except in the most limited situations.
> >
> > Jim Divoky
> > EC Solutions, Inc.
> > > Frankly, I don't think the point really has much to do with the
> > relative
> > > usefulness or power of Perl (or any other language for that
> > matter). The
> > > cold hard fact of the matter is that an 837 is a very complex
> > document to
> > > work with (the average implementation guide runs in the range of
> > 500-600
> > > pages!!!). If you have nothing better to do with your time than to
> > write
> > > Perl or ___ (choose your favorite language), well, you'll certainly
> > be busy.
> > > My own advice, would be to think more about how to divide up the
> > work into
> > > modules maybe: Specifically, I'd recommend that you use Perl or
> > ___
> > > (whatever) to walk through the data and isolate the pieces so that
> > they are
> > > more easily accessible in appropriate data structures (or
> > whatever). Once
> > > it's more accessible, then think about where the data goes.
> > >
> > > Having said all that, I agree with those who suggested a commercial
> > > translator as good, time-saving way to get the most out of EDI
> > (would I be
> > > safe in guessing that 837 isn't the only document being
> > processed?). I
> > > guess this is leading into a build vs. buy debate. I'll let others
> > > (re-)hash that out. 8-)
> > >
> > > Best regards,
> > > Bill Chessman
> > > Inovis(tm), Inc.
> > >
> > > -----Original Message-----
> > > From: EDI [mailto:
> > > Sent: Monday, July 14, 2003 5:13 PM
> > > To:
> > > Subject: Re: [EDI-L] looking for unix utilities to deal with edi
> > > files(X12 837 format)
> > >
> > >
> > > I disagree. Perl can and does parse at least as good and some times
> >
> > > better than commercial translators. It is actually best to have
> > Perl
> > > and a good commercial translator. "Slight" changes will not
> > necessarily
> > > cause a Perl "translator" to fail to correctly parse. Major
> > changes,
> > > such as version changes may. However, version changes will
> > definitely
> > > require you to write a new map for that commercial translator.
> > >
> > > --- Leah Halpin < wrote:
> > > > Eddie,
> > > > Sorry to break this to you, but you need a translator. Or,
> > you'll
> > > > end up writing a "translation" program, say with PERL for
> > instance,
> > > > and if you do that, as soon as they (whoever is sending these
> > claims)
> > > > makes any slightest change, you're screwed.
> > > > Good Luck,
> > > > Leah
> > > > ----- Original Message -----
> > > > From: evhorig
> > > > To:
> > > > Sent: Sunday, July 13, 2003 12:55 AM
> > > > Subject: [EDI-L] looking for unix utilities to deal with edi
> > > > files(X12 837 format)
> > > >
> > > >
> > > > Help!
> > > >
> > > > I am looking for reliable unix utilities
> > > > that deal with edi (837 to be specific) data files?
> > > >
> > > > I'm looking for something that will allow me to pull
> > > > specific fields out of an X12 837 edi file and put it into
> > > > a ascii text file in whatever order i want.
> > > >
> > > > For instance, I could dump all pertinent information for each
> >
> > > > individual claim into seperate files so that i can construct
> > > > a single claim from any single file without having
> > > > to deal with all of the X12 loopibng/parsing.
> > > >
> > > >
> > > > I'm not looking for something really involved with ftping
> > files,
> > > > connecting to clients, having to run a server process etc
> > > >
> > > > Something simple that takes an edi file as an arguement and
> > maybe
> > > >
> > > > some kind of mapping file and spits out fields that i request.
> > > > A program that converts an 837 edi file to individual ub92
> > > > claim files would be a good start.
> > > >
> > > > It doesn't have to be free, but i don't want to break the
> > bank
> > > > either.
> > > >
> > > > Thanks for listening,
> > > >
> > > > Eddie
> > > >
> > > >
> > > >
> > > > Yahoo! Groups Sponsor
> > > > ADVERTISEMENT
> > > >
> > > >
> > > >
> > > >
> > > > To unsubscribe from this group, send an email to:
> > > >
> > > > Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>,
> > > > <EVENT>, <OFF-TOPIC>
> > > > Access the list online at: http://groups.yahoo.com/group/EDI-L
> > > >
> > > >
> > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> > > > Service.
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > > ------------------------ Yahoo! Groups Sponsor
> > > >
> > > > To unsubscribe from this group, send an email to:
> > > >
> > > > Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>,
> > > > <EVENT>, <OFF-TOPIC>
> > > > Access the list online at: http://groups.yahoo.com/group/EDI-L
> > > >
> > > >
> > > > Your use of Yahoo! Groups is subject to
> > > > http://docs.yahoo.com/info/terms/
> > > >
> > > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > SBC Yahoo! DSL - Now only $29.95 per month!
> > > http://sbc.yahoo.com
> > >
> > >
> > > To unsubscribe from this group, send an email to:
> > >
> > > Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>,
> > <EVENT>,
> > > <OFF-TOPIC>
> > > Access the list online at: http://groups.yahoo.com/group/EDI-L
> > >
> > >
> > > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> > > To unsubscribe from this group, send an email to:
> > >
> > > Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>,
> > <EVENT>,
> > > <OFF-TOPIC>
> > > Access the list online at: http://groups.yahoo.com/group/EDI-L
> > >
> > >
> > > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> > >
> > >
> >
> > ------------------------ Yahoo! Groups Sponsor
> >
> > To unsubscribe from this group, send an email to:
> >
> > Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>,
> > <EVENT>, <OFF-TOPIC>
> > Access the list online at: http://groups.yahoo.com/group/EDI-L
> >
> === message truncated ===
>
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>
>
> To unsubscribe from this group, send an email to:
>
> Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
> <OFF-TOPIC>
> Access the list online at: http://groups.yahoo.com/group/EDI-L
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
> To unsubscribe from this group, send an email to:
>
> Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
> Access the list online at: http://groups.yahoo.com/group/EDI-L
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
