> Yes I've seen the misuse as well. JAMA EDIFACT is a standard, the use, > misuse or avoidance is a seperate issue. It's the same with ANSI, > EDIFACT or any standard, you can do mappings that are compliant or not.
Misuse a standard? Say it ain't so.... Origninally posted here 3/21/02: ================================================================= After reviewing a client's customer's implementation guide for an ANSI 856 ASN document, I sent a letter to the client with a few questions I had about the project. In one portion of the letter I referred to a sample segment provided by the customer (customer name edited): " [customer] shows the LIN segments in the "856 Ship Confirmation Example" thus: "LIN*1000*VO*91284**DS**00050**CONSOLIDATED**00000**32340648**1592003A~ "This segment is not ANSI-compliant, as for each pair of LIN04/05, 06/07...14/15, if a item appears in the second element of the pair, the first element of the pair (the qualifier) is required. We should confirm with [customer], but in the absence of other information I would suggest ...[suggestions for qualifier values for the even-numbered elements]." Well, the client DID confirm with his customer, and replied to me thus: "Mike, just fyi [customer] said that they don't use the qualifiers and they have vendors that don't populate the 856 with them. They didn't care if we use them ...." ===================================================================== MCM > :-) > > Back to the orginal question, we recently did a Retail CPG project in > Japan and while there were some unique Japanese requirements the base > message standard was still EDIFACT and our library maps were 80% useable > for ORDERS, DELFOR, etc. Outside North America EDIFACT is more widely > used. > > Best Regards, > > James > > -------- Original Message -------- > Subject: Re: [EDI-L] Which do you prefer, X12 or EDIFACT? > From: Leah Halpin <[EMAIL PROTECTED]> > Date: Fri, September 05, 2008 11:00 am > To: [EMAIL PROTECTED], Steville Mims <[EMAIL PROTECTED]> > Cc: [email protected] > > > Since you mention JAMA I just need to quickly chime in. The Japanese > companies I've seen using JAMA have just forced a flat file into EDIFACT > segments without regard for use of qualifiers or meaningful hierarchical > looping structures, I don't consider this actually "using" a standard. > > Only slightly off-topic. > > Leah > > > > > ------------------------------------ > > ... > 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 > > > ------------------------------------ ... 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/
