Just my personal bias but I always make an industry subset but not multi-version, not
multi standard. Yes, you can
make a single type tree per transaction per version but you could run into the same
problem I ran into last week when
contrary to my recommendation the client wanted one version-one transaction type
trees. They found out that Mercator
uses a very conservative, but nonetheless correct, interpretation of what correct
segment terminators are. As a
result they now need to modify or replace several dozen type trees and, of course,
recompile all there maps after they
add the segment terminators that are used in the REAL world.
Separating the type trees actually makes upgrading more difficult. I have discovered
probably one error per year for
the last three years in Mercator ANIS X12 type trees. By rights, whenever Mercator
releases a new version, e.g., 5.1,
you should re-create your type trees to include any possible corrections Mercator has
made. The more finely you have
sliced and diced the type trees, the more type trees you will have to re-create.
There is NO WAY to re-specify the
type tree from within the IFD. The type tree is only referenced in the Map Designer.
Jim Divoky
EC Solutions, Inc.
PO Box 667
Kent, OH 44240-0012
Providing EDI/EC Consulting and Contracting Services
Mobile 330-606-6826
Pager 877-282-3426 (Toll free)
Email [EMAIL PROTECTED]
To send short message to mobile phone:
email [EMAIL PROTECTED]
----- Original Message -----
From: "Richard Druckenmiller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 30, 2001 6:02 PM
Subject: Mercator's IFD
> For the Mercator knowledge workers:
>
> With Mercator's integration flow designer (IFD) do you have to worry
> anymore about deciding between making industry-subset, multi-version,
> multi-partner, or multi-standard type trees anymore. i.e. Can you just
> make one type tree and one map for each trading partner's document. In
> my opinion having maps seperated makes it a lot easier to upgrade them
> in the future. With the IFD you could then hook all these together to
> read the same source and target could you not?
>
> --
> Richard Druckenmiller
> [EMAIL PROTECTED]
>
> =======================================================================
> To contact the list owner: mailto:[EMAIL PROTECTED]
> Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
>
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
