Quoted text is from <E6C1EDF60CA5D311A83B00902798A618024E5601@JUPITER>,
by Bhushan V. Bandekar <[EMAIL PROTECTED]>
> Are the current available EDI translators generic enough to
> translate any EDI doc(eg.po/invoice/ack) to flat file w/o
> configuring (basically customizing) or we need to configure EDI
> setup for a partcular type of EDI file pertaining to a trading
> partner.
>
That is a rather difficult question. If you reduce the number of record
types in your tagged flat file to an absolute minimum (header and detail
records, with optionally envelope and sub-line detail if required), or
use a genuine flat file with only one record type, then you stand a fair
chance of being able to use the same flat file format for any particular
business document irrespective of the EDI message used to carry it. The
mapping to an EDI message will, however, probably need to be partner
specific; both because different partners can use different messages,
and because within a message there may be different nuances of data
disposition within it for different partners. Your time zone indicates
that you are probably located on the Indian sub-continent, and thus may
be dealing with EDIFACT messages which can be more varied than the
equivalent X12 transactions.
Unless you know all the EDI message variants which you will be dealing
with for any document in advance, your chances of designing a
satisfactory single flat file format are reduced.
Regards
Chris
--
Chris Johnson +44 (0)20 8501 1490 (home)
EDIMatrix Ltd +44 (0)20 8559 2454 (work)
+44 (0)20 8559 2497 (fax)
http://www.edimatrix.co.uk
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
