I agree with everything that everyone has said so far. I also agree that the 'VAN fees' excuse is concerning and if we were in the 1990s the VAN fees may be an issue, but with today's van rates?
They really need re-negotiate their VAN rates if they are concerned about this, maybe they are still paying 1999 rates..:) I want to add my two cents on what the benefits are of sending the product description. The description has helped me with support, testing and reviewing of RAW EDI data with internal functional areas or on the phone with a trading partner. Sometimes it is easier to refer to the blue widget vs the red widget. Your trading partner does not need to map the product description data element across if they do not use it. In reality a lot of the raw data on any given transaction is not mapped across and what's mapped across to the application format file is what will be used in the ERP (however, you do map for all segments on the input side of the map). If you ever share your RAW EDI data internally (it's really not rocket science to read raw EDI data for non-EDI users) let's say for auditing or troubleshooting purposes, it's always handy to have the human readable description of the item there, as long as you do not use like an NTE or MSG segment for custom free form text. Also, just like Mike Rawlins pointed out, for the 944 it is not absolutely necessary, however on the purchasing transactions such as 850s, 860s and etc it would be strongly recommended because of all the issues companies have with item synchronization. Interesting topic. 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 Wed, May 1, 2013 at 4:17 AM, need2know711 <[email protected]> wrote: > ** > > > I'm would like to get the groups opinion on inclusion of description > fields. I recently created a 944 (warehouse stock transfer receipt advice) > specification and I included the line item descriptions. My trading partner > resisted, and felt they were not needed since we passing the part number > ID. I like to include them as sort of a double check in any issues arise > with the part number. My trading partner felt we could save the extra VAN > cost if we did not include them and that they were unnecessary. Whats the > groups take on descriptions? > > > [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/
