Stanley Pool suggested:
> If it is a vendor; then just put the standard terms and conditions in
"NTE"
> segments of the PO. Make them pay the VAN charges.
>
> If it is a customer; then include the segments for payment terms and any
> other information in the NTE segments. Here again make them pay the van
> charges.
>
I proffer dissent. If the data are anything but "free form text" which is
taken "as is" and perhaps added to a sales order or a puchase order as a
"free form comment," then embedding significant information in segment
element NTE02 (in ANSI 004010, data element 352, 1-80 A/N) is totally,
absolutely and abjectly counterproductive.
If you and you partners (customers and vendors) are TRULY using payment
terms which are assigned on an order-by-order basis, use a segment designed
for that: the ITD segment. (I think I've only seen this done once, and
that's since 1983. Usually any cash terms conveyed in a purchase order
document are ignored, and "customer's standard terms and conditions" are
used).
Asking your vendors, or yourself, to parse individual elements of an EDI
document to extract significant data, rather than storing significant data
elements in their own elements, is contrary to the whole idea of
ANSI/EDIFACT EDI (or even XML) , which is, " there is one data element for
each fact, and exactly one fact per element."
That said, yes I know numerous 363.636 kilogram gorillas do this, and
because they are 363.636 kg *customer* gorillas you have to go along; but as
my sainted late mother told me more than once, "Just because everyone does
it does not make it right."
(Note: I am a regular person, not a lawyer). (And damn glad for that.)
Michael C. Mattias
Tal Systems
Racine WI
[EMAIL PROTECTED]
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
