topic Submit in Application Development and Automation Discussions

Submit

Former Member — Thu, 18 Oct 2007 03:15:07 GMT

Hi i transfered fields into one table like

rspar TYPE TABLE OF rsparams

after using submit statement like

SUBMIT RFITEMGL VIA SELECTION-SCREEN WITH SELECTION-TABLE rspar

AND RETURN.

but in RFITEMGL seletion screen i am not getting the values why i dont know can anyone help pls

Re: Submit

Former Member — Thu, 18 Oct 2007 03:17:50 GMT

You need to populate selection screen values before hand. As you are not doing this, you are not able to see any values. There are different ways to pass selection screen parameters in SUBMIT command.

Check this article for more details about SUBMIT -

SUBMIT

Basic forms:

1. SUBMIT rep.

2. SUBMIT (name).

Extras:

1. ... LINE-SIZE col 2. ... LINE-COUNT line

3. ... TO SAP-SPOOL List output to the SAP spool database

4. ... USING SELECTION-SCREEN scr

5. ... VIA SELECTION-SCREEN

6. ... AND RETURN

7. ... EXPORTING LIST TO MEMORY

8. ... USER user VIA JOB job NUMBER n

9. ...Various additions for passing parameters to rep

10. ... USING SELECTION-SETS OF PROGRAM prog

Effect

Calls report rep.

The system leaves the active program and starts the new report rep. In basic form 2, you can specify the name of the report in the field name. You must specify the name in uppercase, otherwise a runtime error occurs.

Note

You can only start programs with type '1' using SUBMIT. If the program has a different type, the system triggers a runtime error.

Please consult Data Area and Modularization Unit Organization documentation as well.

Addition 1

... LINE-SIZE col

Effect

The list generated by the report has the line width col.

Addition 2

... LINE-COUNT line

Effect

The list generated by the report has line lines per page.

Addition 4

... USING SELECTION-SCREEN scr

Effect

When you execute the report, the system uses the selection screen number that you specify in the scr field. This must be a selection screen defined using the SELECT-OPTIONS, PARAMETERS and SELECTION-SCREEN statements.If you omit the addition, the system uses the standard selection screen 1000.

This addition allows you to start the same report in different situations, using a different selection screen each time.

Notes

1. The addition VIA SELECTION SCREEN determines whether the report is processed in the foreground or the background.

2. What happens if the required screen does not exist or is not a selection screen?

Screen 1000:

If you want to use the standard selection screen ( ... USING SELECTION-SCREEN 1000 or do not specify a ... USING SELECTION-SCREEN) addition, the system does not process a selection screen.

Other selection screens:

The system triggers a runtime error.

Addition 5

... VIA SELECTION-SCREEN

Effect

The selection screen is displayed. In this case, the selection screen is displayed again after the report list has been displayed. The values entered by the user remain displayed.

Addition 6

... AND RETURN

Effect

Returns to the calling transaction or program after the called program has been executed. SUBMIT ... AND RETURN creates a new internal session.

Addition 7

... EXPORTING LIST TO MEMORY

Effect

Does not display the output list of the called report, but saves it in ABAP memory and leaves the called report immediately. Since the calling program can read the list from memory and process it further, you need to use the addition ... AND RETURN . Also, since the called report cannot be requested for printing, the addition ... TO SAP-SPOOL is not allowed here. You can read the saved list from SAP memory with the function module 'LIST_FROM_MEMORY' and then (for example) store it in the database with EXPORT. You can process this list further with the function modules 'WRITE_LIST', 'DISPLAY_LIST' ... of the function group "SLST".

Addition 8

... USER user VIA JOB job NUMBER n

Effect

Schedules the specified report in the job specified by the job name job and the job number n. The job runs under the user name user and you can omit the addition USER user. The assignment of the job number occurs via the function module JOB_OPEN (see also the documentation for the function modules JOB_CLOSE and JOB_SUBMIT). This addition can only be used with the addition ...AND RETURN.

Note

When scheduling a report with the SUBMIT ... VIA JOB job NUMBER n statement, you should always use the addition ...TO SAP-SPOOL to pass print and/or archive parameters. Otherwise, default values are used to generate the list and this disturbs operations in a production environment.

SY-SUBRC = 0:

Job scheduled successfully

SY-SUBRC = 4:

Job scheduling terminated by user

SY-SUBRC = 8:

Error in job scheduling ( JOB_SUBMIT)

SY-SUBRC = 12:

Error in internal number assignment

Addition 10

... USING SELECTION-SETS OF PROGRAM prog

Effect

Uses variants of the program prog when executing the program rep.

Note

Important

The programs prog and rep must have the same SELECT-OPTIONS and PARAMETERs. Otherwise, variants of the program prog may be destroyed.

Note

When using this addition, the specified variant vari of the program prog is taken in USING SELECTION-SET vari. On the other hand, all variant-related actions on the selection screen of rep (Get, Save as variant, Display, Delete) refer to the variants of prog.

Example

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.

Note

Non-Catchable Exceptions:

LOAD_PROGRAM_NOT_FOUND: The specified program was not found.

SUBMIT_WRONG_TYPE: The specified program is not a report.

SUBMIT_IMPORT_ONLY_PARAMETER: Only one value passed to a report parameter.

SUBMIT_WRONG_SIGN: Invalid value passed to a selection with the addition SIGN.

SUBMIT_IN_ITAB_ILL_STRUCTURE: Table passed to a selection with WITH sel IN itab had an unexpected structure.

Hope this helps.

ashish

Re: Submit

Former Member — Thu, 18 Oct 2007 03:54:51 GMT

DATA: int TYPE i,

rspar TYPE TABLE OF rsparams,

wa_rspar LIKE LINE OF rspar.

wa_rspar-selname = 'so_wlsak'. wa_rspar-kind = 'S'.

wa_rspar-sign = 'I'. wa_rspar-option = 'BT'.

wa_rspar-low = i_output2-hkont. wa_rspar-high = ' '.

APPEND wa_rspar TO rspar.

wa_rspar-selname = 'so_wlbuk'. wa_rspar-kind = 'S'.

wa_rspar-sign = 'I'. wa_rspar-option = 'EQ'.

wa_rspar-low = I_OUTPUT2-BUKRS.

APPEND wa_rspar TO rspar.

SUBMIT RFITEMGL VIA SELECTION-SCREEN WITH SELECTION-TABLE rspar

AND RETURN.

Re: Submit

Former Member — Thu, 18 Oct 2007 04:07:52 GMT

Hi Chaaya,

Have you checked whether there are any values in the i_output2-hkont and I_OUTPUT2-BUKRS?

Secondly,when you only have to pass a sngle value in the selection screen of the standard program,then y are u using select-optins,use parameters instead.

Debug the program and see if the values are getting populated or not?

Refer to the below code for reference:

REPORT zrat NO STANDARD PAGE HEADING.

************************************************************

*DATA DECLARATION

************************************************************

DATA : BEGIN OF wa_ccode,

bukrs TYPE t001-bukrs,

END OF wa_ccode.

DATA : itab_ccode LIKE TABLE OF wa_ccode.

DATA : BEGIN OF wa_emp,

pernr TYPE pa0001-pernr,

sachp TYPE pa0001-sachp,

sname TYPE pa0001-sname,

END OF wa_emp.

DATA : itab_emp LIKE TABLE OF wa_emp.

DATA : BEGIN OF wa_bdate,

nachn LIKE pa0002-nachn,

vorna LIKE pa0002-vorna,

pernr TYPE pa0002-pernr,

gbdat TYPE pa0002-gbdat,

END OF wa_bdate.

DATA : itab_bdate LIKE TABLE OF wa_bdate.

DATA : new_date LIKE sy-datum.

DATA : diff TYPE i.

DATA : years LIKE p0347-scryy,

months LIKE p0347-scrmm,

days LIKE p0347-scrdd.

DATA : sup_code LIKE pa0001-sachp,

itab_usrid LIKE t526-usrid,

sup_pernr LIKE pa0105-pernr.

DATA : BEGIN OF wa_email,

usrid_long LIKE pa0105-usrid_long,

END OF wa_email.

DATA : sup_email LIKE TABLE OF wa_email.

DATA : gwa_document_data LIKE sodocchgi1,

gc_name TYPE so_obj_nam VALUE 'RETIREMENT',

gc_senst TYPE so_obj_sns VALUE 'P',

gc_size TYPE so_doc_siz VALUE '510',

gi_obj_cnt LIKE TABLE OF solisti1 WITH HEADER LINE,

gi_recievers LIKE somlreci1 OCCURS 0 WITH HEADER LINE,

gwa_obj_cnt LIKE LINE OF gi_obj_cnt.

DATA : smtp_addr LIKE adr6-smtp_addr.

DATA : wa_date LIKE sy-datum,

entries LIKE sy-tabix,

name(15),

line1(18) TYPE c,

line2(20) TYPE c,

line3(20) TYPE c,

line4(23) TYPE c,

line5(10) TYPE c,

line6(45) type c,

date(2) TYPE c,

month(2) TYPE c,

year(4) TYPE c.

************************************************************

*START OF SELECTION

************************************************************

SELECT bukrs

FROM t001

INTO TABLE itab_ccode

WHERE land1 EQ 'GB'.

SORT itab_ccode.

DELETE ADJACENT DUPLICATES FROM itab_ccode.

SELECT pernr sachp sname

FROM pa0001

INTO TABLE itab_emp

FOR ALL ENTRIES IN itab_ccode

WHERE bukrs EQ itab_ccode-bukrs AND begda LE sy-datum AND

endda GE sy-datum and persg eq '1'.

SELECT nachn vorna pernr gbdat

FROM pa0002

INTO TABLE itab_bdate

FOR ALL ENTRIES IN itab_emp

WHERE pernr EQ itab_emp-pernr.

************************************************************

*TO CHECK EMPLOYEES WHOSE AGE IS NEAR 75 YEARS.

************************************************************

LOOP AT itab_bdate INTO wa_bdate.

new_date = wa_bdate-gbdat.

************************************************************

*TO CALCULATE THE AGE TILL DATE

************************************************************

CALL FUNCTION 'HR_HK_DIFF_BT_2_DATES'

EXPORTING

date1 = sy-datum

date2 = new_date

output_format = '05'

IMPORTING

years = years

months = months

days = days

IF sy-subrc <> 0.

ENDIF.

IF years EQ 64 AND months EQ 4.

IF days GE 23 AND days LE 31.

************************************************************

*FETCH THE DATA IF THE AGE IS NEARING 75 YEARS

************************************************************

SELECT SINGLE sachp FROM pa0001 INTO sup_code WHERE pernr EQ

wa_bdate-pernr AND begda LE sy-datum AND endda GE sy-datum.

SELECT SINGLE usrid FROM t526 INTO itab_usrid WHERE sachx EQ

sup_code.

SELECT SINGLE pernr FROM pa0105 INTO sup_pernr WHERE usrid EQ

itab_usrid AND subty EQ '0001'.

clear sup_email[].

SELECT usrid_long FROM pa0105 INTO TABLE sup_email WHERE pernr EQ

sup_pernr AND subty EQ '0010'.

************************************************************

*EMAIL ADDRESS OF THE SUPERVISOR TO BE NOTIFIED

************************************************************

CLEAR gi_obj_cnt.

CLEAR gi_recievers.

CLEAR gwa_document_data.

Loop at sup_email into wa_email.

write sy-uline+0(5).

write sy-uline+10(5).

write sy-uline+20(5).

write sy-uline+30(5).

write sy-uline+40(5).

write sy-uline+50(5).

write sy-uline+60(5).

write sy-uline+70(5).

smtp_addr = wa_email-usrid_long.

gi_recievers-receiver = smtp_addr.

gi_recievers-rec_type = 'U'.

gi_recievers-com_type = 'INT'.

APPEND gi_recievers.

Endloop.

smtp_addr = 'Mairi.Davidson@subsea7.com'.

gi_recievers-receiver = smtp_addr.

gi_recievers-rec_type = 'U'.

gi_recievers-com_type = 'INT'.

APPEND gi_recievers.

gwa_document_data-obj_name = gc_name.

gwa_document_data-obj_descr = 'RETIRE'.

gwa_document_data-sensitivty = gc_senst.

gwa_document_data-obj_langu = sy-langu.

************************************************************

*CONTENT OF THE EMAIL TO BE SENT

************************************************************

line1 = 'Please note that '.

line2 = wa_bdate-vorna.

line3 = wa_bdate-nachn.

line4 = ' will be 65 years on '.

line50(4) = wa_bdate-gbdat4(4).

date = line5+2(2).

month = line5+0(2).

year = wa_bdate-gbdat+0(4) + 65.

CONCATENATE date month year INTO line5 SEPARATED BY '.'.

line6 = '.Please complete the Retirement Procedure.'.

CONCATENATE line1 line2 line3 line4 line5 line6 INTO gwa_obj_cnt

SEPARATED BY space.

APPEND gwa_obj_cnt TO gi_obj_cnt.

CLEAR gwa_obj_cnt.

DESCRIBE TABLE gi_obj_cnt LINES entries.

READ TABLE gi_obj_cnt INDEX entries.

gwa_document_data-doc_size = ( entries - 1 ) * 255 + STRLEN( gi_obj_cnt

************************************************************

*FUNCTION MODULE TO SEND THE EMAIL TO THE CONCERNED PERSONS

************************************************************

CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'

EXPORTING

document_data = gwa_document_data

document_type = 'RAW'

commit_work = 'X'

TABLES

object_content = gi_obj_cnt

receivers = gi_recievers

EXCEPTIONS

too_many_receivers = 1

document_not_sent = 2

document_type_not_exist = 3

operation_no_authorization = 4

parameter_error = 5

x_error = 6

enqueue_error = 7

OTHERS = 8

************************************************************

*MESSAGE TO BE DISPLAYED AFTER THE EXECUTION

************************************************************

endif.

CASE sy-subrc.

WHEN 0.

LOOP AT gi_recievers.

IF gi_recievers-receiver = space.

name = gi_recievers-rec_id.

ELSE.

name = gi_recievers-receiver.

ENDIF.

IF gi_recievers-retrn_code = 0.

WRITE: / name, ': succesfully sent'.

ELSE.

WRITE: / name, ': error occured'.

ENDIF.

ENDLOOP.

WHEN 1.

WRITE: / 'Too many receivers specified !'.

WHEN 2.

WRITE: / 'No receiver got the document !'.

WHEN 4.

WRITE: / 'Missing send authority !'.

WHEN OTHERS.

WRITE: / 'Unexpected error occurred !'.

ENDCASE.

ENDIF.

ENDLOOP.

In case you have any further clarifications,do let me know.

Regards,

Puneet Jhari.