Calling Alv Report From Mobile

Hi All,
I need some information to cal a alv report from mobile. I created one report ans can see the selection screen in gui after calling. Here the screen is really big i need to adjust the size because it may take more load and time if i call from a mobile . Is it possible to call the same from mobile or do i need any separate application to call this from mobile. Please *** you valuable suggestions.
Regards
Madhu.

Hello Madhu,
What is your system details?
Kernel and BASIS?
Device OS & Browser?
What are the GUI Configuration settings of the ITSMobile Service?
What ITSMobile Generation STYLE was used?
Perhaps useful notes:
1037715 ITSmobile: Supported screen elements
1309633 ITSmobile: custom OMRT controls auto-recognized at runtime
1312835 ITSmobile: page navigation in ALV Grid on Windows Mobile
1668784 ITSmobile: new features for ALV Grid
Regards,
Oisin

Similar Messages

Calling a report from Module Pool

While calling a report from the module pool I'm not able to display th alv. The skeleton of the ALV is coming. But the data and headings are also not displayed.
But where as calling the same program from a report it is coming properly. can somebody please guide me where did I go wrong?

MODULE user_command_1001 INPUT.
w_ok_code = ok_code.
CLEAR ok_code.
CASE w_ok_code.
    WHEN 'BACK'.
      LEAVE PROGRAM .
    WHEN 'CREATE'.
      CALL TRANSACTION 'Z_FIRST_TIME'.
    WHEN 'SYNC'.
      CALL TRANSACTION 'Z_SYNC'.
    WHEN 'APPROVE'.
     SUBMIT zds_xx_approval_status WITH po_aname EQ sy-uname AND RETURN.
    WHEN 'OVERVIEW'.
      PERFORM show_all_reqids.
ENDCASE.
ENDMODULE.

Calling ALV report in BAPI

Hi All There ,
I am calling ALV report in my bapi but it is not gettin called it is not giving screen of parameter selection derectly selectin all parameter
coding is as below
points assured.
Data: MTAB_REPORT_HTML type standard table of W3HTML WITH HEADER LINE.
Submit ZSDRUSHORDERSRPT with SELECTION-TABLE SELTAB
        exporting list to Memory and return.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
    listobject = list_tab
EXCEPTIONS
    not_found = 1
    OTHERS     = 2.
CALL FUNCTION 'WWW_HTML_FROM_LISTOBJECT'
EXPORTING
   TEMPLATE_NAME       = 'WEBREPORTING_REPORT'
CHARSET             = 'UTF8'
TABLES
    html                = MTAB_REPORT_HTML
    listobject          = list_tab.
FREE MEMORY.
CLEAR LIST_TAB[].
loop at MTAB_REPORT_HTML.
concatenate htmlstring
             MTAB_REPORT_HTML-LINE into htmlstring.
endloop.

No, It is not specific to ALV. If you can give the example of that SUBMIT then it can be analyzed. It can be for other additions that is used in the submit statement.
Like:
1. ... USING SELECTION-SCREEN dynnr
2. ... VIA SELECTION-SCREEN
Effect
The addition USING SELECTION-SCREEN specifies the selection screen, VIA SELECTION-SCREEN specifies whether it is displayed. The additions selscreen_parameters provide values for the parameters, selection criteria, and the free selection of the called selection screen.
The values are transferred to the selection screen between the events INITIALIZATION and AT SELECTION-SCREEN OUTPUT The following hierarchy applies for transferring values:
1.     First, the variant of the addition USING SELECTION-SET is transferred, which sets all parameters and selection criteria to the values of the variant. The values previously set in the called program are overwritten.
2.     The values of the table of the addition WITH SELECTION-TABLE are then transferred. All parameters and selection criteria specified there are overwritten accordingly.
3.     Finally, the values of the additions WITH sel value are transferred. All parameters and selection criteria are overwritten accordingly. If the addition WITH sel value is used more than once for the same parameter, this is overwritten with the last specified value. If the addition WITH sel value is used more than once for the same selection criterion, a selection table with the corresponding number of lines is transferred.
Providing values for free selections is independent of this hierarchy.
Notes
     The options for parameter transfer enable a selection screen to be viewed as a parameter interface of an executable program. This applies particularly for background selection screen processing and for parameters and selection criteria that are defined without screen elements using the addition NO-DISPLAY
     When transferring data, note that any adjustments made to the screen format, such as abbreviations or the execution of conversion routines, are not executed for fields for which there are no screen elements on the selection screen. This applies for all parameters and selection criteria defined with NO DISPLAY. It also applies for all lines of a selection table with the exception of the first line.
     The additions selscreen_parameters only work the first time the called program is executed. If a selection screen is displayed in the called program, the runtime environment calls the program again after it is finished, thereby replacing the values specified in selscreen_parameters with the previous input values.
Addition 1
... USING SELECTION-SCREEN dynnr
Effect
This addition specifies which selection screen is called. dynnr is a data object that must contain the screen number of a selection screen defined in the called program when the SUBMIT statement is called.
     If the addition USING SELECTION-SCREEN is omitted or the screen number 1000 is entered, the standard selection screen is called. If no standard selection screen is defined in the called program, no selection screen is called.
     If a screen number that is not 1000 is entered in the addition USING SELECTION-SCREEN, the corresponding independent selection screen is called. If no selection screen with this screen number is defined in the called program, this leads to an untreatable exception.
Addition 2
... VIA SELECTION-SCREEN
Effect
If this addition is specified, the selection screen is displayed on the screen. Otherwise, background selection screen processing takes place. In background selection screen processing, the selection screen events are triggered without the selection screen being displayed.
SUBMIT - selscreen_parameters
Syntax
... [USING SELECTION-SET variant]
    [USING SELECTION-SETS OF PROGRAM prog]
    [WITH SELECTION-TABLE rspar]
    [WITH expr_syntax1 WITH expr_syntax2 ...]
    [WITH FREE SELECTIONS texpr] ... .
Extras:
1. ... USING SELECTION-SET variant
2. ... USING SELECTION-SETS OF PROGRAM prog
3. ... WITH SELECTION-TABLE rspar
4. ... WITH expr_syntax1 WITH expr_syntax2 ...
5. ... WITH FREE SELECTIONS texpr
Effect
USING-SELECTION-SET supplies all the selection screen components by means of a Variant variant. If you specify USING-SELECTION-SETS OF PROGRAM, you can use a variant from a different program; if you specify WITH SELECTION-TABLE, values for several selection screen components are transferred as the content of an internal table rspar; WITH expr_syntax supplies individual selection screen components with values. The addition WITH FREE SELECTIONS allows you to transfer free selections to the selection screen for alogical database.
Addition 1
... USING SELECTION-SET variant
Effect
If you specify this edition, the parameters and selection criteria for the selection screen are supplied with values from a variant. For variant, you must specify a character-like data object that contains the name of a variant for the program accessed when the statement is executed. If the variant does not exist, the system sends an error message. If the variant belongs to a different selection screen, it is ignored.
Note
You can create and manage variants for every program in which selection screens are defined, either in the ABAP Workbench or during execution of the program by choosing Goto - Variants on a selection screen.
Addition 2
... USING SELECTION-SETS OF PROGRAM prog
Effect
If you specify this addition, the variants of the program prog are used in the program accessed. For prog, you must specify a character-like data object that contains the name of a program when the statement is executed. The addition has the following effect:
     If a variant variant is specified with USING SELECTION-SET, the system searches for this variant in the program prog.
     If the selection screen is displayed with VIA SELECTION-SCREEN, all the functions that can be accessed by means of the menu path Goto - Variants affect the variants of the program prog. However, these functions are only active if prog is an executable program.
Note
The program prog should contain a selection screen that has the same parameters and selection criteria as the selection screen used in the program accessed.
Addition 3
... WITH SELECTION-TABLE rspar
Effect
If you specify this addition, parameters and selection criteria on the selection screen are supplied from an internal table rspar. You must specify an internal table with the row type RSPARAMS for rspar. The structured data type RSPARAMS is defined in the ABAP Dictionary and has the following components, all of which are data type CHAR:
     SELNAME (length 8),
     KIND (length 1),
     SIGN (length 1),
     OPTION (length 2),
     LOW (length 45),
     HIGH (length 45).
To supply parameters and selection criteria for the selection screen with specific values, the lines in the internal table rspar must contain the following values:
     SELNAME must contain the name of a parameter or selection criterion for the selection screen in block capitals
     KIND must contain the type of selection screen component (P for parameters, S for selection criteria)
     SIGN, OPTION, LOW, and HIGH must contain the values specified for the selection table columns that have the same names as the selection criteria; in the case of parameters, the value must be specified in LOW and all other components are ignored.
If the name of a selection criterion is repeated in rspar, this defines a selection table containing several lines and passes it on to the selection criterion. If parameter names occur several times, the last value is passed on to the parameter.
The contents of the parameters or selection tables for the current program can be entered in the table by the function module RS_REFRESH_FROM_SELECTOPTIONS.
Notes
In contrast to selection tables, the data types of the components LOW and HIGH in table rspar are always of type CHAR and are converted to the type of the parameter or selection criterion during transfer, if necessary.
     When entering values, you must ensure that these are entered in the internal format of the ABAP values, and not in the output format of the screen display.
Addition 4
... WITH expr_syntax1 WITH expr_syntax2 ...
Effect
This addition supplies values to individual parameters or selection criteria for the selection screen. Parameters are supplied with single values and selection criteria with selection tables that overwrite values already specified in the program accessed. The selection table to be transferred is compiled from all the expr_syntax additions that address the same selection criterion sel. You can specify the following statements for expr_syntax, where you have to specify the name of a parameter or a selection criterion directly for sel:
     sel {EQ|NE|CP|NP|GT|GE|LT|LE} dobj [SIGN sign]
Transfer of a single value.
The operators before dobj correspond to the values specified for column OPTION for selection tables. For dobj, you must specify a data object whose data type can be converted to the data type of the selection screen component sel. For sign, you can specify a character-like field that must contain 'I' or 'E'. The standard value is 'I'.
If sel is a selection criterion, the system appends a line in the selection table to be transferred, placing the operator in column OPTION, the content of dobj in column LOW, and the content of sign in column SIGN.
If sel is a parameter, it is set to the value of dobj in the program accessed. The operator and the value of sign are not taken into account.
     sel [NOT] BETWEEN dobj1 AND dobj2 [SIGN sign]
Transfer of an interval.
In this case, sel must be a selection criterion. For dobj, you must specify data objects whose data type can be converted to that of the columns LOW and HIGH for the selection criterion sel. For sign, you can specify a character-like field that must contain 'I' or 'E'. The standard value is 'I'.
A line is appended in the selection table to be transferred. If NOT is specified, the value 'NB' is placed in column OPTION; otherwise, the value entered is 'BT'. The content of the data objects dobj and sign is placed in the columns LOW, HIGH, and SIGN.
     sel IN rtab
Transfer of a ranges table.
In this case, sel must be a selection criterion. For rtab, you must specify an internal table that has the same structure as the selection table for selection criterion sel. A table of this type can be created using the addition RANGE OF to the statements TYPES and DATA.
The lines in table rtab are appended to the selection table to be transferred.
You can specify the addition expr_syntax more than once, and you can also specify the same selection screen component more than once.
Notes:
     = or INCL can also be used instead of the operator EQ.
     When entering values, you must ensure that these have the internal format of the ABAP values, and not the output format of the screen display.
Example
The program report1 has a stand-alone selection screen with the screen number 1100. In the program report2, an internal table with row type RSPARAMS and a ranges table are filled for this selection screen. These are transferred at SUBMIT together with a single condition.
Program accessed
REPORT report1.
DATA text TYPE c LENGTH 10.
SELECTION-SCREEN BEGIN OF SCREEN 1100.
SELECT-OPTIONS: selcrit1 FOR text,
                  selcrit2 FOR text.
SELECTION-SCREEN END OF SCREEN 1100.
Calling program
REPORT report2.
DATA: text       TYPE c LENGTH 10,
      rspar_tab TYPE TABLE OF rsparams,
      rspar_line LIKE LINE OF rspar_tab,
      range_tab LIKE RANGE OF text,
      range_line LIKE LINE OF range_tab.
rspar_line-selname = 'SELCRIT1'.
rspar_line-kind    = 'S'.
rspar_line-sign    = 'I'.
rspar_line-option = 'EQ'.
rspar_line-low     = 'ABAP'.
APPEND rspar_line TO rspar_tab.
range_line-sign   = 'E'.
range_line-option = 'EQ'.
range_line-low    = 'H'.
APPEND range_line TO range_tab.
range_line-sign   = 'E'.
range_line-option = 'EQ'.
range_line-low    = 'K'.
APPEND range_line TO range_tab.
SUBMIT report1 USING SELECTION-SCREEN '1100'
               WITH SELECTION-TABLE rspar_tab
               WITH selcrit2 BETWEEN 'H' AND 'K'
               WITH selcrit2 IN range_tab
               AND RETURN.
Result
After report1 has been accessed by report2, the selection tables for the selection criteria selcrit1 and selcrit2 in the program accessed contain the following entries:
Addition 5
... WITH FREE SELECTIONS texpr
Effect
This addition supplies values to the dynamic selections for the selection screen for a logical database. The program accessed must be linked to a logical database that supports dynamic selections. texpr must be an internal table of the type RSDS_TEXPR from type group RSDS.
In texpr, the selections for the dynamic selections are specified in an internal format (Reverse Polish Notation). You can use function modules FREE_SELECTIONS_INIT, FREE_SELECTIONS_DIALOG, and FREE_SELECTIONS_RANGE_2_EX from the function group SSEL to fill texpr in the calling program. While the first two function modules execute a user dialog, you can transfer ranges tables to FREE_SELECTIONS_RANGE_2_EX for each node in the dynamic selection in an internal table of the type RSDS_TRANGE. These are then converted to a table of the row type RSDS_TEXPR. If the calling program contains a selection screen with the same dynamic selections, you can transfer its content beforehand to a table of the type RSDS_TRANGE using the function module RS_REFRESH_FROM_DYNAMICAL_SEL.
The lines in the internal table type RSDS_TRANGE contain a flat component TABLENAME for each node and a table-like component FRANGE_T of the type RSDS_FRANGE_T for the fields in the node. The lines in RSDS_FRANGE_T contain a flat component FIELDNAME for each field and a table-like component SELOPT_T of the row type RSDSSELOPT from the ABAP Dictionary. RSDSSELOPT contains the four components SIGN, OPTION, LOW, and HIGH and can include the ranges table.
Example
Program report1 is linked to the logical database F1S, which supports dynamic selections for the node SPFLI. Program report2 enters conditions in a nested internal table of the type rsds_trange with selection conditions for field CONNID in node SPFLI; this is then converted to a table of the type rsds_texpr, which is transferred at SUBMIT.
Program accessed
REPORT report1.
NODES: spfli, sflight, sbook.
Calling program
REPORT report2.
TYPE-POOLS rsds.
DATA: trange TYPE rsds_trange,
      trange_line
        LIKE LINE OF trange,
      trange_frange_t_line
        LIKE LINE OF trange_line-frange_t,
      trange_frange_t_selopt_t_line
        LIKE LINE OF trange_frange_t_line-selopt_t,
      texpr TYPE rsds_texpr.
trange_line-tablename = 'SPFLI'.
trange_frange_t_line-fieldname = 'CONNID'.
trange_frange_t_selopt_t_line-sign   = 'I'.
trange_frange_t_selopt_t_line-option = 'BT'.
trange_frange_t_selopt_t_line-low    = '0200'.
trange_frange_t_selopt_t_line-high   = '0800'.
APPEND trange_frange_t_selopt_t_line
TO trange_frange_t_line-selopt_t.
trange_frange_t_selopt_t_line-sign   = 'I'.
trange_frange_t_selopt_t_line-option = 'NE'.
trange_frange_t_selopt_t_line-low    = '0400'.
APPEND trange_frange_t_selopt_t_line
TO trange_frange_t_line-selopt_t.
APPEND trange_frange_t_line TO trange_line-frange_t.
APPEND trange_line TO trange.
CALL FUNCTION 'FREE_SELECTIONS_RANGE_2_EX'
EXPORTING
    field_ranges = trange
IMPORTING
    expressions = texpr.
SUBMIT report1 VIA SELECTION-SCREEN
               WITH FREE SELECTIONS texpr.

How to call ALV Report and SMARTFORMS through Pushbutton

hi,
i have created a report.My task is to create two buttons:
1)ALV Report.
2)SMARTFROMS.
Through these button i have to call ALV Report and SMARTFORMS. i have created both button and when i execute the program,
it shows me the button but not working when i click on it.
this is the coding i have used in my report for calling ALV Report.
''Tables sscrfields,
DATA flag(1) Type c.
selection-screen: begin of screen 500 AS WINDOW TITLE tit,
BEGIN OF LINE,
PUSHBUTTON 2(18) but1 USER-COMMAND cli1,
end of line,
BEGIN OF LINE,
PUSHBUTTON 2(18) but2 USER-COMMAND cli2,
end of line,
end of screen 500.
SET PF-STATUS 'STATUS_0100'.
at selection-screen.
case sscrfields.
WHEN 'cli1'.
flag = '1'.
WHEN 'cli2'.
flag = '2'.
endcase.
at USER-COMMAND.
CASE SY-UCOMM.
WHEN 'Detail'.
select vbakkunnr VBakernam VBAkaudat vbakaufnr vbapKWMENG vbapmatnr vbap~ARKTX
into but1
from vbak inner join vbap
on vbakvbeln = vbapvbeln.
ENDSELECT.
ENDCASE.
START-OF-SELECTION.
tit = 'Format'.
but1 = 'ALV Report'.
but2 = 'SMARTFORMS'.
CALL SELECTION-SCREEN 500.
and i also use in my report
''case sscrfields-ucomm'' and ''submit my_report'' but the still button doesn't show the result.
Thanks & Regards,

Hi,
         I understood your requirement. What i found is, you are creating screen 500 and call it after START-OF-SELECTION,
at that time your AT USER-COMMAND doesn't work.
So what i would suggest , u should create GUI STATUS named ' PFSTAT'
having one functional key 'EXIT' that is standard u can just name it
and
other two u can assign in Freely assigned Function keys as 'BUT1' & 'BUT2'. and than in Application Toolbar u jst have it in ITEM LIST by typing BUT1 and BUT2.
For 'BUT1' text would be 'ALV' and 'BUT2' text would be 'SMARTFORMS'.
Now in Program you can code,,,
START-OF-SELECTION.
SET PF-STATUS 'PFSTAT'.
WRITE:/ 'TEST'.
at user-command.
case SY-UCOMM.
    WHEN 'BUT1'.
    WHEN 'BUT2'.
    WHEN 'EXIT'.
       LEAVE PROGRAM.
endcase.
In Program u set PF STATUS and use at user-command event, whcih gets triggered when u click on button . When u execute program you get two button in application tooldbar.
Please do needful.
Thanks,
Saurin SHah

Print Message Report from Mobile

Hello...
We need modify standard mobile infrastructure java code...
We need print some report from Mobile Front-end.
Is possible to print all MESSAGE data that we can see from front-end of mobile infrastructure 2.5 ???
thank you very much
Stefano

I haven't really done much enhancements on MAM 2.5, but Im sure sami will let you know where to add the code, or you can review the MAM enhancement guide on the CD.
In regards to printing the PIOS API is pretty simple. If you are using a laptop to print to a normal printer then you can just use the Win32 Drivers..(installed via driver addon from web sap console.)If you are using the handheld you will need to find the appropriate drivers.
Here is some code I used in one of my applications:
 Connector conn = Connector.getInstance();
 DriverInfo[] driverInfo = conn.listDrivers(ConnectionType.PRINTER);
 PrinterParameters params = new PrinterParameters(driverInfo[0]);
 params.setPrinterMode(PrinterParameters.GRAPHIC_MODE);
 GraphicPrinter gp = (GraphicPrinter) conn.open(params);
 File myImage = new File("c:
smalllogo.bmp");
 if (myImage.exists()) {
 float x = 0;
 float y = 50;
 try {
 String[] sFonts =
 gp.getFontConfigurationManager().listFontNames();
 PrinterFont pf = gp.getFont(sFonts[0]);
 gp.drawText(
 pf,
 25,
 25,
 "TO For Delivery # = "
 + dbAccess.getItemFieldValue(arrayItems[0], "VBELN"),
 GraphicPrinter.NO_ROTATION);
 for (i = 0; i < arrayItems.length; i++) {
 gp.drawText(
 pf,
 25,
 y,
 "Delivery Item # = "
 + dbAccess.getItemFieldValue(
 arrayItems,
 "POSNR"),
 GraphicPrinter.NO_ROTATION);
 y = y + 10;
 gp.drawText(
 pf,
 25,
 y,
 "Material # = "
 + dbAccess.getItemFieldValue(
 arrayItems,
 "MATNR"),
 GraphicPrinter.NO_ROTATION);
 y = y + 10;
 gp.drawText(
 pf,
 25,
 y,
 "Quantity to Pick = "
 + dbAccess.getItemFieldValue(
 arrayItems,
 "LFIMG"),
 GraphicPrinter.NO_ROTATION);
 y = y + 25;
 gp.doPrint(1);
 gp.close();
 } catch (Throwable tFile) {
 tFile.printStackTrace();
 }
This should give you an idea, you should also read through the MDK documentation for the printer API (PIOS). Its quite easy to pick up and as long as you have the driver and connector installed it prints right away.(You could also use the Peripheral emulator in
NWDS to test the code first)
Hope this helps,
Wael..
Dont forget the rewards
Message was edited by: wael aoudi

**How to call a report from a form by passing a specfic value?????

Hi Expert,
I want to call a report from a form.My problem scenario like, a user is login to his account and there is a option called ADMIT CARD(Push Button).Now when he pressed the button a report will generate.I want that when he pressed the button the user id of the user will passed to the report and the report will generate corresponding to his details which was stored in the database.This scenario is like any online admit card.
Suppose I want a details report of employee whose employee_id=100.How could I pass this value(employee id) to report which will generate a report details.
Thanks,
TAPAN
Message was edited by:
user630863

Thanks for replying.
Actually I am a beginner.I think that I have to use RUN_REPORT_OBJECT built-in.But I cannot understand the parameterlist.Can u plz give me any example or code then I am very thankful.
Suppose I want a details report of employee whose employee_id=100.How could I pass this value(employee id) to report which will generate a report details.
Thanks,
TAPAN

Calling a report from a form based on procedure

I created a form based on a procedure.
It is a entry form where the user is selecting or enters data then on submit I must display the report based on selected data.
I know I can simply create a report with all bind variable and do the job.
My question is what is the syntax to call the report from the procedure for the selected parameters values.
Thanks
Lawrence

If you want to display other HTML page after successful submission, you need to use
either go or call method.
I created a form on SCOTT.EMP and a report on SCOTT.EMP and the report accept a parameter for
the deptno. Here is my on successfull submission code:
declare
l_dept number;
l_url varchar2(2000);
begin
l_dept := p_session.get_value_as_number('DEFAULT', 'A_DEPTNO', 1);
l_url := 'scott.rpt_mask_1.show?p_arg_names=emp.deptno&p_arg_values='| |l_dept;
go(l_url);
end;
null

How to call a report from a web application

Hi,
I have a web server in wich is installed Reports 6i. My question is how can I call reports 6i to generate a pdf using a .rep file from my web application (built with java)?

Hi,
The below link will be very useful for one who need idea on calling Oracle Report from Java Application,
http://www.oracle.com/technology/products/reports/htdocs/getstart/examples/reportswebservice/index.html
Thanks & Rgds,
M T

Call Oracle Reports from Forms ver 9i or 10g

Hi,
Can somebody guide me, how to call Oracle Reports from the Oracle form 9i,
Run_product is no more available into 9i & 10g, Run_report_object is not working with out put type "Screen" or "preview".
What is the best way to call the reports from the form ??? pls help...
Thanks in avdance.
Jitesh ([email protected])

You can use RUN_REPORT_OBJECT with CACHE type, and WEB.SHOW_DOCUMENT to view the document on the screen.
In the Forms help you should find examples.
If you have access to Metalink, have a look at Note:207396.1.

How to call a report from a menu ?

I am converting 6i client/server forms to 9i.
I have a menu that has an option on it to run a report for each menu item selected using RUN_PRODUCT.
9i is making this obsolete, so how can I call a report from a menu (not a form) now then ?
In a form it is fine cos I just use the Report Object - a menu does not have this facility.
Thanks in advance.

Hi,
so here is how this should be done:
1. Create a Reports node in the Forms module that uses the menu (you don't have to create one Reports Object for each report that you want to run)
2. From the menu, before calling Run_Report_Object() use Set_Report_Object_Property() to set the phsical file name of the Reports that should be executed. This is kind of best practice and does not have a performance hit.
There is a bug filed against Forms to extend the menu files with a reports Object node. This could require a change to teh file structure which is why we looking for Forms 10i to implement this. (If it turns out that we can have it without recompiling the menu modules then it may go into a patch set - however this seems unlikely from my point of view)
Fran

Calling a report from Form 6i

Hi,
I want to call a report from Form 6i at run time. And I write the following code in When Buttton Press trigger . when I press the button it will gives no response.
declare
     x report_object;
     y varchar2(100);
begin
     x:=find_report_object('billform');
     y:=run_report_object(x);
end;
for more information , path of my report is: C:\REP\billform.rdf
please send me the solution of this problem
E_mail: [email protected]
Shahzad

hi,
now i am using the following code in when button press trigger. if u give me ur e_mail address i will send u FMB and RDF files used for Scott/tiger EMP table for the sample.
declare
repo_Para     ParamList;
BEGIN
repo_Para:=Get_Parameter_List('Report_para');
IF not Id_null(repo_Para) THEN
     destroy_parameter_list(repo_para);
end if;
repo_Para:=Create_Parameter_List('Report_para');
Add_Parameter(Repo_para,'PARAMFORM',TEXT_PARAMETER,'No');
Add_Parameter(Repo_para,'MAXIMIZE',TEXT_PARAMETER,'Yes');
     Add_Parameter(Repo_para,'BDATE',TEXT_PARAMETER,:BLOCK3.a_dptno);
     Add_Parameter(Repo_para,'EDATE',TEXT_PARAMETER,:BLOCK3.b_dptno);
     RUN_PRODUCT(REPORTS,'c:\apu\DDATE.rep', SYNCHRONOUS,
          runtime, FILESYSTEM,Repo_para,NULL);
end;
BDATE & EDATE are two user parameters created in report.
when i press the button in form pass parameters the report will be called but no data will be display but when i directly run reprot from report buider and pass same values of BDATE & EDATE it will show data.
please give me ur e mail address or help me for this problem
best regards,
shahzad

Calling a Report from a Form

I have uploaded my form to the app server and compiled to Linux. I have copied my RDF file to the reports_path/demo directory. I can run the report via a link from our portal using the URL as follows:
/reports/rwservlet?report=IndRpt.rdf&desformat=pdf&destype=cache&userid=' target="_blank"
That opens the report in a separate window, which is what we want. So far, so good.
I can run the form via a link from our portal as well using the URL as follows:
/forms/frmservlet?config=bsc_ind
The config section hides all the form parameters very nicely.
In the portal, I created a Report Server Access portlet, REP_OMHAST2_MIDTIER, and use the following set_report_object calls in my form:
repid := find_report_object('IndRep');
SET_REPORT_OBJECT_PROPERTYrepid,REPORT_EXECUTION_MODE,BATCH);
SET_REPORT_OBJECT_PROPERTYrepid,REPORT_COMM_MODE,SYNCHRONOUS);
SET_REPORT_OBJECT_PROPERTY(repid,REPORT_DESTYPE,CACHE);
SET_REPORT_OBJECT_PROPERTY(repid,REPORT_DESFORMAT,'PDF');
SET_REPORT_OBJECT_PROPERTYrepid,REPORT_SERVER,'rep_omhast2_midtier');
SET_REPORT_OBJECT_PROPERTY(repid,REPORT_OTHER,ls_param);
v_rep := RUN_REPORT_OBJECT(repid);
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
/*Display report in the browser*/
WEB.SHOW_DOCUMENT('http://omhast2.omh.state.ny.us:7777/reports/rwservlet/getjobid'||
substr(v_rep,instr(v_rep,'_',-1)+1)||'?'||'server=rep_omhast2_midtier ','_blank');
All that comes right out of the white paper.
Now here's the weird part, I have never seen this before. When I click my "Show Report" button in my form, the report seems to be running, but then I get a very strange dark grey, square icon superimposed over my mouse pointer. The icon has a small yellow "starburst" pattern with a tiny red exclamation point inside. The report does not appear on screen.
Incidentally, all of this works correctly when I run the same scenario on my workstation using the call to rwserver as: rwserver server=rep_omhast2_midtier. But when we port it to the app server, it does not run. I think it has to be in the way the form calls the report because the report will run as a stand-alone object.
Anything apparent to anyone out there?

Well, it looks like I stumped the band. And with good reason. Sorry for the error. The problem was that the user running the form and the report had a pop-up blocker that was blocking the report. The form and the report ran from another machine. I allowed pop-ups from the report's URL and that enabled the report to appear.
So, here we have another example of how to call a report from a form. Again, I am sorry for any angst this may have caused.

CALLING A REPORT FROM FORMS (PROBLEM)

MY PROBLEM IS THE NEXT:
I CREATED A MASTER-DETAIL REPORT CALLING 'ASUNTOS'WITH THE NEXT QUERY:
SELECT ABOGADOS.APELLIDO_P,ABOGADOS.APELLIDO_M,ABOGADOS.NOMBRES,
ASUNTOS.EXP_INT,ASUNTOS.MATERIA,ASUNTOS.GERENCIA,
ASUNTOS.EMPRESA,ASUNTOS.RECLAMA,ASUNTOS.PESOS,
ASUNTOS.DOLARES
FROM ABOGADOS,ASUNTOS
WHERE ABOGADOS.FICHA = ASUNTOS.F_ABOG
AND ASUNTOS.F_ABOG = :ABOGADO ;
-- ABOGADO = PARAMETER.
THIS REPORT WORKS FINE THE PROBLEM IS WHEN I TRY CALL THIS REPORT FROM FORM I'VE USE A BUTTON(WHEN_BUTTON_PRESSED) WITH THE NEXT CODE:
DECLARE
LISTA PARAMLIST := GET_PARAMETER_LIST('ABOG');
BEGIN
IF ID_NULL(LISTA) THEN
LISTA := CREATE_PARAMETER_LIST('ABOG');
ADD_PARAMETER(LISTA,'DESTYPE',TEXT_PARAMETER,'PRINTER');
ADD_PARAMETER(LISTA,'DESNAME',TEXT_PARAMETER,'LPT2');
ADD_PARAMETER(LISTA,'ABOGADO',TEXT_PARAMETER,TO_CHAR(:ASUNTOS.F_ABOG));
-- ADD_PARAMETER(LISTA,'PARAMFORM',TEXT_PARAMETER,'YES');
END IF;
RUN_PRODUCT(REPORTS,'ASUNTOS',SYNCHRONOUS,RUNTIME,FILESYSTEM,LISTA,NULL);
END;
BUT THE REPORT NOTHING DISPLAY.
THERE ARE SOMETHING WRONG WITH THE CODE IN THE BUTTON

Roberto,
Does your report work when it is not called from Forms?
try the following:
[TOOLS_HOME]\BIN\RWRUN60 module=ASUNTOS destype=screen userid=<username>/<password>@<tns> ABOGADO=<some_valid_code>
where TOOLS_HOME is the directory where Reports is installed.
I can see nothing wrong with your code.
Maybe some error in the query?
Also, I would check for the existence of multiple ASUNTOS report definitions. Maybe Forms is calling an older one.
Hope this helps,
Pedro das Neves
([email protected])

Calling a Report from Form in 10g

Hi all,
I am very new to Oracle Form builder, I wana to call a report from a Form.
we are using Oracle 10g Developer suit.
Can any body please help me regarding on this?
Regards
Tanmaya Pradhan(Tam)

..or
Take a look at
Re: Run Report10g Through form 10g

Calling a Report from Bapi

Dear all,
I am trying to create a customer from external system through bapi. For this is i have to follow these steps.
1) I am trying to call a report from external system through bapi.
2) I want to pass data from bapi to a bdc program and run it to create a customer.
3) After creating a customer I need to send the ceated customer no again to the bapi from where i passed the data to bdc.
is it possible .
Give me a good idea on this how to work with it.
Regards,
Madhu.

Hi Madhu,
SAP has already given standard BAPI to create customer creation "BAPI_CUSTOMER_CREATEFROMDATA". So there is no need for you to create any thing new. Jut test this BAPI first whether this suit your requirement or not. If it satisfy your requirement then call it directly from external system. On how to call this BAPI or other BAPis searc google or SDn you will definetaly find something.
second approach is if nothing works for you( No BAPI satisfy your requirement) then only go for BDC aapproach. To do that, create a RFC function module( BAPi and RFC FM are diff thing, they looks same but they are not ). Inside your RFC FM directly write the BDC code to create customer.
Regards
Anurag

Calling Alv Report From Mobile

Similar Messages

Maybe you are looking for