Call to predefined Report Query for PDF download does nothing

Question

I am trying to download a PDF report which is based upon 2 queries. Each query has a where clause with values taken from page items. I have installed OBI Publisher 11.1.1.5 and used the OBI Publisher 11.1.1.5 Word plug-in to create the RTF file that I then uploaded to the Shared Components->Report Layout.
I created a new region button to call the Report Query. However, whenever I click on the button to download the PDF, nothing happens. I have looked at the debug and the button appears to be executing OK, except that nothing happens.
The APEX to OBIP configuration is working since I am able to have OBIP generate other report PDFs that aren't using the predefined query. Stated a bit differently, reports regions that have the Print Attributes set to "Enable Report Printing=Yes" and "Report Layout=Default Report Layout" work fine. Reports based upon the predefined query and launched using a region button do not do anything.
Environment: APEX 4.1, DB 11.2.0.2, OBIP 11.1.1.5
Any help with this PDF issue is greatly appreciated.
Thanks,
Reid

Answer 1

Thank you again for your reply, Udo.
Here are my responses:
* As a matter of fact, I am doing a copy / paste from the predefined query to the report region source.
** What exactly do you mean by that? Don't you print the actual region?
I need to produce a PDF that is the compilation of 4-5 queries. Therefore, I cannot print a region to PDF since APEX (as far as I know) does not allow for the printing of multiple regions (1 query per region) to a single PDF file. So, I am creating a PDF that is based upon multiple queries which I predefine in the shared components -> report queries. Then, I'm creating a region button that calls a downloadable report when it is clicked.
Your question has made me realize that indeed it doesn't matter what query I have in the report region since I am calling a predefined report. When nothing was happening when I attempted to generate the PDF, I guess I started to think that the problem was with the queries on the page and so I made them match exactly with what the queries are in the shared components->report queries.
Please advise if something is wrong with my understanding here.
I checked the OBI Publisher logs (at least what I could locate) and I didn't see anything show up there.
/u02/app/ohs/obip_mw/user_projects/domains/bifoundation_domain/servers/AdminServer/logs
I checked the OHS access_log and I didn't see anything that looks like an error. I also don't see anything in the APEX page debug. It appears to process normally when the button is clicked.
From the access_log:
192.168.1.137 - APEX_PUBLIC_USER [27/Dec/2011:22:17:30 -0500] "GET /pls/apex/f?p=4000:RUN_PAGE:55206340610065:BRANCH_TO_PAGE_ACCEPT:NO::FB_FLOW_ID,FB_FLOW_PAGE_ID,F4000_P1_FLOW:103,235,103 HTTP/1.1" 302 -
192.168.1.137 - APEX_PUBLIC_USER [27/Dec/2011:22:17:30 -0500] "GET /pls/apex/f?p=103:235:55206340610065::::: HTTP/1.1" 200 21588
192.168.1.137 - APEX_PUBLIC_USER [27/Dec/2011:22:17:32 -0500] "POST /pls/apex/wwv_flow.accept HTTP/1.1" 302 -
192.168.1.137 - APEX_PUBLIC_USER [27/Dec/2011:22:17:32 -0500] "GET /pls/apex/f?p=103:235:4495899155137965::::: HTTP/1.1" 200 21588
Here is a look at the page debug:
0.00246     0.00107     A C C E P T: Request="TRANSCRIPT_PDF"     4
0.00350     0.00501     Metadata: Fetch application definition and shortcuts     4     
0.00851     0.00080     alter session set nls_language="AMERICAN"     4     
0.00931     0.00060     alter session set nls_territory="AMERICA"     4     
0.00991     0.00078     NLS: CSV charset=WE8MSWIN1252     4     
0.01069     0.00067     ...NLS: Set Decimal separator="."     4     
0.01136     0.00083     ...NLS: Set NLS Group separator=","     4     
0.01219     0.00082     ...NLS: Set g_nls_date_format="DD-MON-RR"     4     
0.01301     0.00079     ...NLS: Set g_nls_timestamp_format="DD-MON-RR HH.MI.SSXFF AM"     4     
0.01380     0.00077     ...NLS: Set g_nls_timestamp_tz_format="DD-MON-RR HH.MI.SSXFF AM TZR"     4     
0.01457     0.00064     ...Setting session time_zone to -05:00     4     
0.01522     0.00077     Setting NLS_DATE_FORMAT to application date format: DD-MON-YYYY HH:MIPM     4     
0.01599     0.00094     Setting NLS_TIMESTAMP_FORMAT to application timestamp format: DD-MON-YYYY HH:MIPM     4     
0.01693     0.00077     ...NLS: Set g_nls_date_format="DD-MON-YYYY HH:MIPM"     4     
0.01770     0.00078     ...NLS: Set g_nls_timestamp_format="DD-MON-YYYY HH:MIPM"     4     
0.01848     0.00068     ...NLS: Set g_nls_timestamp_tz_format="DD-MON-RR HH.MI.SSXFF AM TZR"     4     
0.01916     0.00046     NLS: Language=en-us     4     
0.01962     0.00219     ...metadata, fetch translated application info     4     
0.02181     0.00088     ...fetch session state from database     4     
0.02269     0.00096     fetch items     4     
0.02365     0.00090     ...fetched 32 session state items     4     
0.02455     0.00170     Authentication check: CUSTOM TABLE AUTH (NATIVE_CUSTOM)     4     
0.02625     0.00074     ... sentry+verification success     4     
0.02698     0.00057     ...Session ID 4495899155137965 can be used     4     
0.02755     0.00056     ...Check session 4495899155137965 owner     4     
0.02811     0.00064     Setting NLS_DATE_FORMAT to application date format: DD-MON-YYYY HH:MIPM     4     
0.02875     0.00080     Setting NLS_TIMESTAMP_FORMAT to application timestamp format: DD-MON-YYYY HH:MIPM     4     
0.02955     0.00062     ...NLS: Set g_nls_date_format="DD-MON-YYYY HH:MIPM"     4     
0.03017     0.00069     ...NLS: Set g_nls_timestamp_format="DD-MON-YYYY HH:MIPM"     4     
0.03086     0.00053     ...NLS: Set g_nls_timestamp_tz_format="DD-MON-RR HH.MI.SSXFF AM TZR"     4     
0.03139     0.00130     ...Check for session expiration:     4     
0.03269     0.00055     ...Metadata: Fetch Page, Computation, Process, and Branch     4     
0.03323     0.00102     Session: Fetch session header information     4     
0.03425     0.00047     ...Setting session time_zone to -5:00     4     
0.03472     0.00187     ...metadata, fetch page info     4     
0.03660     0.00092     ...Validate item page affinity.     4     
0.03751     0.00050     ...Validate hidden_protected items.     4     
0.03801     0.00061     ...Check authorization security schemes     4     
0.03862     0.00095     Session State: Save form items and p_arg_values     4     
0.03957     0.00081     ...Session State: Save "P235_TRANSCRIPT_ID" - saving same value: "7"     4     
0.04038     0.00065     Processes - point: ON_SUBMIT_BEFORE_COMPUTATION     4     
0.04102     0.00082     Branch point: Before Computation     4     
0.04185     0.00054     Computation point: After Submit     4     
0.04239     0.00079     Tabs: Perform Branching for Tab Requests     4     
0.04317     0.00065     Branch point: Before Validation     4     
0.04382     0.00111     Validations:     4     
0.04493     0.00165     Perform basic and predefined validations:     4     
0.04658     0.00070     Perform custom validations:     4     
0.04728     0.00054     Branch point: Before Processing     4     
0.04782     0.00057     Processes - point: AFTER_SUBMIT     4     
0.04839     0.00054     Branch point: After Processing     4     
0.04893     0.00096     ...Evaluating Branch: AFTER_PROCESSING type: "REDIRECT_URL" button: (No Button Pressed) branch: (Unconditional)     4     
0.04989     0.00071     Stop APEX Engine detected     4     
0.05059     0.00055     Stop APEX Engine detected     4     
0.05114     0.00122     Final commit     4     
0.05236     -     End Page Processing