I let the translator pass it to my ERP, it will generate an error that Customer 
Service will have to deal with as they see fit.

I firmly believe that EDI should not get involved in trying to figure out why 
any customer ordered an invalid part and then trying to resolve the issue.

JMHO.

Bob Scheuermann



---- Thorsten Evans <[email protected]> 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]
> 



------------------------------------

...
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/

Reply via email to