Translator is the wrong place to validate item numbers. That's a business rule application. If you fail an item number in the translator, you have no automatic way to notify of the fail. 997 does not have a "hey this is not my upc" code.
Most users validate when they build orders. And i've seen them reject the entire order or fill what they can. It's a business decision. Some folks will send an 864 or 855, some will make a phone call. Some will repair the order, some will insist on a resend of the whole order or just the bad part. Again, business rules come into play here. For example, does the order still get a discount with bad items? You need to put on your BA hat and walk around and ask some questions. Then code appropriately.. Brian Lehrhoff, EA ([email protected]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html ________________________________ From: Thorsten Evans <[email protected]> To: "[email protected]" <[email protected]> Sent: Tuesday, February 14, 2012 9:58 AM Subject: [EDI-L] Inactive/invalid Item on inbound order I am trying to get a feel from this group what the best business practice is around receiving and processing an inbound order that was sent with an invalid item (assuming you are the supplier). Where do you deal with the item? Translator? Staging tables? ERP? Other? How do you deal with the item? Delete the line? Change to active/valid item? Have a non-inventoried item that indicates a bad item was sent? Other? Who is responsible for fixing the item? EDI person? Other IT person? Order management person? Other? How do you notify the customer? Auto email? Return EDI doc (like 855)? Phone call? Don't notify? Other? Based on how you handle inactive items, how would you handle it differently? Thanks in advance for feedback on this. Thorsten Evans EDI Developer GMCR [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 [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/
