SAP NetWeaver AS ABAP Release 740, ©Copyright 2014 SAP AG. All rights reserved.
ABAP Keyword Documentation → ABAP − Reference → Calling and leaving program units → Calling ABAP Programs → Calling Executable Programs → SUBMIT →
SUBMIT - list_options
Syntax
... [LINE-SIZE width]
[LINE-COUNT page_lines]
{ [EXPORTING LIST TO MEMORY]
| [TO SAP-SPOOL spool_options] } ... .
Extras:
1. ... LINE-SIZE width
2. ... LINE-COUNT page_lines
3. ... EXPORTING LIST TO MEMORY
4. ... TO SAP-SPOOL spool_options
Effect
These additions modify the basic list in the called program. While LINE-SIZE and LINE-COUNT modify the formatting, the other two additions determine the output type of the list.
EXPORTING LIST TO MEMORY saves the list to the
ABAP Memory and TO
SAP-SPOOL sends it as a spool list to the SAP spool system. If these additions are not specified, the basic list is displayed as a screen list.
Note
The additions only take effect the first time the called program is executed. If a
selection screen is
displayed in the program accessed, the runtime environment accesses the program again after completion,
without taking account of the list_options additions. This is particularly
important to the addition TO SAP-SPOOL, because the basic list is displayed
as a screen list and not as a spool list when the program is accessed again. For this reason, it is
advisable not to use the addition VIA SELECTION-SCREEN when using list_options.
... LINE-SIZE width
... LINE-COUNT page_lines
Effect
These additions define the line width and page length of the basic list. They have the same effect as
the additions of the same name in the introductory program statement for the called program. If the
called program has the same additions in the introductory program statement, these overwrite the values specified for SUBMIT.
... EXPORTING LIST TO MEMORY
Effect
This addition stores the basic list for the program accessed in the ABAP Memory. It can only be used together with the addition AND RETURN.
The list is stored in the ABAP Memory as an internal table of the row type ABAPLIST, ABAPLIST being a structured data type in ABAP Dictionary.
The calling program can access the list stored once the program has been called, using function modules from the function group SLST.
Note
The addition can only work provided the function key Enter is not associated with a function code in the GUI status last defined for the called program.
Example
Once the program report has been called, the list stored there in the ABAP Memory is read using function modules and inserted in the current list.
DATA list_tab TYPE TABLE OF abaplist.
SUBMIT report EXPORTING LIST TO MEMORY
AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
listobject = list_tab
EXCEPTIONS
not_found = 1
OTHERS = 2.
IF sy-subrc = 0.
CALL FUNCTION 'WRITE_LIST'
TABLES
listobject = list_tab.
ENDIF.
... TO SAP-SPOOL spool_options
Effect
If this addition is specified, a new
spool list level is opened in the internal mode of the called program and the first output statement for the basic list of this program creates a new
spool request. All list output for the called program is passed page by page as a
spool list to the
SAP spool system.
The spool_options additions are used to define the spool and archiving parameters for the spool request.
Note
It is not possible to switch from the spool list to the screen list in the called program. The
NEW-PAGE PRINT OFF statement does not modify a spool list level created using SUBMIT TO SAP-SPOOL.
Example
Calls an executable program and creates a spool request. When the name of the called program is passed to the input parameter REPORT of the function module GET_PRINT_PARAMETERS, the information about the line width and page length of the spool list is taken from the statement that introduces the program.