Report Launch Form Error

I have recently installed HeadStart 6i (see version info below).
When I launch a report in the demo app (QMS0012F) and select
the 'Options...' button I receive 'FRM-41052 Cannot find Window:
invalid ID'. This is followed by the 'Report Launch Options'
window but this appears to not work correctly (no lov buttons
and all fields are blank even though they are setup in the
Foundation app correctly). If I dont use the 'Options...' button
the report runs correctly (if all the required report fields are
defaulted in the Foundation app). Thanks, Keith
Headstart Demo Application 6.5
Application Library (hsdapp65) 6.5.0.4
Oracle8i Enterprise Edition Release 8.1.7.1.1 - Production
Oracle Forms Generator 6.5.40.4.0
Headstart Template Package 6.5.1.0
Template Form (qmstpl65) 6.5.0.6
Object Library (qmsolb65) 6.5.1.4
Event Handler Library (qmsevh65) 6.5.1.5
Core Library (qmslib65) 6.5.1.12

This is a duplicate posting, please disreguard

Similar Messages

Calendar function not working in report launch form

We are currently using Headstart 6.5.3.1 for 9i. When we invoke the calendar function for a date parameter in the report launch form (qms0012f), we get the error-message ORA-6508: could not find program unit being called in PL/SQL Program Unit qms$calendar.show.
After closing the report launch form and re-opening it again this error message does not appear again and the calendar is shown without any problems.
Does anyone have experience with this error or know the reason why it is occurring?
Regards,
Gert de Boer

Hi dear
I am Santosh in New Delhi. Hope you will help me.
I M working with report 10G. My problem is that , I am not able to get normal character printing on Dot matrics printer and character mode report of report 3
Thanks

Report launch form - implementation name?

In the report launch form (qms0012f), no reference at all is made to the implementation name defined for the module. This attribute is mandatory when setting up the module definition (via qfd0016f), & according to the on-line help for this form it's used to specify the physical name for the module. We'd like to use it so we can have a generic report module, with separate module definitions for each menu call via qms0012f (& hence different parameters).
Why hasn't this functionality been implemented?

Cheryl,
I'm sorry, on creation of Headstart 2.1 we added the implementation_name to the qms_modules table, but we just plain forgot to modify qms0012f as well. As most people have the implementation name identical to the module name, nobody noticed until you did!
If you want to change this, you should modify library qms0012l.pll.
Go to package qms0012f,
find the declaration of g_short_name_item, and add a similar one g_implementation_name_item where 'SHORT_NAME' is replaced by 'IMPLEMENTATION_NAME'. In the same package qms0012f, find the function get_short_name_item and add a similar one get_implementation_name_item.
Then go to package qms$report, function fill_par_list. At the end of this function, you will see a statement l_module_name := name_in(qms0012f.get_short_name_item);
Change this into l_module_name := name_in(qms0012f.get_implementation_name_item);
I am not able to test this, but I think it should work. Please let us know if this workaround helps, then we can include it in Headstart 6i.
Hope this helps,
Sandra

No color change for mandatory parameters in Report Launch Form

Report Launch Form (qms0012f) does not color the mandatory report parameters when running on 9IAS webserver.
We are using Designer 6i with Headstart 6.5.3.0.
On client server the mandatory report parameters are changed to user preference color.
Testing when running the form with the Developer Web Previewer of Forms Builder 6i the mandatory parameters are also changed to user preference color but the background color is white instead of gray?

Cheryl,
I'm sorry, on creation of Headstart 2.1 we added the implementation_name to the qms_modules table, but we just plain forgot to modify qms0012f as well. As most people have the implementation name identical to the module name, nobody noticed until you did!
If you want to change this, you should modify library qms0012l.pll.
Go to package qms0012f,
find the declaration of g_short_name_item, and add a similar one g_implementation_name_item where 'SHORT_NAME' is replaced by 'IMPLEMENTATION_NAME'. In the same package qms0012f, find the function get_short_name_item and add a similar one get_implementation_name_item.
Then go to package qms$report, function fill_par_list. At the end of this function, you will see a statement l_module_name := name_in(qms0012f.get_short_name_item);
Change this into l_module_name := name_in(qms0012f.get_implementation_name_item);
I am not able to test this, but I think it should work. Please let us know if this workaround helps, then we can include it in Headstart 6i.
Hope this helps,
Sandra

Resetting parameters in the Report Launch Form (qms0012f)

We ran into the problem today that the parameters in the Report Launch Form cannot be reset if they have no default value defined against them. In our situation this proved to be quite confusing and annoying for our end users, so we investigated the logic in the Headstart code and created a very simple solution: we added one character to the code in the qms0012l library. (package qms$param, procedure check_par_value.
For the long story, see http://technology.amis.nl/blog/?p=925
best regards,
Lucas

Gerard,
"when using the LOV query (through Headstart Foundation Application) the user is forced to use the LOV
and is not able to fill in the parameter field (field protected against update). "
This behavior is intentional. The reason for this is that with Hsd6i, we added a display value that is different from
the actual value of the parameters. However, in order not to break applications developed with older releases
of Headstart, the LOV still lists the actual value is still listed first in the lov query. Since the first field in the LOV
is not the field displayed on the screen, you cannot set Validate in LOV to true. So, the only option is to force
users to use the LOV to enter data. If you do not have compatibility issues with older applications, you can
set Validate in LOV to true and change all your LOV queries to put Description first and then value.
"If I use the LOV, Value or Description width fields they generate an On Off behaviour. The values you
specify are not important. When specified the LOV becomes screen wide, disregarding the specified
widths. When cleared the LOV returns to it's initial behaviour. "
I suspect this might be a new forms bug. I've logged a Headstart bug, just in case we can find a workaround.
"The manual describes the use of GLOBAL variables for Default Value and Description.
So far :
the code for the default value will never work
name_in(l_default_value)
should be
name_in(substr(l_default_value,2))
in order to remove the colon.
The code for the Default Description is totally absent."
I have also logged a Headstart bug for this. We will need to investigate it. Certainly, the mechanism is working
correctly, so I'm not sure what is going on here.
Regards,
Lauri

Calling Report from Form Error ORA-06508

Dear all,
I want migrate from Fom6i to Oracle Developer Suite 10g (10.1).
Folder Form = C:\APLIORA\IRS\FORM
Folder Report = C:\APLIORA\IRS\REPORT
I have modified file DEFAULT.ENV
FORMS_PATH=C:\APLIORA\IRS\FORM;C:\APLIORA\IRS\REPORT
i do not have problem call a form from form.
but when i call report from form show error ORA-06508 : PL/SQL : could not find program unit being called ; -6508
my procedure is
PROCEDURE Call_Report IS
     list_id ParamList;
BEGIN
list_id := Get_Parameter_List('input_params');
IF NOT Id_Null(list_id) THEN
Destroy_Parameter_List(list_id);
END IF;
list_id := Create_Parameter_List('input_params');
Add_Parameter(list_id,'MAXIMIZE',TEXT_PARAMETER,'YES');
Add_Parameter(list_id,'ORACLE_SHUTDOWN',TEXT_PARAMETER,'YES');
RP2RRO.RP2RRO_RUN_PRODUCT(REPORTS,'TESTREPORT.REP',SYNCHRONOUS,RUNTIME,FILESYSTEM,list_id,null);
END ;
Do I miss something ?
Can any one help ?
Thanks

Hi,
Thank you for your replay.
The problem have solved.
This my step :
1. Install Windows XP SP2 and Form 10.1.2.0.2 on new pc.
2. Install Jinit version 1.3.1.28.
3. Create report server
3. Compile form, report and pll
4. call report from from with this procedure :
PROCEDURE Call_Report (vFILENAME varchar2) IS
report_id                Report_Object;
ReportServerJob VARCHAR2(100);
vc_rep_status      VARCHAR2(100);
repsvr                          varchar2(21) := 'myserv';
userid                         VARCHAR2(100);
pass                          VARCHAR2(100);
Host                    VARCHAR2(100);
BEGIN
userid          := Get_Application_Property(USERNAME) ;
pass          := Get_Application_Property(PASSWORD) ;
Host          := Get_Application_Property(CONNECT_STRING) ;
report_id:= find_report_object('REPORT');
SET_REPORT_OBJECT_PROPERTY(report_id,REPORT_FILENAME,vFILENAME||'.jsp');
SET_REPORT_OBJECT_PROPERTY(report_id,REPORT_COMM_MODE,SYNCHRONOUS);
SET_REPORT_OBJECT_PROPERTY(report_id,REPORT_SERVER,repsvr);
ReportServerJob:=run_report_object(report_id);
vc_rep_status := REPORT_OBJECT_STATUS(ReportServerJob);
WHILE vc_rep_status in ('RUNNING','OPENING_REPORT','ENQUEUED', null)
LOOP
vc_rep_status:=REPORT_OBJECT_STATUS(ReportServerJob);
END LOOP;
IF vc_rep_status='FINISHED' THEN
WEB.SHOW_DOCUMENT('/reports/rwservlet?report='||vFILENAME||'.jsp'||'&userid='||userid||'/'||pass||'@'||Host||'&destype=CACHE&desformat=PDF&paramform=yes','_blank');
ELSE
message ('Report failed with error message '|| vc_rep_status);
END IF;
END;
Ok, but i have another strange error. I will post new thread.
Thank you and regards
Teguh S

Is it possible to bypass the Reports Launch Form

The question is not if it is possible to bypass the Launch Form, but
1. is it possible to pass parameters (arguments) to fill out the parameters from another form.
2. Assuming the answer to Q1 is Yes, is it possible to automatically launch the report if all parameters has been filled in?
+ken

Calling report from FORM - error Invalid value of paramente 'P_YEAR'

Hi guys,
Could you please help me to figure out what is going wrong
with my form which run a report?
I am using Developer suite 10g.
when i run report from report application it run fine,
but when i call that report from a form it gives me error.
I have checked the datatype, checked the parameter value
that I assign from form is available in the report parameter value.
What else do i have to check in order to run this report
from the form.
Error Message from Report Queue Manager:
Invalid value for parameter 'P_YEAR'.
Your insight will be appreciated.

Thank you for reply Denis,
Here is the code which run_report from form.
DECLARE
-- variables for running individual reports
report_filename               VARCHAR2(40);
var_reportpath               VARCHAR2(100);
report_otherparms      VARCHAR2(200);
-- variables to keep track of successful reports in silent mode
rep_status                         VARCHAR2(40);
rep_req                                   NUMBER := 0;
rep_count                              NUMBER := 0;
dummy                                        NUMBER;
-- variables to load the report names and checkboxes into the parameter list
pl_id                                        PARAMLIST;
plname                                   VARCHAR2(20) := 'rpt_list';
-- variables to loop through the parameter list and run the reports
i                                                  NUMBER;
split_loc                              NUMBER;
     param_value                         VARCHAR2(40);
     checkbox_name                    VARCHAR2(40);
     report_basename               VARCHAR2(40);
     svc_name                              VARCHAR2(4);
     run_report                         BOOLEAN;
     disp_exist BOOLEAN := get_current_service_count( :global.filename_prefix, 'DISP',
                    :reports_control.year_list, :reports_control.quarter_list,
                    :reports_control.group_list );
hosp_exist BOOLEAN := get_current_service_count( :global.filename_prefix, 'HOSPICE',
                    :reports_control.year_list, :reports_control.quarter_list,
                    :reports_control.group_list );
orth_exist BOOLEAN := get_current_service_count( :global.filename_prefix, 'O/P',
                    :reports_control.year_list, :reports_control.quarter_list,
                    :reports_control.group_list );
BEGIN
-- Are any reports selected?
IF BOXES_ARE_CHECKED(:System.Cursor_Block,'PRINT_NULL_REPORT') THEN
if not CHECKBOX_CHECKED('print_null_report') then
disp_exist := TRUE;
orth_exist := TRUE;
hosp_exist := TRUE;
end if;
-- Create Report Parameter Listing
pl_id := GET_PARAMETER_LIST(plname);
if NOT ID_NULL(pl_id) then
     DESTROY_PARAMETER_LIST(pl_id);
end if;
pl_id := CREATE_PARAMETER_LIST(plname);
if ID_NULL(pl_id) then
     GENERIC_ALERT('Error creating report listing');
     RAISE Form_Trigger_Failure;
end if;
ADD_PARAMETER(pl_id,'id1', TEXT_PARAMETER,'cover_page_intro!INTRO');
ADD_PARAMETER(pl_id,'id2', TEXT_PARAMETER,'utilization_profile!ALLUTIL');
ADD_PARAMETER(pl_id,'id3', TEXT_PARAMETER,'utilization_summary!ALL_SUMMARY');
ADD_PARAMETER(pl_id,'id4', TEXT_PARAMETER,'hiv_profile!HIV_PROFILE');
ADD_PARAMETER(pl_id,'id5', TEXT_PARAMETER,'wound_care_profile!WOUND_CARE_PROF');
ADD_PARAMETER(pl_id,'id6', TEXT_PARAMETER,'top_10_diagnosis!TOP10DIAG');
ADD_PARAMETER(pl_id,'id7', TEXT_PARAMETER,'diagnosis_profile!DIAG_PROFILE');
ADD_PARAMETER(pl_id,'id8', TEXT_PARAMETER,'physician_profile!PHYS_PROFILE');
ADD_PARAMETER(pl_id,'id9', TEXT_PARAMETER,'physician_specialty!PHYS_SPECIALTY');
ADD_PARAMETER(pl_id,'id10',TEXT_PARAMETER,'discharge_profile!DISCHARGE_PROFILE');
ADD_PARAMETER(pl_id,'id11',TEXT_PARAMETER,'acute_care_discharge!ACUTE_DSCHRG');
ADD_PARAMETER(pl_id,'id12',TEXT_PARAMETER,'excessive_cost_patients!EXCESSIVE_COST');
ADD_PARAMETER(pl_id,'id13',TEXT_PARAMETER,'provider_profile!PROV_PROFILE');
ADD_PARAMETER(pl_id,'id14',TEXT_PARAMETER,'service_profile!SERVICE_PROFILE');
ADD_PARAMETER(pl_id,'id15',TEXT_PARAMETER,'age_gender_profile!AGE_GENDER_PROF');
ADD_PARAMETER(pl_id,'id16',TEXT_PARAMETER,'network_services!NETWORK_SERVICES');
ADD_PARAMETER(pl_id,'id17',TEXT_PARAMETER,'thh_section_header!THH_COVER');
ADD_PARAMETER(pl_id,'id18',TEXT_PARAMETER,'thh_utilization!THH_UTILIZATION');
ADD_PARAMETER(pl_id,'id19',TEXT_PARAMETER,'thh_service_profile!THH_SVC_PROF');
ADD_PARAMETER(pl_id,'id20',TEXT_PARAMETER,'hit_section_header!HIT_COVER');
ADD_PARAMETER(pl_id,'id21',TEXT_PARAMETER,'hit_utilization!HIT_UTILIZATION');
ADD_PARAMETER(pl_id,'id22',TEXT_PARAMETER,'hit_service_profile!HIT_SVC_PROF');
ADD_PARAMETER(pl_id,'id23',TEXT_PARAMETER,'hme_section_header!HME_COVER');
ADD_PARAMETER(pl_id,'id24',TEXT_PARAMETER,'hme_utilization!HME_UTILIZATION');
ADD_PARAMETER(pl_id,'id25',TEXT_PARAMETER,'hme_service_profile!HME_SVC_PROF');
ADD_PARAMETER(pl_id,'id26',TEXT_PARAMETER,'disp_section_header!DISP_COVER');
ADD_PARAMETER(pl_id,'id27',TEXT_PARAMETER,'disp_utilization!DISP_UTILIZATION');
ADD_PARAMETER(pl_id,'id28',TEXT_PARAMETER,'disp_service_profile!DISP_SVC_PROF');
ADD_PARAMETER(pl_id,'id29',TEXT_PARAMETER,'hosp_section_header!HOSP_COVER');
ADD_PARAMETER(pl_id,'id30',TEXT_PARAMETER,'hosp_utilization!HOSP_UTILIZATION');
ADD_PARAMETER(pl_id,'id31',TEXT_PARAMETER,'hosp_service_profile!HOSP_SVC_PROF');
ADD_PARAMETER(pl_id,'id32',TEXT_PARAMETER,'orth_section_header!ORTH_COVER');
ADD_PARAMETER(pl_id,'id33',TEXT_PARAMETER,'orth_utilization!ORTH_UTILIZATION');
ADD_PARAMETER(pl_id,'id34',TEXT_PARAMETER,'orth_service_profile!ORTH_SVC_PROF');
ADD_PARAMETER(pl_id,'id35',TEXT_PARAMETER,'encounter_detail!ENCOUNTER_DETAIL');
--- set up other parameters to send to generate_report
if :reports_control.output_choices = 'FILE' then
var_reportpath := :global.report_directory || :reports_control.year_list;
if :global.filename_suffix <> '_A10G' then
     var_reportpath := var_reportpath || 'q' || :reports_control.quarter_list;
end if;
var_reportpath := var_reportpath || '_G' || :reports_control.group_list || '_';
else
     var_reportpath := '';
end if;
report_otherparms := 'p_year='||:reports_control.year_list;
if :global.filename_suffix <> '_A10G' then
     report_otherparms := report_otherparms || '     p_quarter='||:reports_control.quarter_list;
end if;
report_otherparms := report_otherparms || ' P_REPORTGROUPID='||:reports_control.group_list;
--- Check if reports are checked and submit to Reports Server
     for i in 1..35 loop
          GET_PARAMETER_ATTR(pl_id,'id'||i,dummy,param_value);
          split_loc := instr(param_value,'!');
          checkbox_name := substr(param_value,1,split_loc-1);
          report_basename := substr(param_value,split_loc+1,length(param_value));
if CHECKBOX_CHECKED(checkbox_name) then
     run_report := TRUE;
     svc_name := substr(report_basename,1,4);
     if svc_name = 'DISP' then
          if not disp_exist then
               run_report := FALSE;
          end if;
     elsif svc_name = 'ORTH' then
          if not orth_exist then
               run_report := FALSE;
          end if;
     elsif svc_name = 'HOSP' then
          if not hosp_exist then
               run_report := FALSE;
          end if;
     end if;
     if run_report then
          report_filename := :global.filename_prefix || report_basename || '_10G';---- :global.filename_prefix || report_basename || :global.filename_suffix;
     GENERIC_ALERT(report_filename || ' ' || report_otherparms);
          rep_status := GENERATE_REPORT(report_filename,:reports_control.output_choices,var_reportpath,report_otherparms);
          rep_req := rep_req + 1;
          if rep_status = 'FINISHED' then
               rep_count := rep_count + 1;
          end if;
     end if;
     end if;
     end loop;
-- if we're in silent mode, display a completion message
     if :reports_control.output_choices = 'FILE' and CHECKBOX_CHECKED('chk_silent') then
          SET_ALERT_PROPERTY('REPORT_CREATED',alert_message_text,
     '' || rep_count || ' of ' || rep_req || ' reports created successfully');
          dummy := SHOW_ALERT('REPORT_CREATED');
end if;
ELSE
dummy := SHOW_ALERT('select_report');
END IF;
END;

Running Reports using DESTYPE=CACHE from Report Launch Form (QMS0012F)

We are trying to run reports via the web. Since this is a 3-tier setup and our report server is running under UNIX the DESTYPE=Preview and Screen are not valid options. When we choose CACHE as DESTYPE we get the error:
'Invalid value '||l_value||' passed for parameter DESTYPE'
I have traced the error down to the QMS0012L.PLL library -> QMS$REPORT (version 6.5.1.3) package -> add_par_to_list procedure.
Is this a legacy of a client/server type setup? I have modified the procedure to allow for DESTYPE=CACHE. Now by submitting a report with DESTYPE=CACHE it gets submitted to the reports server except it doesn't show report. To display the report I believe we have
to use the Web.Show Document function to display the report (eg. http://bill:7777/servlet/RWServlet/getjobid8?server=rep60bill) as per the oracle white paper "Integrating Oracle9iAS Reports in Oracle9iAS Forms"
Has there been a headsdtart patch to include the DESTYPE of CACHE when running reports? or are we the only ones running reports this way.

Raymond,
I have recorded a new bug against Headstart for this. We do not
currently have a fix, but I've looked at the code you mention and
your fix looks correct.
Regards,
Lauri

Report launch form (qms0012f)

Dear Headstart Team,
when using the LOV query (through Headstart Foundation Application) the user is forced to use the LOV
and is not able to fill in the parameter field (field protected against update).
If I use the LOV, Value or Description width fields they generate an On Off behaviour. The values you specify are not important.
When specified the LOV becomes screen wide, disregarding the specified widths. When cleared the LOV returns to it's
initial behaviour.
Are both points as intended ?
With kind regards,
Gerard.

Gerard,
"when using the LOV query (through Headstart Foundation Application) the user is forced to use the LOV
and is not able to fill in the parameter field (field protected against update). "
This behavior is intentional. The reason for this is that with Hsd6i, we added a display value that is different from
the actual value of the parameters. However, in order not to break applications developed with older releases
of Headstart, the LOV still lists the actual value is still listed first in the lov query. Since the first field in the LOV
is not the field displayed on the screen, you cannot set Validate in LOV to true. So, the only option is to force
users to use the LOV to enter data. If you do not have compatibility issues with older applications, you can
set Validate in LOV to true and change all your LOV queries to put Description first and then value.
"If I use the LOV, Value or Description width fields they generate an On Off behaviour. The values you
specify are not important. When specified the LOV becomes screen wide, disregarding the specified
widths. When cleared the LOV returns to it's initial behaviour. "
I suspect this might be a new forms bug. I've logged a Headstart bug, just in case we can find a workaround.
"The manual describes the use of GLOBAL variables for Default Value and Description.
So far :
the code for the default value will never work
name_in(l_default_value)
should be
name_in(substr(l_default_value,2))
in order to remove the colon.
The code for the Default Description is totally absent."
I have also logged a Headstart bug for this. We will need to investigate it. Certainly, the mechanism is working
correctly, so I'm not sure what is going on here.
Regards,
Lauri

Reports Lauch Form

Can anyone tell me how you are supposed to send a report to a file through the reports launch form.
Does anyone know what the "Options" button is supposed to allow?
Running the report to the previewer does allow a file - generate to file - pdf/html/rtf/postscript option but this seems to error.
Any ideas anyone.
Cheers,
Dave

Dave,
To send a report to a file, you press the Options button and change the value for Destination Type to 'FILE'. You can optionally enter a printer driver in the Destination Format parameter. When you run the report, the reports runtime engine creates a printer file in the working directory of your application. Note: this is a printer file and not a word/pdf/html document.
As far as the Options button goes, this is a mechanism to allow users to enter some of the normal command line parameters for reports. In the foundation application, choose Parameters->Standard Report Parameters. This form allows you to define any report command line parameters. If you check the Report Specific checkbox, then this parameter is available to be included in a report. You must then go to Parameters->Module and Parameters and use the Add Standard Report Parameters button to add this parameter to your report(s). The parameter is then available to the end user when they press the Options button.
Headstart doesn't do anything special with these parameters. It simply passes them to the reports runtime engine on the command line. You can read the Report Builder documentation to find out more about the usage of individual parameters.
Regards,
Lauri

Crystal Report Windows Forms Viewer Error in 1 Workstation after upgrade of PL

Hi all,
We just upgraded SAP from 8.82 PL02 to 8.82 PL15.
Afterwards, in just 1 workstation, Crystal Reports layouts have Crystal Report Windows Forms Viewer error I attach.
Before the upgrade this error did not happen.
No permissions or authorizations were changed in the workstation.
The Crystal Reports layouts remain working fine in server and in the other workstations.
In the workstation following are installed:
- Operating System Windows 7;
- Microsoft .NET Framework 4.5;
- SAP Crystal Reports runtime engine for. NET Framework;
- Crystal Report 2008 Runtime SP6;
- Microsoft SQL Server 2008 R2 Native Client.
All, but the operating system, are equal to the other workstations.
User has edit access to SAP folders, temp and access to the attach path.
We already uninstalled SAP client and client agent and re-installed it but with no avail.
Can anyone help me?
Thanks in advance.
Best regards,
Pedro Mariano

Hi San Xu,
Thank you for your input.
However I'm facing problem with each software is suitable.
I installed SAP Crystal Reports for SAP Business One (CR 2011 V14.0.4.738), but with no avail.
Thanks in advance.
Best regards,
Pedro Mariano

Error calling Report from Form

Hi,
I'd like to call a report using a Form.
I have Oracle Form 10.1.2 in Oracle Database 10g.
I create a button and specify a PL/SQL in the when-button-pressed
declare
rep_id REPORT_OBJECT;
v_rep VARCHAR2(100);
begin
rep_id := FIND_REPORT_OBJECT('report9');
if not id_null(rep_id) then
v_rep := RUN_REPORT_OBJECT(rep_id);
else
message('report not available');
end if;
end;
but after I click the button in the form, it gives an error message in the status bar
(in the bottom of the form)
error : FRM-41211: Integration Error: SSL failure running another product
Any help would be grateful.
Thanks,
Buntoro

I have tried your suggestion.
I create my own report server using rwserver server=repsrv.
Another java-based windows showed up. It shows that repsrv is ready.
I do the following:
1. Navigate to http://localhost:8889/reports/rwservlet using web browser.
It showed OracleAS Report Services - Servlet Command Help page.
But there is no other window popup.
2. Navigate to http://localhost:8889/reports/rwservlet?userid=PRACTICE/PRTC@MYDB&report=C:\PRACTICE\FORM\MODULE1.JSP&destype=cache&desformat=html&paramform=no&p_1=P1&p_1=P2
my schema is PRACTICE, password PRACTICE, and database instance MYDB
the report path = C:\FORM\MODULE1.JSP
The following error occured
REP-51002: Bind to Reports Server rep_<computer_name> failed
3. Finally,
http://localhost:8889/reports/rwservlet?server=REPSRV&userid=PRACTICE/PRTC@MYDB&report=C:\PRACTICE\FORM\MODULE1.JSP&destype=cache&desformat=html&paramform=no&p_1=P1&p_1=P2
The following error occured
REP-51002: Bind to Reports Server repsrv failed
I don't understand.
It seems that the Report Service is not recognized although the java-based window state that the Report Server (repsrv) is ready.
My questions:
1. Does it means that my report server is not running?
Or it is running but the browser didn't recognize it?
I use Internet Explorer 6 and Netscape 7, both of them showed the same error message.
2. I have read the PDF you've pointed out.
The paper said there is supposed to be 2 type of server, 'In process' and custom server.
Both of them will create a configuration file in /reports/conf in DevSuiteHomeDirectory.
I can see the custom report server's configuration file which I create using rwserver (repsrv.conf)
but I can't see the 'in process' server's configuration file (rep_<computer_name>.conf).
What am I supposed to do?
Many thanks,
Buntoro

Error while previewing BI Publisher Report Output form Desktop

Hi,
i am getting below error while previewing Report Output form Desktop:
javaw -Xmx256M -jar "C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\jlib\RTF2PDFv2.jar" "C:\Users\mahlawat\AppData\Local\Oracle\BIPublisher\TemplateBuilderforWord\tmp\tb_param.xml"
File not found.
Please suggest
Regards,
Meetu

Hi ,
are u able to login into the bipublisher...check once..
http://10.81.200.102:7777/xmlpserver
generaly while connection to the desktop we will give the url at the bottom.
the vpn is connected or not..
Thanks,
Ananth

Rep-52005 error when running a report from form with parameter form

I am trying to run a report from a web deployed form and this report has a parameter form. I am getting a Rep-52005: The specified key report does not exist in key map file.
I am using Oracle Forms/Reports 10.1.2.0.2. My code is below. The first part works fine where I run a report with no parameter form, but the second part when I have a parameter form gets the about error.
PROCEDURE call_report (
p_report_name VARCHAR2,
p_reportobj_name VARCHAR2 DEFAULT NULL,
p_parameter_list paramlist DEFAULT NULL,
p_parameter_string VARCHAR2 DEFAULT NULL
IS
repid report_object;
v_rep VARCHAR2 (100);
rep_status VARCHAR2 (100);
v_report_url VARCHAR2 (240);
v_interface VARCHAR2 (50);
v_report_parameter VARCHAR2 (1);
vc_user_name VARCHAR2 (100);
vc_user_password VARCHAR2 (100);
vc_user_connect VARCHAR2 (100);
vc_connect VARCHAR2 (300);
v_reportserv VARCHAR2 (30);
v_job_number number;
BEGIN
/* Get the database to run the report against and
find out if the report has any parameters */
SELECT report_parameter_flag
INTO v_report_parameter
FROM program_list
WHERE program_type = 'REPORTS'
AND UPPER (screen_id) = UPPER (p_report_name);
vc_user_name := get_application_property (username);
vc_user_password := get_application_property (password);
vc_user_connect := get_application_property (connect_string);
v_reportserv := 'rep_xxxx_ias10g_home';
v_report_url := 'http://xxxx.state.il.us';
v_job_number := length(v_reportserv) +2;
vc_connect :=
vc_user_name
|| '/'
|| vc_user_password
|| '@'
|| vc_user_connect;
v_interface := get_application_property (user_interface);
IF ( v_interface = 'WEB'
AND v_report_parameter = 'N'
THEN
repid := find_report_object(p_reportobj_name);
set_report_object_property (repid, report_comm_mode, synchronous);
set_report_object_property (repid, report_destype, cache);
set_report_object_property (repid, report_desformat, 'pdf');
-- v_reportserv := get_report_object_property (repid,report_server);
set_report_object_property (repid, report_server, v_reportserv);
set_report_object_property (repid, report_other, p_parameter_string);
v_rep := run_report_object (repid);
rep_status := report_object_status (v_rep);
IF rep_status = 'FINISHED'
THEN
web.show_document (
v_report_url
|| '/reports/rwservlet/getjobid='
|| substr(v_rep,v_job_number)
|| '?server='
|| v_reportserv
,'_blank'
ELSE
message ( rep_status
|| 'Report output aborted');
END IF;
ELSIF ( v_interface = 'WEB'
AND v_report_parameter = 'Y'
THEN
repid := find_report_object (p_reportobj_name);
set_report_object_property (repid, report_comm_mode, synchronous);
set_report_object_property (repid, report_destype, cache);
set_report_object_property (repid, report_desformat, 'pdf');
set_report_object_property (repid, report_server, v_reportserv);
set_report_object_property (
repid,
report_other,
'paramform=yes P_USER_CONNECT='
|| vc_connect
|| ' P_SERVERNAME='
|| v_reportserv
|| ' P_ACTION='
|| v_report_url
|| '/reports/rwservlet'
v_rep := run_report_object (repid);
rep_status := report_object_status (v_rep);
IF rep_status = 'FINISHED'
THEN
web.show_document (
v_report_url
|| '/reports/rwservlet/getjobid='
|| substr(v_rep,v_job_number)
|| '?server='
|| v_reportserv
,'_blank'
ELSE
message ( rep_status
|| 'Report output aborted');
END IF;
ELSE
run_product (
reports,
p_report_name,
synchronous,
runtime,
filesystem,
p_parameter_list,
NULL
END IF;
EXCEPTION
WHEN OTHERS
THEN
message (SQLERRM);
END;
My parameter form comes up and I enter the necessary information and hit submit query button. Then I get the Rep-52005: The specified key report does not exist in key map file.
Any help will be greatly appreciated!!
Shellie Bricker

Your code seems to be implementing metalink note 139546.1 - Using Reports parameter forms with RUN_REPORT_OBJECT on the web.
For what I can see, the P_ACTION parameter should end in ?...
i.e.
P_ACTION=http://<hostname.domain:port>/reports/rwservlet?'
set_report_object_property (
repid,
report_other,
'paramform=yes P_USER_CONNECT='
|| vc_connect
|| ' P_SERVERNAME='
|| v_reportserv
|| ' P_ACTION='
|| v_report_url
|| '/reports/rwservlet?'
);If this does not fix your problem, then to troubleshoot further you would have to post the code in your Before Parameter Form trigger of your report.
Hope this helps,
UPDATE:
If the above does not fix your problem, my guess is that report name is not being generated in the hidden runtime values build by the code in the Before Parameter Form trigger.
i.e.
http://localhost:8889/reports/rwservlet?report=&destype=cache&desformat=PDF
The above code will throw error REP-52005: The specified key report does not exist in key map file.
Edited by: Rodolfo Ferrari on Jul 8, 2009 9:43 PM

Report Launch Form Error

Similar Messages

Maybe you are looking for