Sounds stupid, but we have had partners require it. I doubt they can really enforce it...
Recent Examples: When we went to AS2 with Wal-mart, they "required" a Sterling or IBM mailbox as backup (even if it never gets used). JcPenney- Currently dropping IBM (I know it was acquired by GXS) to only use GXS. They are sending out letters to try and get their vendors to move to GXS as well. While the letter states interconnects are allowed, they discourage the use of them- Warning that they will not be responsible for any problems with your communication. This will most likely get pulled as the wildcard when *any* problem occurs. (The letter even states chargebacks may be assessed for late ASNs because of problems or delays with the "interconnect facility".) What does everyone think? Would you dismiss this? Travis- -----Original Message----- From: Stephen Lee [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 12:59 PM To: EDI-L Listserv Subject: Re: [UCE] RE: [EDI-L] Non-ASCII characters "We communicate with several VANs" I've always wondered why some people communicate with more than one major VAN for X12/EDIFACT when they all interconnect. Isn't it a violation of the standard or unecessary when a customer requires you to connect to a certain major VAN to exchange EDI documents? The only reason I can think of is when TPs are on the same VAN they can access eachothers mailbox pickup times as that isn't exchange through interconnects. Regards, -Steve Travis Truax To: EDI-L Listserv <[EMAIL PROTECTED]> cc: Subject: [UCE] RE: [EDI-L] Non-ASCII characters 04/07/2005 01:52 PM Dan, I think we all understand the importance of standards. If one member of the band decides to play tuned to their "own" key, it sure isn't going to sound good- The EDI standards (at least X-12 which I am most familiar with) are in effect just the conglomeration of the individual needs of the companies who are members of the committees that create the standards - and understandably so.<deep breath> They keep changing all the time, as the needs change. There is no ultimate standard that handles everyone's needs, or we would have a solid, definitive standard- and it would make sense to hold everyone to it. As it is, we use a different standard with just about every customer we deal with, and they are all US companies. We communicate with several VANs, some by dialup, some by VPN, some by sockets. We communicate with some customers via AS2, some using their own intranet ordering system, etc. The bottom line as Kammerer mentioned- Is do you want their business? The CEO and CFO here don't give a crap about EDI standards. Why bother with EDI if everyone doesn't stick exactly to the standards? Because if it can save you time and money, it's still worth it. Even if it would have saved you a bit more had they stuck to the standards. ;) Travis- -----Original Message----- From: Dan Mehlhorn [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 12:19 PM To: EDI-L Listserv Subject: RE: [EDI-L] Non-ASCII characters Travis, First, this is a company policy that was in place when I started years ago. Second, the X12 12.6 standard is well known. Third, and no one has answered this adequately, if you don't adhere to a standard, is it a standard? Fourth, the point is to stay within the standards to STANDARDIZE the communication. Otherwise, why not send and accept anything in any format? Why bother with EDI at all Travis? Dan -----Original Message----- From: Travis Truax Just curious- What is the point in creating a company policy to limit the character sets used to communicate with your partners? :) Travis- -----Original Message----- From: Philippart, Marianne Dan, My point was to show that indeed (some?) EDI software allow for handling of these special characters, the flexibility is there, whether companies decide to use it or not is a different thing. In our case, we have found easier to agree on the usage of some of these characters rather than requesting our trading partners to modify hundreds of product descriptions in their catalog in order to send us an 832. Marianne -----Original Message----- From: Dan Mehlhorn Marianne, I use TIE eVision Enterprise. As company policy we choose not to add characters like `, ^, etc. to the character set. Dan -----Original Message----- From: Philippart, Marianne [mailto:[EMAIL PROTECTED] Sent: Monday, April 04, 2005 1:45 PM To: EDI-L Listserv Subject: RE: [EDI-L] Non-ASCII characters Our EDI software does not cost half-million dollar and it allows us to add any character to the list of acceptable characters. If you are using eVision from Tie Commerce, this is easy to fix, I would be surprised if other products would not have some type of solution to this problem... Marianne Philippart -----Original Message----- From: William J. Kammerer [mailto:[EMAIL PROTECTED] Sent: Monday, April 04, 2005 2:30 PM To: EDI-L Listserv Subject: Re: [EDI-L] Non-ASCII characters You mean you'd tell Nestl� and Banco de M�xico or Hydro-Qu�bec or Petr�leos de Venezuela or Rh�ne-Poulenc or Peugeot Citro�n to take their business elsewhere just because you can't handle a few diacritics? If free e-mail can handle ordinary Latin characters, why not expensive half-million dollar EDI systems? William J. Kammerer Novannet Columbus, OH 43221-3859 . USA +1 (614) 487-0320 ----- Original Message ----- From: "Dan Mehlhorn" <[EMAIL PROTECTED]> To: "EDI-L Listserv" <[email protected]> Sent: Monday, 04 April, 2005 11:17 AM Subject: RE: [EDI-L] Non-ASCII characters This is one issue I've fought within the Electric Supply industry. One problem was when IBM AS400 machines would translate from EBCDIC to ASCII, some characters would not translate to anything usable. Some TPs insisted on using nonprintable characters within their defined as alphanumeric data fields. I can't recall how many times I've sent out the X12 12.6 table to new TPs, but they do listen when you tell them you can't do business if they keep using the barred characters. Dan Mehlhorn Crescent Electric Supply Co. . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> 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/
