Alexander, I disagree, it is not perfectly good. They do not mutually agree, one of them disagrees. Also in this case it is actually really bad because it is leaving out business information on why a line item is changing.
By ignoring the X12 standard, they are ignoring 3 decades of standards development and hard work that was put into place it. What the customer is doing is called standards abuse. If everybody had the same thought process the standards development process would be useless. Gerry's customer is ignorant of the values that come with standards development. Three times a year at X12 meetings, leaders from various industries get together and decide what is the best way to do a Purchase Order or a PO Change or Health Care Claim. It's a 4 day long meeting where people work really hard all day long. Ignoring 30 years of that is not perfectly good, it should be at least considered. I am sure if Gerry's TP really understood the best practices that the standard has to offer. If it were not for the late 1970s and early 1980s pioneers of taking EDI standards seriously there would be a real lack of standards. http://x12.org/ now has a feature where you can make a change request online. If Gerry's TP thinks the data element should be optional they can post there. Thanks, Sergey Sudakov EDI Project Manager Beacon EDI, Inc [email protected] 4445 Eastgate Mall Suite 200 San Diego, CA 92121 800-334-6127 x2 https://beaconedi.com/ EDI Blog: https://beaconedi.com/edi-blog On Fri, May 10, 2013 at 7:37 AM, Alexander Luss <[email protected]>wrote: > Gerry, > > X12 standard is not law that one can be prosecuted for breaking. It doesn't > have a moral side either. Anything that you and your TP can mutually agree > upon is perfectly good, valid, correct and legit. > > > *Thank you, > Alex Luss > ________ > * > > > On Fri, May 10, 2013 at 9:07 AM, Gerardo Santillana > <[email protected]>wrote: > > > ** > > > > > > Hi > > > > I need to send an 855 to a customer, according with his specs he does not > > want element PO301 in segment PO3, but this element is a standard > mandatory > > element. > > > > I can do it but, Is it correct to force the system not to send a > > mandatory element? > > > > Thanks > > > > Gerry > > > > [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 > > > > [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/
