Identifying reports for printing

[olivier_maurice]

Hello,


We are moving towards Peoplesoft Enterprise One which has of course its impact on printing. For the moment we run on Peoplesoft World and we are using Optio as printer server.

We are looking now on how to implement the current functionalities in the new environment. We have a few strategies that could be implemented but they all rely on 1 important thing: the PDF file arriving on the queue should be identified uniquely. I explain:

For the moment, on World, when a report or spool file is released, a banner page is sent right before the spoolfile itself. The banner page contains data like which report is sent, which formtype to use (the formtype identifies the company and division in our case, who have their own headers, footers and e.g. sales conditions), which printer (the physical printer could be somewhere in Signapore), whether a mail should be sent or not... All documents arrive in one queue where the "master script" in optio acts like a hub and runs the right document.

Now we are looking for the same functionality, otherwise all the reports (or a least 70% of them) have to be reviewed while all the headers, footers and back prints (for about 20 companies, each with multiple division and in their mother tongue, also Chinese and Japanese) already exist on the printer server and can be reused easily.

The concept of the banner page is likely to disappear in the new environment, so we are looking for an intermediate file where the data from the banner page is saved. Some standerdized piece of code is inserted in the event rules of each report, so that the report itself only needs minor changes.
Once the PDF files arrives on the printer server, the banner data for the file is fetched from the table.

The problem: how identifying the document? What could possibly (and savely) be used as a key? Is there any data in the header of the PDF that is useful, because that is the only data accessible on the printer server that could be used for fetching the supplemental information. The data for the key, logically, should also be accessible in the event rules to build up a key for the intermediate file? (header included below, from a OneWorld Xe environment, but we are just looking for a strategi)

Or is it possible in OneWorld to include custom tags in this header??? This really would be nice, especially for the aspect of performance (no extra fetch necessary).

Or has anyone of you perhaps another idea? For those custom to working with JDEdwards/Optio combination, I know this is not the standard way of working. If we had to work like that, the number of queues to be created on the production machine and the printer server would be ridicilously large. The custom way of working we created only requires a few new scripts (templated) but no setup when a new document needs to printed or even when a new company is added. And immediately all the combinations are possible, where on the production machine the standard reports can be used.

I would really appreciate any input.

Thanks in advance,


Olivier Maurice


Header of PDF
----------------------------------
%PDF-1.3
%âãÏÓ
1 0 obj
<<
/Type /Catalog
/Pages 2 0 R
>>
endobj
2 0 obj
<<
/Type /Pages
/Kids [ 7 0 R ]
/Count 1
>>
endobj
3 0 obj
<<
/ModDate (D:20040109103012+01'00')
/DLI (2.0P1w \(Nt\))
/OneWorldRelease (B7333)
/CreationDate (D:20040109103012+01'00')
/Name (OLMTEST)
/Version (ROLM0001)
/Author (DPOLIVIER)
/BatchCreationDate (2004/1/9 10:30:10)
/OWEnvironment (DV7333)
/Machine (LVNW4191144)
/DecimalSepChar (,)
/ThousandsSepChar (.)
/Language (English)
/DateFormat (AOE)
/NumberOfCopies (1)
/DateSepChar (-)
/Title (OLM Test document)
/Subject (OLM Test document)
/Producer (J.D.Edwards OneWorld \(B7333\))
/Keywords (OLMTEST, ROLM0001, LVNW4191144, DV7333, )
/FileName (D:\\B7\\PrintQueue\\OLMTEST_ROLM0001_D1040109_T102943495.pdf)
/SystemInfo (fromOS 5 fromCP 1252 toOS 5 toCP 1252)
/PageSize (VertSize 12240 HorzSize 15840, pageOrient 2)
/PageInfo (lpi 205, cpi 38 DCFontSz 70)
/Sect_0 (SN=Page Header;TP=PH;BV=None;SI=2;PI=0)
/Sect_1 (SN=Page Footer;TP=PF;BV=None;SI=3;PI=0)
/Sect_2 (SN=F55X001 - All Columns;TP=CLM|L1;BV=V55X0001A;SI=1;PI=0)
-----------------------------

 

[Alex_Pastuhov]

Olivier,

Since B7334 there's a tag "/JobNumber (XXX)", which gives you a unique Job
Number (within a Host and untill it eventually rolls over, which doesn't
happen very often).

In B7333 you can use "/FileName
(D:\\B7\\PrintQueue\\OLMTEST_ROLM0001_D1040109_T102943495.pdf)" tag (taken
from your example), which has this same Job Number built into the name of
the file.

This number (or file name) will be unique for a period of time on the same
host, meaning that 1) other Servers can use the same numbers independently
and 2) this number will eventually be reused, but not very soon, making it
unique for a year or a few.

Regards,
Alexander Pastuhov
http://www.pastuhov.com.au/index.htm

----- Original Message -----
From: "olivier_maurice"

1. 
   To: <[email protected]>
   Sent: Monday, January 12, 2004 6:50 PM
   Subject: Identifying reports for printing
   
   
   impact on printing. For the moment we run on Peoplesoft World and we are
   using Optio as printer server.
   new environment. We have a few strategies that could be implemented but they
   all rely on 1 important thing: the PDF file arriving on the queue should be
   identified uniquely. I explain:
   banner page is sent right before the spoolfile itself. The banner page
   contains data like which report is sent, which formtype to use (the formtype
   identifies the company and division in our case, who have their own headers,
   footers and e.g. sales conditions), which printer (the physical printer
   could be somewhere in Signapore), whether a mail should be sent or not...
   All documents arrive in one queue where the "master script" in optio acts
   like a hub and runs the right!
   (or a least 70% of them) have to be reviewed while all the headers, footers
   and back prints (for about 20 companies, each with multiple division and in
   their mother tongue, also Chinese and Japanese) already exist on the printer
   server and can be reused easily.
   environment, so we are looking for an intermediate file where the data from
   the banner page is saved. Some standerdized piece of code is inserted in the
   event rules of each report, so that the report itself only needs minor
   changes.
   file is fetched from the table.
   savely) be used as a key? Is there any data in the header of the PDF that is
   useful, because that is the only data accessible on the printer server that
   could be used f!
   should also be accessible in the event rules to build up a key for the
   intermediate file? (header included below, from a OneWorld Xe environment,
   but we are just looking for a strategi)
   This really would be nice, especially for the aspect of performance (no
   extra fetch necessary).
   with JDEdwards/Optio combination, I know this is not the standard way of
   working. If we had to work like that, the number of queues to be created on
   the production machine and the printer server would be ridicilously large.
   The custom way of working we created only requires a few new scripts
   (templated) but no setup when a new document needs to printed or even when a
   new company is added. And immediately all the combinations are possible,
   where on the production machine the standard !
   http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OWDEV&Number=66253
   these messages, login to http://www.jdelist.com/forums, click Control Panel,
   then click Edit by "Subscribe / Unsubscribe from receiving board posts by
   email, change message notifications, etc." and adjust your subscription
   preferences. JDEList is not affiliated with JDEdwards®

 

[olivier_maurice]

Indeed, I was also looking to use that name, because it looked pretty unique to me, but I have no clue how to have access to that name at the moment the report runs (e.g. in the event rules) in order to store extra data in a file.

Thanks anyhow