----- Original Message -----
Do yourself a favor. Tell them what you can easily send and let them tell you whether or not this is sufficient. Yeah, that's pretty much where I'm at with this. Do them a favor, tell your customer you've never actually sent an ASN I've been saying that since we first started talking. and perhaps they should get more input from their other suppliers. I think that would hard from a sales posturing perspective on our side. Also recommend to them that if they could apprise you what data are critical for their business process, you would be better able to help in this partnership. Also what I've been saying :-) Be glad they're asking for your input instead of sending you some unreasonable PITA they got from googling. Leah From: Joe Matuscak <[email protected]> To: Michael Mattias/LS <[email protected]> Cc: EDI-L <[email protected]> Sent: Thursday, August 4, 2011 11:47 AM Subject: Re: [EDI-L] 856 design theory documents/web sites/books?? ----- Original Message ----- > 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. Well that's one of the stranger parts of this. I'm a sender, but the receiver is using us a test case and they have no specs. It's not clear to me that they even have a requirements definition for what their systems need/want for material receipts. We've been trying to architect our internal systems to support pretty elaborate 856 reporting, with stuff like our containers and pallets having SSCC-18 barcodes that we scan at pallet assembly, etc. However, this is the first customer that has actually asked for 856s and we still have some gaps in what we store in our internal systems if we needed to send what I would think of as "full blown" 856s. We've got enough other stuff on our plate that I'd rather not put the time into fleshing out our systems if they won't even use the data. > 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 This is kind of what I'm leaning toward proposing to them, but our shipments can have items from several of their purchase orders so I'm thinking of a "S-I" hierarchy with PO information under each of the items in a PRF segment. Does that make any sense? Or am I misinterpreting what the "O" level means? -- Thanks, Joe Matuscak Rohrer Corporation 717 Seville Road Wadsworth, Ohio 44281 330-335-1541 -- Thanks, Joe Matuscak Rohrer Corporation 717 Seville Road Wadsworth, Ohio 44281 330-335-1541 [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/
