|
In many cases, info other than signatures are noted directly on the invoice: missing, damaged, or refused items (partial or full qty) unexpected return items (no pickup invoice) payment info (cash or check)Having all this matching on both customer & driver copy very important. Maybe I should
not have called this just a "signature".btw-in reference to another post - barcoded & scan to image server in the plan upon return to the office.
jim franz----- Original Message ----- From: "Michael Ryan" <michaelrtr@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, November 15, 2006 9:33 AM Subject: Re: replace multi-part invoice form
Let me just throw another piece of technology into this discussion -signature capture devices. They're getting pretty cheap, and the software is reasonable to write. You can do it with a PDA, and then print the signatureon as many copies as you want. On 11/15/06, daparnin@xxxxxxxxxxxxxx <daparnin@xxxxxxxxxxxxxx> wrote:Future3 is the EDI/shipping document package that we use but it does invoices, both printed and electronic. Their overlay solution is to do overlays with forms designed with Adobe designer. If I recall correctly,under the covers it generates a normal spool file, copies it to a databasefile, and then generates another spool file with the overlay. It's kind of a roundabout way of doing it but it works. It does have the advantage that you can if you have the Designer product you can specify fields in the overlay form that you can reference from their configurable interface code. That might be handy if you do a lot of EDI-related forms printing. If not, it's probably just a lot of extra work.Personally, if you've got a simple RPG invoice program, either in-house ora package, I would recommend creating an overlay and specifying it in an AFPDS printer file. It's pretty easy to design an overlay in Microsoft Word (or your favorite PC application), print it to a file using IBM's free AFP printer driver, upload it to the system, and create the overlay from that. The hard part is getting everyone to agree that it's OK to print multiple copies instead of using mult-part forms. Dave Parnin -- Nishikawa Standard Company 324 Morrow Street Topeka, IN 46571 260-593-2156 ext. 621 daparnin@xxxxxxxxxxxxxx Darrell A Martin <DMartin@xxxxxxxxxxx To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> om> cc: Sent by: Subject: Re: replace multi-part invoice form midrange-l-bounces@m idrange.com 11/15/2006 08:32 AM Please respond to Midrange Systems Technical Discussion Dave: We are moving in exactly the direction you did. It wasn't a case of scrapping our two 4234s; one has died outright and the other has ... coughing fits ... at times. However, we need another "layer" of printer control like Bullwinkle needs a hat rack. How easy -- really! -- is it to set up, use, and maintain the Future3 program? Is spooled/queued output managed only on the iS/400 or are there also other print queues to deal with? In anticipation of your answer, I will wander off to the 'Net. Darrell Darrell A. Martin - 630-754-2187 Manager, Computer Operations dmartin@xxxxxxxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 11/14/2006 02:47:11 PM: > > We scrapped a txinax dot-matrix printer earlier this year that was used for > invoices. (No more twinax--YEA!!!) Our invoices print out of Future3 from > Infor which generates a spool file and merges it with an Adobe overlay. In > a former life I did bills-of-lading that had been multi-part but were > switched to multiple copies of overlays on plain paper. The truck drivers> just signed each one. In both cases it was nice because you didn't > have> the expense of multi-part forms or the worry of running out. > > > Dave Parnin This e-mail, including attachments, may contain information that is confidential and/or proprietary, and may only be used by the person to whom this email is addressed. If the recipient of this e-mail is not the intended recipient or an authorized agent, the reader is hereby notified that any dissemination, distribution, or copying of this e-mail is prohibited. If this e-mail has been delivered to you in error, please notify the sender by replying to this message and deleting this e-mail immediately. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.--This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.