Syntax to call a report

Hi , I want to know the syntax to call a Oracle Reports from my browser.
I'm on OAS 10gr2 on Windows 2008 server with reports 10gr2.
My reports are in "e:\rapports\"
Thanks

Please see this link for syntax for [reports deployment and call URLs on web|http://download.oracle.com/docs/cd/B14099_19/bi.1012/b14048/pbr_run.htm#sthref1411].
thanks
AMN

Similar Messages

  • 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

  • Calling web report in new browser window

    I have one Web-based Oracle report where I am calling another report in a FormatTrigger as:
    http://myserver/cgi-bin/rwcgi60.exe?key1+:param1
    I want to run this second report in a new browser window. I tried using TARGET="_blank"
    but I get syntax errors. I know that without the cgi parameters, it is easy to include the TARGET after the URL. But can anyone tell me the correct syntax for the above case (with parameters)? I tried putting the TARGET before '?' and after the param but both failed.
    Thanks
    null

    try this in your format trigger:
    web.show_document('http://myserver/cgi-bin/rwcgi60.exe?param1=value+param2=value', '_blank');

  • Calling a report from module pool program

    Hi all,
            I had a requirement where I need to call a report from the module pool program where in when we click REPORT button, it should display the report output in the another screen.
    Can we do by calling screen after pushing REPORT button. If so, where we should write that code ( In pbo or pai). Please give me an idea.
    Thanking you,
    Regards,
    Murali Krishna T

    Use submit syntax.
    Press F1 on submit, Donot use return statement with it.
    If so, where we should write that code ( In pbo or pai).
    Please understand about these two events before doing the requirement.

  • Problem when calling a report from java

    Hi all,
    i have created a report using ireport which contains arabic data.
    when i execute the report from ireport to generate a pdf file it works.
    however when i call this report from java i have an exception"
    Could not create the report Could not load the following font :
    pdfFontName : ARIAL.TTF
    pdfEncoding : Identity-H"
    the pdfFont i used it in ireport, also the pdfEncoding.
    did anyone passed with the same problem
    thanks for help

    Hello Oracle experts,
    The parameters are getting passed successfully in my report.
    But I want to know hous to use it in my query group.
    I just want the syntax.
    Thanks

  • Problem in Calling a report from form 6i using parameters

    Hello Oracle experts,
    I am facing a problem while calling a report using form 6i and passing parameters,
    Actually the problem is I want to use the parameters passed to reports in a
    query group in my report. I am not able to use the parameters passed by form to report in one of my query groups in report. Could anybody guide my how to use it.
    Thanks

    Hello Oracle experts,
    The parameters are getting passed successfully in my report.
    But I want to know hous to use it in my query group.
    I just want the syntax.
    Thanks

  • Creating a MaxLStatement to call a report script

    I created a MAxl statement to call a report script to create a text file ouput.
    here's the syntax I am using
    export database appname.databasename using report file '\\\\servername\\dir\\Reportsc.rep' to data_file 'D:\\Hyperion\Essbase\\report.txt'
    When I execute in EAS , get a message that the statement executed successfully, but the file was not created in the directory.
    Any ideas of why the output file is not created?

    A couple things of note.
    1. There is a single backslash in the path, that could affect where it was sent.
    2. Did it go to the D: drive of the EAS server?
    Robert

  • 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.

  • What is the correct syntax to have the report log into different databases?

    Hi,
    My current Oracle Reports are called against several databases, depending on region. I pass 'userid=reports/new1@tsoc' as one of teh parameters to access the 'tsoc' db. I just as well call 'userid=reports/new1@penang'.
    This syntax does not appear to work when placed in the BI Publisher URL as follows:
    http://seerus04.soco.agilent.com:9704/xmlpserver/emerald/tutorial/tutorial.xdo?_xpf=&_xpt=0&_xdo=%2Femerald%2Ftutorial%2Ftutorial.xdo&_xt=tutorial&_xf=html&_xmode=0&userid=reports/[email protected]
    Thn in advance,
    Gary

    Jorge,
    I have 11 databases in different regions. Oracle Reports allows me to pass in the database I wish to connect to.
    This is extremely pertinent to my evaluation as I cannot justify having 11 seperate instances for each of my reports.
    If what you say is true, I would consider BIP a poor subsitute for Oracle Reports.
    Thx,
    Gary

  • Calling one Report from another Report in oracle 10g(Urgent)

    Hi All,
    Can anyone let me know how to make hyperlink to call another report.
    I am trying
    SRW.SET_HYPERLINK('/reports/rwservlet?&report=rep059_v31.rdf&il&destype=cache&desformat=pdf');
    But i am getting message 'make sure the path or internet address is correct' .
    Please let me know what are the attributes used to create hyperlink.
    Thanks
    Nikhil
    Edited by: user9527411 on 29-Apr-2009 05:53
    Edited by: user9527411 on 30-Apr-2009 00:24

    Hello,
    The syntax is correct (except the & after the ?)
    You are using a "relative URL" . It means the browser will use the protocol , server and port from the current page in order to build a full URL
    (full URL = <protocol>://<server>:<port>/reports/rwservlet?report=test&destype=cache&desformat=html)
    Regard

  • Calling another  report by passing selection screen parameter

    Hi,
    I have created a report "ZREPA" with selection screen parameter say, "creator".
    Nw, i hv to call that report "ZREPA" from another report say "ZREPB" by passing an value to the selection screen field "creator".
    Can anyone tell me how to resolve this??
    Thanks,
    Aaru.

    Hi,
    You can call one selection screen from other selection screen program using SUBMIT command.
    The syntax is as follows -
    codeSUBMIT... VIA SELECTION-SCREEN
    USING SELECTION-SET <var>
    WITH <sel> <criterion>
    WITH FREE SELECTIONS <freesel>
    WITH SELECTION-TABLE <rspar>.[/code]
    e.g.
    The following executable program (report) creates a selection screen containing the parameter PARAMET and the selection criterion SELECTO:
    codeREPORT demo_program_submit_rep1.
    DATA number TYPE i.
    PARAMETERS paramet(14) TYPE c.
    SELECT-OPTIONS selecto FOR number.[/code]
    The program DEMO_PROGRAM_SUBMIT_REP1 is called by the following program using various parameters:
    REPORT demo_program_submit_sel_screen NO STANDARD PAGE HEADING.
    DATA: int TYPE i,
    rspar TYPE TABLE OF rsparams,
    wa_rspar LIKE LINE OF rspar.
    RANGES seltab FOR int.
    WRITE: 'Select a Selection!',
    SKIP.
    FORMAT HOTSPOT COLOR 5 INVERSE ON.
    WRITE: 'Selection 1',
    / 'Selection 2'.
    AT LINE-SELECTION.
    CASE sy-lilli.
    WHEN 4.
    seltab-sign = 'I'. seltab-option = 'BT'.
    seltab-low = 1. seltab-high = 5.
    APPEND seltab.
    SUBMIT demo_program_submit_rep1 VIA SELECTION-SCREEN
    WITH paramet eq 'Selection 1'
    WITH selecto IN seltab
    WITH selecto ne 3
    AND RETURN.
    WHEN 5.
    wa_rspar-selname = 'SELECTO'. wa_rspar-kind = 'S'.
    wa_rspar-sign = 'E'. wa_rspar-option = 'BT'.
    wa_rspar-low = 14. wa_rspar-high = 17.
    APPEND wa_rspar TO rspar.
    wa_rspar-selname = 'PARAMET'. wa_rspar-kind = 'P'.
    wa_rspar-low = 'Selection 2'.
    APPEND wa_rspar TO rspar.
    wa_rspar-selname = 'SELECTO'. wa_rspar-kind = 'S'.
    wa_rspar-sign = 'I'. wa_rspar-option = 'GT'.
    wa_rspar-low = 10.
    APPEND wa_rspar TO rspar.
    SUBMIT demo_program_submit_rep1 VIA SELECTION-SCREEN
    WITH SELECTION-TABLE rspar
    AND RETURN.
    ENDCASE.
    => To leave a called program, you can use SUBMIT .... AND RETURN. by choosing F3 or F15 from list level 0 of the called report.
    Regards,
    Omkaram.

  • Calling a report program in another program.

    can we call on report program in another report program. If yes, please give me the right syntax. Thanks in Advance.

    Hi,
      Use SUBMIT AND RETURN statement. In below given codes,
    I'm sending an internal table t_spfli to a memory id abc. After that I'm calling another program by using SUBMIT <program name> AND RETURN.
    Check these two programs
    PROGRAM 1
    REPORT  z_abap_memory.
    DATA:
      w_carrid TYPE spfli-carrid,
      BEGIN OF fs_spfli,
        carrid LIKE spfli-carrid,
        connid LIKE spfli-connid,
        fltime LIKE spfli-fltime,
      END OF fs_spfli.
    DATA:
      t_spfli LIKE
        TABLE OF
              fs_spfli.
    SELECT-OPTIONS:
      s_carrid FOR w_carrid.
    START-OF-SELECTION.
      PERFORM get_spfli.
      PERFORM disp_spfli.
    AT LINE-SELECTION.
      IF sy-lsind EQ 1.
        EXPORT t_spfli TO MEMORY ID 'ABC'.
        SUBMIT z_ABAP_MEMORY1 AND RETURN.
      ENDIF.
    END-OF-SELECTION.
      PERFORM disp_spfli.
    *&      Form  get_spfli
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM get_spfli .
      SELECT carrid
             connid
             fltime
        FROM spfli
        INTO TABLE t_spfli
       WHERE carrid IN s_carrid.
    ENDFORM.                    " get_spfli
    *&      Form  disp_spfli
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM disp_spfli .
      LOOP AT t_spfli INTO fs_spfli.
        WRITE: / fs_spfli-carrid,
                 fs_spfli-connid,
                 fs_spfli-fltime.
             HIDE:
        fs_spfli-carrid,
        fs_spfli-connid.
      ENDLOOP.
    ENDFORM.                    " disp_spfli
    PROGRAM 2
    REPORT  z_abap_memory1.
    DATA:
      BEGIN OF fs_spfli,
        carrid LIKE spfli-carrid,
        connid LIKE spfli-connid,
        fltime LIKE spfli-fltime,
      END OF fs_spfli,
      fs_fl LIKE fs_spfli.
    DATA:
      BEGIN OF fs_flight,
        carrid LIKE sflight-carrid,
        connid LIKE sflight-connid,
        fldate LIKE sflight-fldate,
      END OF fs_flight.
    DATA:
      t_spfli LIKE
        TABLE OF
              fs_spfli.
    DATA:
      t_fl LIKE t_spfli.
    DATA:
      t_flight LIKE
         TABLE OF
               fs_flight.
    IMPORT t_spfli FROM MEMORY ID 'ABC'.
    t_fl = t_spfli.
    SELECT carrid
           connid
           fldate
      FROM sflight
      INTO TABLE t_flight
      FOR ALL ENTRIES IN t_spfli
    WHERE carrid = t_spfli-carrid
       AND connid = t_spfli-connid.
    LOOP AT t_flight INTO fs_flight.
      WRITE: / fs_flight-carrid,
               fs_flight-connid,
               fs_flight-fldate.
    ENDLOOP.
    Regards
    Abhijeet

  • Calling Forms/Reports from a button

    How to call a Report or a Form which had been developed using the Wizard from a button created in a region of a page flow?
    National Steel
    Harirajan

    There are two ways to achieve this.
    1) Assign a URL for the button to redirect to. You will have to use the f?p syntax to do this, so for example, if your FlowID is 100 and your page ID is 4, you could redirect to:
    f?p=100:4:&SESSION
    Note the use of the substitution variable for the user's session.
    2) Create a branch that is fired by the button when the page is submitted. A branch is an instruction that tells the Flow which page to go to next. You only need to specify the page ID which has your form or report on it when you create the branch.
    Team Project Marvel

  • Call printing report

    Hello!
    I have a problem with printing program. I want to print notification during creating of it (IW21). To do this I have to call new report for printing. I use SUBMIT syntax, but I red that there are some problem to trigger that kind of program, if it isn't true please correct me.
    So maybe you know how to do somethuing like this?
    I tried to create new job but always I get error with sy-subrc = 8 (Error in job scheduling (JOB_SUBMIT)) and I don't know why. I didn't have any experience with jobs so far, so I don't know what could be cause of problem.
    My code is:
    call function 'GET_PRINT_PARAMETERS'
      exporting destination           = 'LOCL'
                copies                = 1
                list_name             = 'TEST'
                list_text             = 'SUBMIT ... TO SAP-SPOOL'
                immediately           = 'X'
    *            RELEASE               = 'X'
                new_list_id           = 'X'
                expiration            = 1
                line_size             = 79
                line_count            = 23
    *            LAYOUT                = 'X_PAPER'
    *            SAP_COVER_PAGE        = 'X'
    *            COVER_PAGE            = 'X'
    *            RECEIVER              = 'SAP*'
                department            = 'PM'
    *            no_dialog             = ' '
      importing out_parameters        = params
                valid                 = valid.
    if valid <> space.
      submit z_riprov00 via job 'name' number 1 to sap-spool
        spool parameters params
        without spool dynpro
        and return.
    endif.
    For all hints thanks in advance
    BL

    Maybe there is some mistake form the beginning.
    So maybe you know how to print notification by standart report RIPROV00? Operation is triggered during creating so data are stored in memory.
    If you know any example printing from memory. I will be grateful for any hints.
    Regards
    BL

  • Calling another report from a report

    just wanna explore the possibility...
    i have a.bat which will call a.rep.
    in a.rep, a function will loop and call b.rep.
    is this possible?

    Hi KLC
    This is prasanth again. In reports we can call a report from another report which is called "drilleddown reports"
    If ur requirement is this one, then we can do this by using SRW builtin called srw.run_report.
    syntax is srw.run_report(reportname,<arguements if any)
    Place a push button in report 'a' and put this code in that button.
    I think this will solve your problem. I dont know exactly what requirement you have. Because for ur last question regarding distribution not clearly understood, so i suggestion is incorrect. any way i am trying to distribute the date based on sql model and i will suggesst you soon, Since i am also a developer,please try my suggestion but i am not sure that will work 100% correctly.
    thans and regards
    prasanth a.s.

Maybe you are looking for