What is USING SELECTION-SET in submit statement?

hi,
any body can tel me.
SUBMIT rptedt00
                  USING SELECTION-SET 'HRESS_TEDT00'
                  WITH pnppernr-low EQ i_pernr
                  WITH pnptimr6     EQ 'X'
                  WITH pnpbegda     EQ i_begda
                  WITH pnpendda     EQ i_endda
                  TO SAP-SPOOL
                  SPOOL PARAMETERS ls_params
                  WITHOUT SPOOL DYNPRO
                  AND RETURN.
here use of USING SELECTION-SET and which name we have to specify in quotes.
Regards,
Shankar.

Hi
USING SELECTION-SET <var>
This addition tells the system to start the called program with the variant var
You specify the variant in the quotes.
Check the below links
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/dba51a35c111d1829f0000e829fbfe/frameset.htm
regarding calling another program from current report
Hope this helps
Regards
Shilpa

Similar Messages

How to use selection-set in submit report

Hi ,
How to use,
submit report via selection-screen
                                     using selection-set 'ABC' .
Can somebody pl tell me how to use selection-set 'ABC' in submit report . It would be nice if someone can send me a piece of code.
Regards,
Hardik

Hi,
This is from ABAPDOCU.
SUBMIT REPORT01
       VIA SELECTION-SCREEN
       USING SELECTION-SET 'VARIANT1'
       USING SELECTION-SETS OF PROGRAM 'REPORT00'
       AND RETURN.
Effect
Executes the program REPORT01 with the variant VARIANT1 of the program REPORT00.
You can use f1 help also.

Using a layout in SUBMIT statement

Hi,
I am calling a program from another program using a SUBMIT statement. I'm also using a layout to do so.
SUBMIT rffmepgax
 WITH s_fonds = s_fund-low
 WITH s_fictr = s_fc-low
 WITH s_hkont = c_gl
 WITH p_per_fr = s_poper-low
 WITH p_per_to = s_poper-high
 WITH p_fyr_fr = s_year-low
 WITH p_fyr_to = s_year-low
 WITH s_fipex = c_citem
>>> WITH p_disvar = '/ZTRAVEL'
 WITH p_maxsel = c_max
 WITH s_wrttp = c_vt1
 WITH s_wrttp = c_vt2
 WITH FREE SELECTIONS texpr
 AND RETURN
 EXPORTING LIST TO MEMORY.
The problem is that /ZTRAVEL is a public layout that anyone can change. I can rewrite the code to use a user-specific layout, but then only I can run the program. If anyone else tries, it stops and says the layout doesn't exist.
Is it possible to create a public layout that cannot be changed by anyone? What is the t-code for this?
thanks,
Kevin

Hi
USING SELECTION-SET <var>
This addition tells the system to start the called program with the variant var
You specify the variant in the quotes.
Check the below links
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/dba51a35c111d1829f0000e829fbfe/frameset.htm
regarding calling another program from current report
Hope this helps
Regards
Shilpa

How to use SELECTION-SET with FREE-SELECTIONS?

Hi,
how to use SELECTION-SET with FREE-SELECTIONS?
Regards,
Vinay.

Check http://help.sap.com/abapdocu_70/en/ABAPSUBMIT_SELSCREEN_PARAMETERS.htm

Use call transaction or submit statement

Hi, i have a complex transaction, it has two control programs, a Z program and a standard program. I need execute it by call transaction or submit statement. In this transaction there are some select-options that i want fill with specific values.
Can you help me with it?

Hi Robin, the SHDB transaction was very useful. Now i have other problem. This transaction execute a jobs set.I already have filled all of fields in the transaction, i saved the parameters for the execution by SAVE button (BDC_OKCODE=SAVE), but the transaction don't release the jobs and must do it. The last action (to release the jobs set) is executed by the OK button(BDC_OKCODE=OK).
This is the code that i'm implementing:
REPORT ZPRUEBA_SALDOS_ANTERIORES     .
DATA: BDCDATA TYPE TABLE OF BDCDATA.
DATA: ITAB TYPE TABLE OF BDCMSGCOLL.
DATA: WA_ITAB TYPE BDCMSGCOLL.
DATA: PROGRAM LIKE SY-REPID ,
      WA_BDCDATA TYPE BDCDATA.
DATA: DATE_ID(10).
DATA: DATE_CONV(11).
DATA: T_ID(6).
DATA: DES_ERROR(500).
*"parametro zdo(para tipo de documentos)
*RANGES: R_BLART FOR DFKKOP-BLART,
*        R_VKONT FOR FKKVKP-VKONT.
*INITIALIZATION.
START-OF-SELECTION.
CALL FUNCTION 'CONVERSION_EXIT_SDATE_OUTPUT'
       EXPORTING
            INPUT = SY-DATUM
       IMPORTING
            OUTPUT = DATE_CONV.
DATE_ID = SY-DATUM.
CONCATENATE DATE_ID+6(2) '.' DATE_ID+4(2) '.' DATE_ID+0(4) INTO DATE_ID.
CONCATENATE DATE_CONV+3(3) '_' DATE_CONV+0(2) INTO T_ID.
WA_BDCDATA-PROGRAM = 'SAPLFKKAKTIV2'.
WA_BDCDATA-DYNPRO = '1000'.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = 'FKKAKTIV2_DYNP_1000-LAUFD'.
WA_BDCDATA-FVAL = '11.06.2008'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'FKKAKTIV2_DYNP_1000-LAUFI'.
WA_BDCDATA-FVAL = 'MAR_38'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
* WA_BDCDATA-PROGRAM = 'SAPLZ_CL_PROCESOS_EN_MASA'.
WA_BDCDATA-PROGRAM = 'SAPLFKKAKTIV2'.
* WA_BDCDATA-DYNPRO = '1001'.
WA_BDCDATA-DYNPRO = '1000'.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'P_STICHT'.
WA_BDCDATA-FVAL = DATE_ID.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'S_BUKRS-LOW'.
WA_BDCDATA-FVAL = 'PCS'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'S_VKONT-LOW'.
WA_BDCDATA-FVAL = '0'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'S_VKONT-HIGH'.
WA_BDCDATA-FVAL = '999999999999'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=%01410010001580545'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-PROGRAM = 'SAPLALDB'.
WA_BDCDATA-DYNPRO = '3000'.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
* CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(01)'.
WA_BDCDATA-FVAL = 'BS'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(02)'.
WA_BDCDATA-FVAL = 'FS'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(03)'.
WA_BDCDATA-FVAL = 'CD'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(04)'.
WA_BDCDATA-FVAL = 'EF'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(05)'.
WA_BDCDATA-FVAL = 'TR'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(06)'.
WA_BDCDATA-FVAL = 'TF'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(07)'.
WA_BDCDATA-FVAL = 'TC'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(08)'.
WA_BDCDATA-FVAL = 'LP'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'RSCSEL-SLOW_I(09)'.
WA_BDCDATA-FVAL = 'NC'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=ACPT'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
* WA_BDCDATA-PROGRAM = 'SAPLZ_CL_PROCESOS_EN_MASA'.
WA_BDCDATA-PROGRAM = 'SAPLFKKAKTIV2'.
* WA_BDCDATA-DYNPRO = '1001'.
WA_BDCDATA-DYNPRO = '1000'.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=TAB03'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=PRPRN'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-PROGRAM = 'SAPLSPRI'.
WA_BDCDATA-DYNPRO = '0100'.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = 'PRI_PARAMS-PDEST'.
WA_BDCDATA-FVAL = 'LOCAL'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'PRI_PARAMS-PLIST'.
WA_BDCDATA-FVAL = '1604_SA_16'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=SAVE'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-PROGRAM = 'SAPLFKKAKTIV2'.
WA_BDCDATA-DYNPRO = '1000'.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
* CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=TAB04'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'FKKAKTIV2_DYNP_1190-VARI'.
WA_BDCDATA-FVAL = 'INTERES'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'FKKAKTIV2_DYNP_1200-JOBS_LOAD_BALA'.
WA_BDCDATA-FVAL = '6'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=SAVE'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=DISP'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-PROGRAM = 'SAPLFKJO_JOB'.
WA_BDCDATA-DYNPRO = '0100'.
WA_BDCDATA-DYNBEGIN = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = 'D100_FIELDS-XBACKGR'.
WA_BDCDATA-FVAL = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'D100_FIELDS-XIMMEDIATE'.
WA_BDCDATA-FVAL = 'X'.
APPEND WA_BDCDATA TO BDCDATA.
WA_BDCDATA-FNAM = 'BDC_OKCODE'.
WA_BDCDATA-FVAL = '=OK'.
APPEND WA_BDCDATA TO BDCDATA.
CALL TRANSACTION 'ZPSA' USING BDCDATA MODE 'A'
                           MESSAGES INTO ITAB.
Edited by: Marcel ochoa on Jun 12, 2008 5:01 PM
Edited by: Marcel ochoa on Jun 12, 2008 5:03 PM
Edited by: Marcel ochoa on Jun 12, 2008 5:06 PM
Edited by: Marcel ochoa on Jun 12, 2008 10:43 PM
Edited by: Marcel ochoa on Jun 12, 2008 10:45 PM
Edited by: Marcel ochoa on Jun 12, 2008 11:37 PM

What is use of set operators in OBIEE

Hi Guys,
Colud you please tell me what is main use of Set Operators (Intersection,Union,Union all)in OBIEE.
Is it mandatory to use them in reports?
Pls tell me.
Regards,
siva

Hi,
What scenario we are using set operators.
For Eg.
Col 1 is having values:
A
B
C
Col 2 is having values:
1
2
3
I have to create a new column in answers having values
A
B
C
1
2
3
solution:
You can use SET operators in OBIEE and it's really easy to set it in answers section. So create one request and then add other similar request to it by using UNION operator.
or
we can use case statement also.
2. Is it mandatory to use them in reports?
Normal reports not mandatory.
Hope it helps.
Thanks,
satya

Using select * in a join statement

Ok Wizards,
If I use this code: (select * from tablea a, tableb b where a.index = b.index) joined, I can reference any column in either table using joined.column except a column named in both tables. If both tables contained a columnxyz, any reference to joined.columnxyz returns an error. Must be a naming convention this newbie is unaware of (among many other things). Your wisdom and patience are greatly admired.

You are right SomeoneElse,
Natural join doesn't necessarily apply unless you're using stricts naming conventions.
You could use following syntax:
select * from scott.emp join scott.dept on emp.deptno = dept.deptno;
But we're back to the beginning, i.e we can't referefence deptno - it gives an error as in
select deptno from (
select * from scott.emp join scott.dept on emp.deptno = dept.deptno
So forget about my second sugestion
You could always create a view on the 2 tables joined together if you absolutely want to use *.
Regards,

How to pass radiobuttons using a submit statements.

Hi All,
Can anyone tell me how to pass radiobuttons using Submit statement.
My problem is that I am able to pass one select option and one parameter using the statement:
submit (v_repid) to sap-spool without spool dynpro
 spool parameters s_print_parms
 using selection-screen '1000' WITH SELECTION-TABLE t_rspar_tab
 and return.
This selection screens got to check selections based on 2 radio buttons available in the selection screen which also i need to pass through SUBMIT.Please let me know how do i pass this to the Submit statement.
Thankx in advance...
Helpful answers will be rewarded fully...

Hi Susanth,
 Create Variant for the calling program, Give that variant( here in the below program variant for calling program that I created is VAR1) in the calling program in SUBMIT Statement.

CALLING PROGRAM:

data:
w_variant(5) TYPE c VALUE 'VAR1'.
SUBMIT YH625_CALLED_PROGRAM USING SELECTION-SET w_variant.
CALLING PROGRAM:
TABLES spfli.
parameters:
 w_radio1 RADIOBUTTON GROUP g1,
 w_radio2 RADIOBUTTON GROUP g1.
SELECT-OPTIONS s_table FOR spfli-carrid.
WRITE '*************** This is Called program output **********************'.
Hope this solves your problem.
If you any query you are welcome.
Regards,
V.Raghavender.

Submit report using selection-table to report 'RKAEP000'(Tcode ksb1)

Hi,
I am calling report "RKAEP000'(This is the report for tcode KSB1) using submit statement in my program to import the ksb1 output in my program. For time being I am calling this report using selection-set 'variant'.
The selection screen of ksb1 is designed with modulepool program (screen 100).
The selection screen of my program is similar to ksb1 initial screen, except layout option and controlling area is on the screen itself instead of calling it through menu.
Please tell me how to post the selction criteria of my report to the calling program 'RKAEP000'.
Thanks,
suresh

You can use WITH addition of SUBMIT statement.
SUBMIT report1 USING SELECTION-SCREEN '1100'
               WITH SELECTION-TABLE rspar_tab
               WITH selcrit2 BETWEEN 'H' AND 'K'
               WITH selcrit2 IN range_tab
               AND RETURN.
Regards,
Premal

SUBMIT statement using variant

Hi Gurus,
i am trying to use execute a variant , and that variant has to be submitted in memory.(i.e i have three variants A,B,C whenever i run the report using variant A then that fields only has to be passed to memory) , but instead of that , even if i am using varinat B , but by defaul it is taking another variant which contains all the fields.I think my issue is clear.i am using this submit statement.
SUBMIT (sy-repid)
 AND RETURN
 EXPORTING LIST TO MEMORY
 WITH SELECTION-TABLE i_selscr.
pleasehelp me regarding this ASAP.
Thanks and regards,
Rajeshwar

Hi Rajeshwar
You can submit it by using variant name also:
Submit <Report> USING SELECTION-SET variant .
Check this link:
http://sapdevelopment.co.uk/reporting/rep_submit.htm
http://help.sap.com/abapdocu/en/ABAPSUBMIT_SELSCREEN_PARAMETERS.htm
http://help.sap.com/abapdocu/en/ABAPSUBMIT_SELSCREEN_PARAMETERS.htm
Need information about SUBMIT statement
Regards
Neha
Edited by: Neha Shukla on Nov 30, 2008 12:46 PM
Edited by: Neha Shukla on Nov 30, 2008 3:22 PM

Combination of Submit report with SELECTION-SET and WITH is not working

I tried all possibilities to make the additional parameter also pass to the report along with variant but it just does not work. Anybody faced this issue before?
Code snipped which is not taking pernr parameter along with variant 'Report Dis'.
SUBMIT H99CWTR0 USING SELECTION-SET 'REPORT DIS'
 WITH pernr = pernr-low
 EXPORTING LIST TO MEMORY
AND RETURN.

Hi,
THis sample code worked for me
data:params type rsparams.
data:it type table of rsparams.
params-low = '2003'. "In variant ZSURESHPAGA the actual value is 2004, but it got executed for 2003.
params-kind = 'P'.
params-option = 'EQ'.
params-sign = 'I'.
params-selname = 'P_YEAR'.
append params to it.
CALL FUNCTION 'SUBMIT_REPORT'
EXPORTING
 report = 'Z12256_TASK1'
 VARIANT = 'ZSURESHPAGA'
 SKIP_SELSCREEN = 'X'
TABLES
 SELECTION_TABLE = it
EXCEPTIONS
 JUST_VIA_VARIANT = 1
 NO_SUBMIT_AUTH = 2
 OTHERS = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
SUBMIT H99CWTR0 USING SELECTION-SET 'REPORT DIS'
WITH pernr = pernr-low "<----check this statemnent
EXPORTING LIST TO MEMORY
AND RETURN.
Edited by: Keshav.T on May 13, 2010 4:07 PM

Problem in Submit Statement of Alv Report

Hi All Experts,
i make one report,my requirement is when i execute my report then it displays 100 records, i select 20 records from 100 records
then based upon 20 records execute the another report with out slection screen. i know the process through the submit statement,but it doesn't give exact output 20 of 20 based upon selected entries.
my Code is:SUBMIT ZPS_PROJ_CN41N USING SELECTION-SCREEN '1000' WITH SELECTION-TABLE RSPAR_TAB
 AND RETURN.
give suggistions and correct syntax of submit statement.
Thanks.

Hi,
= 'EQ ' for parameters
In for range or selct-options
SUBMIT <Report name>
 WITH r_budat IN s_budat " Selection screen parameters
 WITH kostl IN s_kostl
 WITH kstar IN s_kstar
 AND RETURN.
"With Variant
SUBMIT <Report Name>
 USING SELECTION-SET 'BPC TEST' "BPC set is Varaint name for report
 EXPORTING LIST TO MEMORY AND RETURN.
"capturing the output to another report
SUBMIT <Report name>
 WITH r_budat IN s_budat " Selection screen parameters
 WITH kostl IN s_kostl
 WITH kstar IN s_kstar
 EXPORTING LIST TO MEMORY AND RETURN.
Prabhudas

SUBMIT statement for MD03 not working (module pool)

I am trying to use SUBMIT stament for transaction MD03.
SUBMIT SAPMM61X USING SELECTION-SETS OF PROGRAM '200'
WITH matnr = matnr
WITH werks = werks
WITH versl = versl
WITH baner = baner
WITH lifkz = lifkz
WITH diser = diser
WITH plmod = plmod
WITH trmpl = trmpl
WITH dispd = dispd
WITH ANZDL = ANZDL
EXPORTING LIST TO MEMORY
AND RETURN.
But getting RUNTIME error
Error analysis
You attempted to start the ABAP/4 program "SAPMM61X" with SUBMIT, but the
    attributes specify this program as type "M" instead of "1". You can
    only start programs of type 1 with SUBMIT.
I want to run MD03 thru a wrapper program and get back the values.
Thanks,
AP
Edited by: Julius Bussche on Jul 23, 2009 9:35 PM
Subject title improved...

Thers is correction to what I posted above
MD03 is working fine with call trasaction as we work with one item and one layer. Only one matarial i can capture that.
But for MD02 we have single-tem and multiple layer. After the tranaction is excute there is Button on the output screen When clicked on it, it displays list of materials (layer). I need to capture the list how do i caapture it in a internal table.

Catching an error in SUBMIT Statement

Hi,
I am using SUBMIT (REPORT) and RETURN.
How to catch an error when there is one in the REPORT Program that i am calling.

hi
Calling Programs
If you need to program an extensive application, one single program can become very complex. To make the program easier to read, it is often a good idea to divide the required functions among several programs.
As well as using external modularization, in which you store procedures in special non-executable ABAP programs like function groups, you can also call independent programs from within an ABAP program.
The following ABAP statements allow you to start an executable program or transaction. You can either exit the calling program, or have the system return to it when the called program finishes running.
Executable Program
Transaction
Call without return
SUBMIT
LEAVE TO TRANSACTION
Call with return
SUBMIT AND RETURN
CALL TRANSACTION
You can use these statements in any ABAP program. For example, while processing a user action in the output list of an executable program, you might call a transaction whose initial screen is filled with data from the selected list line.
The event LOAD-OF-PROGRAM is triggered each time a program is called. If a corresponding event block is defined in the framework program, it is executed once before the first other processing block is executed.
An interesting remark at this point is that each execution of an executable program actually has a SUBMIT statement as its source. When you enter the program name in a transaction like SE38 or SA38 and choose Execute, a SUBMIT statement occurs in the transaction. Technically speaking, therefore, executable programs have the attribute of being able to be called using SUBMIT, although their principal characteristic from a useru2019s point of view is that they are started in the foreground.
Memory Organization in Program Calls
The first ABAP program in a session on the application server opens its own internal session (roll area) within the main session. All externally-called procedures run in the same internal session as the calling program, that is, the main program and working data of the procedure are loaded into the same memory area in the internal session.
When you call an executable program or a transaction, the system opens a new internal session for each program. Here, there are two possible cases: If the second program does not return control to the calling program when it has finished running, the called program replaces the calling program in the internal session. The contents of the memory of the calling program are deleted. If the second program does return control to the calling program when it has finished running, the session of the called program is not deleted. Instead, it becomes inactive, and its memory contents are placed on a stack. The system can open up to 9 further internal sessions in external program calls.
As well as executable programs and transactions, dialog modules also open a new internal session. Dialog modules were previously used for modularizing screen sequences.
Program Calls and SAP LUWs
An SAP LUW is a logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW. There are various bundling techniques that you can use to ensure that all of the database updates belonging to an SAP LUW are made in the same single database LUW.
Externally-called procedures do not open a new SAP LUW.
However, when you start a new executable program or transaction, a new SAP LUW starts. Database updates belonging to these programs are collected in their own database LUW. If the new program does not return control to the calling program, the SAP LUW of the old program concludes when the new program is called. If, on the other hand, the new program does return control to the calling program, the new SAP LUW runs parallel to the SAP LUW of the calling program.
No new SAP LUW is opened when you call a dialog module. Bundling techniques in a dialog module add the database updates to the database LUW of the calling program. You may sometimes need to call a transaction that runs in the same SAP LUW as the calling program. One technique for doing this is to use the existing transaction as a dialog module. To do this, you need to create a new dialog module with the same main program and initial screen as the transaction. Transactions that are used both as transactions and as dialog modules must be programmed to obey certain rules. For further information, refer to Calling Screen Sequences.
The fact that an external program shares (or does not share) the SAP LUW with its caller has special consequences if the program calls update-task functions or uses COMMIT WORK. For further information, refer to Special LUW Considerations.
syntax:
SUBMIT REPORT01 VIA SELECTION-SCREEN USING SELECTION-SET 'VARIANT1' USING SELECTION-SETS OF PROGRAM 'REPORT00' AND RETURN.

Passing values to a select option through submit

hi all,
i am using the following code to submit report.
SUBMIT :rko7co88 USING SELECTION-SET 'ZTEST_PS'
 WITH SELECTION-TABLE seltab
 WITH perio = v_month
 WITH gjahr = v_year
 WITH vaart = c_1.
the table seltab is being populated as shown below.
LOOP AT i_aufnr INTO i_aufnr_wa.
seltab_wa-selname = 'AUFNR'.
seltab_wa-sign = 'I'.
seltab_wa-kind = 'S'.
seltab_wa-option = 'EQ'.
seltab_wa-low = i_aufnr_wa-aufnr.
APPEND seltab_wa TO seltab.
CLEAR seltab_wa.
ENDLOOP.
but when i run this program it gives a short dump saying program has excceded the maximum time permited.
the problem seems to be with passing table seltab to select option, because when i run the program witout that statemant "WITH SELECTION-TABLE seltab" . it works fine.
in seltab i have selected only open orders which r confirmed, when i run the program without passing seltab it takes all the orders and works fine but according to my requirement i have to run the program for only open orders.
pls suggest the way out.
thanks
pankaj sharma

Hi pankaj,
1. I tried the same thing, and now its working fine.
2. I also used the extension of submit
 via selection-screen.
 to temporarily check what values are going in the screen.
3. just copy paste to get a taste of it.
4. Values 11111, 2222 will come in AUFNR.
5.
report abc.
DATA : SELTAB LIKE RSPARAMS OCCURS 0 WITH HEADER LINE.
SELTAB-SELNAME = 'AUFNR'.
SELTAB-KIND = 'S'.
SELTAB-SIGN = 'I'.
SELTAB-OPTION = 'EQ'.
SELTAB-LOW = '11111'.
APPEND SELTAB.
SELTAB-SELNAME = 'AUFNR'.
SELTAB-KIND = 'S'.
SELTAB-SIGN = 'I'.
SELTAB-OPTION = 'EQ'.
SELTAB-LOW = '222222'.
APPEND SELTAB.
submit RKO7CO88
WITH perio = '001'
WITH gjahr = '2006'
WITH vaart = '1'
WITH SELECTION-TABLE SELTAB
via selection-screen.
regards,
amit m.

What is USING SELECTION-SET in submit statement?

Similar Messages

Maybe you are looking for