Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ALV

Former Member
0 Likes
1,233

can anybody help me in learning alv field catalog

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,131

ALV (ABAP LIST VIEWER)

Sap provides a set of ALV (ABAP LIST VIEWER) function modules, which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length. In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain upto 90 columns in the display with the wide array of display options.

The commonly used ALV functions used for this purpose are;

1. REUSE_ALV_VARIANT_DEFAULT_GET

2. REUSE_ALV_VARIANT_F4

3. REUSE_ALV_VARIANT_EXISTENCE

4. REUSE_ALV_EVENTS_GET

5. REUSE_ALV_COMMENTARY_WRITE

6. REUSE_ALV_FIELDCATALOG_MERGE

7. REUSE_ALV_LIST_DISPLAY

8. REUSE_ALV_GRID_DISPLAY

9. REUSE_ALV_POPUP_TO_SELECT

The different steps used for getting the above function modules into use are:

Step 1

DATA DECLARATION

Sap standard type pools: SLIS, KKBLO.

Sap standard tables types taken from the type pools are: SLIS_LAYOUT_ALV,

SLIS_T_FIELDCAT_ALV,

SLIS_T_LISTHEADER,

SLIS_T_EVENT,

SLIS_SELFIELD.

Internal tables to used in the program declared based on the above table types

DATA: I_LAYOUT TYPE SLIS_LAYOUT_ALV,

I_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,

I_HEADING TYPE SLIS_T_LISTHEADER,

I_EVENTS TYPE SLIS_T_EVENT.

TYPES: KKBLO_SELFIELD TYPE SLIS_SELFIELD.

Step 2 (Optional)

SELECTING THE VARIANTS FOR INITIAL LIST DISPLAY (DEFAULT VARIANT)

The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.

The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.

Sample code:

CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'

EXPORTING

i_save = variant save condition (A=all, U = user-specific)

CHANGING

cs_variant = internal table containing the program name (and the default variant---optional)

EXCEPTIONS

not_found = 2.

The user can also choose from the list of existing variants using the function module ‘REUSE_ALV_VARIANT_F4’.

Step 3

DEFININING OUTPUT CHARACTERISTICS: PREPARING DISPLAY FIELDS CATALOG

A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV. Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields).

A field catalog is required for every ALV list output to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.

The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module.

The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.

A field catalog need not be built-up and passed explicitly only under the following conditions:

1. The internal table to be output has the same structure as a Data Dictionary structure, which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.

2. All fields in this structure are to be output

3. The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.

All the values entered in the catalog are specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.

The different possible attributes are:

· Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.

Value set: 0, 1 – 3

· Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display. The parameter specifies the relative column position of the field in the list output. The user can change the column order interactively. If this parameter is initial for all field catalog entries, columns appear in the internal table field sequence.

Value set: 0, 1 – 60

· Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.

Value set: internal output table field name (required parameter)

· Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.

Value set: SPACE, internal output table name.

· Ref_fieldname (reference field name): Name of the Data Dictionary field referred to. This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.

Value set: SPACE, Data Dictionary field name.

· Ref_tabname (reference table/structure field name): Structure or table name of the referred Data Dictionary field. This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).

Value set: SPACE, name of a Data Dictionary structure or table

Link to currency unit

· Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.

Value set: SPACE, output table field name

· Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.

Value set: SPACE, output table field name.

Link to measurement unit

· Qfieldname (measurement unit field name): Only relevant for quantity columns with unit link. Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME. The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.

Value set: SPACE, output table field name.

· Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.

Value set: SPACE, output table field name.

· Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. For fields with a Data Dictionary link this parameter can be left initial. For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).

Initial = column width is the output length of the referred Data Dictionary field (domain).

N = column width is n characters.

Value set: 0 (initial), n.

· Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.

If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.

'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.

Value set: SPACE, 'X'.

· Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field can be hidden interactively.

The user cannot change the key column sequence interactively. The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.

Value set: SPACE, 'X'.

· No_out (field in field list): This parameter is used to remove certain fields from the output during initial display. The user can however interactively choose the field for output from the field list in the display variant.

'X' = field is not displayed in the current list.

Value set: SPACE, 'X'.

· Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.

'X' = technical field.

Value set: SPACE, 'X'.

· Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.

Value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off ,'1'=on).

'X' = column is colored with the default column highlight color.

'Cxyz' = column is colored with a coded color:

- C: Color (coding must begin with C)

- X: color number

- Y: bold

- Z: inverse

· Hotspot (column as hotspot): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.

Value set: SPACE, 'X'.

'X' = column cells are output as hotspots.

· Fix_column (fix column): This parameter is used to fix certain columns in the output. All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively.

Value set: SPACE, 'X'.

'X' = column fixed (does not scroll horizontally).

· Do_sum (sum over column): the user can also call this function interactively.

Value set: SPACE, 'X'.

'X' = a sum is calculated over this internal output table field.

· No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.

Value set: SPACE, 'X'.

· Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.

Value set: SPACE, 'X'.

'X' = column contents to be output as an icon.

· Symbol: The internal output table column must be a valid symbol character.

Value set: SPACE, 'X'

'X' = column contents are to be output as a symbol.

· Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.

Value set: SPACE, 'R', 'L', and ‘C’.

' ' = Default justification for this data type

'R' = right-justified output

'L' = left-justified output

'C' = centered output.

· Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.

Value set: SPACE, 'X'.

'X' = output with leading zeros.

· No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the value fields.

Value set: SPACE, 'X'.

'X' = value output without +/ sign.

· No_zero (suppress zeros): Only relevant for value fields.

Value set: SPACE, 'X'.

'X' = suppress zeros.

· Edit_mask (field formatting): To apply the report output formatting options same as in the WRITE statement in report writing.

Value set: SPACE, template.

The following parameters are used for customizing the texts in the heading of the output of the columns. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored.

If the user changes the column width interactively, the column header text with the appropriate length is always used.

The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.

The 'long field label' is also used in display variant definition,

Sort, etc. Popup.

· Seltext_l (long field label)

· Seltext_m (medium field label)

· Seltext_s (short field label)

· Reptext_ddic (header) Analogous to the Data element main header

· Ddictxt (specify text): You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.

Value set: SPACE, 'L', 'M', and ‘S’.

Sample code:

Suppose I_PO_DETAILS is an internal table containing two fields EBELN (PO number) and EBELP (PO item no).

DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV. “Local variable to hold the parameters

for a particular field of the field catalog

CLEAR L_FIELDCAT.

L_FIELDCAT-TABNAME = 'I_PO_DETAILS'.

L_FIELDCAT-FIELDNAME = 'EBELN'.

L_FIELDCAT-KEY = 'X'. “The PO no is made the key field,

“Colored and non scrollable

L_FIELDCAT-HOTSPOT = 'X'. “The po no becomes a hotspot

L_FIELDCAT-SELTEXT_S = ‘P.O No’.

L_FIELDCAT-SELTEXT_M = 'P order No'.

L_FIELDCAT-SELTEXT_L = 'Purchase order No'.

APPEND L_FIELDCAT TO I_FIELDTAB.

CLEAR L_FIELDCAT

L_FIELDCAT-TABNAME = 'I_PO_DETAILS'.

L_FIELDCAT-FIELDNAME = 'EBELN'.

L_FIELDCAT-KEY = 'X'. “The po item no is made the key field,

“Colored and non scrollable

L_FIELDCAT-SELTEXT_S = 'Item No'.

L_FIELDCAT-SELTEXT_M = 'Item No`.

L_FIELDCAT-SELTEXT_L = 'PO Item No'.

APPEND L_FIELDCAT TO I_FIELDTAB.

CLEAR L_FIELDCAT

Thus the catalog for the report output is prepared.

Step 4

The next step is to build an event table, which are used for firing both user commands and the system dependent events i.e. top of page, end of page etc.

A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.

The function module contains following import and export parameters.

IMPORTING PARAMETERS: I_LIST_TYPE

This parameter has possible values from 0-4.

The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0.

EXPORTING PARAMETERS: I_EVENTS table.

This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events.

The table structure contains the fields:

I_EVENTS-NAME: Name of the Callback event.

I_EVENTS-FORM: Name of the form routine that should be called in the calling program at the event.

Only events with a form routine name are processed.

The I_EVENTS table returns with the following possible constants:

1. Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.

Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.

2. Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.

RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.

RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table.

RS_SELFIELD is initial in this case.

3. Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.

Is called at the beginning of the function module to make special settings. It is not usually used.

4. Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.

As this is a frequently-used Callback event, the form routine can also be passed directly in the interface by passing the user command in the IMPORTING parameter I_CALLBACK_USER_COMMAND.

5. Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

Equivalent to the list processing TOP-OF-PAGE event.

6. Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.

The selection information and list status are output together (if they exist) on a separate page by default

7. Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.

Analogously to TOP_OF_COVERPAGE the user can add other information

to the information output by ALV (selection information, list status) at this event.

8. Slis_ev_foreign_top_of_page TYPE slis_formname VALUE ‘FOREIGN_TOP_OF_PAGE'.

The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).

In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.

9. Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.

The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).

In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.

10. Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.

If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).

The STANDARD status of the function group SALV should be used as a template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.

11. Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.

LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME

R_INDEX LIKE SY-TABIX

R_INDEX_ITEM LIKE SY-TABIX

R_INDEX_SUM LIKE SY-TABIX.

12. Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.

Information output at the start of the list

13. Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.

Information output at the end of a page. This is only called for printing.

14. Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.

Information output at the end of the list

15. Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.

Output information after each output line. Should only be used in justified cases because it costs a lot of performance.

16. Slis_ev_before_line_output TYPE slis_formname VALUE 'BEFORE_LINE_OUTPUT'.

Output information before each output line. Should only be used in justified cases because it costs a lot of performance.

17. Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.

This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.

Sample code :

FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',

FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE', FORMNAME_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND'.

DATA: L_I_EVENT TYPE SLIS_ALV_EVENT.

CALL FUNCTION 'REUSE_ALV_EVENTS_GET'

EXPORTING

I_LIST_TYPE = 0

IMPORTING

ET_EVENTS = I_EVENTS.

READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE

INTO L_I_EVENT.

IF SY-SUBRC = 0.

MOVE FORMNAME_TOP_OF_PAGE TO L_I_EVENT-FORM.

APPEND L_I_EVENT TO I_EVENTS.

ENDIF.

READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE

INTO L_I_EVENT.

IF SY-SUBRC = 0.

MOVE FORMNAME_END_OF_PAGE TO L_I_EVENT-FORM.

APPEND L_I_EVENT TO I_EVENTS.

ENDIF.

CLEAR L_I_EVENT.

READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND

INTO L_I_EVENT.

IF SY-SUBRC = 0.

MOVE FORMNAME_USER_COMMAND TO L_I_EVENT-FORM.

APPEND L_I_EVENT TO I_EVENTS.

ENDIF.

This will prepare the events table for the report.

The report will contain three forms for the above events:

1. FORM TOP_OF_PAGE : This form will contain the top of page event for the report i.e header etc

Using the function module ‘REUSE_ALV_COMMENTARY_WRITE’, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.

2. FORM END_OF_PAGE : This form will contain the end of page event for the report i.e footer etc

3. FORM USER_COMMAND : This form will contain the desired user command i.e pick/line selection

Step 5

A layout is build for the report output list description USING the internal table declared above (I_LAYOUT).

Output list description structure.

The parameters are described under the following heads:

· Display options

· Exceptions

· Totals

· Interaction

· Detail screen

· Display variants (only for hierarchical-sequential lists)

· Color

· Other

The layout table is of type slis_layout_alv_spec and has the following fields:

Display options

1. Colwidth_optimize (1) TYPE c: This parameter optimizes the length of the different columns in the output. The width of the different col. now depends on the max. Length of the data in the column.

Value set: SPACE, 'X'

'X' = optimizes the column width so that all contents are displayed completely.

2. No_colhead(1) TYPE c : This parameter suppresses the column headings

Value set: SPACE, 'X'.

'X' = column headers are not output

3. No_hotspot(1) TYPE c : The heading of the report output are not output as hotspot.

Value set: SPACE, 'X'.

'X' = column headers are not output as hotspot

4. Zebra(1) TYPE c : The report is output in the striped pattern.

Value set: SPACE, 'X'.

'X' = striped pattern (e.g. for wide lists)

5. No_vline(1) TYPE c : The report output contains columns only separated by space and no lines. It is not relevant for: hierarchical-sequential lists and multiple-line lists.

Value set: SPACE, 'X'.

'X' = columns separated by SPACE

6. No_min_linesize(1) TYPE c : The report line size is equal to the width of the list. It is not relevant for block lists.

Value set: SPACE, 'X’.

'X' = line size depends on list width

' ' = Line size is set to 80 or MIN_LINESIZE (if > 0) .

7. Min_linesize LIKE sy-linsz: The report output contains a minimum possible length of line. If initial min_linesize is set to 80 by default, then this parameter is used to customize it. The prerequisite for this is that the parameter no_min_linesize should be ' '.

Value set: 0, 10 - 250

If the list is wider, the format uses the list width (maximum 250 or MAX_LINESIZE (if > 0)).

8. Max_linesize LIKE sy-linsz: The default max. Linesize is 250. To change this default value, this parameter can interactively-define the maximum list width setting.

Value set: 0, 80 - 1020

9. Window_titlebar LIKE rsmpe-tittext: To set the titlebar on the report output.

10. No_uline_hs(1) TYPE c.

Exceptions

11. Lights_fieldname TYPE slis_fieldname: Internal output table field containing the codes of exceptions to be output.

Output table field code: '1' = red traffic light

'2' = yellow traffic light

'3' = green traffic light Fieldname for exception

Value set: SPACE, internal output table field name.

12. Lights_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter LIGHTS_FIELDNAME. If LIGHTS_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists. Only relevant for hierarchical-sequential lists.

. Value set: SPACE, internal output table name.

13. Lights_rollname LIKE dfies-rollname: The documentation of this data element is displayed when you call F1 help for an exception column.

Value set: SPACE, data element name.

14. Lights_condense(1) TYPE c : If a list record is output with 'red traffic light', each

Subtotal that includes this record is also output with 'red traffic light'.

Value set: SPACE, 'X'

'X' = the 'maximum' exception of the items in the subtotal is output at subtotal level.

Sums

15. No_sumchoice(1) TYPE c : This parameter allows the choice for summing up

Only by fieldcatalog.

Value set: SPACE, 'X'

'X' = fields which are to be summed, passed by the calling program (FIELDCAT-DO_SUM = 'X'). The user should not be able to change this value interactively.

16. No_totalline(1) TYPE c : Removes the option of having totals after sub-totals.

Value set: SPACE, 'X'

'X' = no total record is to be output. Subtotals can still be calculated and output. The fields in the subtotals are flagged DO_SUM = 'X' in the field list.

17. No_subchoice(1) TYPE c : Does not allow the user to interactively change the field chosen for subtotals.

Value set: SPACE, 'X'

'X' = value whose change triggers subtotals, provided by the calling program. The user should not be able to change this value interactively.

18. No_subtotals(1) TYPE c : No subtotals possible

Value set: SPACE, 'X'

'X' = no subtotals.

19. Numc_sum(1) TYPE c : Totals only possible for NUMC-Fields.

20. No_unit_splitting TYPE c: No separate total lines by inh.units

21.totals_before_items TYPE c: Display totals before the items

22. Totals_only(1) TYPE c : Show only totals

Value set: SPACE, 'X'

'X' = only total records are output.

23. Totals_text(60) TYPE c : Text for 1st col. in totals

Value set: SPACE, string (max.60)

' ' = The first column in the total record contains an appropriate number of '*'s to indicate the total by default. If the first column is wide enough, the string 'Total' is output after the asterisks.

'String’ = The string passed is output after the total indicated by '*', if the column is wide enough.

24. Subtotals_text(60) TYPE c : Texts for subtotals

Value set: SPACE, string (max.60)

' ' = In the first column of subtotal records, the subtotal is indicated by an appropriate number of '*' by default. If the first column is not a subtotal criterion, the string 'Total' is output after the asterisks, if the column is wide enough.

'String’ = the string passed is output after the subtotal indicated by '*', if the column is wide enough and the first column is not a subtotal criterion. If it is a subtotal criterion, its value is repeated after the total, if the column is wide enough.

Interaction

25. Box_fieldname TYPE slis_fieldname: Fieldname for checkbox in the report output. If the list has checkboxes at the start of records (for selecting several records), this parameter contains the internal output table field name indicated by the checkbox selection column. The field is a checkbox at the start of list records without a list header.

Value set: SPACE, internal output table field name

26. Box_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter BOX_FIELDNAME. If BOX_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists.

Value set: SPACE, internal output table name.

27. Box_rollname LIKE dd03p-rollname: rollname for checkbox

28. Expand_fieldname TYPE slis_fieldname: fieldname flag ‘expand’. The user can show or hide the items by clicking on the folder symbol (hotspot). If the items for a header entry are only to be read by the calling program and passed to ALV when a header has been expanded interactively, this can be controlled via the CALLBACK event 'ITEM_DATA_EXPAND'.

29. Hotspot_fieldname TYPE slis_fieldname: Used to make the fieldname flag hotspot.

30. No_input(1) TYPE c : The fields are only display fields.

Value set: SPACE, 'X'

'X' = all ready-for-input fields in a list are displayed as not ready-for-input. (Record selection checkboxes and fields which can be made ready-for-input via the field list parameter FIELDCAT-INPUT = 'X')

31. F2code LIKE sy-ucomm: To assign an ALV standard function code to double-click (F2), assign the function code to this parameter. Ex.: to assign the ALV standard function 'Detail' ('&ETA') to F2.

=> LAYOUT-F2CODE = '&ETA'.

Value set: SPACE, function code

32. Confirmation_prompt: confirm. Prompt when leaving

Value set: SPACE, 'X'

'X' = if one of the functions ‘Back (F03)', ‘Exit (F15)' or ‘Cancel (F12)' occurs, a confirmation prompt appears.

33. Key_hotspot(1) TYPE c : The key fields are displayed as hotspot. The columns defined in the field catalog as key fields (FIELDCAT-KEY = 'X') are output as hotspots, i.e. clicking on a key column (highlighted in color in the list) calls the function under F2.

Value set: SPACE, 'X'.

34. Reprep(1) TYPE c : report report interface active.

35. Group_buttons(1) TYPE c : group-buttons for COL1 - COL5 . Group output fields via FIELDCAT-SP_GROUP in the field list, and pass the group name to the list module in the interface parameter IT_SPECIAL_GROUPS.

Value set: SPACE, 'X'.

36. No_keyfix(1) TYPE c : Used to make the key fields scrollable.

Value set: SPACE, 'X'.

' ' = The key columns defined in the field catalog by FIELDCAT-KEY = 'X' are fixed in the list output. These columns do not scroll horizontally. The item table key columns are fixed in hierarchical-sequential lists. The header table key fields are not considered here.

'X' = key columns not fixed

37. Get_selinfos(1) TYPE c : To read selection screen.

Value set: SPACE, 'X'.

If the calling program is a report with an ABAP/4 selection screen, setting this parameter makes ALV read the selection screen again. If the selections are read successfully, a pushbutton, via which the user can call a popup which lists the report selections in a simple form, becomes active on the results list output by ALV.

38. group_change_edit(1) TYPE c : Settings by user for new group

Value set: SPACE, 'X'

'X' = the user can enter a format option for each sort criterion in the sort/subtotal popup, for the list format when this value changes (e.g. new page or underline).

39. No_scrolling(1) TYPE c : Does not allow scrolling of the list to the right.

Value set: SPACE, 'X'.

40. Expand_all(1) TYPE c : Expand all positions

Detailed screen

40. Detail_popup(1) TYPE c : show detail in popup.

Value set: SPACE, 'X'

' ' = List record detail display in full-screen mode, with top-of-page.

'X' = list record detail display in popup (without top-of-page).

41. Detail_initial_lines(1) TYPE c : show also initial lines

Value set: SPACE, 'X'

' ' = Only fields whose contents are not initial are output in the detail view.

'X' = initial field contents are also output in detail.

41. detail_titlebar(30) type c : Titlebar for detail screen

Value set: SPACE, string (max.30)

` ' = ' Detail: Display' is output as the title of the detail window.

'String’ = the string passed is output as the title of the detail window.

Display variants

42. Header_text (20) TYPE c: Text for header button. Only relevant for hierarchical-sequential lists. You can toggle between display field and field list views via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.

Value set: SPACE, CHAR (20)

' ' = The header table field pushbutton text is 'Header' by default.

CHAR (20) = header table field pushbutton text.

43.item_text(20) TYPE c : Text for item button. Only relevant for hierarchical-sequential lists. You can toggle the view between the display fields and the field list via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.

Value set: SPACE, CHAR (20)

' ' = The pushbutton text for the item table fields is 'Item' by default.

CHAR (20) = item table field pushbutton text.

44.default_ item(1) TYPE c : Items as default. Only relevant for hierarchical-sequential lists.

Value set: SPACE, 'X'

' ' = The header table fields are displayed by default in the display variant definition popup. The user can switch to the item table fields interactively.

'X' = the item table fields are displayed by default in the display variant Definition Popup. The user can switch to the header table fields interactively.

Colour

45. Info_fieldname TYPE slis_fieldname: infofield for listoutput. A whole list record can be colored individually using a color code in a column of the internal output table for the record. Assign the name of the field containing the color code to this parameter.

Value set: SPACE, internal output table field name

The internal output table field must be of type CHAR(3).

The code must have the following syntax: 'Cxy':

C = color (all codes must start with 'C')

X = color number ('1'-'9')

Y = bold ('0' = off, '1' = on)

46. Coltab_fieldname TYPE slis_fieldname: Cells can be colored individually using a color code which is contained in a column of the internal output table for the record containing the cell. Assign the name of the field to this parameter.

Others

47. List_append(1) TYPE c : no call screen. It is only useful to output block-lists without specifying the above modules if the number of list blocks exceeds, or may exceed, the maximum number specified in the block module documentation. These operations are not possible for user-defined block lists.

Example code :

I_LAYOUT-f2code = ws_fcode.

I_LAYOUT-zebra = 'X'.

I_LAYOUT-colwidth_optimize = 'X'.

I_LAYOUT-no_keyfix = 'X'.

I_LAYOUT-get_selinfos = 'X'.

I_LAYOUT-no_hotspot = 'X'.

I_LAYOUT-no_input = 'X'.

I_LAYOUT-hotspot_fieldname = FIELDNAME.

I_LAYOUT-no_input = ‘X’.

I_LAYOUT-no_vline = `X’.

I_LAYOUT-no_colhead = ‘ ‘.

I_LAYOUT-lights_condense = ` `.

I_LAYOUT-totals_text = ` `.

I_LAYOUT-subtotals_text = ` `.

I_LAYOUT-totals_only = ` `.

I_LAYOUT-key_hotspot = ‘X’.

I_LAYOUT-detail_popup = ‘X’.

I_LAYOUT-group_change_edit = ‘X’.

I_LAYOUT-GROUP_BUTTONS = ‘X’.

Step 6

This step is required to get the selection screen information in the report output.

The prerequisite for this is to set the parameter LAYOUT-GET_SELINFOS of the IMPORTING structure.

The parameters to be passed in the IS_SEL_HIDE table are:

o mode: 'R' = only the entries passed in the internal table IS_SEL_HIDE-T_ENTRIES

Are output in the pop up. Selection info, which the list tool read in the selection screen (when called by a report with a selection screen), is replaced by the values passed.

'S' = the selection info which the list tool read in the selection screen of the calling report are modified by the entries in the table IS_SEL_HIDE-T_ENTRIES.

o t_entries: Selection info table

o t_entries-mode: 'A' = output the selection info for the current table record in the info popup.

'D' = do not output select option or SELNAME parameter selection info in the popup.

o t_entries-selname: (only used in t_entries-mode = 'D') : Name of the select option or parameter.

The following table fields are only used in t_entries-mode = 'A'. They contain the selection information to be added.

· t_entries-field: DDIC field name of the field for which selection information is to be output.

· t_entries-table: DDIC table names of t_entries-field.

· t_entries-stext: Field name in info popup.

· If t_entries-field and t_entries-table have been entered, this text is taken from DDIC.

· t_entries-valuf: Selection condition 'from' value (external format)

· t_entries-valut: Selection condition 'to' value (external format)

· t_entries-sign0: (I)nclusive (E)xclusive

· t_entries-option: All values of the select options Option field allowed.

Step 6

The Table IT_SORT is populated with the sort criteria for the different fields.

The caller specifies the sorting and/or subtotaling of the basic list in the internal table IT_SORT.

This internal table has the following fields:

o spos : Sort sequence

o fieldname : Internal output table field name

o tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.

o up : 'X' = sort in ascending order

o down : 'X' = sort in descending order

o subtot : 'X' = subtotal at group value change

o group : '* ' = new page at group value change ,'UL' = underline at group value change

Step 7

The final step in the output of the report is the use of two ALV functions modules.

1. REUSE_ALV_FIELDCATALOG_MERGE

2. REUSE_ALV_LIST_DISPLAY

The first function module is used to pass the field catalog to the report output and merge it with the internal output table.

FUNCTION reuse_alv_fieldcatalog_merge.

*"----

-


""Lokale Schnittstelle:

*” IMPORTING

*" VALUE(I_PROGRAM_NAME) LIKE SY-REPID OPTIONAL

*" VALUE(I_INTERNAL_TABNAME) TYPE SLIS_TABNAME OPTIONAL

*" VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL

*" VALUE(I_CLIENT_NEVER_DISPLAY) TYPE SLIS_CHAR_1

*" DEFAULT 'X'

*" VALUE(I_INCLNAME) LIKE TRDIR-NAME OPTIONAL

*" CHANGING

*" VALUE(CT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV

*" EXCEPTIONS

*" INCONSISTENT_INTERFACE

*" PROGRAM_ERROR

*"----

-


Import parameters

I_PROGRAM_NAME: Program in which the internal output table is declared and populated

I_INTERNAL_TABNAME: Internal output table name

I_STRUCTURE_NAME: Structure name (structure, table, and view)

I_CLIENT_NEVER_DISPL: Hide client fields default ‘X’

I_INCLNAME: Data declarations include name

CHANGING parameter

CT_FIELDCAT: Field catalog with field descriptions

The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:

1. Performance is affected since the code of the table definition must always be read and interpreted at runtime.

2. Dictionary reference are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.

Step 8

The other function module is used to display the internal output table with the contents

FUNCTION reuse_alv_list_display.

*"----

-


""Lokale Schnittstelle:

*” IMPORTING

*" VALUE(I_INTERFACE_CHECK) DEFAULT SPACE

*" VALUE(I_CALLBACK_PROGRAM) LIKE SY-REPID DEFAULT SPACE

*" VALUE(I_CALLBACK_PF_STATUS_SET) TYPE SLIS_FORMNAME

*" DEFAULT SPACE

*" VALUE(I_CALLBACK_USER_COMMAND) TYPE SLIS_FORMNAME

*" DEFAULT SPACE

*" VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL

*" VALUE(IS_LAYOUT) TYPE SLIS_LAYOUT_ALV OPTIONAL

*" VALUE(IT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV OPTIONAL

*" VALUE(IT_EXCLUDING) TYPE SLIS_T_EXTAB OPTIONAL

*" VALUE(IT_SPECIAL_GROUPS) TYPE SLIS_T_SP_GROUP_ALV

*" OPTIONAL

*" VALUE(IT_SORT) TYPE SLIS_T_SORTINFO_ALV OPTIONAL

*" VALUE(IT_FILTER) TYPE SLIS_T_FILTER_ALV OPTIONAL

*" VALUE(IS_SEL_HIDE) TYPE SLIS_SEL_HIDE_ALV OPTIONAL

*" VALUE(I_DEFAULT) DEFAULT 'X'

" VALUE(I_SAVE) DEFAULT SPACE

" VALUE(IS_VARIANT) LIKE DISVARIANT

" STRUCTURE DISVARIANT DEFAULT SPACE

" VALUE(IT_EVENTS) TYPE SLIS_T_EVENT OPTIONAL

" VALUE(IT_EVENT_EXIT) TYPE SLIS_T_EVENT_EXIT OPTIONAL

" VALUE(IS_PRINT) TYPE SLIS_PRINT_ALV OPTIONAL

" VALUE(IS_REPREP_ID) TYPE SLIS_REPREP_ID OPTIONAL

" VALUE(I_SCREEN_START_COLUMN) DEFAULT 0

" VALUE(I_SCREEN_START_LINE) DEFAULT 0

" VALUE(I_SCREEN_END_COLUMN) DEFAULT 0

" VALUE(I_SCREEN_END_LINE) DEFAULT 0

" EXPORTING

" VALUE(E_EXIT_CAUSED_BY_CALLER)

" VALUE(ES_EXIT_CAUSED_BY_USER) TYPE SLIS_EXIT_BY_USER

" TABLES

" T_OUTTAB

" EXCEPTIONS

" PROGRAM_ERROR

Import parameters

I_INTERFACE_CHECK: Interface consistency check log output.

I_CALLBACK_PROGRAM: Name of the calling program

I_CALLBACK_PF_STATUS_SET: Set EXIT routine to status.

I_CALLBACK_USER_COMMAND: EXIT routine for command handling

I_STRUCTURE_NAME: Internal output table structure name

IS_LAYOUT: List layout specifications

IT_FIELDCAT: Field catalog with field descriptions

IT_EXCLUDING: Table of inactive function codes

IT_SPECIAL_GROUPS: Grouping fields for column selection

IT_SORT: Sort criteria for first list display

IT_FILTER: Filter criteria for first list output

IS_SEL_HIDE : Selection information modification

I_DEFAULT: Initial variant active/inactive logic

I_SAVE: Variants can be saved

IS_VARIANT : Variant information

IT_EVENTS: Table of events to perform

IT_EVENT_EXIT : Standard fcode exit requests table

IS_PRINT: Print information

IS_REPREP_ID: Initialization keys for Re/Re interface

I_SCREEN_START_COLUMN: Coordinates for list in dialog box

I_SCREEN_START_LINE: Coordinates for list in dialog box

I_SCREEN_END_COLUMN: Coordinates for list in dialog box

I_SCREEN_END_LINE: Coordinates for list in dialog box

IT_EVENT_EXIT: Standard fcode exit requests table

IS_PRINT: Print information

IS_REPREP_ID: Initialization keys for Re/Re interface

I_SCREEN_START_COLUMN: Coordinates for list in dialog box

I_SCREEN_START_LINE: Coordinates for list in dialog box

I_SCREEN_END_COLUMN: Coordinates for list in dialog box

I_SCREEN_END_LINE: Coordinates for list in dialog box

Export parameters

E_EXIT_CAUSED_BY_CALLER: Delete list in CALLBACK_USER_COMMAND

ES_EXIT_CAUSED_BY_USER: How the user left the list Tables

T_OUTTAB: Table with data to be displayed ---mandatory

Example Code

WS_REPNAME = SY-REPID.

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING

I_PROGRAM_NAME = WS_REPNAME

I_INTERNAL_TABNAME = Internal output table field name

I_INCLNAME = WS_REPNAME

CHANGING

CT_FIELDCAT = I_FIELDTAB.

IF SY-SUBRC <> 0.

WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_FIELDCATALOG_MERGE'.

ENDIF.

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

EXPORTING

I_CALLBACK_PROGRAM = WS_REPNAME

I_STRUCTURE_NAME = Internal output table field name

IS_LAYOUT = I_LAYOUT

IT_FIELDCAT = I_FIELDTAB

I_DEFAULT = 'A'

I_SAVE = 'A'

IS_VARIANT = 'X'

IT_EVENTS = I_EVENTS[]

IT_SORT = I_SORT

IS_SEL_HIDE = I_SELINFO

TABLES

T_OUTTAB = Internal output table field name.

IF SY-SUBRC <> 0.

WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_LIST_DISPLAY'.

ENDIF

THIS IS THE POP UP TO ALLOW THE USER TO DYNAMICALLY SELECT THE FIELDS FOR DISPLAY. HE CAN CHOOSE FROM THIS FIELDS ACC. TO REQUIREMENT AND HIDE THE OTHER FIELDS

Example report output based prior to selection of the field

THE USER HAS HIDDEN SOME OF THE FIELD FROM THE TOTAL FIELDS TO CUSTOMIZE THE REPORT OUTPUT

Example report output after hiding some of the fields

USER CAN CHOOSE A PARTICULAR SET OF FIELD FROM THE OUTPUT AND CAN SAVE IT AS VARIANTS

Using other function module 'REUSE_ALV_GRID_DISPLAY’ can help us get list output in the form of a grid and also attach logos to the report output.

Sample code

1 Simple list output:

REPORT Y_DEMO_ALV NO STANDARD PAGE HEADING.

*

  • Data to be displayed

DATA: I_SFLIGHT TYPE TABLE OF SFLIGHT.

*----


*

  • Selection

SELECT * FROM SFLIGHT INTO TABLE I_SFLIGHT.

  • Call ABAP List Viewer (ALV)

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

EXPORTING

I_STRUCTURE_NAME = 'SFLIGHT'

TABLES

T_OUTTAB = I_SFLIGHT.

2.Simple grid output:

REPORT Y_DEMO_ALV_1.

*

  • Data to be displayed

DATA: I_SFLIGHT TYPE TABLE OF SFLIGHT.

*----


*

  • Selection

SELECT * FROM SFLIGHT INTO TABLE I_SFLIGHT.

  • Call ABAP List Viewer (ALV)

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

I_STRUCTURE_NAME = 'SFLIGHT'

TABLES

T_OUTTAB = I_SFLIGHT.

3. Demo for 'REUSE_ALV_POPUP_TO_SELECT'

REPORT y_demo_alv_3.

TYPE-POOLS: slis.

DATA: BEGIN OF i_outtab OCCURS 0.

INCLUDE STRUCTURE sflight.

DATA: w_chk TYPE c. "For multiple selection

DATA: END OF i_outtab.

  • I_OUTTAB TYPE SFLIGHT OCCURS 0,

DATA: i_private TYPE slis_data_caller_exit,

i_selfield TYPE slis_selfield,

W_exit(1) TYPE c.

PARAMETERS: p_title TYPE sy-title.

*

START-OF-SELECTION.

SELECT * FROM sflight INTO TABLE i_outtab.

CALL FUNCTION 'REUSE_ALV_POPUP_TO_SELECT'

EXPORTING

i_title = p_title

i_selection = 'X'

i_zebra = 'X'

  • I_SCREEN_START_COLUMN = 0

  • I_SCREEN_START_LINE = 0

  • I_SCREEN_END_COLUMN = 0

  • I_SCREEN_END_LINE = 0

i_checkbox_fieldname = 'W_CHK'

  • I_LINEMARK_FIELDNAME =

  • I_SCROLL_TO_SEL_LINE = 'X'

i_tabname = 'I_OUTTAB'

i_structure_name = 'SFLIGHT'

  • IT_FIELDCAT =

  • IT_EXCLUDING =

  • I_CALLBACK_PROGRAM =

  • I_CALLBACK_USER_COMMAND =

  • IS_PRIVATE = I_PRIVATE

IMPORTING

es_selfield = i_selfield

e_exit = w_exit

TABLES

t_outtab = i_outtab

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

  • MESSAGE i000(0k) WITH sy-subrc.

ENDIF.

*****the internal table is modified with a cross sign for marking the

***rows selected

LOOP AT i_outtab WHERE w_chk = 'X'.

WRITE: / i_outtab-carrid, i_outtab-price.

ENDLOOP.

4. Demo for ALV output using field catalog and layout:

REPORT y_demo_alv NO STANDARD PAGE HEADING.

  • ALV related data declaration

TYPE-POOLS: slis.

  • DB-Table

TABLES sflight.

  • Includes

INCLUDE .

*

CONSTANTS:

c_formname_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

DATA: i_fieldcat TYPE slis_t_fieldcat_alv,

i_layout TYPE slis_layout_alv,

i_sp_group TYPE slis_t_sp_group_alv,

i_events TYPE slis_t_event,

i_print TYPE slis_print_alv,

i_sort TYPE slis_t_sortinfo_alv.

*internal table for data to be displayed

DATA: BEGIN OF i_sflight OCCURS 0.

INCLUDE STRUCTURE sflight.

DATA: box,

lights.

DATA: END OF i_sflight.

*

DATA: w_repid LIKE sy-repid.

DATA: i_list_top_of_page TYPE slis_t_listheader.

  • Report Selections

SELECT-OPTIONS s_carrid FOR sflight-carrid.

SELECT-OPTIONS s_connid FOR sflight-connid.

SELECT-OPTIONS s_fldate FOR sflight-fldate.

*SELECTION-SCREEN SKIP 1.

  • Parameters

PARAMETERS: p_maxrow TYPE i DEFAULT 30."to limit the selection

SELECTION-SCREEN SKIP 1.

  • Variant for ALV display

SELECTION-SCREEN BEGIN OF BLOCK 0 WITH FRAME TITLE text-000.

PARAMETERS: p_varnt LIKE disvariant-variant.

SELECTION-SCREEN END OF BLOCK 0.

  • Layout of the report display

SELECTION-SCREEN BEGIN OF BLOCK a WITH FRAME TITLE text-001.

PARAMETERS: p_zebra AS CHECKBOX DEFAULT ' ', "Striped pattern

p_nocolh AS CHECKBOX DEFAULT ' ', "No column heading

p_novlin AS CHECKBOX DEFAULT ' ', "No vertical lines

p_colopt AS CHECKBOX DEFAULT ' ', "Optimizes col. wd

p_keyhot AS CHECKBOX DEFAULT ' ', "Key fields hot

p_noinpt AS CHECKBOX DEFAULT ' '. "No field for input

SELECTION-SCREEN END OF BLOCK a.

SELECTION-SCREEN BEGIN OF BLOCK b WITH FRAME TITLE text-002.

PARAMETERS: p_lights AS CHECKBOX DEFAULT 'X',

p_lightc AS CHECKBOX DEFAULT 'X'.

SELECTION-SCREEN END OF BLOCK b.

SELECTION-SCREEN BEGIN OF BLOCK c WITH FRAME TITLE text-003.

PARAMETERS: p_totonl AS CHECKBOX DEFAULT ' ',

p_totext(60),

p_sttext(60).

SELECTION-SCREEN END OF BLOCK c.

SELECTION-SCREEN BEGIN OF BLOCK d WITH FRAME TITLE text-004.

PARAMETERS: p_chkbox AS CHECKBOX DEFAULT 'X',

p_detpop AS CHECKBOX DEFAULT 'X',

p_groupb AS CHECKBOX DEFAULT ' ',

p_groups AS CHECKBOX DEFAULT ' '.

SELECTION-SCREEN END OF BLOCK d.

SELECTION-SCREEN BEGIN OF BLOCK e WITH FRAME TITLE text-005.

PARAMETERS: p_print AS CHECKBOX DEFAULT ' ',

p_nosinf AS CHECKBOX DEFAULT ' ',

p_nocove AS CHECKBOX DEFAULT ' ',

p_nonewp AS CHECKBOX DEFAULT ' ',

p_nolinf AS CHECKBOX DEFAULT ' ',

p_reserv TYPE i.

SELECTION-SCREEN END OF BLOCK e.

DATA: w_boxnam TYPE slis_fieldname VALUE 'BOX',

w_f2code LIKE sy-ucomm VALUE '&ETA',

w_lignam TYPE slis_fieldname VALUE 'LIGHTS',

w_save(1) TYPE c,

w_default(1) TYPE c,

w_exit(1) TYPE c,

i_variant LIKE disvariant,

i_variant1 LIKE disvariant.

*----


*

INITIALIZATION.

w_repid = sy-repid.

PERFORM fieldcat_init USING i_fieldcat.

PERFORM eventtab_build USING i_events.

PERFORM comment_build USING i_list_top_of_page.

PERFORM sp_group_build USING i_sp_group.

PERFORM t_sort_build USING i_sort.

  • Set Options: save variant userspecific or general

        • 'A or 'U' are for user-specific variants list

        • 'X' or 'space' for general

w_save = 'A'.

PERFORM variant_init.

  • Get default variant

i_variant1 = i_variant.

CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'

EXPORTING

i_save = w_save

CHANGING

cs_variant = i_variant1

EXCEPTIONS

not_found = 2.

IF sy-subrc = 0.

p_varnt = i_variant1-variant.

ENDIF.

  • Process on value request (list of possible variants)

AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_varnt.

PERFORM f4_for_variant.

  • PAI

AT SELECTION-SCREEN.

PERFORM pai_of_selection_screen.

START-OF-SELECTION.

PERFORM selection.

END-OF-SELECTION.

PERFORM layout_build USING i_layout. "wg. Parameters

PERFORM print_build USING i_print. "wg. Parameters

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING

i_program_name = w_repid

  • i_internal_tabname = 'I_SFLIGHT'

i_structure_name = 'SFLIGHT'

i_client_never_display = 'X'

i_inclname = w_repid

CHANGING

ct_fieldcat = i_fieldcat[]

EXCEPTIONS

inconsistent_interface = 1

program_error = 2

OTHERS = 3.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

  • Call ABAP/4 List Viewer

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

  • I_INTERFACE_CHECK = ' '

i_callback_program = w_repid

  • 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 = 'SFLIGHT'

i_background_id = 'ALV_BACKGROUND'

  • I_GRID_TITLE =

  • I_GRID_SETTINGS =

is_layout = i_layout

it_fieldcat = i_fieldcat[]

  • IT_EXCLUDING =

it_special_groups = i_sp_group[]

it_sort = i_sort[]

  • IT_FILTER =

  • IS_SEL_HIDE =

  • I_DEFAULT = 'X'

i_save = w_save

is_variant = i_variant

it_events = i_events[]

  • IT_EVENT_EXIT =

is_print = i_print

  • IS_REPREP_ID =

  • I_SCREEN_START_COLUMN = 0

  • I_SCREEN_START_LINE = 0

  • I_SCREEN_END_COLUMN = 0

  • I_SCREEN_END_LINE = 0

  • IMPORTING

  • E_EXIT_CAUSED_BY_CALLER =

  • ES_EXIT_CAUSED_BY_USER =

TABLES

t_outtab = i_sflight

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

  • MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

  • WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

  • CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

  • EXPORTING

  • i_callback_program = w_repid

  • i_structure_name = 'SFLIGHT'

  • is_layout = i_layout

  • it_fieldcat = i_fieldcat[]

    • IT_EXCLUDING =

  • it_special_groups = i_sp_group[]

  • it_sort = i_sort[]

    • IT_FILTER =

    • IS_SEL_HIDE =

    • i_default = W_DEFAULT

  • i_save = w_save

  • is_variant = i_variant

  • it_events = i_events[]

    • IT_EVENT_EXIT =

  • is_print = i_print

    • I_SCREEN_START_COLUMN = 0

    • I_SCREEN_START_LINE = 0

    • I_SCREEN_END_COLUMN = 0

    • I_SCREEN_END_LINE = 0

    • IMPORTING

    • E_EXIT_CAUSED_BY_CALLER =

  • TABLES

  • t_outtab = i_sflight.

*----


*

  • FORM FIELDCAT_INIT *

*----


*

  • --> L_FIELDCAT *

*----


*

FORM fieldcat_init USING l_fieldcat TYPE slis_t_fieldcat_alv.

DATA: ls_fieldcat TYPE slis_fieldcat_alv.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'SEATSOCC'.

*The field is not displayed in the initial output, can be interactively

  • chosen for display

ls_fieldcat-no_out = 'X'.

*This field is assigned to a special group with tech. key 'A' and can be

*displayed using the special group buttons

ls_fieldcat-sp_group = 'A'.

*The field cannot be summed irrespective of its data type

ls_fieldcat-no_sum = 'X'.

APPEND ls_fieldcat TO l_fieldcat.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'SEATSMAX'.

ls_fieldcat-no_out = 'X'.

ls_fieldcat-sp_group = 'A'.

APPEND ls_fieldcat TO l_fieldcat.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'PRICE'.

ls_fieldcat-no_out = 'X'.

ls_fieldcat-sp_group = 'B'.

APPEND ls_fieldcat TO l_fieldcat.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'CARRID'.

ls_fieldcat-outputlen = 7.

APPEND ls_fieldcat TO l_fieldcat.

ENDFORM.

*----


*

  • FORM DATA_ADD *

*----


*

  • --> L_SFLIGHT

*----


*

FORM data_add TABLES l_sflight STRUCTURE i_sflight.

LOOP AT l_sflight.

IF sy-tabix > 10.

l_sflight-box = 'X'.

l_sflight-lights = '3'.

ELSE.

IF sy-tabix = 1.

l_sflight-lights = '2'.

ELSE.

l_sflight-lights = '1'.

ENDIF.

ENDIF.

MODIFY l_sflight.

ENDLOOP.

ENDFORM.

*----


*

  • FORM EVENTTAB_BUILD *

*----


*

  • --> l_EVENTS *

*----


*

FORM eventtab_build USING l_events TYPE slis_t_event.

DATA: ls_event TYPE slis_alv_event.

*

CALL FUNCTION 'REUSE_ALV_EVENTS_GET'

EXPORTING

i_list_type = 0

IMPORTING

et_events = l_events.

READ TABLE l_events WITH KEY name = slis_ev_top_of_page INTO ls_event.

IF sy-subrc = 0.

MOVE c_formname_top_of_page TO ls_event-form.

APPEND ls_event TO l_events.

ENDIF.

ENDFORM.

*----


*

  • FORM COMMENT_BUILD *

*----


*

  • --> L_TOP_OF_PAGE *

*----


*

FORM comment_build USING l_top_of_page TYPE slis_t_listheader.

DATA: ls_line TYPE slis_listheader.

***Header

CLEAR ls_line.

ls_line-typ = 'H'.

  • LS_LINE-KEY: not used for this type

ls_line-info = 'Heading list'.

APPEND ls_line TO l_top_of_page.

***Selection

CLEAR ls_line.

ls_line-typ = 'S'.

ls_line-key = 'Key 1'.

ls_line-info = 'Information'.

APPEND ls_line TO l_top_of_page.

ls_line-key = 'Key 2'.

APPEND ls_line TO l_top_of_page.

***Action

CLEAR ls_line.

ls_line-typ = 'A'.

  • LS_LINE-KEY: not used for this type

Ls_line-info = 'Status list'.

APPEND ls_line TO l_top_of_page.

ENDFORM.

*----


*

  • FORM LAYOUT_BUILD *

*----


*

  • <-> LS_LAYOUT *

*----


*

FORM layout_build USING ls_layout TYPE slis_layout_alv.

ls_layout-f2code = w_f2code.

ls_layout-zebra = p_zebra.

ls_layout-colwidth_optimize = p_colopt.

IF p_chkbox = 'X'.

*Fieldname for check box on the report output

ls_layout-box_fieldname = w_boxnam.

ELSE.

ls_layout-box_fieldname = space.

ENDIF.

ls_layout-no_input = p_noinpt.

ls_layout-no_vline = p_novlin.

ls_layout-no_colhead = p_nocolh.

IF p_lights = 'X' OR p_lightc = 'X'.

**Fieldname for lights on the report output

ls_layout-lights_fieldname = w_lignam.

ELSE.

CLEAR ls_layout-lights_fieldname.

ENDIF.

ls_layout-lights_condense = p_lightc.

ls_layout-totals_text = p_totext.

ls_layout-subtotals_text = p_sttext.

ls_layout-totals_only = p_totonl.

ls_layout-key_hotspot = p_keyhot.

ls_layout-detail_popup = p_detpop.

ls_layout-group_change_edit = p_groups.

  • E05_LS_LAYOUT-GROUP_BUTTONS = P_GROUPB.

  • ls_layout-group_buttons = 'X'.

ENDFORM.

*----


*

  • FORM SP_GROUP_BUILD *

*----


*

  • --> L_SP_GROUP *

*----


*

FORM sp_group_build USING l_sp_group TYPE slis_t_sp_group_alv.

DATA: ls_sp_group TYPE slis_sp_group_alv.

*Fields are assigned to the special group

CLEAR ls_sp_group.

ls_sp_group-sp_group = 'A'.

ls_sp_group-text = 'Reservation status'.

APPEND ls_sp_group TO l_sp_group.

CLEAR ls_sp_group.

ls_sp_group-sp_group = 'B'.

ls_sp_group-text = 'Flight charges'.

APPEND ls_sp_group TO l_sp_group.

ENDFORM.

*----


*

  • FORM SELECTION *

*----


*

FORM selection.

SELECT * FROM sflight INTO CORRESPONDING FIELDS OF TABLE i_sflight

UP TO p_maxrow ROWS WHERE carrid IN s_carrid

AND connid IN s_connid AND fldate IN s_fldate.

PERFORM data_add TABLES i_sflight.

ENDFORM.

*----


*

  • FORM TOP_OF_PAGE *

*----


*

  • ........ *

*----


*

FORM top_of_page.

*

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

i_logo = 'ENJOYSAP_LOGO'

it_list_commentary = i_list_top_of_page.

ENDFORM.

*----


*

  • FORM F4_FOR_VARIANT *

*----


*

FORM f4_for_variant.

*

CALL FUNCTION 'REUSE_ALV_VARIANT_F4'

EXPORTING

is_variant = i_variant

i_save = w_save

  • it_default_fieldcat =

IMPORTING

e_exit = w_exit

es_variant = i_variant1

EXCEPTIONS

not_found = 2.

IF sy-subrc = 2.

MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ELSE.

IF w_exit = space.

p_varnt = i_variant1-variant.

ENDIF.

ENDIF.

ENDFORM.

*&----


*

*& Form PAI_OF_SELECTION_SCREEN

*&----


*

  • to check whether right variant is entered on the selection scr

*----


*

FORM pai_of_selection_screen.

*

IF NOT p_varnt IS INITIAL.

MOVE i_variant TO i_variant1.

MOVE p_varnt TO i_variant1-variant.

CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'

EXPORTING

i_save = w_save

CHANGING

cs_variant = i_variant1.

i_variant = i_variant1.

ELSE.

PERFORM variant_init.

ENDIF.

ENDFORM. " PAI_OF_SELECTION_SCREEN

*&----


*

*& Form VARIANT_INIT

*----


*

FORM variant_init.

*

CLEAR i_variant.

i_variant-report = w_repid.

ENDFORM. " VARIANT_INIT

*----


*

  • FORM PRINT_BUILD *

*----


*

  • ........ *

*----


*

FORM print_build USING l_print TYPE slis_print_alv.

*

l_print-print = p_print.

l_print-no_print_selinfos = p_nosinf.

l_print-no_coverpage = p_nocove.

l_print-no_new_page = p_nonewp.

l_print-no_print_listinfos = p_nolinf.

l_print-reserve_lines = p_reserv.

l_print-print = p_print.

ENDFORM.

*----


*

  • FORM T_SORT_BUILD *

*----


*

FORM t_sort_build USING l_sort TYPE slis_t_sortinfo_alv.

DATA: ls_sort TYPE slis_sortinfo_alv.

ls_sort-fieldname = 'CARRID'.

ls_sort-spos = 1.

ls_sort-up = 'X'.

ls_sort-subtot = 'X'.

APPEND ls_sort TO l_sort.

ENDFORM.

7 REPLIES 7
Read only

Former Member
0 Likes
1,131

Hi,

ALV OOPS Blog

/people/vijaybabu.dudla/blog/2006/07/21/topofpage-in-alv-using-clguialvgrid

Simple ALV report

http://www.sapgenie.com/abap/controls/alvgrid.htm

http://wiki.ittoolbox.com/index.php/Code:Ultimate_ALV_table_toolbox

ALV Interactive Reports

ALV Easy Reference Guide OOPS

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e8a1d690-0201-0010-b7ad-d9719a41...

ALV

1. Please give me general info on ALV.

http://www.sapfans.com/forums/viewtopic.php?t=58286

http://www.sapfans.com/forums/viewtopic.php?t=76490

http://www.sapfans.com/forums/viewtopic.php?t=20591

http://www.sapfans.com/forums/viewtopic.php?t=66305 - this one discusses which way should you use - ABAP Objects calls or simple function modules.

2. How do I program double click in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=11601

http://www.sapfans.com/forums/viewtopic.php?t=23010

Check the program in the following link:

http://sap-img.com/abap/display-secondary-list-using-alv-grid.htm

3. How do I add subtotals (I have problem to add them)...

http://www.sapfans.com/forums/viewtopic.php?t=20386

http://www.sapfans.com/forums/viewtopic.php?t=85191

http://www.sapfans.com/forums/viewtopic.php?t=88401

http://www.sapfans.com/forums/viewtopic.php?t=17335

http://www.sapdevelopment.co.uk/reporting/alv/alvgrid_basic.htm

4. How to add list heading like top-of-page in ABAP lists?

http://www.sapfans.com/forums/viewtopic.php?t=58775

http://www.sapfans.com/forums/viewtopic.php?t=60550

http://www.sapfans.com/forums/viewtopic.php?t=16629

5. How to print page number / total number of pages X/XX in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=29597 (no direct solution)

6. ALV printing problems. The favourite is: The first page shows the number of records selected but I don't need this.

http://www.sapfans.com/forums/viewtopic.php?t=64320

http://www.sapfans.com/forums/viewtopic.php?t=44477

7. How can I set the cell color in ALV?

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/snippets/coloring%2ba%2brow%2band%2bcolumn%2bin%2...

8. How do I print a logo/graphics in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=81149

http://www.sapfans.com/forums/viewtopic.php?t=35498

http://www.sapfans.com/forums/viewtopic.php?t=5013

9. How do I create and use input-enabled fields in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=84933

http://www.sapfans.com/forums/viewtopic.php?t=69878

10. How can I use ALV for reports that are going to be run in background?

http://www.sapfans.com/forums/viewtopic.php?t=83243

http://www.sapfans.com/forums/viewtopic.php?t=19224

11. How can I display an icon in ALV? (Common requirement is traffic light icon).

http://www.sapfans.com/forums/viewtopic.php?t=79424

http://www.sapfans.com/forums/viewtopic.php?t=24512

12. How can I display a checkbox in ALV?

http://www.sapfans.com/forums/viewtopic.php?t=88376

http://www.sapfans.com/forums/viewtopic.php?t=40968

http://www.sapfans.com/forums/viewtopic.php?t=6919

13. Top-of-page in ALV

14. ALV Group Heading

http://www.sap-img.com/fu037.htm

How to add list heading like top-of-page in ABAP lists?

http://www.sapfans.com/forums/viewtopic.php?t=58775

http://www.sapfans.com/forums/viewtopic.php?t=60550

http://www.sapfans.com/forums/viewtopic.php?t=16629

15. ALV output to PDF conversion

It has an example code for PDF Conversion.

http://www.erpgenie.com/abap/code/abap51.htm

Go thru these programs they may help u to try on some hands on

ALV Demo program

BCALV_DEMO_HTML

BCALV_FULLSCREEN_DEMO ALV Demo: Fullscreen Mode

BCALV_FULLSCREEN_DEMO_CLASSIC ALV demo: Fullscreen mode

BCALV_GRID_DEMO Simple ALV Control Call Demo Program

BCALV_TREE_DEMO Demo for ALV tree control

BCALV_TREE_SIMPLE_DEMO

BC_ALV_DEMO_HTML_D0100

Using ALV, We can have three types of reports:

1. Simple Report

2. Block Report

3. Hierarchical Sequential Report

There are some function modules which will enable to produce the above reports without much effort.

All the definitions of internal tables, structures and constants are declared in a type-pool called SLIS.

1. SIMPLE REPORT.

The important function modules are:

A. Reuse_alv_list_display

B. Reuse_alv_fieldcatalog_merge

C. Reuse_alv_events_get

D. Reuse_alv_commentary_write

E. Reuse_alv_grid_display

A. REUSE_ALV_LIST_DISPLAY

This is the function module which prints the data.

The important parameters are :

I. Export :

i. I_callback_program : report id

ii. I_callback_pf_status_set : routine where a user can set his own pf status or change the functionality of the existing pf status

iii. I_callback_user_command : routine where the function codes are handled

iv. I_structure name : name of the dictionary table

v. Is_layout : structure to set the layout of the report

vi. It_fieldcat : internal table with the list of all fields and their attributes which are to be printed (this table can be populated automatically by the function module REUSE_ALV_FIELDCATALOG_MERGE

vii. It_events : internal table with a list of all possible events of ALV and their corresponding form names.

II. Tables :

i. t_outtab : internal table with the data to be output

B. REUSE_ALV_FIELDCATALOG_MERGE:

This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.

The important Parameters are:

I. Export:

i. I_program_name : report id

ii. I_internal_tabname : the internal output table

iii. I_inclname : include or the report name where all the dynamic forms are handled.

II Changing

ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is

declared in the type pool SLIS.

C. REUSE_ALV_EVENTS_GET:

Returns table of possible events for a list type

Parameters :

I. Import:

Et_Events: The event table is returned with all possible CALLBACK events

for the specified list type (column 'NAME'). For events to be processed by Callback, their 'FORM' field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field 'FORM' filled and the entry modified using constants from the type pool SALV.

II. Export:

I_List_type:

0 = simple list REUSE_ALV_LIST_DISPLAY

1 = hierarchcal-sequential list REUSE_ALV_HIERSEQ_LIST_DISPLAY

2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND

3 = hierarchical-sequential block list

REUSE_ALV_BLOCK_LIST_HS_APPEND

D. REUSE_ALV_COMMENTARY_WRITE:

This is used in the Top-of-page event to print the headings and other comments for the list.

Parameters :

I. it_list_commentary : internal table with the headings of the type slis_t_listheader.

This internal table has three fields :

Typ : ‘H’ – header, ‘S’ – selection , ‘A’ - action

Key : only when typ is ‘S’.

Info : the text to be printed

E. REUSE_ALV_GRID_DISPLAY:

A new function in 4.6 version, to display the results in grid rather than as a preview.

Parameters : same as reuse_alv_list_display

This is an example for simple list.

2. BLOCK REPORT

This is used to have multiple lists continuously.

The important functions used in this report are:

A. REUSE_ALV_BLOCK_LIST_INIT

B. REUSE_ALV_BLOCK_LIST_APPEND

C. REUSE_ALV_BLOCK_LIST_HS_APPEND

D. REUSE_ALV_BLOCK_LIST_DISPLAY

A. REUSE_ALV_BLOCK_LIST_INIT

This function module is used to set the default gui status etc.

Parameters:

I. I_CALLBACK_PROGRAM

II. I_CALLBACK_PF_STATUS_SET

III. I_CALLBACK_USER_COMMAND

B. REUSE_ALV_BLOCK_LIST_APPEND

This function module adds the data to the block.

Repeat this function for all the different blocks to be displayed one after the other.

Parameters :

Export :

I. is_layout : layout settings for block

II. it_fieldcat : field catalog

III. i_tabname : internal table name with output data

IV. it_events : internal table with all possible events

Tables :

i. t_outtab : internal table with output data.

C. REUSE_ALV_BLOCK_LIST_HS_APPEND

This function module is used for hierarchical sequential blocks.

D. REUSE_ALV_BLOCK_LIST_DISPLAY

This function module display the list with data appended by the above function.

Parameters : All the parameters are optional.

Here the functions REUSE_ALV_FIELDCATALOG_MERGE, REUSE_ALV_EVENTS_GET, REUSE_ALV_COMMENTARY_WRITE can be used.

3. Hierarchical Reports:

Hierarchical sequential list output.

The function module is

A. REUSE_ALV_HIERSEQ_LIST_DISPLAY

Parameters:

I. Export:

i. I_CALLBACK_PROGRAM

ii. I_CALLBACK_PF_STATUS_SET

iii. I_CALLBACK_USER_COMMAND

iv. IS_LAYOUT

v. IT_FIELDCAT

vi. IT_EVENTS

vii. i_tabname_header : Name of the internal table in the program containing the

output data of the highest hierarchy level.

viii. i_tabname_item : Name of the internal table in the program containing the

output data of the lowest hierarchy level.

ix. is_keyinfo : This structure contains the header and item table field

names which link the two tables (shared key).

II. Tables

i. t_outtab_header : Header table with data to be output

ii. t_outtab_item : Name of the internal table in the program containing the

output data of the lowest hierarchy level.

slis_t_fieldcat_alv : This internal table contains the field attributes. This internal table can be populated automatically by using ‘REUSE_ALV_FIELDCATALOG_MERGE’.

Important Attributes :

A. col_pos : position of the column

B. fieldname : internal fieldname

C. tabname : internal table name

D. ref_fieldname : fieldname (dictionary)

E. ref_tabname : table (dictionary)

F. key(1) : column with key-color

G. icon(1) : icon

H. symbol(1) : symbol

I. checkbox(1) : checkbox

J. just(1) : (R)ight (L)eft (C)ent.

K. do_sum(1) : sum up

L. no_out(1) : (O)blig.(X)no out

M. outputlen : output length

N. seltext_l : long key word

O. seltext_m : middle key word

P. seltext_s : short key word

Q. reptext_ddic : heading (ddic)

R. ddictxt(1) : (S)hort (M)iddle (L)ong

S. datatype : datatype

T. hotspot(1) : hotspot

Regards,

Satish

Read only

Former Member
0 Likes
1,131

Hi,

Field catelog is nothig but the properties of the columns of ALV.

Rgds,

Bujji

Read only

Former Member
0 Likes
1,131

Hi...

Go to SE37 Transaction.

Give the function module name as REUSE_ALV_LIST_DISPLAY ..

Click on Display.

Then go to the IMPORT Tab.

In the import parameters you can find IT_FIELDCAT..

CLick on the Last column which is having a green indicator on it..

It gives u the entire information about fieldcatalog.

Regards,

Sai Ramesh

Read only

Former Member
0 Likes
1,132

ALV (ABAP LIST VIEWER)

Sap provides a set of ALV (ABAP LIST VIEWER) function modules, which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length. In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain upto 90 columns in the display with the wide array of display options.

The commonly used ALV functions used for this purpose are;

1. REUSE_ALV_VARIANT_DEFAULT_GET

2. REUSE_ALV_VARIANT_F4

3. REUSE_ALV_VARIANT_EXISTENCE

4. REUSE_ALV_EVENTS_GET

5. REUSE_ALV_COMMENTARY_WRITE

6. REUSE_ALV_FIELDCATALOG_MERGE

7. REUSE_ALV_LIST_DISPLAY

8. REUSE_ALV_GRID_DISPLAY

9. REUSE_ALV_POPUP_TO_SELECT

The different steps used for getting the above function modules into use are:

Step 1

DATA DECLARATION

Sap standard type pools: SLIS, KKBLO.

Sap standard tables types taken from the type pools are: SLIS_LAYOUT_ALV,

SLIS_T_FIELDCAT_ALV,

SLIS_T_LISTHEADER,

SLIS_T_EVENT,

SLIS_SELFIELD.

Internal tables to used in the program declared based on the above table types

DATA: I_LAYOUT TYPE SLIS_LAYOUT_ALV,

I_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,

I_HEADING TYPE SLIS_T_LISTHEADER,

I_EVENTS TYPE SLIS_T_EVENT.

TYPES: KKBLO_SELFIELD TYPE SLIS_SELFIELD.

Step 2 (Optional)

SELECTING THE VARIANTS FOR INITIAL LIST DISPLAY (DEFAULT VARIANT)

The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.

The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.

Sample code:

CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'

EXPORTING

i_save = variant save condition (A=all, U = user-specific)

CHANGING

cs_variant = internal table containing the program name (and the default variant---optional)

EXCEPTIONS

not_found = 2.

The user can also choose from the list of existing variants using the function module ‘REUSE_ALV_VARIANT_F4’.

Step 3

DEFININING OUTPUT CHARACTERISTICS: PREPARING DISPLAY FIELDS CATALOG

A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV. Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields).

A field catalog is required for every ALV list output to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.

The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module.

The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.

A field catalog need not be built-up and passed explicitly only under the following conditions:

1. The internal table to be output has the same structure as a Data Dictionary structure, which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.

2. All fields in this structure are to be output

3. The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.

All the values entered in the catalog are specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.

The different possible attributes are:

· Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.

Value set: 0, 1 – 3

· Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display. The parameter specifies the relative column position of the field in the list output. The user can change the column order interactively. If this parameter is initial for all field catalog entries, columns appear in the internal table field sequence.

Value set: 0, 1 – 60

· Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.

Value set: internal output table field name (required parameter)

· Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.

Value set: SPACE, internal output table name.

· Ref_fieldname (reference field name): Name of the Data Dictionary field referred to. This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.

Value set: SPACE, Data Dictionary field name.

· Ref_tabname (reference table/structure field name): Structure or table name of the referred Data Dictionary field. This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).

Value set: SPACE, name of a Data Dictionary structure or table

Link to currency unit

· Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.

Value set: SPACE, output table field name

· Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.

Value set: SPACE, output table field name.

Link to measurement unit

· Qfieldname (measurement unit field name): Only relevant for quantity columns with unit link. Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME. The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.

Value set: SPACE, output table field name.

· Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.

Value set: SPACE, output table field name.

· Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. For fields with a Data Dictionary link this parameter can be left initial. For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).

Initial = column width is the output length of the referred Data Dictionary field (domain).

N = column width is n characters.

Value set: 0 (initial), n.

· Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.

If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.

'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.

Value set: SPACE, 'X'.

· Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field can be hidden interactively.

The user cannot change the key column sequence interactively. The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.

Value set: SPACE, 'X'.

· No_out (field in field list): This parameter is used to remove certain fields from the output during initial display. The user can however interactively choose the field for output from the field list in the display variant.

'X' = field is not displayed in the current list.

Value set: SPACE, 'X'.

· Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.

'X' = technical field.

Value set: SPACE, 'X'.

· Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.

Value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off ,'1'=on).

'X' = column is colored with the default column highlight color.

'Cxyz' = column is colored with a coded color:

- C: Color (coding must begin with C)

- X: color number

- Y: bold

- Z: inverse

· Hotspot (column as hotspot): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.

Value set: SPACE, 'X'.

'X' = column cells are output as hotspots.

· Fix_column (fix column): This parameter is used to fix certain columns in the output. All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively.

Value set: SPACE, 'X'.

'X' = column fixed (does not scroll horizontally).

· Do_sum (sum over column): the user can also call this function interactively.

Value set: SPACE, 'X'.

'X' = a sum is calculated over this internal output table field.

· No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.

Value set: SPACE, 'X'.

· Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.

Value set: SPACE, 'X'.

'X' = column contents to be output as an icon.

· Symbol: The internal output table column must be a valid symbol character.

Value set: SPACE, 'X'

'X' = column contents are to be output as a symbol.

· Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.

Value set: SPACE, 'R', 'L', and ‘C’.

' ' = Default justification for this data type

'R' = right-justified output

'L' = left-justified output

'C' = centered output.

· Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.

Value set: SPACE, 'X'.

'X' = output with leading zeros.

· No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the value fields.

Value set: SPACE, 'X'.

'X' = value output without +/ sign.

· No_zero (suppress zeros): Only relevant for value fields.

Value set: SPACE, 'X'.

'X' = suppress zeros.

· Edit_mask (field formatting): To apply the report output formatting options same as in the WRITE statement in report writing.

Value set: SPACE, template.

The following parameters are used for customizing the texts in the heading of the output of the columns. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored.

If the user changes the column width interactively, the column header text with the appropriate length is always used.

The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.

The 'long field label' is also used in display variant definition,

Sort, etc. Popup.

· Seltext_l (long field label)

· Seltext_m (medium field label)

· Seltext_s (short field label)

· Reptext_ddic (header) Analogous to the Data element main header

· Ddictxt (specify text): You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.

Value set: SPACE, 'L', 'M', and ‘S’.

Sample code:

Suppose I_PO_DETAILS is an internal table containing two fields EBELN (PO number) and EBELP (PO item no).

DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV. “Local variable to hold the parameters

for a particular field of the field catalog

CLEAR L_FIELDCAT.

L_FIELDCAT-TABNAME = 'I_PO_DETAILS'.

L_FIELDCAT-FIELDNAME = 'EBELN'.

L_FIELDCAT-KEY = 'X'. “The PO no is made the key field,

“Colored and non scrollable

L_FIELDCAT-HOTSPOT = 'X'. “The po no becomes a hotspot

L_FIELDCAT-SELTEXT_S = ‘P.O No’.

L_FIELDCAT-SELTEXT_M = 'P order No'.

L_FIELDCAT-SELTEXT_L = 'Purchase order No'.

APPEND L_FIELDCAT TO I_FIELDTAB.

CLEAR L_FIELDCAT

L_FIELDCAT-TABNAME = 'I_PO_DETAILS'.

L_FIELDCAT-FIELDNAME = 'EBELN'.

L_FIELDCAT-KEY = 'X'. “The po item no is made the key field,

“Colored and non scrollable

L_FIELDCAT-SELTEXT_S = 'Item No'.

L_FIELDCAT-SELTEXT_M = 'Item No`.

L_FIELDCAT-SELTEXT_L = 'PO Item No'.

APPEND L_FIELDCAT TO I_FIELDTAB.

CLEAR L_FIELDCAT

Thus the catalog for the report output is prepared.

Step 4

The next step is to build an event table, which are used for firing both user commands and the system dependent events i.e. top of page, end of page etc.

A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.

The function module contains following import and export parameters.

IMPORTING PARAMETERS: I_LIST_TYPE

This parameter has possible values from 0-4.

The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0.

EXPORTING PARAMETERS: I_EVENTS table.

This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events.

The table structure contains the fields:

I_EVENTS-NAME: Name of the Callback event.

I_EVENTS-FORM: Name of the form routine that should be called in the calling program at the event.

Only events with a form routine name are processed.

The I_EVENTS table returns with the following possible constants:

1. Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.

Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.

2. Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.

RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.

RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table.

RS_SELFIELD is initial in this case.

3. Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.

Is called at the beginning of the function module to make special settings. It is not usually used.

4. Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.

As this is a frequently-used Callback event, the form routine can also be passed directly in the interface by passing the user command in the IMPORTING parameter I_CALLBACK_USER_COMMAND.

5. Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

Equivalent to the list processing TOP-OF-PAGE event.

6. Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.

The selection information and list status are output together (if they exist) on a separate page by default

7. Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.

Analogously to TOP_OF_COVERPAGE the user can add other information

to the information output by ALV (selection information, list status) at this event.

8. Slis_ev_foreign_top_of_page TYPE slis_formname VALUE ‘FOREIGN_TOP_OF_PAGE'.

The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).

In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.

9. Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.

The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).

In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.

10. Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.

If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).

The STANDARD status of the function group SALV should be used as a template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.

11. Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.

LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME

R_INDEX LIKE SY-TABIX

R_INDEX_ITEM LIKE SY-TABIX

R_INDEX_SUM LIKE SY-TABIX.

12. Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.

Information output at the start of the list

13. Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.

Information output at the end of a page. This is only called for printing.

14. Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.

Information output at the end of the list

15. Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.

Output information after each output line. Should only be used in justified cases because it costs a lot of performance.

16. Slis_ev_before_line_output TYPE slis_formname VALUE 'BEFORE_LINE_OUTPUT'.

Output information before each output line. Should only be used in justified cases because it costs a lot of performance.

17. Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.

This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.

Sample code :

FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',

FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE', FORMNAME_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND'.

DATA: L_I_EVENT TYPE SLIS_ALV_EVENT.

CALL FUNCTION 'REUSE_ALV_EVENTS_GET'

EXPORTING

I_LIST_TYPE = 0

IMPORTING

ET_EVENTS = I_EVENTS.

READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE

INTO L_I_EVENT.

IF SY-SUBRC = 0.

MOVE FORMNAME_TOP_OF_PAGE TO L_I_EVENT-FORM.

APPEND L_I_EVENT TO I_EVENTS.

ENDIF.

READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE

INTO L_I_EVENT.

IF SY-SUBRC = 0.

MOVE FORMNAME_END_OF_PAGE TO L_I_EVENT-FORM.

APPEND L_I_EVENT TO I_EVENTS.

ENDIF.

CLEAR L_I_EVENT.

READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND

INTO L_I_EVENT.

IF SY-SUBRC = 0.

MOVE FORMNAME_USER_COMMAND TO L_I_EVENT-FORM.

APPEND L_I_EVENT TO I_EVENTS.

ENDIF.

This will prepare the events table for the report.

The report will contain three forms for the above events:

1. FORM TOP_OF_PAGE : This form will contain the top of page event for the report i.e header etc

Using the function module ‘REUSE_ALV_COMMENTARY_WRITE’, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.

2. FORM END_OF_PAGE : This form will contain the end of page event for the report i.e footer etc

3. FORM USER_COMMAND : This form will contain the desired user command i.e pick/line selection

Step 5

A layout is build for the report output list description USING the internal table declared above (I_LAYOUT).

Output list description structure.

The parameters are described under the following heads:

· Display options

· Exceptions

· Totals

· Interaction

· Detail screen

· Display variants (only for hierarchical-sequential lists)

· Color

· Other

The layout table is of type slis_layout_alv_spec and has the following fields:

Display options

1. Colwidth_optimize (1) TYPE c: This parameter optimizes the length of the different columns in the output. The width of the different col. now depends on the max. Length of the data in the column.

Value set: SPACE, 'X'

'X' = optimizes the column width so that all contents are displayed completely.

2. No_colhead(1) TYPE c : This parameter suppresses the column headings

Value set: SPACE, 'X'.

'X' = column headers are not output

3. No_hotspot(1) TYPE c : The heading of the report output are not output as hotspot.

Value set: SPACE, 'X'.

'X' = column headers are not output as hotspot

4. Zebra(1) TYPE c : The report is output in the striped pattern.

Value set: SPACE, 'X'.

'X' = striped pattern (e.g. for wide lists)

5. No_vline(1) TYPE c : The report output contains columns only separated by space and no lines. It is not relevant for: hierarchical-sequential lists and multiple-line lists.

Value set: SPACE, 'X'.

'X' = columns separated by SPACE

6. No_min_linesize(1) TYPE c : The report line size is equal to the width of the list. It is not relevant for block lists.

Value set: SPACE, 'X’.

'X' = line size depends on list width

' ' = Line size is set to 80 or MIN_LINESIZE (if > 0) .

7. Min_linesize LIKE sy-linsz: The report output contains a minimum possible length of line. If initial min_linesize is set to 80 by default, then this parameter is used to customize it. The prerequisite for this is that the parameter no_min_linesize should be ' '.

Value set: 0, 10 - 250

If the list is wider, the format uses the list width (maximum 250 or MAX_LINESIZE (if > 0)).

8. Max_linesize LIKE sy-linsz: The default max. Linesize is 250. To change this default value, this parameter can interactively-define the maximum list width setting.

Value set: 0, 80 - 1020

9. Window_titlebar LIKE rsmpe-tittext: To set the titlebar on the report output.

10. No_uline_hs(1) TYPE c.

Exceptions

11. Lights_fieldname TYPE slis_fieldname: Internal output table field containing the codes of exceptions to be output.

Output table field code: '1' = red traffic light

'2' = yellow traffic light

'3' = green traffic light Fieldname for exception

Value set: SPACE, internal output table field name.

12. Lights_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter LIGHTS_FIELDNAME. If LIGHTS_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists. Only relevant for hierarchical-sequential lists.

. Value set: SPACE, internal output table name.

13. Lights_rollname LIKE dfies-rollname: The documentation of this data element is displayed when you call F1 help for an exception column.

Value set: SPACE, data element name.

14. Lights_condense(1) TYPE c : If a list record is output with 'red traffic light', each

Subtotal that includes this record is also output with 'red traffic light'.

Value set: SPACE, 'X'

'X' = the 'maximum' exception of the items in the subtotal is output at subtotal level.

Sums

15. No_sumchoice(1) TYPE c : This parameter allows the choice for summing up

Only by fieldcatalog.

Value set: SPACE, 'X'

'X' = fields which are to be summed, passed by the calling program (FIELDCAT-DO_SUM = 'X'). The user should not be able to change this value interactively.

16. No_totalline(1) TYPE c : Removes the option of having totals after sub-totals.

Value set: SPACE, 'X'

'X' = no total record is to be output. Subtotals can still be calculated and output. The fields in the subtotals are flagged DO_SUM = 'X' in the field list.

17. No_subchoice(1) TYPE c : Does not allow the user to interactively change the field chosen for subtotals.

Value set: SPACE, 'X'

'X' = value whose change triggers subtotals, provided by the calling program. The user should not be able to change this value interactively.

18. No_subtotals(1) TYPE c : No subtotals possible

Value set: SPACE, 'X'

'X' = no subtotals.

19. Numc_sum(1) TYPE c : Totals only possible for NUMC-Fields.

20. No_unit_splitting TYPE c: No separate total lines by inh.units

21.totals_before_items TYPE c: Display totals before the items

22. Totals_only(1) TYPE c : Show only totals

Value set: SPACE, 'X'

'X' = only total records are output.

23. Totals_text(60) TYPE c : Text for 1st col. in totals

Value set: SPACE, string (max.60)

' ' = The first column in the total record contains an appropriate number of '*'s to indicate the total by default. If the first column is wide enough, the string 'Total' is output after the asterisks.

'String’ = The string passed is output after the total indicated by '*', if the column is wide enough.

24. Subtotals_text(60) TYPE c : Texts for subtotals

Value set: SPACE, string (max.60)

' ' = In the first column of subtotal records, the subtotal is indicated by an appropriate number of '*' by default. If the first column is not a subtotal criterion, the string 'Total' is output after the asterisks, if the column is wide enough.

'String’ = the string passed is output after the subtotal indicated by '*', if the column is wide enough and the first column is not a subtotal criterion. If it is a subtotal criterion, its value is repeated after the total, if the column is wide enough.

Interaction

25. Box_fieldname TYPE slis_fieldname: Fieldname for checkbox in the report output. If the list has checkboxes at the start of records (for selecting several records), this parameter contains the internal output table field name indicated by the checkbox selection column. The field is a checkbox at the start of list records without a list header.

Value set: SPACE, internal output table field name

26. Box_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter BOX_FIELDNAME. If BOX_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists.

Value set: SPACE, internal output table name.

27. Box_rollname LIKE dd03p-rollname: rollname for checkbox

28. Expand_fieldname TYPE slis_fieldname: fieldname flag ‘expand’. The user can show or hide the items by clicking on the folder symbol (hotspot). If the items for a header entry are only to be read by the calling program and passed to ALV when a header has been expanded interactively, this can be controlled via the CALLBACK event 'ITEM_DATA_EXPAND'.

29. Hotspot_fieldname TYPE slis_fieldname: Used to make the fieldname flag hotspot.

30. No_input(1) TYPE c : The fields are only display fields.

Value set: SPACE, 'X'

'X' = all ready-for-input fields in a list are displayed as not ready-for-input. (Record selection checkboxes and fields which can be made ready-for-input via the field list parameter FIELDCAT-INPUT = 'X')

31. F2code LIKE sy-ucomm: To assign an ALV standard function code to double-click (F2), assign the function code to this parameter. Ex.: to assign the ALV standard function 'Detail' ('&ETA') to F2.

=> LAYOUT-F2CODE = '&ETA'.

Value set: SPACE, function code

32. Confirmation_prompt: confirm. Prompt when leaving

Value set: SPACE, 'X'

'X' = if one of the functions ‘Back (F03)', ‘Exit (F15)' or ‘Cancel (F12)' occurs, a confirmation prompt appears.

33. Key_hotspot(1) TYPE c : The key fields are displayed as hotspot. The columns defined in the field catalog as key fields (FIELDCAT-KEY = 'X') are output as hotspots, i.e. clicking on a key column (highlighted in color in the list) calls the function under F2.

Value set: SPACE, 'X'.

34. Reprep(1) TYPE c : report report interface active.

35. Group_buttons(1) TYPE c : group-buttons for COL1 - COL5 . Group output fields via FIELDCAT-SP_GROUP in the field list, and pass the group name to the list module in the interface parameter IT_SPECIAL_GROUPS.

Value set: SPACE, 'X'.

36. No_keyfix(1) TYPE c : Used to make the key fields scrollable.

Value set: SPACE, 'X'.

' ' = The key columns defined in the field catalog by FIELDCAT-KEY = 'X' are fixed in the list output. These columns do not scroll horizontally. The item table key columns are fixed in hierarchical-sequential lists. The header table key fields are not considered here.

'X' = key columns not fixed

37. Get_selinfos(1) TYPE c : To read selection screen.

Value set: SPACE, 'X'.

If the calling program is a report with an ABAP/4 selection screen, setting this parameter makes ALV read the selection screen again. If the selections are read successfully, a pushbutton, via which the user can call a popup which lists the report selections in a simple form, becomes active on the results list output by ALV.

38. group_change_edit(1) TYPE c : Settings by user for new group

Value set: SPACE, 'X'

'X' = the user can enter a format option for each sort criterion in the sort/subtotal popup, for the list format when this value changes (e.g. new page or underline).

39. No_scrolling(1) TYPE c : Does not allow scrolling of the list to the right.

Value set: SPACE, 'X'.

40. Expand_all(1) TYPE c : Expand all positions

Detailed screen

40. Detail_popup(1) TYPE c : show detail in popup.

Value set: SPACE, 'X'

' ' = List record detail display in full-screen mode, with top-of-page.

'X' = list record detail display in popup (without top-of-page).

41. Detail_initial_lines(1) TYPE c : show also initial lines

Value set: SPACE, 'X'

' ' = Only fields whose contents are not initial are output in the detail view.

'X' = initial field contents are also output in detail.

41. detail_titlebar(30) type c : Titlebar for detail screen

Value set: SPACE, string (max.30)

` ' = ' Detail: Display' is output as the title of the detail window.

'String’ = the string passed is output as the title of the detail window.

Display variants

42. Header_text (20) TYPE c: Text for header button. Only relevant for hierarchical-sequential lists. You can toggle between display field and field list views via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.

Value set: SPACE, CHAR (20)

' ' = The header table field pushbutton text is 'Header' by default.

CHAR (20) = header table field pushbutton text.

43.item_text(20) TYPE c : Text for item button. Only relevant for hierarchical-sequential lists. You can toggle the view between the display fields and the field list via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.

Value set: SPACE, CHAR (20)

' ' = The pushbutton text for the item table fields is 'Item' by default.

CHAR (20) = item table field pushbutton text.

44.default_ item(1) TYPE c : Items as default. Only relevant for hierarchical-sequential lists.

Value set: SPACE, 'X'

' ' = The header table fields are displayed by default in the display variant definition popup. The user can switch to the item table fields interactively.

'X' = the item table fields are displayed by default in the display variant Definition Popup. The user can switch to the header table fields interactively.

Colour

45. Info_fieldname TYPE slis_fieldname: infofield for listoutput. A whole list record can be colored individually using a color code in a column of the internal output table for the record. Assign the name of the field containing the color code to this parameter.

Value set: SPACE, internal output table field name

The internal output table field must be of type CHAR(3).

The code must have the following syntax: 'Cxy':

C = color (all codes must start with 'C')

X = color number ('1'-'9')

Y = bold ('0' = off, '1' = on)

46. Coltab_fieldname TYPE slis_fieldname: Cells can be colored individually using a color code which is contained in a column of the internal output table for the record containing the cell. Assign the name of the field to this parameter.

Others

47. List_append(1) TYPE c : no call screen. It is only useful to output block-lists without specifying the above modules if the number of list blocks exceeds, or may exceed, the maximum number specified in the block module documentation. These operations are not possible for user-defined block lists.

Example code :

I_LAYOUT-f2code = ws_fcode.

I_LAYOUT-zebra = 'X'.

I_LAYOUT-colwidth_optimize = 'X'.

I_LAYOUT-no_keyfix = 'X'.

I_LAYOUT-get_selinfos = 'X'.

I_LAYOUT-no_hotspot = 'X'.

I_LAYOUT-no_input = 'X'.

I_LAYOUT-hotspot_fieldname = FIELDNAME.

I_LAYOUT-no_input = ‘X’.

I_LAYOUT-no_vline = `X’.

I_LAYOUT-no_colhead = ‘ ‘.

I_LAYOUT-lights_condense = ` `.

I_LAYOUT-totals_text = ` `.

I_LAYOUT-subtotals_text = ` `.

I_LAYOUT-totals_only = ` `.

I_LAYOUT-key_hotspot = ‘X’.

I_LAYOUT-detail_popup = ‘X’.

I_LAYOUT-group_change_edit = ‘X’.

I_LAYOUT-GROUP_BUTTONS = ‘X’.

Step 6

This step is required to get the selection screen information in the report output.

The prerequisite for this is to set the parameter LAYOUT-GET_SELINFOS of the IMPORTING structure.

The parameters to be passed in the IS_SEL_HIDE table are:

o mode: 'R' = only the entries passed in the internal table IS_SEL_HIDE-T_ENTRIES

Are output in the pop up. Selection info, which the list tool read in the selection screen (when called by a report with a selection screen), is replaced by the values passed.

'S' = the selection info which the list tool read in the selection screen of the calling report are modified by the entries in the table IS_SEL_HIDE-T_ENTRIES.

o t_entries: Selection info table

o t_entries-mode: 'A' = output the selection info for the current table record in the info popup.

'D' = do not output select option or SELNAME parameter selection info in the popup.

o t_entries-selname: (only used in t_entries-mode = 'D') : Name of the select option or parameter.

The following table fields are only used in t_entries-mode = 'A'. They contain the selection information to be added.

· t_entries-field: DDIC field name of the field for which selection information is to be output.

· t_entries-table: DDIC table names of t_entries-field.

· t_entries-stext: Field name in info popup.

· If t_entries-field and t_entries-table have been entered, this text is taken from DDIC.

· t_entries-valuf: Selection condition 'from' value (external format)

· t_entries-valut: Selection condition 'to' value (external format)

· t_entries-sign0: (I)nclusive (E)xclusive

· t_entries-option: All values of the select options Option field allowed.

Step 6

The Table IT_SORT is populated with the sort criteria for the different fields.

The caller specifies the sorting and/or subtotaling of the basic list in the internal table IT_SORT.

This internal table has the following fields:

o spos : Sort sequence

o fieldname : Internal output table field name

o tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.

o up : 'X' = sort in ascending order

o down : 'X' = sort in descending order

o subtot : 'X' = subtotal at group value change

o group : '* ' = new page at group value change ,'UL' = underline at group value change

Step 7

The final step in the output of the report is the use of two ALV functions modules.

1. REUSE_ALV_FIELDCATALOG_MERGE

2. REUSE_ALV_LIST_DISPLAY

The first function module is used to pass the field catalog to the report output and merge it with the internal output table.

FUNCTION reuse_alv_fieldcatalog_merge.

*"----

-


""Lokale Schnittstelle:

*” IMPORTING

*" VALUE(I_PROGRAM_NAME) LIKE SY-REPID OPTIONAL

*" VALUE(I_INTERNAL_TABNAME) TYPE SLIS_TABNAME OPTIONAL

*" VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL

*" VALUE(I_CLIENT_NEVER_DISPLAY) TYPE SLIS_CHAR_1

*" DEFAULT 'X'

*" VALUE(I_INCLNAME) LIKE TRDIR-NAME OPTIONAL

*" CHANGING

*" VALUE(CT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV

*" EXCEPTIONS

*" INCONSISTENT_INTERFACE

*" PROGRAM_ERROR

*"----

-


Import parameters

I_PROGRAM_NAME: Program in which the internal output table is declared and populated

I_INTERNAL_TABNAME: Internal output table name

I_STRUCTURE_NAME: Structure name (structure, table, and view)

I_CLIENT_NEVER_DISPL: Hide client fields default ‘X’

I_INCLNAME: Data declarations include name

CHANGING parameter

CT_FIELDCAT: Field catalog with field descriptions

The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:

1. Performance is affected since the code of the table definition must always be read and interpreted at runtime.

2. Dictionary reference are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.

Step 8

The other function module is used to display the internal output table with the contents

FUNCTION reuse_alv_list_display.

*"----

-


""Lokale Schnittstelle:

*” IMPORTING

*" VALUE(I_INTERFACE_CHECK) DEFAULT SPACE

*" VALUE(I_CALLBACK_PROGRAM) LIKE SY-REPID DEFAULT SPACE

*" VALUE(I_CALLBACK_PF_STATUS_SET) TYPE SLIS_FORMNAME

*" DEFAULT SPACE

*" VALUE(I_CALLBACK_USER_COMMAND) TYPE SLIS_FORMNAME

*" DEFAULT SPACE

*" VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL

*" VALUE(IS_LAYOUT) TYPE SLIS_LAYOUT_ALV OPTIONAL

*" VALUE(IT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV OPTIONAL

*" VALUE(IT_EXCLUDING) TYPE SLIS_T_EXTAB OPTIONAL

*" VALUE(IT_SPECIAL_GROUPS) TYPE SLIS_T_SP_GROUP_ALV

*" OPTIONAL

*" VALUE(IT_SORT) TYPE SLIS_T_SORTINFO_ALV OPTIONAL

*" VALUE(IT_FILTER) TYPE SLIS_T_FILTER_ALV OPTIONAL

*" VALUE(IS_SEL_HIDE) TYPE SLIS_SEL_HIDE_ALV OPTIONAL

*" VALUE(I_DEFAULT) DEFAULT 'X'

" VALUE(I_SAVE) DEFAULT SPACE

" VALUE(IS_VARIANT) LIKE DISVARIANT

" STRUCTURE DISVARIANT DEFAULT SPACE

" VALUE(IT_EVENTS) TYPE SLIS_T_EVENT OPTIONAL

" VALUE(IT_EVENT_EXIT) TYPE SLIS_T_EVENT_EXIT OPTIONAL

" VALUE(IS_PRINT) TYPE SLIS_PRINT_ALV OPTIONAL

" VALUE(IS_REPREP_ID) TYPE SLIS_REPREP_ID OPTIONAL

" VALUE(I_SCREEN_START_COLUMN) DEFAULT 0

" VALUE(I_SCREEN_START_LINE) DEFAULT 0

" VALUE(I_SCREEN_END_COLUMN) DEFAULT 0

" VALUE(I_SCREEN_END_LINE) DEFAULT 0

" EXPORTING

" VALUE(E_EXIT_CAUSED_BY_CALLER)

" VALUE(ES_EXIT_CAUSED_BY_USER) TYPE SLIS_EXIT_BY_USER

" TABLES

" T_OUTTAB

" EXCEPTIONS

" PROGRAM_ERROR

Import parameters

I_INTERFACE_CHECK: Interface consistency check log output.

I_CALLBACK_PROGRAM: Name of the calling program

I_CALLBACK_PF_STATUS_SET: Set EXIT routine to status.

I_CALLBACK_USER_COMMAND: EXIT routine for command handling

I_STRUCTURE_NAME: Internal output table structure name

IS_LAYOUT: List layout specifications

IT_FIELDCAT: Field catalog with field descriptions

IT_EXCLUDING: Table of inactive function codes

IT_SPECIAL_GROUPS: Grouping fields for column selection

IT_SORT: Sort criteria for first list display

IT_FILTER: Filter criteria for first list output

IS_SEL_HIDE : Selection information modification

I_DEFAULT: Initial variant active/inactive logic

I_SAVE: Variants can be saved

IS_VARIANT : Variant information

IT_EVENTS: Table of events to perform

IT_EVENT_EXIT : Standard fcode exit requests table

IS_PRINT: Print information

IS_REPREP_ID: Initialization keys for Re/Re interface

I_SCREEN_START_COLUMN: Coordinates for list in dialog box

I_SCREEN_START_LINE: Coordinates for list in dialog box

I_SCREEN_END_COLUMN: Coordinates for list in dialog box

I_SCREEN_END_LINE: Coordinates for list in dialog box

IT_EVENT_EXIT: Standard fcode exit requests table

IS_PRINT: Print information

IS_REPREP_ID: Initialization keys for Re/Re interface

I_SCREEN_START_COLUMN: Coordinates for list in dialog box

I_SCREEN_START_LINE: Coordinates for list in dialog box

I_SCREEN_END_COLUMN: Coordinates for list in dialog box

I_SCREEN_END_LINE: Coordinates for list in dialog box

Export parameters

E_EXIT_CAUSED_BY_CALLER: Delete list in CALLBACK_USER_COMMAND

ES_EXIT_CAUSED_BY_USER: How the user left the list Tables

T_OUTTAB: Table with data to be displayed ---mandatory

Example Code

WS_REPNAME = SY-REPID.

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING

I_PROGRAM_NAME = WS_REPNAME

I_INTERNAL_TABNAME = Internal output table field name

I_INCLNAME = WS_REPNAME

CHANGING

CT_FIELDCAT = I_FIELDTAB.

IF SY-SUBRC <> 0.

WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_FIELDCATALOG_MERGE'.

ENDIF.

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

EXPORTING

I_CALLBACK_PROGRAM = WS_REPNAME

I_STRUCTURE_NAME = Internal output table field name

IS_LAYOUT = I_LAYOUT

IT_FIELDCAT = I_FIELDTAB

I_DEFAULT = 'A'

I_SAVE = 'A'

IS_VARIANT = 'X'

IT_EVENTS = I_EVENTS[]

IT_SORT = I_SORT

IS_SEL_HIDE = I_SELINFO

TABLES

T_OUTTAB = Internal output table field name.

IF SY-SUBRC <> 0.

WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_LIST_DISPLAY'.

ENDIF

THIS IS THE POP UP TO ALLOW THE USER TO DYNAMICALLY SELECT THE FIELDS FOR DISPLAY. HE CAN CHOOSE FROM THIS FIELDS ACC. TO REQUIREMENT AND HIDE THE OTHER FIELDS

Example report output based prior to selection of the field

THE USER HAS HIDDEN SOME OF THE FIELD FROM THE TOTAL FIELDS TO CUSTOMIZE THE REPORT OUTPUT

Example report output after hiding some of the fields

USER CAN CHOOSE A PARTICULAR SET OF FIELD FROM THE OUTPUT AND CAN SAVE IT AS VARIANTS

Using other function module 'REUSE_ALV_GRID_DISPLAY’ can help us get list output in the form of a grid and also attach logos to the report output.

Sample code

1 Simple list output:

REPORT Y_DEMO_ALV NO STANDARD PAGE HEADING.

*

  • Data to be displayed

DATA: I_SFLIGHT TYPE TABLE OF SFLIGHT.

*----


*

  • Selection

SELECT * FROM SFLIGHT INTO TABLE I_SFLIGHT.

  • Call ABAP List Viewer (ALV)

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

EXPORTING

I_STRUCTURE_NAME = 'SFLIGHT'

TABLES

T_OUTTAB = I_SFLIGHT.

2.Simple grid output:

REPORT Y_DEMO_ALV_1.

*

  • Data to be displayed

DATA: I_SFLIGHT TYPE TABLE OF SFLIGHT.

*----


*

  • Selection

SELECT * FROM SFLIGHT INTO TABLE I_SFLIGHT.

  • Call ABAP List Viewer (ALV)

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

I_STRUCTURE_NAME = 'SFLIGHT'

TABLES

T_OUTTAB = I_SFLIGHT.

3. Demo for 'REUSE_ALV_POPUP_TO_SELECT'

REPORT y_demo_alv_3.

TYPE-POOLS: slis.

DATA: BEGIN OF i_outtab OCCURS 0.

INCLUDE STRUCTURE sflight.

DATA: w_chk TYPE c. "For multiple selection

DATA: END OF i_outtab.

  • I_OUTTAB TYPE SFLIGHT OCCURS 0,

DATA: i_private TYPE slis_data_caller_exit,

i_selfield TYPE slis_selfield,

W_exit(1) TYPE c.

PARAMETERS: p_title TYPE sy-title.

*

START-OF-SELECTION.

SELECT * FROM sflight INTO TABLE i_outtab.

CALL FUNCTION 'REUSE_ALV_POPUP_TO_SELECT'

EXPORTING

i_title = p_title

i_selection = 'X'

i_zebra = 'X'

  • I_SCREEN_START_COLUMN = 0

  • I_SCREEN_START_LINE = 0

  • I_SCREEN_END_COLUMN = 0

  • I_SCREEN_END_LINE = 0

i_checkbox_fieldname = 'W_CHK'

  • I_LINEMARK_FIELDNAME =

  • I_SCROLL_TO_SEL_LINE = 'X'

i_tabname = 'I_OUTTAB'

i_structure_name = 'SFLIGHT'

  • IT_FIELDCAT =

  • IT_EXCLUDING =

  • I_CALLBACK_PROGRAM =

  • I_CALLBACK_USER_COMMAND =

  • IS_PRIVATE = I_PRIVATE

IMPORTING

es_selfield = i_selfield

e_exit = w_exit

TABLES

t_outtab = i_outtab

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

  • MESSAGE i000(0k) WITH sy-subrc.

ENDIF.

*****the internal table is modified with a cross sign for marking the

***rows selected

LOOP AT i_outtab WHERE w_chk = 'X'.

WRITE: / i_outtab-carrid, i_outtab-price.

ENDLOOP.

4. Demo for ALV output using field catalog and layout:

REPORT y_demo_alv NO STANDARD PAGE HEADING.

  • ALV related data declaration

TYPE-POOLS: slis.

  • DB-Table

TABLES sflight.

  • Includes

INCLUDE .

*

CONSTANTS:

c_formname_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

DATA: i_fieldcat TYPE slis_t_fieldcat_alv,

i_layout TYPE slis_layout_alv,

i_sp_group TYPE slis_t_sp_group_alv,

i_events TYPE slis_t_event,

i_print TYPE slis_print_alv,

i_sort TYPE slis_t_sortinfo_alv.

*internal table for data to be displayed

DATA: BEGIN OF i_sflight OCCURS 0.

INCLUDE STRUCTURE sflight.

DATA: box,

lights.

DATA: END OF i_sflight.

*

DATA: w_repid LIKE sy-repid.

DATA: i_list_top_of_page TYPE slis_t_listheader.

  • Report Selections

SELECT-OPTIONS s_carrid FOR sflight-carrid.

SELECT-OPTIONS s_connid FOR sflight-connid.

SELECT-OPTIONS s_fldate FOR sflight-fldate.

*SELECTION-SCREEN SKIP 1.

  • Parameters

PARAMETERS: p_maxrow TYPE i DEFAULT 30."to limit the selection

SELECTION-SCREEN SKIP 1.

  • Variant for ALV display

SELECTION-SCREEN BEGIN OF BLOCK 0 WITH FRAME TITLE text-000.

PARAMETERS: p_varnt LIKE disvariant-variant.

SELECTION-SCREEN END OF BLOCK 0.

  • Layout of the report display

SELECTION-SCREEN BEGIN OF BLOCK a WITH FRAME TITLE text-001.

PARAMETERS: p_zebra AS CHECKBOX DEFAULT ' ', "Striped pattern

p_nocolh AS CHECKBOX DEFAULT ' ', "No column heading

p_novlin AS CHECKBOX DEFAULT ' ', "No vertical lines

p_colopt AS CHECKBOX DEFAULT ' ', "Optimizes col. wd

p_keyhot AS CHECKBOX DEFAULT ' ', "Key fields hot

p_noinpt AS CHECKBOX DEFAULT ' '. "No field for input

SELECTION-SCREEN END OF BLOCK a.

SELECTION-SCREEN BEGIN OF BLOCK b WITH FRAME TITLE text-002.

PARAMETERS: p_lights AS CHECKBOX DEFAULT 'X',

p_lightc AS CHECKBOX DEFAULT 'X'.

SELECTION-SCREEN END OF BLOCK b.

SELECTION-SCREEN BEGIN OF BLOCK c WITH FRAME TITLE text-003.

PARAMETERS: p_totonl AS CHECKBOX DEFAULT ' ',

p_totext(60),

p_sttext(60).

SELECTION-SCREEN END OF BLOCK c.

SELECTION-SCREEN BEGIN OF BLOCK d WITH FRAME TITLE text-004.

PARAMETERS: p_chkbox AS CHECKBOX DEFAULT 'X',

p_detpop AS CHECKBOX DEFAULT 'X',

p_groupb AS CHECKBOX DEFAULT ' ',

p_groups AS CHECKBOX DEFAULT ' '.

SELECTION-SCREEN END OF BLOCK d.

SELECTION-SCREEN BEGIN OF BLOCK e WITH FRAME TITLE text-005.

PARAMETERS: p_print AS CHECKBOX DEFAULT ' ',

p_nosinf AS CHECKBOX DEFAULT ' ',

p_nocove AS CHECKBOX DEFAULT ' ',

p_nonewp AS CHECKBOX DEFAULT ' ',

p_nolinf AS CHECKBOX DEFAULT ' ',

p_reserv TYPE i.

SELECTION-SCREEN END OF BLOCK e.

DATA: w_boxnam TYPE slis_fieldname VALUE 'BOX',

w_f2code LIKE sy-ucomm VALUE '&ETA',

w_lignam TYPE slis_fieldname VALUE 'LIGHTS',

w_save(1) TYPE c,

w_default(1) TYPE c,

w_exit(1) TYPE c,

i_variant LIKE disvariant,

i_variant1 LIKE disvariant.

*----


*

INITIALIZATION.

w_repid = sy-repid.

PERFORM fieldcat_init USING i_fieldcat.

PERFORM eventtab_build USING i_events.

PERFORM comment_build USING i_list_top_of_page.

PERFORM sp_group_build USING i_sp_group.

PERFORM t_sort_build USING i_sort.

  • Set Options: save variant userspecific or general

        • 'A or 'U' are for user-specific variants list

        • 'X' or 'space' for general

w_save = 'A'.

PERFORM variant_init.

  • Get default variant

i_variant1 = i_variant.

CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'

EXPORTING

i_save = w_save

CHANGING

cs_variant = i_variant1

EXCEPTIONS

not_found = 2.

IF sy-subrc = 0.

p_varnt = i_variant1-variant.

ENDIF.

  • Process on value request (list of possible variants)

AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_varnt.

PERFORM f4_for_variant.

  • PAI

AT SELECTION-SCREEN.

PERFORM pai_of_selection_screen.

START-OF-SELECTION.

PERFORM selection.

END-OF-SELECTION.

PERFORM layout_build USING i_layout. "wg. Parameters

PERFORM print_build USING i_print. "wg. Parameters

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'

EXPORTING

i_program_name = w_repid

  • i_internal_tabname = 'I_SFLIGHT'

i_structure_name = 'SFLIGHT'

i_client_never_display = 'X'

i_inclname = w_repid

CHANGING

ct_fieldcat = i_fieldcat[]

EXCEPTIONS

inconsistent_interface = 1

program_error = 2

OTHERS = 3.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

  • Call ABAP/4 List Viewer

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'

EXPORTING

  • I_INTERFACE_CHECK = ' '

i_callback_program = w_repid

  • 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 = 'SFLIGHT'

i_background_id = 'ALV_BACKGROUND'

  • I_GRID_TITLE =

  • I_GRID_SETTINGS =

is_layout = i_layout

it_fieldcat = i_fieldcat[]

  • IT_EXCLUDING =

it_special_groups = i_sp_group[]

it_sort = i_sort[]

  • IT_FILTER =

  • IS_SEL_HIDE =

  • I_DEFAULT = 'X'

i_save = w_save

is_variant = i_variant

it_events = i_events[]

  • IT_EVENT_EXIT =

is_print = i_print

  • IS_REPREP_ID =

  • I_SCREEN_START_COLUMN = 0

  • I_SCREEN_START_LINE = 0

  • I_SCREEN_END_COLUMN = 0

  • I_SCREEN_END_LINE = 0

  • IMPORTING

  • E_EXIT_CAUSED_BY_CALLER =

  • ES_EXIT_CAUSED_BY_USER =

TABLES

t_outtab = i_sflight

EXCEPTIONS

program_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

  • MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

  • WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

  • CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'

  • EXPORTING

  • i_callback_program = w_repid

  • i_structure_name = 'SFLIGHT'

  • is_layout = i_layout

  • it_fieldcat = i_fieldcat[]

    • IT_EXCLUDING =

  • it_special_groups = i_sp_group[]

  • it_sort = i_sort[]

    • IT_FILTER =

    • IS_SEL_HIDE =

    • i_default = W_DEFAULT

  • i_save = w_save

  • is_variant = i_variant

  • it_events = i_events[]

    • IT_EVENT_EXIT =

  • is_print = i_print

    • I_SCREEN_START_COLUMN = 0

    • I_SCREEN_START_LINE = 0

    • I_SCREEN_END_COLUMN = 0

    • I_SCREEN_END_LINE = 0

    • IMPORTING

    • E_EXIT_CAUSED_BY_CALLER =

  • TABLES

  • t_outtab = i_sflight.

*----


*

  • FORM FIELDCAT_INIT *

*----


*

  • --> L_FIELDCAT *

*----


*

FORM fieldcat_init USING l_fieldcat TYPE slis_t_fieldcat_alv.

DATA: ls_fieldcat TYPE slis_fieldcat_alv.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'SEATSOCC'.

*The field is not displayed in the initial output, can be interactively

  • chosen for display

ls_fieldcat-no_out = 'X'.

*This field is assigned to a special group with tech. key 'A' and can be

*displayed using the special group buttons

ls_fieldcat-sp_group = 'A'.

*The field cannot be summed irrespective of its data type

ls_fieldcat-no_sum = 'X'.

APPEND ls_fieldcat TO l_fieldcat.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'SEATSMAX'.

ls_fieldcat-no_out = 'X'.

ls_fieldcat-sp_group = 'A'.

APPEND ls_fieldcat TO l_fieldcat.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'PRICE'.

ls_fieldcat-no_out = 'X'.

ls_fieldcat-sp_group = 'B'.

APPEND ls_fieldcat TO l_fieldcat.

*

CLEAR ls_fieldcat.

ls_fieldcat-fieldname = 'CARRID'.

ls_fieldcat-outputlen = 7.

APPEND ls_fieldcat TO l_fieldcat.

ENDFORM.

*----


*

  • FORM DATA_ADD *

*----


*

  • --> L_SFLIGHT

*----


*

FORM data_add TABLES l_sflight STRUCTURE i_sflight.

LOOP AT l_sflight.

IF sy-tabix > 10.

l_sflight-box = 'X'.

l_sflight-lights = '3'.

ELSE.

IF sy-tabix = 1.

l_sflight-lights = '2'.

ELSE.

l_sflight-lights = '1'.

ENDIF.

ENDIF.

MODIFY l_sflight.

ENDLOOP.

ENDFORM.

*----


*

  • FORM EVENTTAB_BUILD *

*----


*

  • --> l_EVENTS *

*----


*

FORM eventtab_build USING l_events TYPE slis_t_event.

DATA: ls_event TYPE slis_alv_event.

*

CALL FUNCTION 'REUSE_ALV_EVENTS_GET'

EXPORTING

i_list_type = 0

IMPORTING

et_events = l_events.

READ TABLE l_events WITH KEY name = slis_ev_top_of_page INTO ls_event.

IF sy-subrc = 0.

MOVE c_formname_top_of_page TO ls_event-form.

APPEND ls_event TO l_events.

ENDIF.

ENDFORM.

*----


*

  • FORM COMMENT_BUILD *

*----


*

  • --> L_TOP_OF_PAGE *

*----


*

FORM comment_build USING l_top_of_page TYPE slis_t_listheader.

DATA: ls_line TYPE slis_listheader.

***Header

CLEAR ls_line.

ls_line-typ = 'H'.

  • LS_LINE-KEY: not used for this type

ls_line-info = 'Heading list'.

APPEND ls_line TO l_top_of_page.

***Selection

CLEAR ls_line.

ls_line-typ = 'S'.

ls_line-key = 'Key 1'.

ls_line-info = 'Information'.

APPEND ls_line TO l_top_of_page.

ls_line-key = 'Key 2'.

APPEND ls_line TO l_top_of_page.

***Action

CLEAR ls_line.

ls_line-typ = 'A'.

  • LS_LINE-KEY: not used for this type

Ls_line-info = 'Status list'.

APPEND ls_line TO l_top_of_page.

ENDFORM.

*----


*

  • FORM LAYOUT_BUILD *

*----


*

  • <-> LS_LAYOUT *

*----


*

FORM layout_build USING ls_layout TYPE slis_layout_alv.

ls_layout-f2code = w_f2code.

ls_layout-zebra = p_zebra.

ls_layout-colwidth_optimize = p_colopt.

IF p_chkbox = 'X'.

*Fieldname for check box on the report output

ls_layout-box_fieldname = w_boxnam.

ELSE.

ls_layout-box_fieldname = space.

ENDIF.

ls_layout-no_input = p_noinpt.

ls_layout-no_vline = p_novlin.

ls_layout-no_colhead = p_nocolh.

IF p_lights = 'X' OR p_lightc = 'X'.

**Fieldname for lights on the report output

ls_layout-lights_fieldname = w_lignam.

ELSE.

CLEAR ls_layout-lights_fieldname.

ENDIF.

ls_layout-lights_condense = p_lightc.

ls_layout-totals_text = p_totext.

ls_layout-subtotals_text = p_sttext.

ls_layout-totals_only = p_totonl.

ls_layout-key_hotspot = p_keyhot.

ls_layout-detail_popup = p_detpop.

ls_layout-group_change_edit = p_groups.

  • E05_LS_LAYOUT-GROUP_BUTTONS = P_GROUPB.

  • ls_layout-group_buttons = 'X'.

ENDFORM.

*----


*

  • FORM SP_GROUP_BUILD *

*----


*

  • --> L_SP_GROUP *

*----


*

FORM sp_group_build USING l_sp_group TYPE slis_t_sp_group_alv.

DATA: ls_sp_group TYPE slis_sp_group_alv.

*Fields are assigned to the special group

CLEAR ls_sp_group.

ls_sp_group-sp_group = 'A'.

ls_sp_group-text = 'Reservation status'.

APPEND ls_sp_group TO l_sp_group.

CLEAR ls_sp_group.

ls_sp_group-sp_group = 'B'.

ls_sp_group-text = 'Flight charges'.

APPEND ls_sp_group TO l_sp_group.

ENDFORM.

*----


*

  • FORM SELECTION *

*----


*

FORM selection.

SELECT * FROM sflight INTO CORRESPONDING FIELDS OF TABLE i_sflight

UP TO p_maxrow ROWS WHERE carrid IN s_carrid

AND connid IN s_connid AND fldate IN s_fldate.

PERFORM data_add TABLES i_sflight.

ENDFORM.

*----


*

  • FORM TOP_OF_PAGE *

*----


*

  • ........ *

*----


*

FORM top_of_page.

*

CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'

EXPORTING

i_logo = 'ENJOYSAP_LOGO'

it_list_commentary = i_list_top_of_page.

ENDFORM.

*----


*

  • FORM F4_FOR_VARIANT *

*----


*

FORM f4_for_variant.

*

CALL FUNCTION 'REUSE_ALV_VARIANT_F4'

EXPORTING

is_variant = i_variant

i_save = w_save

  • it_default_fieldcat =

IMPORTING

e_exit = w_exit

es_variant = i_variant1

EXCEPTIONS

not_found = 2.

IF sy-subrc = 2.

MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ELSE.

IF w_exit = space.

p_varnt = i_variant1-variant.

ENDIF.

ENDIF.

ENDFORM.

*&----


*

*& Form PAI_OF_SELECTION_SCREEN

*&----


*

  • to check whether right variant is entered on the selection scr

*----


*

FORM pai_of_selection_screen.

*

IF NOT p_varnt IS INITIAL.

MOVE i_variant TO i_variant1.

MOVE p_varnt TO i_variant1-variant.

CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'

EXPORTING

i_save = w_save

CHANGING

cs_variant = i_variant1.

i_variant = i_variant1.

ELSE.

PERFORM variant_init.

ENDIF.

ENDFORM. " PAI_OF_SELECTION_SCREEN

*&----


*

*& Form VARIANT_INIT

*----


*

FORM variant_init.

*

CLEAR i_variant.

i_variant-report = w_repid.

ENDFORM. " VARIANT_INIT

*----


*

  • FORM PRINT_BUILD *

*----


*

  • ........ *

*----


*

FORM print_build USING l_print TYPE slis_print_alv.

*

l_print-print = p_print.

l_print-no_print_selinfos = p_nosinf.

l_print-no_coverpage = p_nocove.

l_print-no_new_page = p_nonewp.

l_print-no_print_listinfos = p_nolinf.

l_print-reserve_lines = p_reserv.

l_print-print = p_print.

ENDFORM.

*----


*

  • FORM T_SORT_BUILD *

*----


*

FORM t_sort_build USING l_sort TYPE slis_t_sortinfo_alv.

DATA: ls_sort TYPE slis_sortinfo_alv.

ls_sort-fieldname = 'CARRID'.

ls_sort-spos = 1.

ls_sort-up = 'X'.

ls_sort-subtot = 'X'.

APPEND ls_sort TO l_sort.

ENDFORM.

Read only

Former Member
0 Likes
1,131

ABAP List Viewer

The common features of report are column alignment, sorting, filtering, subtotals, totals etc. To implement these, a lot of coding and logic is to be put. To avoid that we can use a concept called ABAP List Viewer (ALV).

This helps us to implement all the features mentioned very effectively.

Using ALV, We can have three types of reports:

1. Simple Report

2. Block Report

3. Hierarchical Sequential Report

There are some function modules which will enable to produce the above reports without much effort.

All the definitions of internal tables, structures and constants are declared in a type-pool called SLIS.

1. SIMPLE REPORT.

The important function modules are

a. Reuse_alv_list_display

b. Reuse_alv_fieldcatalog_merge

c. Reuse_alv_events_get

d. Reuse_alv_commentary_write

e. Reuse_alv_grid_display

A. REUSE_ALV_LIST_DISPLAY : This is the function module which prints the data.

The important parameters are :

I. Export :

i. I_callback_program : report id

ii. I_callback_pf_status_set : routine where a user can set his own pf status or change the functionality of the existing pf status

iii. I_callback_user_command : routine where the function codes are handled

iv. I_structure name : name of the dictionary table

v. Is_layout : structure to set the layout of the report

vi. It_fieldcat : internal table with the list of all fields and their attributes which are to be printed (this table can be populated automatically by the function module REUSE_ALV_FIELDCATALOG_MERGE

vii. It_events : internal table with a list of all possible events of ALV and their corresponding form names.

II. Tables :

i. t_outtab : internal table with the data to be output

B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.

The Important Parameters are :

I. Export :

i. I_program_name : report id

ii. I_internal_tabname : the internal output table

iii. I_inclname : include or the report name where all the dynamic forms are handled.

II Changing

ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is

declared in the type pool SLIS.

C. REUSE_ALV_EVENTS_GET : Returns table of possible events for a list type

Parameters :

I. Import :

Et_Events : The event table is returned with all possible CALLBACK events

for the specified list type (column 'NAME'). For events to be processed by Callback, their 'FORM' field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field 'FORM' filled and the entry modified using constants from the type pool SALV.

II. Export :

I_List_type :

0 = simple list REUSE_ALV_LIST_DISPLAY

1 = hierarchcal-sequential list REUSE_ALV_HIERSEQ_LIST_DISPLAY

2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND

3 = hierarchical-sequential block list

REUSE_ALV_BLOCK_LIST_HS_APPEND

D. REUSE_ALV_COMMENTARY_WRITE : This is used in the Top-of-page event to print the headings and other comments for the list.

Parameters :

I. it_list_commentary : internal table with the headings of the type slis_t_listheader.

This internal table has three fields :

Typ : ‘H’ – header, ‘S’ – selection , ‘A’ - action

Key : only when typ is ‘S’.

Info : the text to be printed

E. REUSE_ALV_GRID_DISPLAY : A new function in 4.6 version, to display the results in grid rather than as a preview.

Parameters : same as reuse_alv_list_display

This is an example for simple list.

2. BLOCK REPORT

This is used to have multiple lists continuously.

The important functions used in this report are:

A. REUSE_ALV_BLOCK_LIST_INIT

B. REUSE_ALV_BLOCK_LIST_APPEND

C. REUSE_ALV_BLOCK_LIST_HS_APPEND

D. REUSE_ALV_BLOCK_LIST_DISPLAY

A. REUSE_ALV_BLOCK_LIST_INIT

Parameters:

I. I_CALLBACK_PROGRAM

II. I_CALLBACK_PF_STATUS_SET

III. I_CALLBACK_USER_COMMAND

This function module is used to set the default gui status etc.

B. REUSE_ALV_BLOCK_LIST_APPEND

Parameters :

Export :

I. is_layout : layout settings for block

II. it_fieldcat : field catalog

III. i_tabname : internal table name with output data

IV. it_events : internal table with all possible events

Tables :

i. t_outtab : internal table with output data.

This function module adds the data to the block.

Repeat this function for all the different blocks to be displayed one after the other.

C. REUSE_ALV_BLOCK_LIST_HS_APPEND

This function module is used for hierarchical sequential blocks.

D. REUSE_ALV_BLOCK_LIST_DISPLAY

Parameters : All the parameters are optional.

This function module display the list with data appended by the above function.

Here the functions REUSE_ALV_FIELDCATALOG_MERGE, REUSE_ALV_EVENTS_GET, REUSE_ALV_COMMENTARY_WRITE can be used.

3. Hierarchical reports :

Hierarchical sequential list output.

The function module is

A. REUSE_ALV_HIERSEQ_LIST_DISPLAY

Parameters:

I. Export:

i. I_CALLBACK_PROGRAM

ii. I_CALLBACK_PF_STATUS_SET

iii. I_CALLBACK_USER_COMMAND

iv. IS_LAYOUT

v. IT_FIELDCAT

vi. IT_EVENTS

vii. i_tabname_header : Name of the internal table in the program containing the

output data of the highest hierarchy level.

viii. i_tabname_item : Name of the internal table in the program containing the

output data of the lowest hierarchy level.

ix. is_keyinfo : This structure contains the header and item table field

names which link the two tables (shared key).

II. Tables

i. t_outtab_header : Header table with data to be output

ii. t_outtab_item : Name of the internal table in the program containing the

output data of the lowest hierarchy level.

slis_t_fieldcat_alv : This internal table contains the field attributes. This internal table can be populated automatically by using ‘REUSE_ALV_FIELDCATALOG_MERGE’.

Important Attributes :

A. col_pos : position of the column

B. fieldname : internal fieldname

C. tabname : internal table name

D. ref_fieldname : fieldname (dictionary)

E. ref_tabname : table (dictionary)

F. key(1) : column with key-color

G. icon(1) : icon

H. symbol(1) : symbol

I. checkbox(1) : checkbox

J. just(1) : (R)ight (L)eft (C)ent.

K. do_sum(1) : sum up

L. no_out(1) : (O)blig.(X)no out

M. outputlen : output length

N. seltext_l : long key word

O. seltext_m : middle key word

P. seltext_s : short key word

Q. reptext_ddic : heading (ddic)

R. ddictxt(1) : (S)hort (M)iddle (L)ong

S. datatype : datatype

T. hotspot(1) : hotspot

Read only

Former Member
0 Likes
1,131

REUSE_ALV_EVENTS_GET

Description

This table tells ALV which events are processed by the caller by CALLBACK.

The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.

You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module

REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.

The table structure contains the fields:

• IT_EVENTS-NAME

Name of the Callback event.

Possible Callback events:

• Action

USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD

Process actions on the list

As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.

PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB

If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).

The STANDARD status of the function group SALV should be used as a template for a user-specific status.

As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.

ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C

Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.

Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.

RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.

RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.

CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.

• List processing events

IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.

TOP_OF_LIST no USING parameter. Information output at the start of the list

END_OF_LIST no USING parameter. Information output at the end of the list

TOP_OF_PAGE no USING parameter

Equivalent to the list processing TOP-OF-PAGE event

END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.

Information output at the end of a page. This is only called for printing.

TOP_OF_COVERPAGE no USING parameter

The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:

IS_PRINT-NO_COVERPAGE

IS_PRINT-NO_PRINT_SELINFOS

IS_PRINT-NO_PRINT_LISTINFOS

IS_LAYOUT-GET_SELINFOS

The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.

END_OF_COVERPAGE no USING parameter

Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.

FOREIGN_TOP_OF_PAGE no USING parameter

The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).

In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.

FOREIGN_END_OF_PAGE no USING parameter

The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).

In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.

BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO

Output information before each output line. Should only be used in justified cases because it costs a lot of performance.

AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO

Output information after each output line. Should only be used in justified cases because it costs a lot of performance.

• Internal use only

LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME

R_INDEX LIKE SY-TABIX

R_INDEX_ITEM LIKE SY-TABIX

R_INDEX_SUM LIKE SY-TABIX

• IT_EVENTS-FORM

Name of the form routine which should be called in the calling program at the event.

Field_catalog:

Field catalog with field descriptions

2.7.1. Description

Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.

The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module

See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.

The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.

A field catalog need not be built-up and passed explicitly only under the following conditions:

• The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.

• all fields in this structure are to be output

• the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.

See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.

Positioning

• row_pos (row position)

value set: 0, 1 - 3

Only relevant if the list output is to be multi-line (two or three lines) by default.

A multi-line list can also be defined by the user interactively if the default list is one-line.

The parameter specifies the relative output line of the column in a multi-line list.

• col_pos (column position)

value set: 0, 1 - 60

only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.

Identification

• fieldname (field name)

value set: internal output table field name (required parameter)

Name of the internal output table field which is described by this field catalog entry

• tabname (internal output table)

value set: SPACE, internal output table name

This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.

Name of the internal output table which contains the field FIELDCAT-FIELDNAME.

Data Dictionary reference

• ref_fieldname (reference field name)

value set: SPACE, Data Dictionary field name

Name of the Data Dictionary field referred to.

This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.

• ref_tabname (reference table/structure field name)

value set: SPACE, name of a Data Dictionary structure or table

Structure or table name of the referred Data Dictionary field.

This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).

Reference to fields with currency/measurement unit

Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:

• the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)

• There is a field in the internal output table which contains the associated unit.

• There is also an entry in the field catalog for the unit field.

(If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.

The association of a value field to a unit affects the output as follows:

• appropriate decimal places display for the unit

• an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.

• an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.

• When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.

Link to currency unit

• cfieldname (currency unit field name)

value set: SPACE, output table field name

Only relevant for amount columns with associated unit.

Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.

• ctabname (internal currency unit field output table)

value set: SPACE, output table field name

only relevant for hierarchical-sequential lists

Name of the internal output table containing the FIELDCAT-CFIELDNAME field.

Link to measurement unit

• qfieldname (measurement unit field name)

value set: SPACE, output table field name

only relevant for quantity columns with unit link.

Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.

The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.

• qtabname (internal measurement unit field output table)

value set: SPACE, output table field name

only relevant for hierarchical-sequential lists

Name of the internal output table containing the FIELDCAT-QFIELDNAME field.

Column output options

• outputlen (column width)

value set: 0 (initial), n

For fields with a Data Dictionary link this parameter can be left initial.

For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).

initial = column width is the output length of the referred Data Dictionary field (domain).

n = column width is n characters

• key (key column)

value set: SPACE, 'X' 'X' = kex field (key field output in color)

Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.

For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.

• key_sel (hideable key column)

value set: SPACE, 'X'

only relevant when FIELDCAT-KEY = 'X'

Key field which can be hidden interactively.

The key column sequence cannot be changed interactively by the user.

The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.

• no_out (field in field list)

value set: SPACE, 'X' 'X' = field is not displayed in the current list.

The user can interactively choose the field for output from the field list.

The user can display the contents of these fields at line level using the 'Detail' function.

See also the 'Detail screen' documentation of the parameter IS_LAYOUT.

• tech (technical field)

value set: SPACE, 'X' 'X' = technical field

Field cannot be output in the list and cannot be displayed interactively.

Field can only be used in the field catalog (not in IT_SORT, ...).

• emphasize (highlight columns in color)

value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)

'X' = column is colored with the default column highlight color.

'Cxyz' = column is colored with a coded color:

• C: Color (coding must begin with C)

• x: color number

• y: bold

• z: inverse

• hotspot (column as hotspot)

value set: SPACE, 'X'

'X' = column cells are output as hotspots

• fix_column (fix column)

value set: SPACE, 'X'

Not relevant for block lists (output of several lists consecutively)

'X' = column fixed (does not scroll horizontally)

All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter

IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.

• do_sum (sum over column)

value set: SPACE, 'X' 'X' = a sum is to be calculated over this internal output table field.

This function can also be called by the user interactively.

• no_sum (sums forbidden)

value set: SPACE, 'X' 'X' = no sum can be calculated over this field, although the data type of the field would allow summing.

• input (column ready for input)

Function not available

Format column contents

• icon

value set: SPACE, 'X' 'X' = column contents to be output as an icon.

The caller must consider the printability of icons.

• symbol

value set: SPACE, 'X' 'X' = column contents are to be output as a symbol.

The internal output table column must be a valid symbol character.

The caller must consider the printability of symbols.

Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.

• just (justification)

value set: SPACE, 'R', 'L', 'C'

Only relevant for fields of data type CHAR or NUMC

' ' = default justification for this data type

'R' = right-justified output

'L' = left-justified output

'C' = centered output

The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.

• lzero (leading zeros)

value set: SPACE, 'X'

Only relevant for fields of data type NUMC

ALV outputs NUMC fields right-justified without leading zeros by default.

'X' = output with leading zeros

Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.

• no_sign (no +/- sign) Only relevant for value fields

value set: SPACE, 'X' 'X' = value output without +/ sign

• no_zero (suppress zeros) Only relevant for value fields

value set: SPACE, 'X' 'X' = suppress zeros

• edit_mask (field formatting)

value set: SPACE, template

template = see documentation of WRITE formatting option USING EDIT MASK template

The output conversion conv can be made by template = '== conv'.

Texts

The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.

The 'long field label' is also used in display variant definition, sort, etc. popups.

• seltext_l (long field label)

• seltext_m (medium field label)

• seltext_s (short field label)

• reptext_ddic (header)

analogous to the Data element maintenance 'Header'

The specified text is not necessarily output in the list, an optimum among all texts is sought.

• ddictxt (specify text)

value set: SPACE, 'L', 'M', 'S'

You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.

Parameters for program fields without Data Dictionary reference

see also 'Text' parameters

• datatype (data type)

value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)

Only relevant for fields without Data Dictionary reference

Program field data type

• ddic_outputlen (external output length)

value set: 0 (initial), n

Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.

Prerequisites:

• FIELDCAT-EDIT_MASK = '==conv'

see also the documentation of the parameter FIELDCAT-EDIT_MASK

• FIELDCAT-INTLEN = n

see also the documentation of the parameter FIELDCAT-INTLEN

n = external format field output length

The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).

• intlen (internal output length)

value set: 0 (initial), n

Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.

Prerequisites:

• FIELDCAT-EDIT_MASK = '==conv'

see also the documentation of the parameter FIELDCAT-EDIT_MASK

• FIELDCAT-DDIC_OUTPUTLEN = n

see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN

n = internal format field output length

• rollname (data element)

value set: SPACE, Data Dictionary data element name

F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.

When F1 help is called for this field, the documentation of the specified data element is displayed.

If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.

Others

• sp_group (field group key)

value set: SPACE, CHAR(1)

Field group key.

Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).

When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.

• reprep (Report/Report interface selection criterion)

value set: SPACE, 'X'

Prerequisites:

• The system contains the Report/Report interface (function group RSTI, table TRSTI)

• Parameter LAYOUT-REPREP = 'X'

(see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )

'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.

2.7.2. Default

• The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :

• fieldname

• ref_tabname

Notes:

ALV gets the remaining information from the Data Dictionary.

If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.

REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.

Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.

Priority rule:

Entries in the field catalog have priority over differing entries in the Data Dictionary.

• The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):

• fieldname

• outputlen

• datatype

• seltext_s

• seltext_m

• seltext_l

Notes:

F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.

If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.

Read only

Former Member
0 Likes
1,131

use type-pools SLIS for field catalog use SLIS_T_FIELDCAT_ALV

and work area SLIS_FIELDCAT_ALV