Lissa,
It's not sufficient just to have some names of vendors. First, you must have
a set of requirements for such an EDI mapping tool. In my EDI workshops I
provide a random list of potential functional requirements, some of which
may not be applicable to everyone. I've inserted this list below. With this
in hand, you should be able to determine what your company's specific
requirements are. This will give you evaluation criteria as you gather
vendor names and examine their products.
Good luck,
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http:/www.rfa-edi.com
Automated Mapping Tools
Functional Requirements Checklist
Graphical user interface
Capability to map native application formats directly to standards
no intermediate formatting or programming
Ability to simultaneously gather & manipulate data from internal data stores
as well as multiple incoming transactions
Simultaneous reference of multiple files or databases
Ability to read one transaction & update many files
Creation of multiple transactions from one transaction
Ability to flag data to be stored for later processing within a transaction
Ability to go from any level on the source transaction to any level on the
target transaction
Ability to combine or separate fields
Ability to map the envelope data as well as the transaction data, e.g., ISA,
UNB, X.400, SMTP/MIME
Ability to tailor mapping logic with exits for user-defined processing,
i.e., support user exits at data element, segment, transaction or group
levels
Support for database, table and file lookups
Support to handle complex data restructuring tasks
Support for unique trading partner processing within a map
Ability to share processing rules and user data among maps
Support for conditional tests, e.g., loop processing: if/then/else;
while/do/then; and/or
Support for relationships between fields, e.g., greater than, equal to,
equal to or greater than, not equal to, less than, equal or less than
Data element and application field checks
presence of data in a field or part of a field
empty field
check accumulator value
check positive or negative values
Ability to flag fields as a result of inter-field relationship checking
Ability to access system information, e.g., current date, time
Ability for the runtime mapper to report activities to an audit system
Availability of mapping reports
Ability to copy a map or application data format to create a new map
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
