|
I'm somewhat hesitant to suggest this but have you considered a different color paper for the statement? Of course, you still have to print everything in the required order but it does eliminate the separator page.
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Sent: Thursday, November 2, 2017 3:39 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Suggestions wanted on reducing time to assemble month-end invoices
Thanks, Justin - that helps!
On 11/2/2017 5:10 PM, Justin Taylor wrote:
The most recent case, we had a *SCS spooled file, a *USERASCII spooled file and a PDF for each order. We just sent them to the OUTQ with the three for a given order back-to-back. Originally, the *SCS, *USERASCII and PDF's all came from separate programs, so we had to change the process to create all the documents for a single order together.
We do not use separator pages. The documents themselves are distinct enough to server as separators.
In the OUTQ, the spooled files look like this:
*SCS-Order#123
*USERASCII-Order#123
*PDF-Order#123
*SCS-Order#456
*USERASCII-Order#456
*PDF-Order#456
*SCS-Order#789
*USERASCII-Order#789
*PDF-Order#789
-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Thursday, November 02, 2017 4:50 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Suggestions wanted on reducing time to assemble month-end invoices
Hi Justin
A little more detail, maybe - do you mean each statement and associated invoices are one document?
And did you include am easily-recognizable separator?
The invoice run precedes the statement run - and there are other processes in between - I don't know yet if those have any bearing on the statement run.
Thanks
Vern
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.