Joe, I'm right there with you, man. The shipping process, 856, and UCC labels are like the Bermuda Triangle for us. I'm just glad I don't have to deal with any healthcare-related stuff, since I hear plenty of groans about that stuff on the list. The shipping folks want their process to be a certain way, without too much complexity or they don't have enough time in their ship window to get the product labeled and on the truck. The ASN requires the back-end data be in a certain structure, or it's of no use. It basically feels impossible to satisfy both sides without developing our own software. We're still using an out of date piece of junk ASN add-on software package because our ERP has some major shortcomings. I've drawn up countless flow charts and concepts to try to bridge the gap, and I've never gotten there. It's the hierarchy part that always gets us - our software doesn't handle it without a boatload of trouble for the shipping team.
If you just have problems with the mapping side, we have far more problems than you... Hope you find a solution. Travis- ----- Original Message ----- From: "Joe Matuscak" <[email protected]> To: "edi list" <[email protected]> Sent: Thursday, August 4, 2011 9:44:45 AM Subject: [EDI-L] 856 design theory documents/web sites/books?? 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? -- Thanks, Joe Matuscak Rohrer Corporation 717 Seville Road Wadsworth, Ohio 44281 330-335-1541 ------------------------------------ ... 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/
