Complain, complain ... here's your basic design (see below). As we've learned from too many engagements - if you don't have data, you can't send it. If you can't add it, you can't send it. If your partner really needs those invoice numbers (800 pound gorilla requirement) you may
need to rethink your SAP processing flow to get them. There's nothing new under the sun about 856. Pick-pack or standard pack? That's usually the only variance. Here's the "golden rule": 1. what's on the truck? (ship level) 2. what orders/invoices are on the truck? (order level) 3. what pallets are on the truck? (maybe) 4. what cartons are on the pallet? (carton level) 5. what's in the box? (item level) Only thing you really need at the carton level is the UCC128. Item level can be as simple as UPC and quantity. When in doubt, follow the KISS rule. Brian Lehrhoff, EA ([email protected]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html ________________________________ From: Michael Mattias/LS <[email protected]> To: EDI-L <[email protected]> Sent: Thursday, August 4, 2011 11:07 AM Subject: Re: [EDI-L] 856 design theory documents/web sites/books?? 8/4/11 > I'm in the process of working through a design of an 856 transaction and > I've been looking for something that would describe generic design > considerations > in the implementation of an 856. Things like how what makes sense for the > hierarchy, etc. I've Googled around and while I've found lots of > organizations > implementation guides, I've not found anything that really addresses sort > of > addresses the zen of how to build an 856. > > Does anyone have any pointers? Are you designing this as the 'sender' or the 'receiver' ? If you are the receiver, well, you know what you want in terms of application data If you are the sender, ask a few potential recipients what pieces of info they would like. I have worked with literally scores of ASN implementations over the years ... all across the board as far as 'how much info' to transmit. Some folks like "lots of detail".... addresses, mulitple part numbers, part descriptions, additional pricing info, invoice number, yadda, yadda yadda... yet some want minimal data... eg one party wants.. Date shipped Carrier, pieces and weight Pro/tracking numbers Then items... Po#, PO line number, qty shipped this item ... ONLY. No part numbers, no descriptions, no nothing else. About all I could suggest is you stick to one of the 'common' hierarchies... S-O-I (no package detail eg you don't barcode ("license plate") cartons S-O-P-I ("pick and pack") S-O-I-P (only if you only ship/receive in standard packs) (Personally I still don't understand the use of the "order" hierarchical level...you can always put the PO number in the LIN segment at the item level.. but EVERYONE seems to 'insist' on a discrete "order level" in the 856). ..because your partner will be most familiar with those organizations; and use the optional CTT controls totals segment elements one (HL count) and two (sum SN102). Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... 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 <*> 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/
