Presentation variable problem in PDF generation

Hi,
I have created the custom field using the following code
*case when (V_balance.yr<=@{var_year}{2009} and V_balance.yr>=@{var_year-3}{2006}) then 1 else 0 end*
Use this field I have created the filter and remove the field from report.
When I run the report with different prompts, its working fine as I expected in dashboard.
But when I generate the PDF for different prompt values ( var_year=2008 ) , I got same result. That is its generate var_year=2009 (default presentation variable)
Its generate the pdf with 'presentation variable default values' instead of presentation variable.
How could I rectify this problem.
Any one facing this problem.
Is there any alternative for this condition
Note:
We are using bise1 10.1.3.2.1
but I got a right answer in obiee 10.1.3.4.0
Thanks
Mohan
Edited by: Mohan 8732779 on Nov 23, 2009 5:50 AM

This is a known issue in 10.1.3.2. Oracle solved this problem in the new upgraded 10.1.3.4. Check the Meta link for the service request numbers raised for this problem. How hard it would be for you to migrate to 10.1.3.4.
Thanks
Prash

Similar Messages

Problem un PDF generation

Hi all,
      I have a litle problem in the generation of a PDF file that become in a base64 file, from R3, later, i'm proces it and get the URL to finally show incide in a IFRAME in the propertie "SOURCE".
     That work successfully but only for PDF's that contain only 1 page. Now for other files with more than 1 page, the IFRAME not solve the archive, que keep a loop to never end, obviously because not found the second page.
     Some idea's ???, some that was the same problem???
Thaks in advance.
Jorge.

Hi Chaitanya,
     The URL that is generated, besides i'm displaying in a textEdit to look the URL. This text i'm make a copy / paste in other page, and neither show the same loop. Now using a Link to URL show the same problem.
     By the way, i'm send the same routine to a friend and he's make a deploy to other WAS and was generated correctly the PDF, but in my was not work.
Thanks in advance.
Jorge

Problem With PDF Generation With CFDOCUMENT

I am having a problem with generating PDF's from my web
pages.
For example...if you go here
http://www.michaelpumo.com
and click the "Convert to PDF" link on the left you'll see that the
output is totally wrong.
Is it to do with my markup? I can't figure this out.
Many thanks in advance.

I, along with many others have had these types of problems
and so far adobe hasn't addressed them (or at least I couldn't find
anywhere where they have).
Kapitaine, Have you tried outputting to flashpaper? Most of
my formatting problems only occur in PDF.
For instance, align right does not work properly. It pushes
everything to the right, but is not flushed to the right so the
output looks very unprofessional. This cfdocument was a good idea,
and a good selling point but it is embarrassing to have sold my
boss on it only to find out it is almost worthless in it's current
state. BTW I'm working on a CFMX7.0.2 on Linux RHEL4.

Problem with PDF generation from Interactive Report

Greetings,
I created an interactive report and chose CSV and PDF download options. I am able to create CSV but when I try to download a PDF it says that that acrobat reader cannot open the created pdf file. I am not sure what I should do to make it work. Please help.
-Vatsa

Hey there,
That happened to me when I had an & sign in the page title name. If you have some weird symbols in the page title, try changing them. Then it will work.
PS
Make sure in the title name and page name there are no weird symbols.
Mike
Message was edited by:
weezy f

APEX 4.1 - APACHE FOP PDF generation problem.

Hi all,
I'm having problem with PDF generation using APACH FOP on OC4J.
When I test my print server as described here:
http://marcsewtz.blogspot.com/2008/06/heres-another-posting-on-pdf-printing.html
everything works without problem. But when I upload my Layout to APEX and try to generate PDF from apex I'm getting error:
oracle.xml.parser.v2.XMLParseException: Unexpected EOF.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
     at oracle.xml.parser.v2.XMLReader.popXMLReader(XMLReader.java:549)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1375)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:362)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:308)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:337)
     at oracle.xml.xslt.XSLProcessor.newXSLStylesheet(XSLProcessor.java:714)
     at oracle.xml.xslt.XSLStylesheet.<init>(XSLStylesheet.java:322)
     at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:114)
     at apex_fop._jspService(_apex__fop.java:71)
     [SRC:/apex_fop.jsp:21]
I could see similar post here:
Handling Special characters in call to apex_util.download_print_document
But it doesn't explain my case as it's crashing even when I generate empty pdf(no data so no special characters, only empty XML file with no data should be sent to print server)
Is there any way to see what xml is sent do print server for processing? That could eventually show where is a problem.
Palo

My mistake, there was really an "&" character in my template. now when I replaced it with %26 it works.
However I would be still interested if there is a way to see what data is APEX engine sending to print server cause it will help me to find this kind of errors.
Palo

BI 7.0 Web PDF Generation

Hi folks,
I do have a severe problem with PDF generation and it looks like a common issue.
I integrated Button to convert my Management Webreport to PDF, no big issue so far.
But the generated PDF is not bevaing like expected. We do have a BI report that contains 3 charts horizontally alligned by a table to fit the screen and 1 table below
those charts.
This report fits perfectly on one page landscape.
When generating PDF locally (PDF generator installed on client PC) Internetexplorer ==>PDF works as expected.
When using the Button in Webtemplate to use the BI functionality to export to PDF the PDF is a mess.
All template items are displayed in sequence taht means instead of 3 horizontal charts I see 3 charts and 1 table underneath each other.
It looks like the old fashioned 3.x print function.
My question:
Is there a way to influence the PDF generation. Maybe a class ( like former 3.x Table Interface) to modify to render the PDF like the template appearance?
We cannot install PDF clients locally nor can we ship management those reports coming from BI. Report designer is no alternative because of missing functionality.
TIA
Joerg

Thanks so far,
currently when using the container item and referring by command wizard ( export to PDF) the system is not generating any item.
Error Message 'file has no page and can't be opened...' occurs.
I think this is a really urgent Development issue because I think printing via PDF is getting more and more important since not everyone is using IE7 ( which is not fully supported by SAP either) to scale pages for printing.
Best regards
Joerg

PDF Generation has problems

Hi there,
Our company uses Colffusion to make PDFs for our client.
Recently, the PDF generation is incredible instable, causing
corrupt PDF files or performance issues.
I found out, that the problem lies within the including some
picture. This slows down almost everything or sometimes the
generation does not happen at all.
Is there a solution for this? Is there a hot fix for that?
Thanks for your reply

Try <cfreport> instead of <cfdocument> which give
better results for these type of pdf conversion and image
issues...

PDF generation : FileNotFoundException problem

Hi all,
I'm developing a dynamic PDF generation module in web application using iText framework. This module creates PDF on the server side then sends it to the client. Sometimes, Even though the PDF file is created on the hard disk, I got FileNotFoundException when calling the servlet that sends it.
My program is very simple (no thread used) :
1- The client calls enters some inputs,
2 - The iText based class generates the PDF,
3 - The PDF created is saved as an attribute in the client session (HttpSession).
4 - The request is redirected to servlet that sends the PDF.
What could be the problem ?
thx,

In fact, I don't know what you mean by:
3 - The PDF created is saved as an attribute in the client session (HttpSession).What do you mean by this? Did you save the proprietry PDF object? Or the java.io.File object? If it is the PDF object, does its class implement java.io.Serializable?
Um ... Here are some suggestions ...
First of all, make sure that the file really exists there.
Secondly, try to write a Java SE program to read the file using the absolute path you provided.
Then, if the Java SE program works, I think the reason may be that you haven't closed the "OutputStream" which writes the PDF file, or the security settings of your JSPServer prevents you from getting the file.
Asuka Kenji (UserID = 289)
(Duke Dollar Hunting now ...)

Help: PDF Generation Problems in Reports 3.0

Hi Techies,
We are generating PDFs from Oracle Reports 3.0
The PDF generation is fine in some datbases.
But in some database,when the records are more, during PDF
generation, Dr.Watson error is encountered, saying access
violation.
Can any one please clarify whether the error is due to memory
constraints on the system or if it has something to do with
Oracle Reports setting, while generating PDFs.
Do note that the reports are running fine, when the report has
less number of records.
Any suggestion/tip is awaited at the earliest.
Thanks in advance,
Geoff
null

Hi!
Remove cache from output dir from time time.
(i.e. from virtual dir where report server puts output)
let me know ...
later
Geoff (guest) wrote:
: Hi Techies,
: We are generating PDFs from Oracle Reports 3.0
: The PDF generation is fine in some datbases.
: But in some database,when the records are more, during PDF
: generation, Dr.Watson error is encountered, saying access
: violation.
: Can any one please clarify whether the error is due to memory
: constraints on the system or if it has something to do with
: Oracle Reports setting, while generating PDFs.
: Do note that the reports are running fine, when the report has
: less number of records.
: Any suggestion/tip is awaited at the earliest.
: Thanks in advance,
: Geoff
null

PDF Generation problems in Reports 3.0

Hi,
I am generating PDFs from Oracle Reports 3.0
The PDF generation is fine in some datbases.
But in some database,when the records are more, during PDF
generation, Dr.Watson error is encountered, saying access
violation.
Can any one please clarify whether the error is due to memory
constraints on the system or if it has something to do with
Oracle Reports setting, while generating PDFs.
Do note that the reports are running fine, when the report has
less number of records.
Any help in this matter is appreciated.
Regards,
PRAKASH
null

Hi!
Remove cache from output dir from time time.
(i.e. from virtual dir where report server puts output)
let me know ...
later
Geoff (guest) wrote:
: Hi Techies,
: We are generating PDFs from Oracle Reports 3.0
: The PDF generation is fine in some datbases.
: But in some database,when the records are more, during PDF
: generation, Dr.Watson error is encountered, saying access
: violation.
: Can any one please clarify whether the error is due to memory
: constraints on the system or if it has something to do with
: Oracle Reports setting, while generating PDFs.
: Do note that the reports are running fine, when the report has
: less number of records.
: Any suggestion/tip is awaited at the earliest.
: Thanks in advance,
: Geoff
null

Date format problem - dashboard prompt - presentation variable

Hi,
I've created a dashboard prompt on a date and defined a presentation variable.
In my report I make use of the following object : TimeStampAdd(SQL_TSI_MONTH,-12,date '@{pv_afw_start_date}' )
My report works when making use of a drop down list, but when I want to make use of a calendar to select from, I receive the following error
*A general error has occurred. [nQSError: 46047] Datetime value 17/11/2009 from 17/11/2009 does not match the specified format. (HY000)*
Is there a difference in the date formats used by the prompt type (drop down list, calendar, ..)? And how you can align them..
Txs for your help.
Kr
A

Timestampadd ask for a timestamp not for a date.
Check here :
http://download.oracle.com/docs/cd/E12103_01/books/admintool/admintool_SQL14.html
The syntax is :
TimestampAdd(SQL_TSI_DAY, 3, TIMESTAMP '2000-02-27 14:30:00')You may have to change your prompt to retrieve a timestamp.
Where do you use your formula ? In a formula column ?

Can I pass parameters from a dashboard via a dashboard prompt and presentation variable to publisher report based on a data model with select statements in OBIEE 11g ?

I have a publisher 11g (v 11.1.1.7) report with a single parameter. The report is based on a data model not a subject area. I created a dashboard put a dashboard prompt and link to the report in separate section on the same page. The dashboard prompt sets a presentation variable named the same as the parameter in the report.
The problem was when I created the dashboard prompt, it forced me to select a subject area which I did (though did not want to) and then I created both a column and variable prompts. But clicking on the
report link completely ignored the value that I thought would be passed in the presentation variable to the report.
Side note : My report uses a pdf template for its layout where I have mapped the columns names from my data model to the form fields on the pdf form. I noticed that if I create a publisher report based on a subject area, then I do not have the choice to choose a PDF as a template type for my layout. (I only see BI Publisher Template as a choice).
I see some documentation online that suggest it could be done in 10g.
Thanks
M. Jamal

Ok,
I just tried that and it still doesn't pass anything to the prompt.
I changed the prompt to an edit field and I made the following weblink but when i click the link from an account it doesn't put anything in the prompt and all data for all accounts is shown.
This is the URL maybe I messed something up...
https://secure-ausomx###.crmondemand.com/OnDemand/user/Dashboard?OMTHD=ShowDashboard&OMTGT=ReportIFrame&SelDashboardFrm.Dashboard Type=%2fshared%2fCompany_########_Shared_Folder%2f_portal%2f360+Report&Option=rfd&Action=Navigate&P0=1&P1=eq&P2=Account."Account Name"&P3=%%%Name%%%
thanks

Problem submitting PDF form in WorkSpace

Hi, my server is ES2.5 Turnkey install (Express mode) on Windows.
Client is IE-8 with latest Reader.
My form is a PDF form created in the WorkBench,
it has 2 pages, with some Digital Signature fields,
I have also added the "Process Fields" group onto page 2 of the form.
The form is to be routed in the standard WorkSpace.
At the Initiator step (Start Point), I use the Action Profile to do the Pre-fill of the form.
I have checked the Reader Extended box.
I use a Document variable as the Output from the StartPoint, the doc variable references my .PDF form template.
Everything works fine at the Initiator step, the form fields are all properly Pre-filled.
The problem is:
after I click the Complete button, it goes to the next participant of the workflow process,
when that person opens up the form in the WorkSpace, it's all blank, none of the data at the Initiator step show up.
This User task uses the same Document variable as the Input (specified at the Presentation & Data tab).
What do I need to do to pass the form data along with the form to the next person in the Process?
What have I done wrong? what should I check?
thanks.

I sort of narrowed down the problem a little bit.
I created a smaller PDF form, it has Digital Signature field as well as the Process Fields group, plus some Text fields. When I used it in the SAME process (changed the Document variable to point to this new small form of course) everything worked! No data loss. Everything on the form including the Signature got passed to the next person in the workflow just fine.
So I think my Process design is fine, the problem appears to be in the original 2-page PDF form.
But I can't figure out what thing on the form could have caused the data loss!
There's no error message anywhere, nothing in the JBoss server log either.
Has anybody seen similar problem like this?
thanks.

Date format is changing in presentation variable

Hello,
I have a problem with date stored in presentation variable.
I have simple prompt with calendar field (default date value is setted from repository or session variable to current date). Selected date is stored in PP_DATE presentation variable.
I have simple report with title to show the content of variable PP_DATE.
And now the problem.
When I navigate to dashboard page with this report I will get date from PP_DATE variable in some format (there is difference when I use repository or session variable). After I will push the start button I will get another date format from PP_DATE variable.
Screenshots are stored and described in this PDF: [PDF with screenshots|https://docs.google.com/uc?export=download&id=0B2LOPOBteIShMDRmYTJlYTItNmYyZC00ODdkLWE5NjktNzI1N2RlNWMwZjBk]
There is difference between session and repository variable. When I use repository variable I will get 'TIMESTAMP .......' from PP_DATE variable, which is the default initializer in repository variable manager. I tried to delete default initializer, but I is automatically added after saving changes.
When is the default value of prompt setted from session variable I will get another format of date from PP_DATE variable which refers to DATE_TIME_DISPLAY_FORMAT = "yyyy-mm-dd hh:mi:ss.mss" (from NQSConfig.ini). I have changed DATE_TIME_DISPLAY_FORMAT from standard value "yyyy/mm/dd hh:mi:ss" to "yyyy-mm-dd hh:mi:ss.mss" because I am reading some data from excel, where are dates stored in MSSQL format. But this is not the reason of my problem. I have the same problem also with standard DATE_TIME_DISPLAY_FORMAT.
The result of this strange behaviour is that I am getting errors when I am doing some calculations (for example TimeStampDiff) with PP_DATE variable. I am getting error when I am navigating to dashboard page. Everything is ok after I will push the start button.
Do you have some tips?
Thank you

Kishore Guggilla wrote:
Hey,
you are talking about so many pieces here seems..
first letz break down your issues list..
1. error, this is because of default date(using repository variable) used in prompt..
2. using presentation variables in timetampdiff functions..
3. showing variable in title list..
we'll go through each issue..
because, its' messed up..I think that everywhere is the same problem. So solving issue number 1 will solve my other problems.
"1. error, this is because of default date(using repository variable) used in prompt.. "
I want to use date prompt with default date value (from repository or session variable) and then use pp_date presentation variable from this prompt to filter my results.
I would like to use repos. or session variables, I dont want to write some select to fill default date value in each prompt.
I tried to change one date in initialization block from "trunc(sysdate, 'DD')" to "to_char(sysdate, 'YYYY-MM-DD')" because it is the same format as DATE_DISPLAY_FORMAT = "yyyy-mm-dd" in NQSConfig.ini
And now it seems to be working now.
I can use repository var. as default date value in my prompt and use date variable pp_date to filter my results. Report return result after navigation on it and after pushing Go button.
Can you confirm me that date format in initialization block must be the same as DATE_DISPLAY_FORMAT = "yyyy-mm-dd" in NQSConfig.ini?

Problems Creating PDFs

A lot of problems creating PDFs come from using the wrong printer to create the PDF or underlying printfile.
You should use Adobe's Distiller printer instance to create a PDF. This comprises the latest Adobe Postscript printer for your operating system plus the Distiller PPD.
Don't use an HP printer to create your PDF. PostScript, or otherwise.
Don't use a Xerox printer to create your PDF. PostScript or otherwise.
See #1.
Note: If you are outputting to a service bureau, you might want to use something other than the Distiller printer instance. However, if you encounter problems with your particular PDFs, try using the official method with the Distiller printer to see whether any problems are limited just to your setup. If problems persist, you might have to create your PostScript output using one printer driver and the PDF using Adobe's Distiller printer instance.
Common problems include:
Black and white, or greyscale, PDFs created from color FrameMaker books and documents.
Distiller terminating the PDF creation process early, thus no PDF is created.
Troubleshooting:
For lack-of-color problems, first check you don't have Spot as Black set in the Frame Print dialog.
Update the printer you are using to the latest Adobe PostScript printer driver version.
Uninstall the printer you are using to create PDFs and to reinstall the latest version from scratch.

FAQ: Creating PDF Files from FrameMaker Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!
Dov Isaacs - 07:02pm Dec 6, 2001 Pacific
An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
GOOD NEWS
I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
DON'T USE "SAVE AS PDF"
But what's wrong with "save as PDF" as currently implemented?
The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
(1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
(2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
(3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
(4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
(5) Some or all text in the resultant PDF file cannot be searched or indexed.
(6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
(7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
(8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
(9) Some or all page content is missing (other than margin areas).
(10) Relatively inefficient PDF is generated.
If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
Whether the printer supports color (Acrobat Distiller does)
What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
Resident fonts (Acrobat Distiller doesn't really have resident fonts)
Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
DON'T USE PDFWRITER
The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
Case 3: Acrobat 3
Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
- Dov

Presentation variable problem in PDF generation

Similar Messages

Maybe you are looking for