Gerald -
I have worked with the ASN (856) document several times. IMO, it is one of
the most complex EDI documents, since it contains hierarchical levels.
When I did it using the old Premenos EDI package, I created multiple
database files with several common key fields (depending on the hierarchical
level, keys were shipment #, and trading-partner ID, order number, carton
number, and item number) and used a multi-format logical file over the
header and detail files in order to arrange the hierarchical information
into the order required, since there is shipment-level, order-level,
pack/carton-level, and Item level information contained in the document, as
well as barcode information at all levels.
Sorry I can't be more specific, but you should be able to ascertain your
data structure by viewing your trading partner's requirements document.
Here is one example of a trading partner's requirements document:
http://www.wakefields.com/edi/EDI856.html
- sjl
Gerald wrote:
You are correct, (and you are correctly confused by what I wrote).
I do need to wind up with a list of records in a delimited file format.
The two current programs use data structures, allowing for either zero
fill, or blank fill to the "standard size" of the fields. (I'm told
that the data structures are "self documenting")
It may be the very best for me, to just start from scratch and evaluate
the string.
midrange.com
