I have little experience with TL for Windows. However, I am almost positive the answer to #3 is yes, but you need windows tools as you suggest.
I do have a suggestion, in case you haven't considered it, now might be the time to upgrade to TLE or to another product altogether. You don't mention specifics, but you do say the EDI and ERP have complex structures, perhaps migrating to a product more suited to those structures and more easily adaptable might be the way to go, thus preparing your potential client for further expansion/development. The one thing I do remember about TL for windows is that it's not really suited for a high volume environment. Another business consideration might be how willing GXS is to continue supporting this product, since they bought out Inovis. Perhaps one of our GXS colleagues who occasionally drop by might provide an answer? Good Luck, Leah ________________________________ From: Michael Mattias/LS <[email protected]> To: EDI-L <[email protected]> Sent: Thu, January 6, 2011 3:00:14 PM Subject: [EDI-L] Trusted Link Intrinsic Features? 1/7/11 OK, serious time... for those who are getting bored or disgusted with a little levity..... An associate and I have been asked to provide a proposal for a manufacturer located in "flyover country." This prospect is currently doing a lot of EDI using Trusted Link/Windows to support "rip and read" on inbound documents and "key in the data on the screen" for outbound documents. The prospect has decided it's time to look at an alternative to ripping, reading and especially keying. I would like to use the existing Trusted Link Software as part of the solution, but it's been like five or six years since I have done so and have forgotten some things. I was hoping someone reasonably current on TL could provide some straight answers. I do not need details; all I need to know is if these are *intrinsic* features of the Trusted Link software. 1. If you have a print overlay kit (Puchased from Trusted Link publisher or official support organization) for inbound documents, would you automatically have an application flat file definition for the "Convert EDI to Flat file" operation or would you have to develop that separately? 2. If you have a 'screen entry kit' for outbound documents, do you automatically have the application flat file definition for the "import from flat file and envelope an outbound document" operation? 3. Can you either/both automate (run on a schedule) or run from a command prompt (which you can automate with Windows' Scheduler or other products)... A) "Pick up documents from partner, convert to flat file" and/or B) "import from flat file, convert to EDI, envelope and send to partner" operations? (Above: you may substitute "export raw EDI" for "convert to flat file" for the inbound. I can use either) I am also interested in recommendations for any "flat file to flat file" mapping software products, suitable for use by a "junior programmer/sophisticated user." Since both the ANSI EDI and ERP interfaces in this particular case are fairly complex, I am thinking I will handle that part and leave a system which allows the user or his agent to "map customer specifics from simplified input/output formats." e.g., ANSI EDI and in this case the ERP interface both use deeply-nested hierarchical structures; I am thinking I will "flatten out" those structures into a simpler "header, line items, trailer"structure (eg like you'd use with Gentran mainframe or AS/400) and have the user maintain THOSE mapping relationships. A tool to maintain those mapping relationships would be nice. This tool would NOT need to support either ANSI/EDIFACT on the EDI side or anything very complex on the ERP sides of the map: I will handle the complex parts myself. If that tool supports "code exits" (any mechanism) it would quickly earn MANY "bonus consideration points." All responses appreciated. Michael C. Mattias Tal Systems Inc. Racine WI [email protected] [Non-text portions of this message have been removed] ------------------------------------ ... 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/
