Wow...! The "retail guru"...! What a great title... I think I may just add that to the signature block I use!
Truly, Tim and Art may have well answered your question... But, as has been said - the Inovis translator (TrustedLink) is just a translator and can sort through the data you're receiving (be it an 832 or whatever) and populate your end system with said data - as long as the end system is capable of accepting that data and using it. The data is, to the translator, just the data. Whether it's a UPC or a GTIN or whatever - it's all the same to the translator - it's just numbers and letters that go ... someplace. So, in that regard, I guess you could say that the translator is .. compliant. When I'm explaining what TrustedLink does to non-EDI thinking people, I usually just liken it to a traffic cop or one of those guys in the parking lots when you're going to some concert or Disneyland - where they're just directing the flow of traffic (i.e. your car) into a specific spot... The translator takes the data in (UPC number) and then puts it into the field in the file and record you specify in the translation format... So, it's kind of hard to answer that question directly and with any great, perfect-fit, 100% correct answer. Currently, our buying group receives UPC information in a variety of ways from a variety of sources: * Inovis Catalog * Vendor website * Vendor e-mail * Excel spreadsheet e-mail * Sales Rep agency contact * Etc., etc., etc... They get it in a written form and then manually enter it into our system. And our system is not currently set up to accept the 13 digit UPC, let alone the 14 digit GTIN entry. We're "locked" at 12. Now, mind you, since we're the retailer (we're Home Depot), we're sending out the PO with the UPC that we have in our system. If the vendor is using GTIN or the 13 digit UPC, we're still only capable of sending them 12. And we don't really use the UPC that they send back on the ASN - we're based upon our own SKU so the UPC is nearly irrelevant. Does this help or yet confuse the issue all the more...? Craig E. Dunham EDI Coordinator EYE Analyst Retail Guru Home Depot and Global Data Synchronization EDI? <http://groups.yahoo.com/group/EDI-L/message/24008;_ylc=X3oDMTJyMDE1NXE5BF9TAzk3MzU5NzE1BGdycElkAzIxMDc2NzYEZ3Jwc3BJZAMxNzA1MDA1NTgyBG1zZ0lkAzI0MDA4BHNlYwNkbXNnBHNsawN2bXNnBHN0aW1lAzEyMzEzMjUzNDA-> Posted by: "Leah Halpin" Tue Jan 6, 2009 10:45 am (PST) Hi All, I've had an interesting question posed to me about Home Depot and GDS Global Data Synchronization. A client has asked if the Inovis translator is compliant with GDS Standards. Now, I did a little googling and I even called Big Hammer (love that name) who is HD's "preferred vendor" for this process. Since they've told me that they don't accept 832 Catalog or any EDI, rather they use excel spreadsheets and or data entry, I'm having a hard time understanding how a translator (any translator) could be either compliant or non-compliant. If the "synchronized" data is being sent in EDI between customer and supplier without having to go through some third party doing some fancy schmancy data conversion, as long as the ERP is capable of interpreting and returning the data, if required, on the ASN, it's no different from any other piece of data, right? Am I missing something here? Craig, you're the retail guru, what am I missing? Thanks everyone, Leah [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: mailto:[email protected] mailto:[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/
