Vous êtes sur la page 1sur 15

FU REUSE_ALV_GRID_DISPLAY

____________________________________________________
Short text
Output of a simple list (single-line)

Functionality
The function module outputs an internal table with whatever structure in the form of a formatted single- oder
multi-line list.
Process:
Passing an internal table with the set of information to be output

Passing a structure with general layout specifications for list layout

Passing a field catalog in the form of an internal table

The field catalog describes the fields to be output in the list.

Notes

All interactions performed on the list refer directly to the internal output table. Sorting the list, for
example, also involves a resorting of the internal output table passed (since it was passed by
reference).

An important factor determining the usability of the tool or of various generic functions (totals,
subtotals) is the expected amount of data to be displayed.
The application is responsible for critically testing this aspect and consider it when it comes to
decision-making.

Parameter
I_INTERFACE_CHECK
I_BYPASSING_BUFFER
I_BUFFER_ACTIVE
I_CALLBACK_PROGRAM
I_CALLBACK_PF_STATUS_SET
I_CALLBACK_USER_COMMAND
I_CALLBACK_TOP_OF_PAGE
I_CALLBACK_HTML_TOP_OF_PAGE
I_CALLBACK_HTML_END_OF_LIST
I_STRUCTURE_NAME
I_BACKGROUND_ID
I_GRID_TITLE
I_GRID_SETTINGS
IS_LAYOUT
IT_FIELDCAT
IT_EXCLUDING
IT_SPECIAL_GROUPS
IT_SORT
IT_FILTER

IS_SEL_HIDE
I_DEFAULT
I_SAVE
IS_VARIANT
IT_EVENTS
IT_EVENT_EXIT
IS_PRINT
IS_REPREP_ID
I_SCREEN_START_COLUMN
I_SCREEN_START_LINE
I_SCREEN_END_COLUMN
I_SCREEN_END_LINE
IT_ALV_GRAPHICS
IT_ADD_FIELDCAT
IT_HYPERLINK
E_EXIT_CAUSED_BY_CALLER
ES_EXIT_CAUSED_BY_USER
T_OUTTAB

Exceptions
PROGRAM_ERROR

Function group
SLVC_FULLSCREEN

I_INTERFACE_CHECK

Interface consistency check log output

Description
So that the performance of the list output is not reduced due to interface consistency checks, these checks
are performed in a special call mode.
If this parameter is set to 'X', interface consistency is checked when the function module is called and an
error log is displayed.
You should only set this parameter for testing purposes during the development process (for example, for
debugging).
You can also perform the interface check on the result list by entering function code &SOS.
THIS PARAMETER IS CURRENTLY NOT SUPPORTED IN FULLSCREEN MODE! As a workaround, go to
the print preview from within the list and enter function code &SOS there.

Default
SPACE
I_CALLBACK_PROGRAM

Name of the calling program


Description
Program from which the function module is called and that contains the exit routines.The program should
always be a report, function group, module pool or form routine pool (it should not be an include).

Caution: Never pass SY-REPID directly at the interface. If field SY-REPID contains the desired program
name, you must absolutely assign this name to an auxiliary variable and pass this variable to the interface.
I_CALLBACK_PF_STATUS_SET

Set EXIT rountine to status


Description
Passing an EXIT routine indicates to the ALV that the caller wants to set a self-defined user status.
As a result, the default status of the ALV is not set.
The interface of the form routine specified must be defined as follows:
FORM set_pf_status USING rt_extab TYPE slis_t_extab
Table RT_EXTAB contains the function codes that would be hidden on the standard user interface.
If the caller wants to use a self-defined user interface (for example, in order to provide additional list
functions or use existing functions), we recommend that you copy standard status STANDARD from function
group SALV and modify it accordingly. ALV standard function codes always start with '&'.
See also the documentation on parameter I_CALLBACK_USER_COMMAND.
If a self-defined user interface is used that includes function codes of the standard user interface, the
function codes of the excluding table passed should be taken into account.
This means that the user status should generally be set as follows:
SET PF-STATUS user status EXCLUDING rt_extab.
Application functions can be added to excluding table rt_extab if they are to be disabled.
The routine is called whenever the standard user interface would be set with SET PF-STATUS.

Default
If no EXIT routine is specified, the ALV sets a status that corresponds to status STANDARD of function
group SALV.
I_CALLBACK_USER_COMMAND

EXIT routine for command handling


Description
Passing an EXIT routine indicates to the ALV that the application wants to respond to certain function codes.
Generally, these are function codes that are unknown to the ALV (that is, are not standard ALV functions)
and that were defined and set by a user status.
See also the documentation on parameter I_CALLBACK_PF_STATUS_SET.
The interface of the form routine specified must be defined as follows:
FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
Parameter R_UCOMM contains the function code triggered.
Structure RS_SELFIELD contains the following information:
tabname : Name of the internal output table

tabindex : Index of the internal output table

fieldname: Field name

endsum : Cursor is located on the totals line

sumindex : If >0, the cursor is located on a subtotals line

value : Value of the field on the list

refresh : (Exporting) List should be set up again

col_stable:(Exporting) Keep column position when list is set up again

row_stable:(Exporting) Keep row position when list is set up again

exit :(Exporting) Exit list (and ALV)

before_action: Call before standard action execution

after_action : Call after standard action execution, before list setup

ignore_multi : Internal use

sel_tab_field: Internal use

The EXIT routine is called whenever a function unknown to the ALV is triggered or if the routine call
before/after the execution of a standard function code has been defined by interface parameter
IT_EVENT_EXIT.
See also the documentation on parameter IT_EVENT_EXIT.
The function code and the current cursor position are then passed on to the calling program through the
EXIT routine.
If the user has selected multiple rows by selecting checkboxes, the output table field designated as the
checkbox contains the current state of the checkbox in the list.
I_CALLBACK_TOP_OF_PAGE

EXIT routine for handling TOP-OF-PAGE


Description
If the caller specifies an EXIT routine, this routine must have the following form:
FORM top_of_page.
Module REUSE_ALV_COMMENTARY_WRITE can then be called within the EXIT routine. This module is
responsible for formatting the header information and also ensures online HTML formatting. In the print
preview or in batch mode, the text passed is then output in the normal format.
If module REUSE_ALV_COMMENTARY_WRITE cannot be used, you must use two parameters instead. In
I_CALLBACK_TOP_OF_PAGE you pass the form routine that is responsible for normal formatting in batch
mode or in the print preview mode. The form routine that is responsible for online formatting, is passed in
parameter I_CALLBACK_HTML_TOP_OF_PAGE. If one of these parameters is not filled, top-of-page is not
output in the respective mode.
Return ->
EXIT routine for handling TOP-OF-PAGE

I_STRUCTURE_NAME

Internal output table structure name

Description
If the internal output table is defined through an ABAP Dictionary structure (INCLUDE STRUCTURE struct
or LIKE struct), you can automatically set up the field catalog by passing the structure name.

The field catalog is then internally set up for this structure as follows:
All fields are on the list (NO_OUT = SPACE) except fields of data type CLNT.

The key fields of the Dictionary structure are adopted in the field catalog as key fields.

References to unit fields stored in the Dictionary are adopted provided that the reference fields are
contained in the structure.

If you additionally pass a field catalog as parameter, the structure information is merged with this
field catalog.

For more information on how to set up the field catalog automatically, see the documentation on function
module REUSE_ALV_FIELDCATALOG_MERGE.
Return ->
Internal output table structure name
I_BACKGROUND_ID

Object ID of wallpaper
Description
You can use this parameter to pass a wallpaper for the output in Top-of-Page.
Caution: Since wallpaper-based formatting does not ensure a standards-based display of the page area in
the new design, you should only use this parameter in exceptional cases.
I_GRID_TITLE

Control title
Description
Specifies the title of the control. This text is displayed above the grid.
Return ->
Control title
I_GRID_SETTINGS

Grid settings
Description
If Top-of-Page or End-of-List are output online, these areas are displayed in a splitter above or below the list.
Using I_GRID_SETTINGS you can reduce the default size to 0%. To do this, you use two fields:
COLL_TOP_P: Sets Top-of-Page to 0%
COLL_END_L: Sets End-of-List to 0%

IS_LAYOUT

List layout specifications


Description
Structure for describing the list to be output.
The parameters are described and grouped based on the following categories:

Display options

Exceptions

Totals

Interaction

Detail screen

Color

Other

Note the section on pre-defined settings.


Display options
colwidth_optimize

Value range: SPACE, 'X'


'X' = Optimizes the column width to ensure that the content is displayed completely.
no_colhead

Value range: SPACE, 'X'


'X' = Do not output column headings.
zebra

Value range: SPACE, 'X'


'X' = Striped pattern (for wide lists, for example)
no_vline

Value range: SPACE, 'X'


'X' = Separate columns by SPACE.
Exceptions
lights_fieldname

Value range: SPACE, field name of the internal output table


Field of the internal output table that contains the coding of the exceptions to be output
Coding in the field of the output table:
'1' = red traffic light
'2' = yellow traffic light
'3' = green traffic light
lights_tabname

Value range: SPACE, table name of the internal output table


Table name of the internal output table that contains the specified field in parameter
LIGHTS_FIELDNAME.
lights_rollname

Value range: SPACE, data element name


The documentation defined for this data element is displayed when the F1 help for an exception
column is called.
lights_condense

Value range: SPACE, 'X'


'X' = The system outputs the 'maximum' exception of the items included in the total at subtotal level.
Example: If a list row is output with a 'red traffic light', each subtotal included in this list row is also
displayed with a 'red traffic light'.
Totals

no_sumchoice

Value range: SPACE, 'X'


'X' = Value fields for which totals are calculated are communicated by the calling program
(FIELDCAT-DO_SUM = 'X'). The user should not be allowed to change this pre-defined setting
interactively.
no_totalline

Value range: SPACE, 'X'


'X' = No overall totals line should be displayed. If required, subtotals can nevertheless be calculated
and displayed. The fields which are used for calculating subtotals are to be marked with DO_SUM
= 'X' in the field catalog.
no_subchoice

Value range: SPACE, 'X'


'X' = Characteristics at whose control level subtotals should be calculated are communicated by the
calling program.
The user should not be allowed to change this pre-defined setting interactively.
See also the documentation on IMPORTING parameter IT_SORT.
no_subtotals

Value range: SPACE, 'X'


'X' = Calculating subtotals should not be allowed.
totals_only

Value range: SPACE, 'X'


'X' = Data is output in compressed format only at totals line level.
Prerequisite: IMPORTING parameter IT_SORT is filled accordingly with the sort criteria and the
subtotals indicator.
See also the documentation on IMPORTING parameter IT_SORT.
totals_text

Value range: SPACE, string (not more than 60)


' ' = In the first column, the standard system indicates the totals level by displaying an adequate
number of '*' for the overall total. After the asterisks, the system displays the string 'total' provided
that the column width of the first output column is large enough. If the column width is not sufficient,
only the asterisks are displayed.
'string' = After the totals level indicated visually by means of '*', the system displays the string
passed provided that the column width is sufficient.
subtotals_text

Value range: SPACE, string (not more than 60)


' ' = In the first column, the standard system indicates the totals level by displaying an adequate
number of '*' for the subtotals line. After the asterisks, the system displays the string *total*
provided that the column width of the first output column is large enough and the characteristic of
the first column is not a subtotal criterion. If the column width is not sufficient, only the asterisks are
displayed.
'string' = After the totals level indicated visually by means of '*', the system displays the string
passed provided that the column width is sufficient and the characteristic of the first column is not a
subtotal criterion.
If the characteristic is a subtotal criterion, the system repeats the characteristic value for which
subtotals were calculated after the totals level provided that the column width is sufficient.
numc_sum

Value range: SPACE, 'X'


' ' = In the standard system, it is not possible to calculate totals for NUMC fields.
'X' = It is generally possible to calculate totals for NUMC fields. If this indicator is set, you can use
parameter FIELDCAT-NO_SUM to control for each NUMC column whether totals can be calculated
or not.
Interaction
box_fieldname

Value range: SPACE, field name of the internal output table


If the list should have checkboxes at the beginning of each list row (to allow the user to select
multiple rows at once), you must fill this parameter with the field name of the internal output table
that represents the selection column for selecting rows with the help of checkboxes.
The field is always displayed as a checkbox at the beginning of each list row without a list heading.
box_tabname

Value range: SPACE, table name of the internal output table


f2code

Value range: SPACE, function code


Meaning when the ALV standard interface is used:
If you want to assign a standard ALV function code to a double-click (F2), you must assign this
function code to this parameter.
Example: You want to assign the standard ALV function 'Detail' ('&ETA') to F2.
=> LAYOUT-F2CODE = '&ETA'
Meaning if a self-defined interface is used:
Case 1:
You leave the standard ALV function code for F2 '&IC1' in the copied interface of the application.
However, you want to have a function executed with F2 that is not assigned to F2 in the interface
(standard ALV function or application function). You must communicate this function code to the
ALV using parameter F2CODE.
Case 2:
You remove the standard ALV function code for F2 '&IC1' from the interface of the application and
use another function code instead (standard ALV function or application function). You must
communicate this function code to the ALV using parameter F2CODE. This is required if you want
to allow columns to be selected.
confirmation_prompt

Value range: SPACE, 'X'


'X' = If one of the functions 'Back(F03)', 'Exit(F15)' or 'Cancel(F12)' is triggered, the system asks the
user if he wants to leave the list.
key_hotspot

Value range: SPACE, 'X'


The columns defined as key fields in the field catalog
(FIELDCAT-KEY = 'X') are output as a hotspot. This means that single-clicking a key field
(highlighted in color in the list) triggers the function assigned to F2.
reprep
Value range: SPACE, 'X'
'X' = Enable report/report interface
Prerequisite: Application system (=> report RKKBRSTI exists).
The list module acts as a potential sender in the report/report interface (interface initialization, if
required).
The calling report/module pool entered in I_CALLBACK_PROGRAM is declared to the report/report
interface as the sender report with type RT=Report.
If the sender report is assigned to receiver reports in table TRSTI, function code BEBx is set to
active.
( x = function code class)

Example:
If sender RKTFGS15 has a receiver assignment for Report Writer report group 7KOI with function
code class '3' (SAP setting), this receiver report group is called through the report/report interface
at function code 'BEB3'. The selections passed to the report/report interface are the report
selections and the key information of the selected row.
For more information on the report/report interface, see the documentation on function group
'RSTI'.
Detail screen
detail_initial_lines

Value range: SPACE, 'X'


' ' = In the detail view, the system displays only fields whose content is not set to initial.
'X' = Initial field contents are also displayed on the detail screen.
detail_titlebar
Value range: SPACE, string (not more than 30)
' ' = The system displays 'Detail: Display' as the title of the detail screen.
'string' = The system displays the string passed as the title of the detail screen.

Color

info_fieldname

Value range: SPACE, field name of the internal output table


You can color an entire list row individually by using a color code that is set for each row in a
column of the internal output table. You must assign the field name of the field with the color code
to this parameter.
The field of the internal output table must be of type CHAR(3).
The code must comply with the following syntax:
'Cxy':
C = Color (each code must begin with 'C')
x = Color number ('1'-'9')
y = Intensified ('0' = off, '1' = on)
Note: The color of the key column is not affected. If you also want to color the key column at row or
cell level, you can use complex coloring which is described below for parameter
COLTAB_FIELDNAME.
For information on coloring columns, see the documentation on field catalog parameter FIELDCATEMPHASIZE of IMPORTING parameter IT_FIELDCAT.
coltab_fieldname
Value range: SPACE, field name of the internal output table
You can color cells individually by using a color code that is set for the row of the cells in a column
of the internal output table.
You must assign the field name of the field with the color code to this parameter.
The field of the internal output table must be of type SLIS_T_SPECIALCOL_ALV.
Principle: The field for the color code is filled in the row in which the cells to be colored are located.
The field then contains an internal table of the above structure that includes the field names of the
cells to be colored with the color code. The cell coordinates are therefore derived from the row
position in which the color code is written and the column information contained in the color table.
The row structure of the internal color table of type SLIS_T_SPECIALCOL_ALV is as follows:
Farbtabelle-NAME = Field name of cell to be colored
Farbtabelle-COLOR-COL = Color number (1 - 9)
Farbtabelle-COLOR-INT = Intensified (0 = off, 1 = on)
Farbtabelle-COLOR-INV = Inverse (0 = off, 1 = on)
Farbtabelle-NOKEYCOL = Ignore key coloring ('X' = yes, ' ' = no)
If parameter Farbtabelle-NAME is not filled, all color specifications refer to all fields. As a result, the
entire row is colored.

Default

In many cases, the default layout settings can be kept so that you frequently do not need to pass this
structure with modified flags.
Note:
All other fields not specified here explicitly are not relevant for use with REUSE_ALV_GRID_DISPLAY or are
not released.
Return ->
List layout specifications

IT_SPECIAL_GROUPS

Grouping fields for column selection


Description
If fields were grouped in the field catalog based on a commom value for parameter SP_GROUP, an
assignment is made in this internal table between the technical key of the group (FIELDCAT-SP_GROUP)
and the associated field group text.
See also the documentation on field catalog parameter
FIELDCAT-SP_GROUP of IMPORTING parameter IT_FIELDCAT.
Return ->
Grouping fields for column selection
IT_SORT

Sort criteria for first list display


Description
Using internal table IT_SORT, the caller determines the sort order and/or the subtotalling of the basic list.
The following fields of this internal table must be filled:
spos

Sort order
fieldname

Field name in the internal output table


up

'X' = Sorted in ascending order


down

'X' = Sorted in descending order


subtot
'X' = Subtotals for control level changes
comp (INTERNAL USE ONLY)

expa
Prequisite:
IT_SORT-SUBTOT = 'X', that is, the sort criterion is also the subtotals criterion.
If no complete breakdown but only a breakdown to totals level n that can be further expanded by
the user should be displayed when the list is output for the first time, you must set the indicator for
the totals level criterion of level n.

Return ->
Sort criteria for first list display

I_SAVE

Variants can be saved


Description
Controls the save mode
Prerequisite:
Parameter IS_VARIANT is filled accordingly.
See also the documentation on IMPORTING parameter IS_VARIANT.

Value Range

' ' = Display variants cannot be saved

Defined display variants (such as delivered display variants) can be selected for presentation
regardless of this indicator. However, changes cannot be saved.
'X' = Standard save mode

Display variants can be saved as standard display variants.


Saving display variants as user-specific is not possible.
'U' = User-specific save mode

Display variants can only be saved as user-specific.


'A' = Standard and user-specific save mode
Display variants can be saved both as user-specific and as standard
variants. Users make their choice on the dialog box for saving the
display variant.

Default
SPACE
Return ->
Variants can be saved

IS_VARIANT

Variant information

Description
This structure is only relevant if display variants are to be saved and/or read.
Variant information including the name of the list variant that is used to output the list.
To allow display variants to be read within the ALV, you must specify the acess path using fields REPORT
(required field), HANDLE (optional field) and/or LOG_GROUP (optional field).
If you also want to allow display variants to be saved, you must additionally fill parameter I_SAVE
accordingly.

See also the documentation on IMPORTING parameter I_SAVE.


A variant is uniquely described through:
The program to which the variant is assigned (REPORT)

The handle (HANDLE), if, for example, multiple lists with different structures and data are called in
a program (I_CALLBACK_PROGRAM).
The handle is a CHAR(4) field that must be uniquely defined and describes the assignment of the
call to the current structure of the internal output table.
Example:
Depending on the user interaction, several types of lists can be output in program x.
The user should be able to define display variants for each type of list.
You provide this function to the user by assigning a HANDLE to each list. If variants for the program
and the handle are saved, the handle must not be modified any more.
The logical group, if, for example, the same list is created with different settings through various
transactions (LOG_GROUP).

The logical group is a CHAR(4) that must be uniquely defined and specifies the assignment.
Example:
Program x is called through transactions T1 and T2. Depending on the transaction code, the fields
available to the user through the field catalog differ in their assignment to different logical groups.
If variants for the program and the logical group are saved, the logical group must not be modified
any more.
The user name, if user-specific variants are saved (USERNAME).

You do not have to fill this parameter manually since the variant name is unique.
The variant name (VARIANT).
You only have to fill this parameter if this structure is to be used to read a concrete variant and the
list is to be output with this variant.

Value Range
To call a list with a variant, you must specify the above fields.

Default
If the structure is initial, but saving is active (I_SAVE is not initial), then IS_VARIANT-REPORT =
I_CALLBACK_PROGRAM is set.
For a possible entries help for variants, function module REUSE_ALV_VARIANT_F4 is available.
Return ->
Variant information
IT_EVENTS

Table of events to perform

Description
This table is used to notify the ALV of all events that are processed by means of a CALLBACK through the
caller.
You can initialize the table containing the possible events for each list type using function module
REUSE_ALV_EVENTS_GET .
Using function module REUSE_ALV_EVENT_NAMES_GET , you can display the name of the constants of
type pool SLIS that represent each event. To do this, you use the single test function. Only events that have
a form routine name assigned to them are processed.

The table structure includes the following two fields:


IT_EVENTS-NAME
Name of callback event
The following callback events exist:
o Interaction

USER_COMMAND USING R_UCOMM LIKE SY-UCOMM


RS_SELFIELD TYPE SLIS_SELFIELD
Processing interactions on the list
Since this is a frequently used callback event, you can also pass the corresponding form
routine directly in the interface using IMPORTING parameter
I_CALLBACK_USER_COMMAND.
PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
If you want to set a specific status for the list, you must do this in the form routine that is
assigned to this event. Parameter RT_EXTAB contains the ALV-specific function codes
that must currently not be active. You must pass this table at command SET PF-STATUS
(if required, with caller-specific inactive function codes).
In order to copy a user-specific status, you should use status STANDARD of function
group SALV as a template.
Since this is a callback event used very frequently, you can pass the corresponding form
routine directly in the interface using IMPORTING parameter
I_CALLBACK_PF_STATUS_SET.
Time of list processing
IMPORTANT NOTE: You must not manipulate the internal output table and/or its header in
the callback routines of the application. This restriction applies to all callbacks that are
called within list output and are listed below.
TOP_OF_LIST No USING parameters
Possibility to display information at the beginning of the list
END_OF_LIST No USING parameters
Possibility to display information at the end of the list
TOP_OF_PAGE No USING parameters
Corresponds to TOP-OF-PAGE during list processing
END_OF_PAGE No USING parameters
Not available for hierarchical-sequential lists.
Possibility to display information at the beginning of a page. This call is only executed
during the printout process.
TOP_OF_COVERPAGE No USING parameters
In the standard system, the selection information and the list status (if available) are
output together on a separate page. For more information, see also the documentation on
the following parameters:
IS_PRINT-NO_COVERPAGE
IS_PRINT-NO_PRINT_SELINFOS
IS_PRINT-NO_PRINT_LISTINFOS
IS_LAYOUT-GET_SELINFOS
Specifying a callback routine for this event allows the user to customize the header of the
'cover page'.
END_OF_COVERPAGE No USING parameters
As with TOP_OF_COVERPAGE, the user can append additional information at this event
to the information output by the ALV (selection information, list status).
FOREIGN_TOP_OF_PAGE No USING parameters
Event Top-of-page is always processed within the ALV and passed through to the user by
means of the callback mechanism only. This is also true if the caller, based on a user
interaction, for example, processes a details list (such as a dialog box with additional
information on the selected list line displayed by the ALV) not formatted by the ALV.
In this case, Top-of-page must not be formatted by the ALV like the basic list, but must
entirely be handled by the caller. Event Top-of-page is nevertheless located in the ALV. If
the ALV recognizes that a Top-of-page event is processed which is not triggered by an
ALV output, the form routine specified in FOREIGN_TOP_OF_PAGE is accessed.
FOREIGN_END_OF_PAGE No USING parameters

Event End-of-page is always processed within the ALV and passed through to the user by
means of the callback mechanism only. This is also true if the caller, based on a user
interaction, for example, processes a details list (such as a dialog box with additional
information on the selected list line displayed by the ALV) not formatted by the ALV.
In this case, End-of-page must not be formatted by the ALV like the basic list, but must
entirely be handled by the caller. Event End-of-page is nevertheless located in the ALV. If
the ALV recognizes that an End-of-page event is processed which is not triggered by an
ALV output, the form routine specified in FOREIGN_END_OF_PAGE is accessed.
IT_EVENTS-FORM

Name of the form routine that is to be executed in the calling program for the corresponding event.
Return ->
Table of events to perform

IS_PRINT

Print information

Description
Control parameters relevant for printing
PRINT

Value range: SPACE, 'X'


'X' = Print list and do not display it on the screen. Further settings can be made on the print
parameter screen.
NO_PRINT_SELINFOS

Value range: SPACE, 'X'


'X' = Do not print existing selection information (see also LAYOUT-GET_SELINFOS)
NO_COVERPAGE

Value range: SPACE, 'X'


'X' = Print selection information and list status, if available, on a separate page.
NO_NEW_PAGE

Value range: SPACE, 'X'


Internal use only
RESERVE_LINES

Value range: 0, n
n = Number of lines output in the footer by the user during printout at END_OF_PAGE in the
corresponding callback event.
NO_PRINT_LISTINFOS

Value range: SPACE, 'X'


'X' = Do not print list status (sort information, subtotals information and filter information).
NO_CHANGE_PRINT_PARAMS
Value range: SPACE, 'X'
SPACE = (default) The output format (number of columns) is dynamically adjusted depending on
the list width (255 at most).
'X' = The current print parameters are always used. If the list is wider, the output width is not
adjusted dynamically.

Return ->
Print information

Vous aimerez peut-être aussi