One solution I came up with worked when a customer was consistent with their SKU errors: I created a customer SKU cross-reference table. Then we tweaked the Order Import process so that when a SKU validation failed against the Item Master, the process attempted a look-up in the SKU XREF table: First by ship-to, then by customer, then a general look-up. The original SKU was stored in an extra field in the sales order, which was passed on to the ASN and the Invoice interface files. Then we mapped those extra fields to the outbound product code. The problem we ran into was when the customer placed a phone order. Then we didn't have the "original" SKU for the invoice. Solution? They outsourced EDI before we addressed that one, so I have no idea.
Art Douglas Lead Consultant Blackwater Network (877) 464-8915 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Holt, Jake Sent: Tuesday, September 16, 2008 12:49 PM To: [email protected] Subject: RE: [EDI-L] <Random venting?> Resending... you what? I hear what you guys are saying, the only problem is I run into exactly what Art said. They just expect me to accept and adjust it but then it delays everything down the line. If I correct the issue, now I have labeling problems (which I get to handle too), ASN problems, etc. and we all know where that leads (hint: $$$$). Generally we can challenge the fines but that costs money too. I would be fine if they didn't "resend" a PO since I can understand that's a no no for some people, but certainly I would think implementing an EDI solution to the problem would be valuable to both parties. That PO hold is a pretty solid Idea, and it could tie right into my current validation engine. Amazing how you can miss the simple answers in favor of the complex ones that make everyone mad =). Now I feel better... until next week when someone else does it. From: Dale Marthaller [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2008 12:47 PM To: 'Art Douglas'; 'Earl Wertheimer'; Holt, Jake; '[email protected]' Subject: RE: [EDI-L] <Random venting?> Resending... you what? We have the mother of all hybrid systems. We receive EDI PO's with vague and/or incorrect UPC's, determine and ship the correct ones billing the customer back with their own UPC codes. We are lucky that our product's packaging does not have bar codes on them. Dale Marthaller [EMAIL PROTECTED] The Oppenheimer Group expect the world from us From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Art Douglas Sent: September/16/2008 10:26 AM To: 'Earl Wertheimer'; 'Holt, Jake'; [email protected] Subject: RE: [EDI-L] <Random venting?> Resending... you what? If the customer sends an incorrect SKU, part number, UPC, etc., and the supplier "figures it out" and creates a sales order with the correct part number on it, ships it, and invoices it, then dollars to donuts the customer's A/P department will delay payment because "the PO doesn't match the invoice." One of the big advantages of EDI is that it forces trading partners to synchronize their product catalogs and price lists. If they don't, then things won't work as they should. My initial response to Jake's dilemma would be to reject the order. But on further consideration, I think I would recommend placing the order on hold pending a PO Change, replacement order, etc. A verbal "okay" from the buyer is insufficient. The buyer _never_ informs his/her A/P department of the change. This rant also applies to pricing, quantity, changes etc. If it is not in writing or EDI, the approval for a change doesn't exist. Art Douglas Lead Consultant Blackwater Network (877) 464-8915 -----Original Message----- From: [email protected] <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Earl Wertheimer Sent: Tuesday, September 16, 2008 10:02 AM To: Holt, Jake; [email protected] <mailto:EDI-L%40yahoogroups.com> Subject: Re: [EDI-L] <Random venting?> Resending... you what? Jake > If a customer requires me to correct and resend any document that they > can't process due to an error (which isn't a problem), shouldn't they be > able to do the same when they can't get a UPC right to save their life? They are the client. If it becomes too expensive to handle their requirements, you can add the cost to their prices or ask them to go elsewhere. I would suggest a bit of gentle training. "Garbage In, Garbage Out" still applies. If they cannot submit the correct UPC to you, then you always have the option to reject the PO and send them a notice that they are wrong, ship them the wrong goods, or correct it yourself... > Email is a good way to resolve errors on POs, right? anyone? It depends on the error. If there are turnaround documents from the 850 (ie. Invoice or ASN), then the email will not correct the error on the PO. Email is a good way to explain a problem and supply a backup, but nothing can beat a correct PO ;-) Earl Wertheimer [EMAIL PROTECTED] <mailto:earlw%40spe-edi.com> http://www.spe-edi.com ------------------------------------ ... 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 ------------------------------------ ... 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/
