Hmmm... I took this thread all the way back to the original post Adam made...
A lot of posts have flown around - answering the question and then with other questions asked. I think, first, however, we may need to know what industry Adam is working in before we can truly answer any of his questions.... So, Adam, not giving a "who" - but what type of EDI are you doing...? Working for a retailer and dealing with suppliers and manufacturers? Or are you in a manufacturing/distribution company that deals with retailers...? Or in a total other industry that uses EDI - medical, schooling, banking, real estate, automotive, etc., etc., etc...? In the retailing world, yes the 850, the 856 and the 810 are the "big 3"... but then you will also have the 997 (Functional Acknowledgement) and some would also add the 860 (PO Change) and a few other documents to the "regular documents" side of the equation. Then the next post you make - also below - seems to Me that it hints at maybe you're working for a manufacturer or distributor of CPG (consumer packaged goods)... If you're having issues with the 850 PO and none with the 856, it makes Me wonder which you're receiving and which you're sending. Seems to Me that you'd be receiving the PO from your customers and sending them the ASN. And then following it up with the Invoice. Now, having said all of that... I work for a fairly big retailer (well over $900 million in annual sales, over 400 stores, etc., etc., etc.) and I am the EDI ... department. I do it all - from mapping to monitoring - and all the rest. We currently trade the 850 PO and the 856 ASN and the required 997 documents and I've created and have been testing and will start the 810 Invoice in 2009. I have no problems with My outbound 850 POs. Sometimes, there may be an issue with a UPC - in that our buying department doesn't get the correct one - OR - the product is changed somehow (enough) and the UPC is now changed for the product and we don't get the new UPC or the buying group puts the "new" UPC into the wrong place in our system and the PO process still picks up the old... The 856 - we do have some issues with the ASN coming in. Or at least so I've been told... When the ASN is translated properly - i.e. no errors - and moves through to our production side, the only issues may be if the "virtual cartons" on the ASN do not match the physical carton that arrives on our dock. If the vendor does not put our SKU on the ASN (which we provide in the PO and can also send a listing of current SKUs, if needed) - then it may fail in translation... Also, if a vendor puts incorrectly formatted data (alpha/numeric instead of numeric) or incorrect codes in some elements, it will fail in translation and never make it to production. We do not issue chargebacks - yet - for bad EDI data. However, as we move forward into the invoice process, it may become a policy of our accounting group to start them... Mentioned in one of the posts is a comment about "HUGE ALLOWANCES" to which the vendor may not be eligible... That's a very ... ambiguous ... statement, at best. I wonder how many retailers would send allowances to which they are not eligible. Again, as a retailer, we make VERY sure that any of our allowances (of which we get a lot) are correct and proper. If there is a "year end" allowance (rebate) based upon the dollars ordered throughout the year - that is something that doesn't get sent via EDI - as it's not an "order by order" kind of allowance. It's a rebate and needs to be calculated off of the ordered product through the year, and you just can't really do that on an EDI document... Well, you can, but... The biggest issue I see with allowances is how the vendor/supplier calculates and applies the allowances. In our case, we send the posted cost of the item (list) and then separate SAC segments for each line item, as we may have some allowances that do not apply to all items on an order. We also send the quantity being ordered (obviously), so it becomes a simple process for the vendor to just do the calculations on their side to properly invoice us the amount owed with allowances (and charges!) applied. If we're ordering 1000 items at $10.00 each, but we get 1% allowance for defective, then the vendor's side needs to do the calculation that "nets" the cost of each item at $9.00 and totals the invoice at $9,000.00.... I'm pretty sure that even the most rudimentary ordering system can process the math... If you can multiply 10 times 1000 and come up with 10,000, then why can't you multiply 10 by 1%, subtract that 1% and net the cost at 9 and multiply by 1000? And then finally... as to the concepts of insults and insinuations... Adam, I'm sure you've been around here enough to understand that there is a lot of ribbing(good natured, usually) and sarcasm that gets thrown around. Michael has been on here for years and is a valuable source of information... just as Art and Leah and Richard and many other of the regular posters can provide great info. Sometimes, however, you may have to dig through a bit of humor (ill or not) and sarcasm to find it... EDI is a very simple process, really. It's taking some data (information), processing it into a format that is transmitted, and then processing the data into your own system. Then turning that data around and sending it back - in a different format - to be processed again into another system. Craig E. Dunham EDI Coordinator EYE Analyst Some major retailer... Original messages: the Big 3 - 810, 850, 856 <http://groups.yahoo.com/group/EDI-L/message/23938;_ylc=X3oDMTJyZTBiam8yBF9TAzk3MzU5NzE1BGdycElkAzIxMDc2NzYEZ3Jwc3BJZAMxNzA1MDA1NTgyBG1zZ0lkAzIzOTM4BHNlYwNkbXNnBHNsawN2bXNnBHN0aW1lAzEyMzA0NjIzMjM-> Posted by: "Adam West" Sat Dec 27, 2008 3:52 pm (PST) Hi - Am I correct in stating the big 3 documents in EDI are 810-850-856? I recall in my programming of these documents some issues to be concerned about were sending wrong data, as well as receiving wrong data. That is, even if the customer sent in bad data, for example some bad UPC number, if we did not rectify this situation, we get the chargeback. This has happened many times here at work. or for example, if the sent their data in such a way as to get a Huge Allowance rebate more than they are supposed to. I cannot recall similar problems with the 810 but am sure this exists. Am interested in hearing like cases of problems and situations you have had to deal with in these 3 documents, or anything else which is used in the Manufacturers side as well. Re: the Big 3 - 810, 850, 856 <http://groups.yahoo.com/group/EDI-L/message/23943;_ylc=X3oDMTJydjc0YWtlBF9TAzk3MzU5NzE1BGdycElkAzIxMDc2NzYEZ3Jwc3BJZAMxNzA1MDA1NTgyBG1zZ0lkAzIzOTQzBHNlYwNkbXNnBHNsawN2bXNnBHN0aW1lAzEyMzA1NDc1NzA-> Posted by: "Adam West" Sun Dec 28, 2008 6:50 am (PST) What are some of the typical issues you are seeing with the 856? At my current job, they do work pretty well, as opposed to the 850's. [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/
