Doug, Wow. I meant pretty much what I said: This is not truly an "identifier" in the usual sense with ANSI X12 as it's not their code. Usually ID's of this type will refer to an outside list of codes maintained by another authority. SCAC codes are indeed such codes.
Seems like we're agreeing, so what's up? I also said that I had not seen codes that weren't all alpha and were anything other than 4 characters, but that that did not mean there weren't any. Again, not sure why you took issue with that? I don't have a book. I don't have the budget to pay for one, nor do many, nor is it really necessary to answer this question, which I don't think you did. In fact, I think you dissed Chris for his efforts. He obviously has a 990 in front of him, so that is his question, what to do with what he's got. Normally, you're very helpful, so, maybe, go have a nice lunch, calm down, regroup? Leah ________________________________ From: Doug Anderson <[email protected]> To: 'Leah Halpin' <[email protected]>; Chris Johnson <[email protected]>; [email protected] Sent: Thursday, April 12, 2012 10:36 AM Subject: RE: [EDI-L] 5030 990 B1 query Leah SCAC codes can be obtained from the National Motor Freight Traffic Association (NMFTA.org). SCAC's are 2 to 4 alpha character codes. For example a two character code would be the Norfolk Southern RR (NS). An example of a four character code would be Estes Express (EXLA). Most if not all containers have a SCAC on them. They are used primarily to identify transportation carriers. Also, if you have an X12 standards book handy, you would see that data element (DE) 140 points to code source 17. If you look at code source 17 you will see that it indeed points to the NMFTA as the maintainer of the outside code list. I do note that the URL is incorrect in the code source and I will submit a DM to fix that. Not sure what you mean when you say that DE 140 is not truly and identifier in the usual sense. Again, if you open your X12 standards book you will find in section 3.5.1.3 of X12.6 (Application Control Structure) that an ID type is "An identifier data element always contains a unique value from a single, predefined list of values that is maintained by ASC X12 or some other body recognized by ASC X12 and identified by a reference in Appendix A of X12.3 Data Element Dictionary." So DE 140 is truly an "identifier". That said, Chris, why would you start with the 990? The 990 is only used in response to a load tender (204). Without the 204 the 990 is useless. Doug Doug Anderson Chair, ASC X12 Transportation Subcommittee Vice President Sales Support Kleinschmidt Inc. 847-405-7457 (Office direct) 847-826-3531 (cell) www.kleinschmidt.com www.facebook.com/kleinschmidtinc -----Original Message----- >From: Leah Halpin [mailto:[email protected]] >Sent: Thursday, April 12, 2012 8:58 AM >To: Chris Johnson; [email protected] >Subject: Re: [EDI-L] 5030 990 B1 query > > >This is interesting. I am unfamiliar with this particular transaction, but >very familiar with X12. The B101 is defined as Standard Carrier Alpha Code >(more commonly and redundantly SCAC code). This is not truly an "identifier" >in the usual sense with ANSI X12 as it's not their code. Usually ID's of this >type will refer to an outside list of codes maintained by another authority. >SCAC codes are indeed such codes. I've never seen one that wasn't 4 >characters and I've never seen one with numbers, (note the ALPHA in SCAC). >Doesn't mean there isn't a longer or shorter one or that one might not have >numbers. > >However, 6 is going to violate the X12 standard. So, creative is a nice word for it. I'd suggest asking them WTH? Nicely, of course. > >Happy almost Friday. >Leah > >________________________________ >From: Chris Johnson <[email protected]> >To: [email protected] >Sent: Thursday, April 12, 2012 7:32 AM >Subject: [EDI-L] 5030 990 B1 query > > > >X12 is little used in the UK, and I consequently have little experience >of it. I am currently mapping a 5030 990 transaction (it seemed like an >easy one to start with). The client sample messages have a six character >alphanumeric as the first field of the B1 segment. According to my >specifications this is a 140 data element which should be ID,2,4. > >Are my specifications incorrect, or is the client being creative? > >Regards >Chris >-- >Chris Johnson mobile:+44 (0)7785 302122 Fax: +44 (0)870 0519 818 >EDI website http://www.edimatrix.co.uk >EDIMatrix Ltd work: 0845 126 0680 or +44 20 8778 1402 >Registered in UK no. 2777624 Reg.Office: 34 Sydenham Rd, London SE26 5QF > >[Non-text portions of this message have been removed] > > > [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 <*> 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: [email protected] [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/
