Mike,
You are always quite direct when answering on this list. So, I will do the same. The process you describe seems to be unnecessarily complex. Our many years of experience with TrustedLink has resulted in the development of highly efficient and accurate routines that respond to these questions- are the suppliers creating serialized container labels such as UCC-128, B-10, PDF417? How are these labels generated? How are the serial numbers being captured? How are the carton contents captured? If the ERP system cannot handle the ASN information, it seems reasonable to seek a simpler, field proven bolt-on ASN system for TrustedLink and the ERP. The problem with using TLW forms with flat files is that each trading partner will need a different flat file format. Please consider contacting Amy Rubin at GXS Inovis ( <mailto:[email protected]> [email protected], 301 340 5108) and ask about the ComplyLink automated bolt-on for TLW and many ERP's such as JD Edwards, SAP-B1, MAS200, Peachtree and many more. The ComplyLink ASN / UCC-128 system can used with any EDI translator. If your customer decides to move to another translator or to integrate to an on-network translator solution, their investment is protected. Feel free to contact me if you have any questions. _______________________________________________ Regards, Todd LaBonte Phone: 231-933-7212 Fax: 231-933-7236 e-mail: <mailto:[email protected]> [email protected] Web-site: <http://www.e-supplylink.com> www.e-supplylink.com e-SupplyLink . exceptional Supply Chain Solutions From: [email protected] [mailto:[email protected]] On Behalf Of Michael Mattias/LS Sent: Thursday, October 27, 2011 12:04 PM To: EDI-L Subject: [EDI-L] Trusted Link question 10/26/11 Using Inovis' Trusted Link for Windows, is it possible to programmatically create some kind of file which can then be edited using the regular (kit installed) TLW "Data Entry" entry screens for outbound documents? Here is my situation: With help I received here some time ago, I put together an application to extract invoice information from the client ERP system, create the required TLW 'Flat file', and we now use the TLW "Flat file to EDI" function to generate an '810' invoice and send it. Everyone is insanely happy with this, as it replaced hours each week of manual entry of invoice data using the TLW screens. The client is currently using TLW "kits" to perform "data entry" for ASNs; this, too, is time consuming. He has all the information required for Data Entry on paper (fill-in-the-blanks stuff from the shipping dept).. but not all the information on paper makes it back to the ERP system from which I could extract it. . We want to do the same thing we did for invoices with ASNs .. EXCEPT... we have the "missing shipment information (paper only)" hill to climb. I was thinking there are two ways to do this: 1. Create "something" to allow manual entry of only the "missing" information; then create "something" to merge this manually-entered information with the data which are available from the ERP system and create the TLW flat file as we did for invoices. 2. (preferred) Obtain from the ERP system the information which *is* available, and put that into "something" which would result in an "editable" TLW form for the user. I see there is an "open partially filled form" function in TLW which kind of sounds like what I am looking for, but I don't like assuming things like this. That is, the user would ONLY have to use TLW data entry to enter the few pieces of info which currently exist only on paper. I'm also looking at "a third way" to accomplish the goal (eliminate as much manual entry as possible), but that totally cuts TLW out of the picture so I am not detailing that here. I am right now open to any of these three options (and would be open to any more) but before I commit to anything I'd like to know if my "partially-filled form" (option 2 above) option is viable because right now that is the most attractive. Any and all guidance/pointers will be appreciated. Thanks, Michael C. Mattias Tal Systems Inc. Racine WI [email protected] <mailto:mmattias%40talsystems.com> [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/
