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