If the customer requires certain information then the application creating the 
file should make it mandatory for that customer. In the typical EDI world, EDI 
receives the file, translates and sends to customer. Anything mandatory from 
the application should be marked as a mandatory record in the application. If 
it's not, EDI ends up owning something that really isn't an EDI issue. Right? 
Even if you sync now, you will be out of sync in the future if the application 
doesn't own the customer data requirements in order to produce consistent data.

Did I misunderstand? Where does this data come from? Manual entry or is it from 
a file that the customer is sending to you?

-Ashlie

  ----- Original Message ----- 
  From: Narayanan Bharadwaj 
  To: edi list 
  Sent: Thursday, February 03, 2011 7:07 PM
  Subject: [EDI-L] customer info sync up


    
  Hi all,one more topic in the same week:-)We are a disty and this request came 
from our vendor.The basic issue is that  - we report the end customer 
information in the EDI messages (867/POS, 852/sell through) to the vendor. 
However, the structure/format of the end customer information is in our control 
and is definitely not consistent. The vendor is running some analysis and 
generating some reports on their end based on the end customer information.So, 
they are having lot of "unidentifed" records on their end which is a pain to 
manage. They are proposing to sync up the end customer information on both 
ends. Their first proposal is to use 816 message.
  816 is for sync up of addresses, so we are not sure if this is the best 
option for us.I just want to get a feel from the group about what is the best 
way to  go about, in this situation.
  Please share your opinion.Also, if you have any other out of the box 
alternatives, please do share.
  Thanks in advance for your help.Take careNB

  [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

<*> 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