> We have a customer that insists on receiving the SAC-05 element with the > explicit decimal as opposed to the implied decimal type N2 defined in the > standards. > Has anyone heard of this type of exception being used that defies the > standards. > Any thoughts are appreciated.
I've dealt with only, I think, three requests from all my clients' customers over the years to *send* 'non standard' data . Two I was able to talk into us sending standard-compliant data, and they actually thanked me. The third had requested LIN segments in 856 ASN documents with identifiers but no qualifiers but he said we could send the qualifiers if we wanted but he would ignore them and just go by ordinal position. I've actually handled far more cases of client partners SENDING my client non-compliant data; they always corrected a problem on their end. I will probably get shot for saying this, but I've found my clients' partners to be pretty much universally cooperative dealing with me when I point out standards compliance issues to them. (Yes, 90+ percent of my clients are the 'seller' in a seller-buyer relationship). Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... 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/
