OK. transactions of one type (eg 850) will be in one GS-GS. I'll not use the group type. A ISA-IEA will have one GS-GE
kind regards Henk-Jan Ebbers Hurd, Richard [SLCUS] wrote: >>> However if you are sending me 500 invoices, for instance, > I would greatly appreciate it if you would combine them all under one IN > group and in one ISA otherwise you are giving me an excess number of files > to archive. << > > this is not necessarily true with all translators. My translator, for > example, batches ALL input transactions for a particular inbound run in a > single file. > > Annoying, yes, if you come from file-based interchanges; but it actually > makes searching a lot easier. :) > > > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of > Samantha Scott > Sent: Wednesday, September 19, 2007 4:32 PM > To: henkjanebbers > Cc: [email protected] > Subject: Re: [EDI-L] more questions about X12 (building open source x12 > translator) > > > 1. If you are using N2 as your format that is an implied decimal two > positions to the left so 1.0 would look like "100" and .01 would look like > "1". Only the trailing zeroes are significant. You may choose to pad that > field's empty spaces with zeros or spaces as you like in your application > layouts but EDI is all about using the smallest amount of data to > communicate the information so you never pad your data on the EDI side*. > *unless your customer doesn't know any better and wants it that when in > which case you give them exactly what they want. > > 2. Yes you may have only one group per ISA. Our translator (GIS) always > makes one group (GS-GE) per ISA no matter what. Even though the standard > says there may be many, ASN's always go in one and FA's in another each with > their own ISA. Most people using a real EDI translator will hardly even > notice the difference as long as what you do follows the standards. Its > perfectly legitimate to have one ST transaction inside one GS group inside > one ISA envelope. However if you are sending me 500 invoices, for instance, > I would greatly appreciate it if you would combine them all under one IN > group and in one ISA otherwise you are giving me an excess number of files > to archive. Its not functionally wrong but its annoying. It is also > permissible to put many (properly formed) ISA's inside a single document > that you send, again most real translators won't even notice because parsing > data is what they are designed to do. That is what the batches from the VAN > would look like back when we used to connect once an hour and pull a batch. > > > The ISA changed slightly at version 4030 with the release character but that > was just changing how a particular element was used, not the length. I > haven't had to use much past version 4030 to notice other tweaks. If you > changed the ISA length it would break the system. That ISA is the key to > reading everything that follows it and so it must remain functionally the > same regardless of the version used. > > > > On 9/19/07, henkjanebbers <[EMAIL PROTECTED]> wrote: >> First, thanks for all of your answers. They were very helpful. >> We have a working SEF to Bots-format converter. This save a lot of time, >> our grammar for the x12 order (850)is over 13000 lines! >> I can read and write x12 now, but have to improve some things. >> >> So my questions are: >> >> 1. If a field with format N2 contains only one digit, say '1', how do >> I interpret this? As '0.01'? >> >> 2. In a functional group (GS-GE) I can expect more than one >> Transaction Set type, as long as their Group Type is the same (is >> first field in GS (GS01, Functional Identifier Code). OK, no problem. >> But generating x12 is harder. Questions: >> - what if I use only one Transaction Set type in a functional group >> (GS-GE)? Does anybody bother? >> - what if I always put only one envelope in a functional group >> (GS-GE)? Does anybody care? >> - Is it possible in an x12 file to have more than one ISA? >> >> 3. Has the ISA segment ever been changed? >> >> best regards, >> Henk-Jan Ebbers >> >> >> > > > [Non-text portions of this message have been removed] > > > > ... > Please use the following Message Identifiers as your subject prefix: <SALES>, > <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > > Job postings are welcome, but for job postings or requests for work: <JOBS> > IS REQUIRED in the subject line as a prefix. > Yahoo! Groups Links > > > > -- best regards, Henk-Jan Ebbers Bots open source edi software [EMAIL PROTECTED] http://bots.sourceforge.net ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
