olivier_maurice
Active Member
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)
-----------------------------
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)
-----------------------------