There is still the problem with outbound documents when an item fails and that is why I insist that the order be fixed, not just the item. Some retailers require certain orders be shipped complete and any inbound error may ultimately put the outbound documents out of sync with the inbound. Unless the retailer updates his/her copy of the order with the same changes you make to yours, there could be problems. On the other hand, there are times where a new skew is entered incorrectly so I might check the ERP system and see what it contains. I then e-mail customer service and see what they want to do about it. If it is a simple correction then I will wait for them to make it and resubmit the order. Scope of the problem: Most Pos will have an expected ship date and cancel date. During regular business hours these issues can be solved quickly. However, if they happen overnight or on a weekend you may have to consider what kind of notification you want to provide. I once handled EDI for a food distributor and nearly everything that was ordered had a two day window. Much of the ordering was done over the weekend for Monday shipment so I had to check the system several times on the weekend. More than once I had to get customer service involved in order to get the failing Pos through. So to expidite any new skews I requested a list of them every Friday and double checked ERP to make sure they were entered properly. I realize that this was not in the job description but it sure eliminated a lot of weekend holdups.
I keep one thing in the back of my mind: There are not customers who do EDI, they are EDI customers. And with that I proceed accordingly. Sincerely, Jason McMahon 8079 Village Drive Cincinnati, OH 45242-4315 [email protected] http://gutausse.weebly.com/articles.html http://gutausse.blogspot.com http://www.linkedin.com/pub/jason-mcmahon/11/743/51b -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Records Sent: Tuesday, February 14, 2012 10:14 AM To: Thorsten Evans Cc: [email protected] Subject: Re: [EDI-L] Inactive/invalid Item on inbound order Thorston, A bad item number needs to be dealt with in the ERP by the Customer Service group. At the EDI level, you have no way of validating an item, nor should you in my opinion. There are different approaches that have been taken by different clients. One was to map each item to an separate doc to load into the ERP, that way one bad item record would fail, not the whole order. The second one was where I did the ERP side of it and put the bad item number in the description field and used a generic term like "BADITEM" or something similar that would be flagged in the order and the order would not be confirmed until a CSR contacted the customer to resolve the issue, usually by phone or email. These two ways I mentioned worked well for the clients I set it up for. One way holds the whole order up until the issue is resolved, the other only holds the bad item up until it's resolved, but in every case, the resolution belongs to a CSR, not the EDI group. Regards, Dave Records Records Consulting, LLC Email: [email protected] On Feb 14, 2012, at 9:58 AM, Thorsten Evans wrote: 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] [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 ------------------------------------ ... 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/
