[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

Re: ISA 15 change

From: Mike Rawlins <mcr@...>
Date: Tue Apr 12, 2005  8:56 pm
Subject: Re: [EDI-L] ISA 15 change
You have two choices for doing this in TLE:

1) Modify the standard inbound envelope to add this code for all customers
- I don't have it in front of me, but I believe it's the ANSIFCT
table. Look up in prodansi the code set reference for the data element,
then modify ANSIFCT in prodid to add "I" in addition to "P" and "T".

or

2) Create an inbound envelope table for just this customer - Copy the
ANSIFCT table files to a new name, make the change as described in #1, then
modify the event to use your new envelope.

#2 is a bit more involved, but not much. My inclination would probably be
to go with #2 since it would only affect this (oddball) customer.

Mike

At 03:27 PM 4/12/2005 -0400, Vernon, Cindy wrote:

>Hello Everyone,
>
>
>
>I have a customer who wants to send an I in the ISA15 for an 820. I would
>then use the ISA15 segment to determine if the 820 was a copy of
>information they received from their Affiliates or if its P, then the
>money has been transacted with the banks. I realize that this is not
>within the standards, but does anyone know of a way that I could
>accomplish this. Right now if I try to process a document with an Iin the
>ISA15 it errors out immediately. I am using TLE v5.2 on Unix.
>
>
>
>Thanks in advance!
>
>
>
>Cindy Vernon
>
>E-Commerce Analyst
>
>LENOX / American Saw & Mfg Co
>
>Ph: 413-526-5231
>
>Fax: 413-525-9637
>
>
>
>
>This message may contain information that is confidential and/or protected
>by law. If the reader of this message is not the intended recipient, you
>are hereby notified that any dissemination, distribution, copying or
>communication of this message is strictly prohibited. If you have received
>this communication in error, please contact the sender immediately and
>delete the message. Please note that although we will take all
>commercially reasonable efforts to prevent viruses from being transmitted
>from our systems, it is the responsibility of the recipient to check for
>and prevent adverse action by viruses on its own systems.
>
>
>.
>Please use the following Message Identifiers as your subject prefix:
><SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
>Access the list online
>at: <http://groups.yahoo.com/group/EDI-L>http://groups.yahoo.com/group/EDI-L
>
>
>
>
>----------
>Yahoo! Groups Links
> * To visit your group on the web, go to:
> *
> <http://groups.yahoo.com/group/EDI-L/>http://groups.yahoo.com/group/EDI-L/
> *
> * To unsubscribe from this group, send an email to:
> *
>
<mailto: yahoogroups.com
>
> *
> * Your use of Yahoo! Groups is subject to the
> <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.

---------------------------------------------------------------
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
Using XML with Legacy Business Applications (Addison-Wesley, 2003)
www.awprofessional.com/titles/0321154940




 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.