There's nothing inherently "un-real-time" about traditional X12 or EDIFACT EDI, and I suppose any of those transaction sets would do for pricing. But why not skip the X12 altogether if no customers are calling for it specifically? Why not look at RosettaNet, EAN.UCC XML or OAGIS messages instead? Then you'll have "real" XML-based EDI which can be used with a modern real-time transport protocol like SOAP or ebXML messaging services.
William J. Kammerer Novannet Columbus, OH 43221-3859 . USA +1 (614) 487-0320 ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, 11 February, 2005 11:42 AM Subject: [EDI-L] edi pricing transactions My company is expanding our real-time pricing transaction and we are considering whether or not to try to include EDI in our offering. I would like to know whether or not anyone knows of EDI being used this way (the 503, 832, and 879 seem likely candidates). If so, how common is its usage? Is the ability to create one of these as common as the ability to create an 850 among businesses? I'd appreciate any insight you might have. Thanks, Matt Pierce . 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/
