I agree with Michael.. What you need to do is have a discussion with your technology team and WMS folks (Warehouse Management System) to see what is needed.
>From there you can put together an application layout that your data will get >translated to. >From there you probably need to reach out to a larger company who already is >EDI capable and get their EDI 856 spec to determine what they will be sending >you and if the content matches what you need for your internal needs. In a >lot of cases, the larger companies already have an established 856 layout >which you won't have much luck in changing. >From there you can work to set up your first map, then establish a testing >phase with your TP. After you have set up some existing 856's from others, you can then start to work on establishing your own specs.. But for the 'big boys' in the industry, you'll have to use their existing 856 specs. Hope this helps. Ken [email protected] ________________________________ From: Michael Mattias/LS <[email protected]> To: EDI-L <[email protected]> Sent: Wednesday, February 22, 2012 8:34 AM Subject: Re: [EDI-L] Re: Create ASN 856 >> > I'm new to this form and new to EDI. I would like to obtain some >> information on how to create ASN 856 EDI specifications for the company >> I work for. I've scoured the internet for any general specifications for >> ASNs ..... An ANSI ASC X12 856 or EDIFACT DESADV is a "document" , pure and simple. What info would you ask for were you asking your vendors, "Please fax me a notice of shipment when your truck leaves?" Well, you want the exact same info on your electronic document. It's just a document! So where are these various pieces of info "conventionally" conveyed in an '856' document? If you've looked at the other IGs, you will have noticed the same data are are pretty much all conveyed in the same loops, segments and elements and they only thing whch really changes are code and qualifier values. You'll want to ask your vendors to convey the shipment info in the "conventional" loops, segments and elements... unless you want a rep as a PITA customer. (That is, when your letter goes out with the salutation, "Dear Valued Vendor" you should mean it!) Michael C. Mattias Tal Systems Inc. Racine WI [email protected] [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/
