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

Similar Messages

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

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

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

Is there a way to trace an IPOD even if it is Jailbroken.... how is it possible to bypass the ICloud Lost feature in the device? third time my 64 gb iPod touch gets stolen.

Is there a way to trace an IPOD even if it is Jailbroken.... how is it possible to bypass the ICloud Lost feature in the device? third time my 64 gb iPod touch gets stolen.

If it is off or not connected to wi-fi, then you cannot track it.

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

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

Is it possible to bypass the interactive report

Hi -
Is there a way to skip the interactive report and go directly to page 2 of my application if the report only returns one row?
Thanks,
Matt

user1055564 wrote:
Could you give me an example?I can't give you an example because I haven't actually done this, and we're trying to establish connectivity for my new project (no Apex connectivity yet).
I'm thinking of something like having region item that's populated by a query, probably the count you are lookng for. The region header might have some JavaScript code looking at the count value as a substitution variable or text value you assign and possibly perform a redirect based on that value as set up in the page header.

Is it possible to open a report or form from a package on the DB?

Please help..
Marty

Wrong forum. You probably won't get the best answers here.
Please help..Why you would want a Database server to be the client participant in a Form is beyond my understanding. You might want to restate what you are trying to accomplish.
For a report, you have some options, something like this could be pulled off inside a stored procedure
SELECT utl_http.request( 'http://your_report_server?args_that_output_to_file_not_cache' )
INTO buffer
FROM DUAL;
Where you don't care about buffer, since the report has been initiated.

Is it possible to bypass the Default rules in a task?

Hello,
looking at a article on the internet on how to configure PO Release workflow. I configured my system( IDES) to create new PO Release workflow accordingly.
I am able to create a new PO and based on the configuration the Release strategy is displayed in the PO screen.
The STD PO RELEASE workflow WS20000075 provided by SAP is is activated and agent assignment is done in the configuration.
So as soon a PO is created the workflow is triggered and the workflow errors out. It does not send any workitem to the recipient. I tried to diagnose the workflow and the issue is with the default rule which gets triggered to determine a AGENT. The default rule triggers the FM ME_REL_GET_RESPONSIBLE
to determine the agents and it is not able to determine the agent.
Any idea what is missing or how to bypass the default rule defined in a std task?
Regards
Chky

Hi Imthiaz,
I implemented the OSS Note and deteted the entry in SWEC as suggested in the OSS Note. But after deleting, The event is not raised at all. I did a comparison of SWEL trace before and after deleting the record.
Anyways i put back the SWEC i deleted from the system. When i tried to dig further in the issue i realized that when i check the trace in SWEL it gives me a error message
Import container contains errors (are any obligatory elements missing?)
Then i checked back to see if all the Bindings are fine from Workflow to Task and From Task to the default Rule and all seems to be fine.
Not sure why still i am getting the error as mentioned above.
Also I tried to Test the workflow from SWDD transaction and passed the PO number and the Release code in the testing. The workflow Error's out. When i check the workflow log it just stops at the first step.
Any idea what next i should try?
Anyways thanks for your help. Appreciate that !!
Cheers
Chky

Is it possible to bypass the internal dac?

can i get a digital output , bypassing the internal dac like you can with an iphone?

That's nice but (1) as I said the camera connection kit doesn't work with the Nano and (2) according to your blog iOS 7.x or later is required for it to work. The iPod Nano does not run iOS.

REP-50134 occurs when using the submit button on the Reports Parameter Form

Good Morning,
I get the "REP-50134: Cache subitem reports does not exist" error after clicking on the Submit Button from a Reports parameter form.
I am using Forms/Reprots 9i.
Using the source code given in the Whitepaper 'Oracle Forms Services - Using Run_Report_Object() to call Reports with a parameter form', all works well when paramform=no, but when I have a Form print a report with paramform=yes, the parameter form appears correctly, but generates the error after clicking the Submit Button.
Any inputs as to causation or possible places to look to solving this problem would be greatly appreciated.
Thank you

Hello and thanks.
The value in the tag is <form method=post action="reports?">
Looking at this I suspect my problem is related to this setting. I am trying to follow all the instructions in the White Papers but they are a little confusing as they are not all exactly the same. Each attempts to explain a specific functionality without regards to the whole.
For instance I believe I need to have the variables P_ACTION, P_USER_CONNECT and P_SERVER_NAME in the report being called and then add a Before Parameter Form trigger to reset the values. But this seems to duplicate and override what has already been sent via the REPORT_OTHERS property. It is a tad bit confusing.
Can you confirm?
Thanks for any clarification you can provide.

Problem with output from report to excel, calling the report from form 10g

Hi everyone, I'm having a problem generating a excel from a report, which is called from a form, I'm using Forms 10g. The problem is this: My report has a variable number of columns. These columns appear according to data obtained from the database, these columns are dates, In vesion 6 excel file generated shows the columns one after another starting in column A1 to column CP. I mean that the dates are correlative. But in version 10g the excel file generated shows the same report starting in column A to column T, only shows the 20 dates correlative corresponding to this columns, the rest of the dates are down the excel sheet in groups of 20 dates, it's something, the file in 6i grows across and in 10g grows down the excel sheet. The report (rdf file) is the same in 6i and 10g, I compiled the 6i version to obtain the 10g version. The excel sheet generated in 10g looks like the report was in pdf format, because PDF format, cuts the report in pages and the file grows down, if I generate the report in PDF format it has the same structure excel file in 10g has. I hope yo can help because I have days trying to solve this but I have no succes. If someone could help I could email the excel files generated in two versions. Here I put the code I use to generate the files in 6i and 10g. I have tried with DESFORMAT=SPREADSHEET in 10g but the result is the same. Thanks for your help. Greetings for all.
Code for version 6i (Works Very well)
PROCEDURE GUARDAREXCEL IS
pl_id ParamList;
nom_rep varchar2(20);
cla_rep varchar2(20);
cod_dis varchar2(4);
nom_arch varchar2(100);
fec date;
BEGIN
pl_id := Get_Parameter_List('tmpdata');
IF NOT Id_Null(pl_id) THEN
Destroy_Parameter_List( pl_id );
END IF;
pl_id := Create_Parameter_List('tmpdata');
IF :BK_PARAMETROS.LI_COD_DIS IS NOT NULL THEN
cod_dis := :BK_PARAMETROS.LI_COD_DIS;
END IF;
IF :BK_PARAMETROS.TI_COD_CLI IS NOT NULL THEN
Add_Parameter(pl_id,'P_COD_CLI',TEXT_PARAMETER,:BK_PARAMETROS.TI_COD_CLI||'%');
ELSE
Add_Parameter(pl_id,'P_COD_CLI',TEXT_PARAMETER,'%');
:BK_PARAMETROS.TI_COD_CLI:='%';
END IF;
IF :BK_PARAMETROS.CLAS_REP=1 THEN
cla_rep := '001';
ELSE
     IF :BK_PARAMETROS.CLAS_REP=2 THEN
          cla_rep := '002';
     ELSE
          IF :BK_PARAMETROS.CLAS_REP=3 THEN
          cla_rep := '003';
     ELSE
          cla_rep := '004';
     END IF;
     END IF;
END IF;
Add_Parameter(pl_id,'P_COD_DIS',TEXT_PARAMETER, cod_dis);
Add_Parameter(pl_id,'P_FECHA',TEXT_PARAMETER,to_char(:BK_PARAMETROS.FECFIN, 'DD/MM/YYYY'));
Add_Parameter(pl_id,'P_CLASE',TEXT_PARAMETER, cla_rep);
Add_Parameter(pl_id,'PARAMFORM',TEXT_PARAMETER,'NO');
Add_Parameter(pl_id,'DESTYPE',TEXT_PARAMETER,'File');
Add_Parameter(pl_id,'MODE',TEXT_PARAMETER,'Character');
Add_Parameter(pl_id,'DESFORMAT',TEXT_PARAMETER,'DELIMITED' );
select sysdate into fec from dual;
IF :BK_PARAMETROS.TIPO_REP=1 THEN
     BEGIN
nom_rep := 'tdvenrli1577.rep';
nom_arch := 'c:\windows\temp\RepCobranzaPlanos' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
END;
ELSIF :BK_PARAMETROS.TIPO_REP=2 THEN
          BEGIN
          nom_rep := 'tdvenrli1578.rep';
          nom_arch := 'c:\windows\temp\RepCobranzaLargos' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
          END;
ELSIF :BK_PARAMETROS.TIPO_REP=3 THEN
     BEGIN
                    Add_Parameter(pl_id,'P_XLS',TEXT_PARAMETER, '1');
          nom_rep := 'tdvenrli1576.rep';
          nom_arch := 'c:\windows\temp\RepCobranzaDetallados' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
          END;
ELSE
          BEGIN
                    nom_rep := 'TDVENRLI1545.REP';
          nom_arch := 'c:\windows\temp\RepCobranzaTodos' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
          END;
END IF;
--Add_Parameter(pl_id,'DESNAME',TEXT_PARAMETER,nom_arch );
Add_Parameter(pl_id,'DESNAME',TEXT_PARAMETER, nom_arch);
standard.commit;
Run_Product(REPORTS, nom_rep, SYNCHRONOUS, runtime, FILESYSTEM, pl_id,'');
EXCEPTION WHEN Run_Product_Failure THEN
message('Error');
END;
Code for version 10g
PROCEDURE GUARDAREXCEL IS
pl_id ParamList;
nom_rep varchar2(20);
cla_rep varchar2(20);
cod_dis varchar2(4);
nom_arch varchar2(100);
fec date;
--byt12122007.sn
repid REPORT_OBJECT;
     vURL VARCHAR2(500);
     rep_status VARCHAR2(20);
     vJobID VARCHAR2(100);
     v_rep VARCHAR2(100);
VAR NUMBER;
w_name_repserv VARCHAR2(30);
--byt1212007.en
BEGIN
     --w_name_repserv:=F_OBTIENE_SERVREP;
w_name_repserv:='repserv';
pl_id := Get_Parameter_List('mytmp_params');
IF NOT Id_Null(pl_id) THEN
Destroy_Parameter_List( pl_id );
END IF;
pl_id := Create_Parameter_List('mytmp_params');
IF :BK_PARAMETROS.LI_COD_DIS IS NOT NULL THEN
     cod_dis := :BK_PARAMETROS.LI_COD_DIS;
END IF;
IF :BK_PARAMETROS.TI_COD_CLI IS NOT NULL THEN
Add_Parameter(pl_id,'P_COD_CLI',TEXT_PARAMETER,:BK_PARAMETROS.TI_COD_CLI||'%');
ELSE
Add_Parameter(pl_id,'P_COD_CLI',TEXT_PARAMETER,'%');
:BK_PARAMETROS.TI_COD_CLI:='%';
END IF;
IF :BK_PARAMETROS.CLAS_REP=1 THEN
cla_rep := '001';
ELSE
     IF :BK_PARAMETROS.CLAS_REP=2 THEN
          cla_rep := '002';
     ELSE
          IF :BK_PARAMETROS.CLAS_REP=3 THEN
          cla_rep := '003';
     ELSE
          cla_rep := '004';
     END IF;
     END IF;
END IF;
Add_Parameter(pl_id,'P_COD_DIS',TEXT_PARAMETER, cod_dis);
Add_Parameter(pl_id,'P_FECHA',TEXT_PARAMETER,to_char(:BK_PARAMETROS.FECFIN, 'DD/MM/YYYY'));
Add_Parameter(pl_id,'P_CLASE',TEXT_PARAMETER, cla_rep);
Add_Parameter(pl_id,'PARAMFORM',TEXT_PARAMETER,'NO');
/*Add_Parameter(pl_id,'DESTYPE',TEXT_PARAMETER,'File');
Add_Parameter(pl_id,'MODE',TEXT_PARAMETER,'Character');
Add_Parameter(pl_id,'DESFORMAT',TEXT_PARAMETER,'DELIMITED' );*/
select sysdate into fec from dual;
IF :BK_PARAMETROS.TIPO_REP=1 THEN
BEGIN
     repid := find_report_object('tdvenrli1577');
--nom_rep := 'tdvenrli1577.rep';
nom_arch := 'c:\windows\temp\RepCobranzaPlanos' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_FILENAME,'tdvenrli1577');
END;
ELSIF :BK_PARAMETROS.TIPO_REP=2 THEN
BEGIN
     repid := find_report_object('tdvenrli1578');
          --nom_rep := 'tdvenrli1578.rep';
          nom_arch := 'c:\windows\temp\RepCobranzaLargos' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
          SET_REPORT_OBJECT_PROPERTY(repid, REPORT_FILENAME,'tdvenrli1578');
          END;
ELSIF :BK_PARAMETROS.TIPO_REP=3 THEN
BEGIN
     repid := find_report_object('tdvenrli1576');
                    Add_Parameter(pl_id,'P_XLS',TEXT_PARAMETER, '1');
          --nom_rep := 'tdvenrli1576.rep';
          nom_arch := 'c:\windows\temp\RepCobranzaDetallados' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
          SET_REPORT_OBJECT_PROPERTY(repid, REPORT_FILENAME,'tdvenrli1576');
          END;
ELSE
BEGIN
     repid := find_report_object('tdvenrli1545');
                    --nom_rep := 'TDVENRLI1545.REP';
          nom_arch := 'c:\windows\temp\RepCobranzaTodos' || TO_CHAR(fec, 'ddmmyyyy') || '.xls';
          SET_REPORT_OBJECT_PROPERTY(repid, REPORT_FILENAME,'tdvenrli1545');
          END;
END IF;
--Add_Parameter(pl_id,'DESNAME',TEXT_PARAMETER,nom_arch );
--Add_Parameter(pl_id,'DESNAME',TEXT_PARAMETER, nom_arch);
standard.commit;
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_DESNAME,nom_arch);
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_COMM_MODE, SYNCHRONOUS);
     SET_REPORT_OBJECT_PROPERTY(repid, REPORT_EXECUTION_MODE, RUNTIME);
     SET_REPORT_OBJECT_PROPERTY(repid, REPORT_DESTYPE, 'File');
     SET_REPORT_OBJECT_PROPERTY(repid, REPORT_DESFORMAT, 'DELIMITED');
     SET_REPORT_OBJECT_PROPERTY(repid, REPORT_SERVER, w_name_repserv);
     SET_REPORT_OBJECT_PROPERTY(repid, REPORT_OTHER, 'paramform=no');
     v_rep := RUN_REPORT_OBJECT(repid, pl_id);
     rep_status := REPORT_OBJECT_STATUS(v_rep);
     WHILE rep_status IN ('RUNNING','OPENING_REPORT','ENQUEUED')     LOOP
          rep_status:= report_object_status(v_rep);
     END LOOP;
     IF rep_status = 'FINISHED' THEN
          vJobID := SUBSTR(v_rep, INSTR(v_rep, '_', -1)+1);
          vURL:='/reports/rwservlet/getjobid'||vJobID||'?'||'server='||w_name_repserv;
     END IF;
     WEB.SHOW_DOCUMENT(vURL, '_blank');
     IF NOT form_success THEN
          MESSAGE('Error: PL/SQL held against Button failed to execute');
          RAISE FORM_TRIGGER_FAILURE;
     END IF;
/*Run_Product(REPORTS, nom_rep, SYNCHRONOUS, runtime, FILESYSTEM, pl_id,'');
EXCEPTION WHEN Run_Product_Failure THEN
message('Error');*/
END;

There are two problems with your VI. First, the basic logic of writing/appending to a file (Excel, TDMS, anything) should go something like this: Open the file, position yourself at the end of the file, then, in the loop, acquire data and write it to the file until you are finished with data acquisition. When you exit the acquire/write to file loop, then close the file. In particular, the opening and the closing of the file should not be inside the loop.
As others have pointed out, writing to Excel might not be optimal, particularly if you are acquiring data at a high rate (and would therefore be writing a lot of data). We actually use Excel in our data acquisition routine, mainly reading from a WorkSheet to get the parameters of a particular stimulus, but also writing the outcome of the response to the stimulus. As it happens, our "acquisition rate" in this example is on the order of several samples per minute, so there's no problem using Excel (we also sample 16 channels of analog data at 1 KHz -- this gets written as a binary file).
Second, if you really do want to use Excel, use the (existing) Excel file to which you want to append as the "template" argument of the New Report function. Then use the Excel Get Last Row function to position yourself at "end of file", as noted above.
Good Luck.
Bob Schor

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

Error running the report from Form

Hi,
I am try to run the report from the form by using these code of line
DECLARE
RPT_OBJECT REPORT_OBJECT;
RPT_RUN VARCHAR2(100);
BEGIN
RPT_OBJECT := FIND_REPORT_OBJECT('REPORT7');
SET_REPORT_OBJECT_PROPERTY(RPT_OBJECT, REPORT_COMM_MODE, SYNCHRONOUS);
SET_REPORT_OBJECT_PROPERTY(RPT_OBJECT, REPORT_DESTYPE, CACHE);
SET_REPORT_OBJECT_PROPERTY(RPT_OBJECT, REPORT_OTHER,'P_CITYCODE'||:CITYCODE||'PARAMFORM = YES');
RPT_RUN := RUN_REPORT_OBJECT(RPT_OBJECT);
END;
but i m not using any Form server and Report Server i m completly using Oracle9iDS
It gives the error rep-0110 file not found and
rep-1070 error while opening and saving the file
please give me the solution
Shehzad

Shehzad,
this means that Reports Server cannot access the Reports module. You can test this assumption by copying your Reports module into <Oracle Home>\reports\samples\demo. The demo directory is out of the box accessible fro Reports.
If this allows you to run the Report, then all you need to do is to specify the Reports_Path to include the reports modules.
btw.: An other reason can be that your Reports contains uncompiled PLSQL, so you may want to check this too.
Frank

Is it possible to bypass the Reports Launch Form

Similar Messages

Maybe you are looking for