> By a "Pre-Mapping" document, I was hoping someone had already created a
> document for Syteline mapping that would clarify where to map the various
> ANSI elements to the various flat file fields.. This is usually done in an
> Excel
spreadsheet.
>.....
Um, that is not possible.. because each document specifier (the developer of the
Implementation Guide)
has the freedom to select the
exact
segment and element in which various pieces of applications data are
actually sent.
For example, while the PO1 segment is used in the '850' and the LIN segment in
the '830' to convey "part number", both segments
allow multiple occurrences of the item identifier... e.g., you can send the
item identifier as a vendor part number, a buyer part
number, a UPC code... or could send them all... and you could send them in any
order... not to mention, different recipients may use
different identifiers regardless of which identifiers are sent.
> Some flat file definitions I've mapped from in the past have, reference the
> various
EDI elements that the data should be populated from. The wording in
> the documentation I have from Syteline doesn't provide any type of guidance
> as to what elements should be used to map to the flat file.
Any "segment-element to flat file map" is perforce implementation-specific; it
is IMNSHO totally silly to create the flat file
documentation in any terms other than "business data element" terms such as
"part number", "quantity" and "date."
That said, anyone who has been around the block more than once with these
documents would know (SHOULD know!) that if the flat-file
doc says "Populate from segment PO1 element 7" it really means "populate using
the item identifier from elements 7, 9, 11, 13....
25 as appropriate to your application requirements."
Michael C. Mattias
Tal Systems Inc.
Racine WI
Cart
