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

Similar Messages

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

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

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

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

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

Display parameters in the report....

Hi friends,
I have one requirement to show up the parameters the user has selected in the 'report customization form' in the report .Any thoughts pl help..I know it is possible in dynamic pages but i never tried in the report ...pl help
Vishnu singireddy

You can try something in the additional PL/SQL section..
If you are running it as portlet:
htp.prn( <portal_schema>.wwv_name_value.get_string( l_arg_names,
l_arg_values,p_reference_path|| '.<parameter_name>');
If you are running in Normal Full Page Mode
htp.prn( <portal_schema>.wwv_name_value.get_string( l_arg_names,
l_arg_values,'<parameter_name>');
e.g.
htp.prn(portal30.wwv_name_value.get_string( l_arg_names,
l_arg_values,p_reference_path|| '.department');
Thanx,
Chetan.

PASSING PARAMETERS TO CRYSTAL REPORTS THRU FORMS!

Hi! all,
Is there someone who passed parameters to crystal reports from
forms 5.0?
The problem is when I call the report executable from the form,
its giving a login prompt again which is not desirable as @ this
stage the user has already logged in once. So is there a way to
pass this as a parameter to crystal or may be any better way???
Thanx for the solution,
Hima
null

First make sure you are on SP 3:
https://smpdl.sap-ag.de/~sapidp/012002523100007123572010E/cr2008_sp3.exe
SP 3 msi
https://smpdl.sap-ag.de/~sapidp/012002523100007123592010E/cr2008sp3_redist.zip
SP 3 msm
https://smpdl.sap-ag.de/~sapidp/012002523100007123582010E/cr2008sp3_mm.zip
Have a look at [Crystal Reports for Visual Studio 2005 Walkthroughs|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2081b4d9-6864-2b10-f49d-918baefc7a23]
(The above does apply to your version of CR also)
Have a look at the samples:
https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsfor.NETSDK+Samples
And look at the Developer Help file:
http://help.sap.com/businessobject/product_guides/boexir31/en/crsdk_net_dg_12_en.chm
And don't forget to use the search box at the top right corner of this web page. It will bring up KBases, blogs, wikis, articles and more. Searching these forums is also a good idea.
- Ludek

How to add the parameters onto the reports while calling from forms

Hi all,
I am using oracle forms 10g. I want to call a report from the form.
But i dont know how to add parameters to the url while using
web.show_document();
i have a sample code. But it does not add the forms values onto the url.
DECLARE
v_host varchar2(100);
v_port varchar2(10);
v_parameter_string varchar2(4000);
v_username varchar2(50);
v_password varchar2(50);
v_database varchar2(50);
BEGIN
-- Get the full domain name of the server from the formsweb.cfg
tool_env.getvar('SERVER_URL',v_host);
-- Get the username/password and database from the .env file
tool_env.getvar('APPLICATION_USERNAME',v_username);
tool_env.getvar('APPLICATION_PASSWORD',v_password);
tool_env.getvar('APPLICATION_DATABASE',v_database);
-- If it is localhost then we are running on windows and need to use the windows port, otherwise we
-- are on AIX and need to use the AIX port
IF v_host = 'localhost' THEN
     v_port := '8889';
ELSE
     v_port := '7778';
END IF;
-- Now build the parameter string for running the report
v_parameter_string := 'server=rep_fsprod';
v_parameter_string := v_parameter_string||'&report=AAP_TOTAL_CONTRACT_VALUE_RPT.rdf';
v_parameter_string := v_parameter_string||'&userid='||v_username||'/'||v_password||'@'||v_database;
v_parameter_string := v_parameter_string||'&execution_mode=batch';
v_parameter_string := v_parameter_string||'&comm_mode=synchronous';
v_parameter_string := v_parameter_string||'&destype=cache';
v_parameter_string := v_parameter_string||'&desformat=pdf';
-- Now run the report
web.show_document('http://'||v_host||':'||v_port||'/reports/rwservlet?'||v_parameter_string,'_blank');
END;
Are we able to add the text values in the form from to the URL.
Please let me know....
thanks in advance....
Naveen

hello
read the following white paper http://www.oracle.com/technology/products/forms/pdf/10g/frm10gsrw10g.pdf
cheers
Q

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

How to call a BW WEB template from R/3 and pass parameters to the report

Is it possible to call a BW web template from an R/3 system, through an abap program?
I have a BW WEB report template. This works very good, and i have 3 variables in the query.
Now, i need to invoke the BW web template from inside of an abap in R/3..
And i want to pass 3 variables from the R/3 ABAP to the BW WEB TEMPLATE.....
Is possible to call BW web templates from R/3??
PLEASE!!! HELP ME..
Carlos E. España
ADATSA
[email protected]

Thank you very much for your valuable help, i checked your suggestion and looks great. But i need to pass 3 parameters from an ABAP to the wad query report.
How can i pass the parameters to the web template???
another issue: My WAS (Web Application Server 6.20) is not public, is currently working for a local area network.
The access to this report is from outside of the office, so we need to access this through the PORTAL.

Please help me for Parameters of the reports in client server mode

Dear reader,
I have a problem,
suppose there is a hierarchy of listings in reports e.g.
countries, states, provinces, districts.
in the parameter if i want to list the districts of the selected
provinces, provinces of the selected states, states of the
selected countries,
then how the code for the parameter must be written. this i am
unable to do as the parameter's select statement does not accept
a bind variable as the WHERE condition.
please help me in integrating the 4 parameters.
thanks in advances. please reply as soon as possible.
thanks & regards.
Bhakti.

Dear ileana,
I have tried the the option you have suggested and i was
successful.
Now there is another problem. As i had described the problem, i
have 4 parameters to use in hierarchy. but if i leave any of
them as NULL the report goes bust. i have defined REF cursors
for each of the parameter but cannot use it simultaneously as a
group error occurs.
could you help me out with this too.
thanks in advance.
bye
Bhakti

Resetting parameters in the Report Launch Form (qms0012f)

Similar Messages

Maybe you are looking for