Yoicks! So, if you did it right, but didn't send the pairs in the order they wanted them, could they handle it or did it choke? I'm guessing from their answer, they had done something like hard coded LIN13 = vendor part number (for example)?
Trippy. Leah ________________________________ From: Michael Mattias/LS <[email protected]> To: [email protected] Sent: Friday, May 10, 2013 10:58 AM Subject: Re: [EDI-L] 855 Mandatory element not needed 5/10/13 > If you stay in the EDI field long enough you will see *plenty* of your > clients'/employers' partners specify documents which are > not standard-compliant. For example, here's a post I made in EDI-L March 21 2002.... ===================================================================== Too good not to share..... 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 ...." ========================== .. and the most recent example came earlier this week... client's partner specifies ANSI 004010 '850' with MSG segment(s) at header level outside an N9, SPI or LM loop. MCM [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/
