COMPLETE ALV DOCUMENTATION

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 up to 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 described below.


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 be 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 : Selecting the variants(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’.




Step3(Defining Output Characteristics)

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 column order can be changed interactively by the user. 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 cannot 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 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.
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’.



Step 4(Build up events table)

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 from 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.



Step 5(Report Output list description)

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 headings 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 field catalog.
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.



Step 6(Pass Selection-screen Information)

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.

 t_entries: Selection info table

 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.

 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 7(Deciding Sort Criteria)

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:
• spos : Sort sequence
• fieldname : Internal output table field name
• tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.
• up : 'X' = sort in ascending order
• down : 'X' = sort in descending order
• subtot : 'X' = subtotal at group value change
• group : '* ' = new page at group value change ,'UL' = underline at group value change

Step 8(Final Step)

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(Display Internal Output Table)


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


Documentation on function module : REUSE_ALV_GRID_DISPLAY

The function module outputs an internal table with whatever structure in the form of a formatted single- or multi-line list.

Process:

 Passing an internal table with the set of information to be output

 Passing a structure with general layout specifications for list layout

 Passing a field catalog in the form of an internal table

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

Notes

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


 An important factor determining the usability of the tool or of various generic functions (totals, subtotals) is the expected amount of data to be displayed.



Parameters :


• I_INTERFACE_CHECK
• I_BYPASSING_BUFFER
• I_BUFFER_ACTIVE
• I_CALLBACK_PROGRAM
• I_CALLBACK_PF_STATUS_SET
• I_CALLBACK_USER_COMMAND
• I_CALLBACK_TOP_OF_PAGE
• I_CALLBACK_HTML_TOP_OF_PAGE
• I_CALLBACK_HTML_END_OF_LIST
• I_STRUCTURE_NAME
• I_BACKGROUND_ID
• I_GRID_TITLE
• I_GRID_SETTINGS
• IS_LAYOUT
• IT_FIELDCAT
• IT_EXCLUDING
• IT_SPECIAL_GROUPS
• IT_SORT
• IT_FILTER
• IS_SEL_HIDE
• I_DEFAULT
• I_SAVE
• IS_VARIANT
• IT_EVENTS
• IT_EVENT_EXIT
• IS_PRINT
• IS_REPREP_ID
• I_SCREEN_START_COLUMN
• I_SCREEN_START_LINE
• I_SCREEN_END_COLUMN
• I_SCREEN_END_LINE
• IT_ALV_GRAPHICS
• IT_ADD_FIELDCAT
• IT_HYPERLINK
• E_EXIT_CAUSED_BY_CALLER
• ES_EXIT_CAUSED_BY_USER


I_CALLBACK_PROGRAM: Name of the calling program

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

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

I_CALLBACK_PF_STATUS_SET: Set EXIT runtime to status

Passing an EXIT routine indicates to the ALV that the caller wants to set a self-defined user status. As a result, the default status of the ALV is not set. The interface of the form routine specified must be defined as follows:

FORM set_pf_status USING rt_extab TYPE slis_t_extab

Table RT_EXTAB contains the function codes that would be hidden on the standard user interface.

If the caller wants to use a self-defined user interface (for example, in order to provide additional list functions or use existing functions), we recommend that you copy standard status STANDARD from function group SALV and modify it accordingly. ALV standard function codes always start with '&'.

See also the documentation on parameter I_CALLBACK_USER_COMMAND.

If a self-defined user interface is used that includes function codes of the standard user
interface, the function codes of the excluding table passed should be taken into account.

This means that the user status should generally be set as follows:
SET PF-STATUS user status EXCLUDING rt_extab.

Application functions can be added to excluding table rt_extab if they are to be disabled.

The routine is called whenever the standard user interface would be set with SET PF-
STATUS.

Default

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

I_CALLBACK_USER_COMMAND

EXIT routine for command handling

Description
Passing an EXIT routine indicates to the ALV that the application wants to respond to certain function codes.
Generally, these are function codes that are unknown to the ALV (that is, are not standard ALV functions) and that were defined and set by a user status.

See also the documentation on parameter I_CALLBACK_PF_STATUS_SET.

The interface of the form routine specified must be defined as follows:

FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.

Parameter R_UCOMM contains the function code triggered.

Structure RS_SELFIELD contains the following information:


o tabname : Name of the internal output table
o tabindex : Index of the internal output table
o fieldname: Field name
o endsum : Cursor is located on the totals line
o sumindex : If >0, the cursor is located on a subtotals line
o value : Value of the field on the list
o refresh : (Exporting) List should be set up again
o col_stable: (Exporting) Keep column position when list is set up again
o row_stable: (Exporting) Keep row position when list is set up again
o exit : (Exporting) Exit list (and ALV)
o before_action: Call before standard action execution
o after_action : Call after standard action execution, before list setup
o ignore_multi : Internal use
o sel_tab_field: Internal use

The EXIT routine is called whenever a function unknown to the ALV is triggered or if the routine call before/after the execution of a standard function code has been defined by interface parameter
IT_EVENT_EXIT.

See also the documentation on parameter IT_EVENT_EXIT.

The function code and the current cursor position are then passed on to the calling program through the EXIT routine.

If the user has selected multiple rows by selecting checkboxes, the output table field designated as the checkbox contains the current state of the checkbox in the list.






I_CALLBACK_TOP_OF_PAGE


EXIT routine for handling TOP-OF-PAGE

Description
If the caller specifies an EXIT routine, this routine must have the following form:

FORM top_of_page.

Module REUSE_ALV_COMMENTARY_WRITE can then be called within the EXIT routine. This module is responsible for formatting the header information and also ensures online TML formatting. In the print preview or in batch mode, the text passed is then output in the normal
format.

If module REUSE_ALV_COMMENTARY_WRITE cannot be used, you must use two parameters instead. In I_CALLBACK_TOP_OF_PAGE you pass the form routine that is responsible for normal formatting in batch mode or in the print preview mode. The form routine that is responsible for online formatting, is passed in parameter I_CALLBACK_HTML_TOP_OF_PAGE. If one of these parameters is not filled, top-of-page is not output in the respective mode.

I_CALLBACK_HTML_TOP_OF_PAGE

EXIT routine for HTML TOP-OF-PAGE

Description
If function module REUSE_ALV_COMMENTARY_WRITE is not used in the form for
CALLBACK_TOP_OF_PAGE, the form routine must be passed in parameter
I_CALLBACK_HTML_TOP_OF_PAGE for the online mode. The form should then
have the following format:

form top_of_page using cl_dd type ref to cl_dd_document.

In the form, you can, for example, use methods of class CL_DD_DOCUMENT
to display text in HTML format.


I_CALLBACK_HTML_END_OF_LIST

EXIT routine for HTML END-OF-LIST

Description
In this parameter, you can pass a form for the online handling of end-of-list. The form must have the followiong format:

form end_of_list using cl_dd type ref to cl_dd_document.

I_STRUCTURE_NAME

Internal output table structure name

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

The field catalog is then internally set up for this structure as follows:

o All fields are on the list (NO_OUT = SPACE) except fields of data type CLNT.
o The key fields of the Dictionary structure are adopted in the field catalog as key fields.
o References to unit fields stored in the Dictionary are adopted provided that the reference
fields are contained in the structure.
o If you additionally pass a field catalog as parameter, the structure information is merged
with this field catalog.

For more information on how to set up the field catalog automatically, see the documentation on function module REUSE_ALV_FIELDCATALOG_MERGE.


I_GRID_TITLE

Control title

Description : Specifies the title of the control. This text is displayed above the grid.

I_GRID_SETTINGS

Grid settings

Description

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

COLL_TOP_P: Sets Top-of-Page to 0%
COLL_END_L: Sets End-of-List to 0%


IS_LAYOUT

List layout specifications

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

• Display options
• Exceptions
• Totals
• Interaction
• Detail screen
• Color
• Other

Note the section on pre-defined settings.

Display options

• colwidth_optimize
Value range: SPACE, 'X'
X' = Optimizes the column width to ensure that the content is
displayed completely.

• no_colhead
Value range: SPACE, 'X'
'X' = Do not output column headings.

• zebra
Value range: SPACE, 'X'
'X' = Striped pattern (for wide lists, for example)

• no_vline
Value range: SPACE, 'X'
'X' = Separate columns by SPACE.

Exceptions

lights_fieldname
Value range: SPACE, field name of the internal output table field of the internal output table that contains the coding of the exceptions to be output .

Coding in the field of the output table:
'1' = red traffic light
'2' = yellow traffic light
'3' = green traffic light

lights_tabname
Value range: SPACE, table name of the internal output table Table name of the internal output table that contains the specified field in parameter LIGHTS_FIELDNAME.

lights_rollname
Value range: SPACE, data element name
The documentation defined for this data element is displayed when the F1 help for an exception column is called.
lights_condense
Value range: SPACE, 'X'
'X' = The system outputs the 'maximum' exception of the items included in the total at subtotal level.
Example: If a list row is output with a 'red traffic light', each subtotal included in this list row is also displayed with a 'red traffic light'.

Totals

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

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

• no_subchoice
Value range: SPACE, 'X'
'X' = Characteristics at whose control level subtotals should be calculated are communicated by the calling program. The user should not be allowed to change this pre-defined setting
interactively.

See also the documentation on IMPORTING parameter IT_SORT.

• no_subtotals
Value range: SPACE, 'X'
'X' = Calculating subtotals should not be allowed.

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


• totals_text
Value range: SPACE, string (not more than 60)
' ' = In the first column, the standard system indicates the totals level by displaying an adequate number of '*' for the overall total.After the asterisks, the system displays the string 'total' provided that the column width of the first output column is large enough. If the column width is not sufficient, only the asterisks are displayed. 'string' = After the totals level indicated visually by means of '*', the system displays the string passed provided that the column width is sufficient.

• subtotals_text
Value range: SPACE, string (not more than 60) ' ' = In the first column, the standard system indicates the totals level by displaying an adequate number of '*' for the subtotals line. After the asterisks, the system displays the string *total* provided that the column width of the first output column is large enough and the characteristic of the first column is not a subtotal criterion. If the column width is not sufficient, only the asterisks are displayed.

'string' = After the totals level indicated visually by means of '*', the system displays the string passed provided that the column width is sufficient and the characteristic of the first column is not a subtotal criterion.

If the characteristic is a subtotal criterion, the system repeats the characteristic value for which subtotals were calculated after the totals level provided that the column width is sufficient.

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


Interaction

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

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

• f2code
Value range: SPACE, function code
Meaning when the ALV standard interface is used:
If you want to assign a standard ALV function code to a double-click (F2), you must assign this function code to this parameter.
Example: You want to assign the standard ALV function 'Detail'
('&ETA') to F2.
=> LAYOUT-F2CODE = '&ETA'
Meaning if a self-defined interface is used:

Case 1:
You leave the standard ALV function code for F2 '&IC1' in the copied interface of the application. However, you want to have a function executed with F2 that is not assigned to F2 in the interface
(standard ALV function or application function). You must communicate this function code to the ALV using parameter F2CODE.

Case 2:
You remove the standard ALV function code for F2 '&IC1' from the interface of the application and use another function code instead (standard ALV function or application function). You must
communicate this function code to the ALV using parameter F2CODE.

This is required if you want to allow columns to be selected.

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

• key_hotspot
Value range: SPACE, 'X'
The columns defined as key fields in the field catalog (FIELDCAT-KEY = 'X') are
output as a hotspot. This means that single-clicking a key field (highlighted in color in
the list) triggers the function assigned to F2.

• reprep
Value range: SPACE, 'X'
'X' = Enable report/report interface
Prerequisite: Application system (=> report RKKBRSTI exists).
The list module acts as a potential sender in the report/report interface (interface
initialization, if required).

The calling report/module pool entered in I_CALLBACK_PROGRAM is declared to the report/report interface as the sender report with type RT=Report. If the sender report is assigned to receiver reports in table TRSTI, function code BEBx is set to active. ( x = function code class)

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

For more information on the report/report interface, see the documentation on function group 'RSTI'.



Detail screen

• detail_initial_lines
Value range: SPACE, 'X'
' ' = In the detail view, the system displays only fields whose content is not set to
initial.
'X' = Initial field contents are also displayed on the detail screen.

• detail_titlebar
Value range: SPACE, string (not more than 30)
' ' = The system displays 'Detail: Display' as the title of the
detail screen.
'string' = The system displays the string passed as the title of the
detail screen.


Color

• info_fieldname
Value range: SPACE, field name of the internal output table.
You can color an entire list row individually by using a color code that is set for each row in a column of the internal output table. You must assign the field name of the field with the color code to
this parameter.

The field of the internal output table must be of type CHAR(3).
The code must comply with the following syntax: 'Cxy':
C = Color (each code must begin with 'C')
x = Color number ('1'-'9')
y = Intensified ('0' = off, '1' = on)
Note: The color of the key column is not affected. If you also want
to color the key column at row or cell level, you can use complex
coloring which is described below for parameter COLTAB_FIELDNAME.
For information on coloring columns, see the documentation on field catalog
parameter FIELDCAT-EMPHASIZE of IMPORTING parameter IT_FIELDCAT.


• coltab_fieldname
Value range: SPACE, field name of the internal output table
You can color cells individually by using a color code that is set for the row of the cells in a column of the internal output table. You must assign the field name of the field with the color code to this parameter.

The field of the internal output table must be of type SLIS_T_SPECIALCOL_ALV.
Principle: The field for the color code is filled in the row in which the cells to be colored are located. The field then contains an internal table of the above structure that includes the field
names of the cells to be colored with the color code. The cell coordinates are therefore derived from the row position in which the color code is written and the column information contained in the
color table. The row structure of the internal color table of type SLIS_T_SPECIALCOL_ALV is as follows:

Farbtabelle-NAME = Field name of cell to be colored
Farbtabelle-COLOR-COL = Color number (1 - 9)
Farbtabelle-COLOR-INT = Intensified (0 = off, 1 = on)
Farbtabelle-COLOR-INV = Inverse (0 = off, 1 = on)
Farbtabelle-NOKEYCOL = Ignore key coloring ('X' = yes, ' ' = no)

If parameter Farbtabelle-NAME is not filled, all color
specifications refer to all fields. As a result, the entire row is
colored.


Default

In many cases, the default layout settings can be kept so that you
frequently do not need to pass this structure with modified flags.


IT_FIELDCAT

Field catalog with field descriptions

Description

Field catalog containing the field descriptions of the fields to be considered for the list output (usually, this is a subset of the fields in the internal output table).

Basically, you need a field catalog for each list output that uses the ALV.

The field catalog associated with the output table is generated in the code of the caller. You can generate the field catalog automatically or semi-automatically by calling function module
REUSE_ALV_FIELDCATALOG_MERGE.

See also the documentation on function module : REUSE_ALV_FIELDCATALOG_MERGE.

The minimum values required for the field catalog are documented in the 'Default' section. The caller can optionally use all other parameters to assign non-standard output attributes to a field.

It is only in the following cases that you are not required to generate the field catalog and pass it explicitly:

• The structure of the internal table to be output corresponds to a structure stored in the Data Dictionary and is referenced with LIKE or INCLUDE STRUCTURE in the declaration of the internal table.

• All fields of this structure should be output in the list.

• The structure name is declared to the ALV using parameter
I_STRUCTURE_NAME.
See also the documentation on IMPORTNG parameter I_STRUCTURE_NAME.


Positioning

• col_pos (column position)
Value range: 0, 1 - 60
Only relevant if the relative column positions should by default not be identical to the sequence of the fields in the field catalog.

The parameter determines the relative column position of the field in the list output. The column sequence can interactively be changed by the user. If this parameter is set to its initial value for each field catalog entry, the columns are arranged in the order of the fields in the field catalog.


Identification

• fieldname (field name)
Value range: Field name of the internal output table (required parameter)
Field name of the field in the internal output table that is described by this field
catalog entry.

Reference to the Data Dictionary

ref_fieldname (field name of the reference field)
Value range: SPACE, name of a field in the Data Dictionary Name of the referenced
field in the Data Dictionary.

This parameter is only required if the field in the internal output table that is described by the current entry in the field catalog has a reference to the Data Dictionary (that is, is not a program field) and if the field name in the internal output table is not identical to the field name of the field in the Data Dictionary. If both field names are identical, it is sufficient to specify the Data Dictionary structure or table in parameter FIELDCAT-REF_TABNAME.


• ref_tabname (field name of the reference table/structure)
Value range: SPACE, name of a structure or table in the Data Dictionary
Structure or table name of the referenced field in the Data Dictionary.

This parameter is only required if the field in the internal output table that is described by the current entry in the field catalog has a reference to the Data Dictionary (that is, is not a program field).

Reference to fields with currency units/units of measure Each amount or quantity field of the internal output table whose decimal places are to be displayed with the proper unit in the list
output, must comply with the following conventions:


- The field is of data type QUAN or CURR (internal type P). (Physically, the field must actually belong to this data type.Overriding the physical data type with parameter FIELDCAT-DATATYPE has no effect.)

- There is one field in the internal output table that contains the relevant unit.

- There is also an entry for the unit field in the field catalog. (If the unit should not be displayed as a column in the list and the user should not be able to show the unit interactively, for example, because the unit is always unique and therefore explicitly output by the caller in the list header, then you can assign parameter FIELDCAT-TECH = 'X' to the field catalog entry for the unit field.

If a value field has a reference to a unit, this has the following effects when the list is output:

- The decimal places are displayed with the proper unit.

- An initial value field with reference to a non-initial unit is displayed as '0' (provided that FIELDCAT-NO_ZERO is initial). If unit-specific totals are calculated for this value field, the unit is considered in the analysis of whether homogeneous units exist.

- An initial value field with reference to an initial unit is displayed as SPACE. If unit-specific totals are calculated for this value field, the unit SPACE has no effect on the homogeneity of the unit if the value field is initial.

- For non-initial value fields with initial unit, the unit SPACE is considered as a unit when unit-specific totals are calculated.


Reference to the currency unit

• cfieldname (field name of the currency unit field) Value range: SPACE, name of a field of the output table Only relevant to amount columns with unit reference.

Field name of the field in the internal output table that contains the currency unit for the amount field FIELDCAT-FIELDNAME.
There must be a separate field catalog entry for the field specified in FIELDCAT-CFIELDNAME.

Reference to the unit of measure

• qfieldname (field name of the unit of measure field)
Value range: SPACE, name of a field of the output table
Only relevant to quantity columns with unit reference.
Field name of the field in the internal output table that contains
the unit of measure for the amount field FIELDCAT-FIELDNAME.
There must be a separate field catalog entry for the field specified
in FIELDCAT-QFIELDNAME.


Output options for a column

• outputlen (column width)
Value range: 0 (initial), n
For fields with reference to the Data Dictionary you can leave this
parameter set to initial.
For fields without reference to the Data Dictionary (program fields)
you must set the parameter to the desired field output length on the
list (column width).
initial = The column width is derived from the output length of the
referenced field (domain) in the Data Dictionary.
n = The column width is n characters.

• key (key column)
Value range: SPACE, 'X'
'X' = Key field (colored output for key fields)
Key fields cannot be hidden interactively by the user.
Parameter FIELDCAT-NO_OUT must be left set to initial.
For exceptions, see the documentation on parameter FIELDCAT-KEY_SEL.


• key_sel (key column that can be hidden)
Value range: SPACE, 'X'
Only relevant if FIELDCAT-KEY = 'X'
Key field that can be hidden interactively by the user.
The user cannot interactively change the sequence of the key
columns.
As with non-key fields, output control is performed using parameter
FIELDCAT-NO_OUT.


• no_out (field in the available fields list)
Value range: SPACE, 'X'
'X' = Field is not displayed on the current list.
The field is available to the user in the field list and can be
interactively selected as a display field.
At row level, the user can use the detail function to display the
content of these fields.
See also the documentation on the 'Detail screen' section of
parameter IS_LAYOUT.


• tech (technical field)
Value range: SPACE, 'X'
'X' = Technical field
The field cannot be output on the list and cannot be shown
interactively by the user.
The field may only be used in the field catalog (not in IT_SORT,
...).


• emphasize (highlight column in color)
Value range: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
'X' = The column is highlighted in the default color for color
highlighting.
'Cxyz' = The column is highlighted in the coded color:

- C: Color (coding must start with C)

- x: Color number

- y: Intensified

- z: Inverse


• hotspot (column as hotspot)
Value range: SPACE, 'X'
'X' = The cells of the column are output as a hotspot.


• do_sum (calculate totals for column)
Value range: SPACE, 'X'
'X' = Totals are calculated for this field of the internal output
table.
This function can also be used interactively by the user.


• no_sum (totals calculation not allowed)
Value range: SPACE, 'X'
'X' = No totals may be calculated for this field although the data
type of the field allows totalling.


Formatting column contents

• icon (icon)
Value range: SPACE, 'X'
'X' = The column contents are displayed as an icon.
The column contents of the internal output table must consist of
valid icon strings (@xx@).
The caller should consider the problem of printing icons.


• symbol (symbol)
Value range: SPACE, 'X'
'X' = The column contents are output as a symbol.
The column contents of the internal output table must consist of
valid symbol characters.
The caller should consider the problem of printing symbols.
Although symbols can generally be printed, they are not always shown
correctly depending on the printer configuration.


• just (justification)
Value range: SPACE, 'R', 'L', 'C'
Only relevant to fields of data type CHAR or NUMC
' ' = Default justification according to data type
'R' = Right-justified output

'L' = Left-justified output
'C' = Centered output
The justification of the column header depends on the justification
of the column contents. You cannot justify the column header
independently of the column contents.


• lzero (leading zeros)
Value range: SPACE, 'X'
Only relevant to fields of data type NUMC
By default, NUMC fields are output in the ALV right-justified
without leading zeros.
'X' = Output with leading zeros


• no_sign (no +/- sign)
Value range: SPACE, 'X'
Only relevant to value fields
'X' = Value output without +/- signs.


• no_zero (suppress zeros)
Value range: SPACE, 'X'
Only relevant to value fields
'X' = Supress zeros


• edit_mask (field formatting)
Value range: SPACE, mask
mask = See documentation on the WRITE formatting option
USING EDIT MASK mask
Using mask = '== conv' you can force an output conversion conv.


Texts
The following parameters for texts are always required for program
fields without reference to the Data Dictionary.
For fields with reference to the Data Dictionary, the texts are
retrieved from the Data Dictionary. If you do not want this, you can
fill the text parameters also for fields with reference to the Data
Dictionary. If you do this, the corresponding texts from the Data
Dictionary will be ignored.

If the user changes the column width interactively, the text with
the appropriate length is always used as the column header.
If the user optimizes the column width interactively, both the field
contents and the column headings are considered for the list output:
If all field contents are shorter than the shortest column heading,
the column width is set based on the column heading.

The long field label is also used in the dialog boxes for defining
the display variant, the sort order, and so on.


• seltext_l (long field label)


• seltext_m (medium field label)


• seltext_s (short field label)


• reptext_ddic (heading)
Same as the 'heading' for data element maintenance.
When the list is output, the system does not necessarily retrieve
the text stored here, but uses the text that fits best.



• ddictxt (determine text)
Value range: SPACE, 'L', 'M', 'S', 'R'
Using possible values 'L', 'M', 'S', 'R' you can predefine the
keyword that should always be retrieved as the column header. If the
column width is changed, the system tries to find a heading that
fits the new output width.


Parameter for program fields without reference to the Data Dictionary
See also the parameter in the 'Texts' section.

• datatype (data type)
Value range: SPACE, data type from the Data Dictionary (CHAR,
NUMC,...)
Only relevant to fields without reference to the Data Dictionary.
Data type of program field


• ddic_outputlen (external output length)
Value range: 0 (initial), n
Only relevant to fields without reference to the Data Dictionary
whose output should nevertheless be modified using a conversion
exit.
Prerequisites:

- FIELDCAT-EDIT_MASK = '==conv'
See also the documentation on parameter FIELDCAT-EDIT_MASK

- FIELDCAT-INTLEN = n
See documentation on parameter FIELDCAT-INTLEN
n = Field output length of the external display
The column width FIELDCAT-OUTPUTLEN must not be equivalent to the
output length of the external display (FIELDCAT-DDIC_OUTPUTLEN).


o intlen (internal output length)
Value range: 0 (initial), n
Only relevant to fields without reference to the Data Dictionary
whose output should nevertheless be modified using a conversion
exit.
Prerequisites:

- FIELDCAT-EDIT_MASK = '==conv'
See also the documentation on parameter FIELDCAT-EDIT_MASK

- FIELDCAT-DDIC_OUTPUTLEN = n
See also the documentation on parameter FIELDCAT-DDIC_OUTPUTLEN
n = Field output length of the internal display

o rollname (data element)
Value range: SPACE, name of a data element from the Data Dictionary
You can use this parameter to provide an F1 help for a program field
without reference to the Data Dictionary or to provide an F1 help
other than that of the Data Dictionary for a field with reference to
the Data Dictionary.
When the F1 help is called for this field, the documentation for the
data element assigned is displayed.
If, for fields with reference to the Data Dictionary,
FIELDCAT-ROLLNAME is initial, the documentation for the data element
of the referenced field in the Data Dictionary is displayed.


Other

o sp_group (field group key)
Value range: SPACE, CHAR(1)
Key for grouping fields
You assign the key to the group description using parameter
IT_SPECIAL_GROUPS (see also the documentation on parameter
IT_SPECIAL_GROUPS).
If you define such an assignment in the field catalog using
IT_SPECIAL_GROUPS, the fields in the field list of the display
variant dialog box are grouped accordingly.


o reprep (selection criterion of the report/report interface)
Value range: SPACE, 'X'
Prerequisites:

- The report/report interface exists in the system.
(function group RSTI, table TRSTI)

- Parameter LAYOUT-REPREP = 'X'
(See also the documentation on parameter
LAYOUT-REPREP of IMPORTING parameter IS_LAYOUT)
'X' = If the report/report interface is called, the value of this
field is passed as a selection criterion in the selected branch line
of the interface.


Default

o For internal table fields with reference to a field defined in the
Data Dictionary, it is normally sufficient to make the following
specifications:

- fieldname

- ref_tabname

Note:

All fields not explicitly mentioned here are either not relevant in this
context or are not released!

All other information is retrieved by the ALV from the Data Dictionary.

If you do not specify the relative column position (COL_POS), the fields
are output in the list in the order in which they were added to the
field catalog.

REF_FIELDNAME must only be specified if the field name of the internal
table field is not identical to the field name of the referenced field
in the Data Dictionary.

Priority rule:
Specifications made in the field catalog take priority over
specifications in the Data Dictionary.


• For internal table fields without reference to the Data Dictionary
(program fields), it is normally sufficient to make the following
specifications:

- fieldname

- outputlen

- datatype (without data type, character is the default)

- seltext_s

- seltext_l

Note:

If you assign a data element to parameter ROLLNAME, you can, for
example, implement an F1 help for program fields.

IT_EXCLUDING

Table of inactive function codes

Description

Optional IMPORTING parameter IT_EXCLUDING is an internal table. You must
only fill this table if the caller uses the standard interface of the
list tool but does not need certain interface functions and therefore
wants to disable them.

In this case, you must enter the function codes of these standard
functions into the table.

IT_SORT



Sort criteria for first list display

Description

Using internal table IT_SORT, the caller determines the sort order
and/or the subtotalling of the basic list.

The following fields of this internal table must be filled:

o spos
Sort order


o fieldname
Field name in the internal output table


o up
'X' = Sorted in ascending order


o down
'X' = Sorted in descending order

subtot
'X' = Subtotals for control level changes


o comp (INTERNAL USE ONLY)


o expa
Prequisite:
IT_SORT-SUBTOT = 'X', that is, the sort criterion is also the
subtotals criterion.


If no complete breakdown but only a breakdown to totals level n that
can be further expanded by the user should be displayed when the
list is output for the first time, you must set the indicator for
the totals level criterion of level n.


IT_FILTER



Filter criteria for first list output

Description

Table with filter criteria

Using this parameter, you can pass on filter criteria resulting from
explicitly loading a display variant in advance, for example, to list
output.

This table should never be set up 'manually'.



IS_SEL_HIDE



Selection information modification

Description

This parameter is currently not supported!

Only relevant if layout parameter
LAYOUT-GET_SELINFOS of IMPORTING structure IS_LAYOUT is set.

Complex type for modifying information displayed on the selection dialog
box:

o mode: 'R' = Only entries passed in internal table
IS_SEL_HIDE-T_ENTRIES are output on
the dialog box. Selection information
obtained by the list tool by reading the
selection screen again (only if the report
is called with selection screen) are
replaced by the entries passed.

'S' = The selection information obtained by the
list tool by reading the selection screen
of the calling report again, are modified
by the entries of table
IS_SEL_HIDE-T_ENTRIES.


o t_entries: Table with selection information


o t_entries-mode: 'A' = Display selection information of the current
table row on the information dialog box.
'D' = Do not display selection information of the
the Select option or of parameter SELNAME on the dialog box.


o t_entries-selname: (required only if t_entries-mode = 'D')
name of Select option or parameter


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

o t_entries-field: DDIC field name of the field for which selection
information is to be displayed


o t_entries-table: DDIC table name of t_entries-field.


o t_entries-stext: Field description on the information dialog box.
If t_entries-field and t_entries-table were
filled, this text is taken from the DDIC.


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


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


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


o t_entries-optio: All values of the option field of the Select
option are allowed.


The remaining fields are used internally and are irrelevant to the
caller.



I_DEFAULT

Initial variant active/inactive logic

Description

Initial variant maintenance active/inactive. .

Prerequisite: Parameter IS_VARIANT is filled accordingly.
See also the documentation on the IMPORTING parameter IS_VARIANT.

Value Range

SPACE = Definition of initial variants not allowed

'X' = Definition of initial variants allowed

Default : SPACE


I_SAVE

Variants can be saved

Description

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

Value Range

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


o 'X' = Standard save mode
Display variants can be saved as standard display variants.
Saving display variants as user-specific is not possible.


o 'U' = User-specific save mode
Display variants can only be saved as user-specific.


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

Default : SPACE .


IS_VARIANT

Variant information

Description

This structure is only relevant if display variants are to be saved
and/or read.

Variant information including the name of the list variant that is used
to output the list.

To allow display variants to be read within the ALV, you must specify
the acess path using fields REPORT (required field), HANDLE (optional
field) and/or LOG_GROUP (optional field).

If you also want to allow display variants to be saved, you must
additionally fill parameter I_SAVE accordingly.

See also the documentation on IMPORTING parameter I_SAVE.

A variant is uniquely described through:

o The program to which the variant is assigned (REPORT)


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


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


o The user name, if user-specific variants are saved (USERNAME).
You do not have to fill this parameter manually since the variant
name is unique.


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


Value Range

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

Default

If the structure is initial, but saving is active (I_SAVE is not
initial), then IS_VARIANT-REPORT = I_CALLBACK_PROGRAM is set.


For a possible entries help for variants, function module
REUSE_ALV_VARIANT_F4 is available.


I_SCREEN_START_COLUMN
I_SCREEN_START_LINE
I_SCREEN_END_COLUMN
I_SCREEN_END_LINE

OOPS AT A GLANCE

Object orientation (OO), or to be more precise, object-oriented programming, is a problem-solving method in which the software solution reflects objects in the real world.

A comprehensive introduction to object orientation as a whole would go far beyond the limits of this introduction to ABAP Objects. This documentation introduces a selection of terms that are used universally in object orientation and also occur in ABAP Objects. In subsequent sections, it goes on to discuss in more detail how these terms are used in ABAP Objects. The end of this section contains a list of further reading, with a selection of titles about object orientation.

Objects

An object is a section of source code that contains data and provides services. The data forms the attributes of the object. The services are known as methods (also known as operations or functions). Typically, methods operate on private data (the attributes, or state of the object), which is only visible to the methods of the object. Thus the attributes of an object cannot be changed directly by the user, but only by the methods of the object. This guarantees the internal consistency of the object.

Classes

Classes describe objects. From a technical point of view, objects are runtime instances of a class. In theory, you can create any number of objects based on a single class. Each instance (object) of a class has a unique identity and its own set of values for its attributes.

Object References

In a program, you identify and address objects using unique object references. Object references allow you to access the attributes and methods of an object.

In object-oriented programming, objects usually have the following properties:

Encapsulation

Objects restrict the visibility of their resources (attributes and methods) to other users. Every object has an interface, which determines how other objects can interact with it. The implementation of the object is encapsulated, that is, invisible outside the object itself.

Polymorphism

Identical (identically-named) methods behave differently in different classes. Object-oriented programming contains constructions called interfaces. They enable you to address methods with the same name in different objects. Although the form of address is always the same, the implementation of the method is specific to a particular class.

Inheritance

You can use an existing class to derive a new class. Derived classes inherit the data and methods of the superclass. However, they can overwrite existing methods, and also add new ones.

Uses of Object Orientation

Below are some of the advantages of object-oriented programming:

Complex software systems become easier to understand, since object-oriented structuring provides a closer representation of reality than other programming techniques.
In a well-designed object-oriented system, it should be possible to implement changes at class level, without having to make alterations at other points in the system. This reduces the overall amount of maintenance required.
Through polymorphism and inheritance, object-oriented programming allows you to reuse individual components.
In an object-oriented system, the amount of work involved in revising and maintaining the system is reduced, since many problems can be detected and corrected in the design phase.

ALV In BRIEF

Introduction

Here is the definition for ALV from SAP Help: “The ALV Grid control is a flexible tool for displaying lists.

The tool provides common list operations as generic functions and can be enhanced by self-defined options.”

The ALV Grid control is used to build non-hierarchical, interactive, and modern-design lists. As a control, it is a component that is installed on the local PC.

The ALV Grid control provides typical list functions as sorting, filtering, summing, etc.,while also gives the opportunity to develop user functions where needed.
It presents numerous interfaces like Excel Inplace and Crystal Reports.

The wrapper class implemented to encapsulate ALV Grid functionality is “CL_GUI_ALV_GRID”.
There is another way to display lists with ALV utilizing “REUSE_ALV...” functions.

Building Blocks

While preparing a list to be displayed via an ALV grid control, we have some basic components to prepare.
These are;

i. List data:
Obviously, this is the data in an internal table to be listed. Standard ALV functions except sorting makes just read access to the list data. However, sorting changes state of the internal table.
The internal table holding list data may be of any flat type. Deep types are only allowed when set for some functionalities of ALV Grid.

ii. Field Catalog: We use another internal table to define specifications on how the fields of our list will be displayed. This internal table is called the
“field catalog”.
The field catalog must comprise some technical and additional information about display options for each column to be displayed.
There are three procedures to generate the field catalog as “Automatic generation”, “Semi-automatic generation”, and “Manual generation”.
The internal table for the field catalog must be referenced to the dictionary type “LVC_T_FCAT”.

iii. Layout Structure: We fill a structure to specify general layout options for the grid. With this structure we can set general display options, grid customizing, totals options, color adjustments etc...
The layout structure must be of type “LVC_S_LAYO”.

iv. Event Handler: We should define and implement an event handler class if we want to handle events triggered by the ALV Grid instance.
After creating ALV Grid instance, we must register an instance of this event handler class to handle ALV Grid events.

v. Additional Data: To trigger some additional features of ALV Grid we can have some additional data to pass as parameters. For example, initial sorting criteria, buttons to be deactivated, etc...


General Scheme

Now, we can figure out a primitive scheme to prepare our ALV Grid. As a control object, ALV Grid instance requires a container to be linked to the screen.
Generally, an instance of the class “cl_gui_custom_container” is used for this purpose.
Instances of some other container classes such as “cl_gui_docking_container”, “cl_gui_dialogbox_container” may also be used.
In our example we take a custom container.

To create a custom container instance, we need a custom control area on the screen. Step 1.
Add a custom control on the screen which will be related to the custom container.
Let’s give it the name ‘CC_ALV’.
Step 2
Declare global variables to be used for ALV Grid. Code Part 1 – Global data definitions for ALV
*-- Global data definitions for ALV
*--- ALV Grid instance reference DATA gr_alvgrid TYPE REF TO cl_gui_alv_grid .
*--- Name of the custom control added on the screen DATA gc_custom_control_name TYPE scrfname VALUE ‘CC_ALV’ . *--- Custom container instance reference DATA gr_ccontainer TYPE REF TO cl_gui_custom_container .
*--- Field catalog table DATA gt_fieldcat TYPE lvc_t_fcat .
*--- Layout structure DATA gs_layout TYPE lvc_s_layo .

Step 3
Declare your internal table which is supposed to hold the list data. Let’s name it “gt_list”. Here is an example declaration.
*--- Internal table holding list data DATA BEGIN OF gt_list OCCURS 0 . INCLUDE STRUCTURE SFLIGHT .
*--In further sections, some additional fields will added here
*--for some functionality DATA END OF gt_list .

Code Part 2

Declaration of the internal table that will hold the list data Step 4 �� Somewhere in your program before calling list display, fill your list data as you want.
Here, it is not our concern what the data are. We assume the internal table is filled reasonably.
We will use the data of table SFLIGHT as our list data. Step 5 �� Call the screen which comprises the ALV Grid control.
At PBO of this screen we will deal with creating the ALV Grid instance.

CODE Part 3

PBO of the flow logic for the screen containing ALV Grid control *--PBO PROCESS BEFORE OUTPUT . ... MODULE display_alv . ...

Code Part 4

Inside the module ... MODULE display_alv OUTPUT . PERFORM display_alv . ENDMODULE .
Step 6 �� Now, it is high time we wrote something to play. So, this piece will be the one we will deal mainly. What we do is, checking whether an instance of the container (or ALV Grid) exists.
If it exists, refreshing it, and if not, creating and setting ALV for the first display. FORM display_alv .

he 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).

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.

Simple Report

The important function modules are:

· Reuse_alv_list_display

· Reuse_alv_fieldcatalog_merge

· Reuse_alv_events_get

· Reuse_alv_commentary_write

· Reuse_alv_grid_display

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

The important parameters are:

1. Export:

a. I_callback_program : report id

b. I_callback_pf_status_set : routine where a user can set his own pf status or change the

functionality of the existing pf -status.

c. I_callback_user_command : routine where the function codes are handled.

d. I_structure name : name of the dictionary table

e. Is_Layout : structure to set the layout of the report

f. 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)

g. It_events : internal table with a list of all possible events of ALVand their

corresponding routine names.

2. Tables:

a. 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:

1. Export:

a. I_program_name : report id

b. I_internal_tabname : the internal output table

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

2. 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 a list type

1. 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 the

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 SLIS.

2. Export:

I_list_type:

0 = simple list

1 = hierarchical-sequential list

2 = simple block list

3 = hierarchical-sequential block list

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

1. 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 list.

Parameters : same as reuse_alv_list_display

HIERARCHICAL REPORTS

A. REUSE_ALV_HIERSEQ_LIST_DISPLAY

1. Export:

a. I_CALLBACK_PROGRAM

b. I_CALLBACK_PF_STATUS_SET

c. I_CALLBACK_USER_COMMAND

d. IS_LAYOUT

e. IT_FIELDCAT

f. IT_EVENTS

g. I_TABNAME_HEADER : Name of the internal table in the program containing the output data of the

highest hierarchy level.

h. I_TABNAME_ITEM : Name of the internal table in the program containing the output data of the

lowest hierarchy level.

i. IS_KEYINFO : This structure contains the header and item table field names which link the two tables

(shared key).

2. Tables

a. T_OUTTAB_HEADER : Header table with data to be output

b. T_OUTTAB_ITEM : Name of the internal table in the program containing the output data of the

lowest hierarchy level.

BLOCK REPORT

This is used to display 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_DISPLAY

D. REUSE_ALV_BLOCK_HS_LIST_APPEND

A. REUSE_ALV_BLOCK_LIST_INIT

Parameters:

a. I_CALLBACK_PROGRAM

b. I_CALLBACK_PF_STATUS_SET

c. I_CALLBACK_USER_COMMAND

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

B. REUSE_ALV_BLOCK_LIST_APPEND

Export :

a. IS_LAYOUT : layout settings for block

b. IT_FIELDCAT : field catalog

c. I_TABNAME : Internal table name of the output data

d. IT_EVENTS : internal table name with all possible events

Tables :

a. T_OUTTAB : internal table with output data.

This function module adds the data to the block.

INTERNAL TABLES IN SLIS

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. hotspot(1) : hotspot

i. Symbol(1) : symbol

j. Checkbox(1) : checkbox

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

l. do_sum(1) : sum up

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

n. outputlen : output length

o. seltext-l : long key word

p. seltext_m : middle key word

q. seltext_s : short key word

r. reptext_ddic : heading(ddic)

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

t. datatype : datatype

SLIS_T_EVENT :

Internal table for storing all the possible events of the ALV. This can be populated by the function module Reuse_alv_events_get

The columns are :

name : name of the event

form : name of the routine

SYNTAXES FOR THE ROUTINES

I_CALLBACK_PF_STATUS_SET

Syntax :

FORM set_pf_status USING rt_extab TYPE slis_t_extab

The table RT_EXTAB contains the function codes which are hidden in the standard interface.

I_CALLBACK_USER_COMMAND

Syntax :

FORM user_command USING r_ucomm LIKE sy-ucomm

rs_selfield TYPE slis_selfield.

The parameter r_ucomm contains the function code.

The structure rs_selfield has the details about the current cursor position

Performance Tuning

For all entries
The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of
entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the
length of the WHERE clause.

The plus

* Large amount of data
* Mixing processing and reading of data
* Fast internal reprocessing of data
* Fast

The Minus

* Difficult to program/understand
* Memory could be critical (use FREE or PACKAGE size)

Some steps that might make FOR ALL ENTRIES more efficient:

* Removing duplicates from the the driver table
* Sorting the driver table

If possible, convert the data in the driver table to ranges so a BETWEEN statement is used instead of and OR statement:
FOR ALL ENTRIES IN i_tab
WHERE mykey >= i_tab-low and
mykey <= i_tab-high. Nested selects The plus: * Small amount of data * Mixing processing and reading of data * Easy to code - and understand The minus: * Large amount of data * when mixed processing isn’t needed * Performance killer no. 1 Select using JOINS The plus * Very large amount of data * Similar to Nested selects - when the accesses are planned by the programmer * In some cases the fastest * Not so memory critical The minus * Very difficult to program/understand * Mixing processing and reading of data not possible Use the selection criteria SELECT * FROM SBOOK. CHECK: SBOOK-CARRID = 'LH' AND SBOOK-CONNID = '0400'. ENDSELECT. SELECT * FROM SBOOK WHERE CARRID = 'LH' AND CONNID = '0400'. ENDSELECT. Use the aggregated functions C4A = '000'. SELECT * FROM T100 WHERE SPRSL = 'D' AND ARBGB = '00'. CHECK: T100-MSGNR > C4A.
C4A = T100-MSGNR.
ENDSELECT.

SELECT MAX( MSGNR ) FROM T100 INTO C4A
WHERE SPRSL = 'D' AND
ARBGB = '00'.

Select with view

SELECT * FROM DD01L
WHERE DOMNAME LIKE 'CHAR%'
AND AS4LOCAL = 'A'.
SELECT SINGLE * FROM DD01T
WHERE DOMNAME = DD01L-DOMNAME
AND AS4LOCAL = 'A'
AND AS4VERS = DD01L-AS4VERS
AND DDLANGUAGE = SY-LANGU.
ENDSELECT.

SELECT * FROM DD01V
WHERE DOMNAME LIKE 'CHAR%'
AND DDLANGUAGE = SY-LANGU.
ENDSELECT.

Select with index support

SELECT * FROM T100
WHERE ARBGB = '00'
AND MSGNR = '999'.
ENDSELECT.

SELECT * FROM T002.
SELECT * FROM T100
WHERE SPRSL = T002-SPRAS
AND ARBGB = '00'
AND MSGNR = '999'.
ENDSELECT.
ENDSELECT.

Select … Into table

REFRESH X006.
SELECT * FROM T006 INTO X006.
APPEND X006.
ENDSELECT

SELECT * FROM T006 INTO TABLE X006.

Select with selection list

SELECT * FROM DD01L
WHERE DOMNAME LIKE 'CHAR%'
AND AS4LOCAL = 'A'.
ENDSELECT

SELECT DOMNAME FROM DD01L
INTO DD01L-DOMNAME
WHERE DOMNAME LIKE 'CHAR%'
AND AS4LOCAL = 'A'.
ENDSELECT

Key access to multiple lines

LOOP AT TAB.
CHECK TAB-K = KVAL.
" ...
ENDLOOP.

LOOP AT TAB WHERE K = KVAL.
" ...
ENDLOOP.

Copying internal tables

REFRESH TAB_DEST.
LOOP AT TAB_SRC INTO TAB_DEST.
APPEND TAB_DEST.
ENDLOOP.

TAB_DEST[] = TAB_SRC[].

Modifying a set of lines

LOOP AT TAB.
IF TAB-FLAG IS INITIAL.
TAB-FLAG = 'X'.
ENDIF.
MODIFY TAB.
ENDLOOP.

TAB-FLAG = 'X'.
MODIFY TAB TRANSPORTING FLAG
WHERE FLAG IS INITIAL.

Deleting a sequence of lines

DO 101 TIMES.
DELETE TAB_DEST INDEX 450.
ENDDO.

DELETE TAB_DEST FROM 450 TO 550.

Linear search vs. binary

READ TABLE TAB WITH KEY K = 'X'.

READ TABLE TAB WITH KEY K = 'X' BINARY SEARCH.

Comparison of internal tables

DESCRIBE TABLE: TAB1 LINES L1,
TAB2 LINES L2.

IF L1 <> L2.
TAB_DIFFERENT = 'X'.
ELSE.
TAB_DIFFERENT = SPACE.
LOOP AT TAB1.
READ TABLE TAB2 INDEX SY-TABIX.
IF TAB1 <> TAB2.
TAB_DIFFERENT = 'X'. EXIT.
ENDIF.
ENDLOOP.
ENDIF.

IF TAB_DIFFERENT = SPACE.
" ...
ENDIF.

IF TAB1[] = TAB2[].
" ...
ENDIF.

Modify selected components

LOOP AT TAB.
TAB-DATE = SY-DATUM.
MODIFY TAB.
ENDLOOP.

WA-DATE = SY-DATUM.
LOOP AT TAB.
MODIFY TAB FROM WA TRANSPORTING DATE.
ENDLOOP.

Appending two internal tables

LOOP AT TAB_SRC.
APPEND TAB_SRC TO TAB_DEST.
ENDLOOP

APPEND LINES OF TAB_SRC TO TAB_DEST.

Deleting a set of lines

LOOP AT TAB_DEST WHERE K = KVAL.
DELETE TAB_DEST.
ENDLOOP

DELETE TAB_DEST WHERE K = KVAL.

Tools available in SAP to pin-point a performance problem

The runtime analysis (SE30)

SQL Trace (ST05)

Tips and Tricks tool

The performance database

Optimizing the load of the database
Using table buffering
Using buffered tables improves the performance considerably. Note that in some cases a stament can not be used with a buffered table, so when using these staments the buffer will be bypassed. These staments are:

* Select DISTINCT
* ORDER BY / GROUP BY / HAVING clause
* Any WHERE clasuse that contains a subquery or IS NULL expression
* JOIN s
* A SELECT... FOR UPDATE

If you wnat to explicitly bypass the bufer, use the BYPASS BUFFER addition to the SELECT clause.
Use the ABAP SORT Clause Instead of ORDER BY
The ORDER BY clause is executed on the database server while the ABAP SORT statement is executed on the application server. The datbase server will usually be the bottleneck, so sometimes it is better to move thje sort from the datsbase server to the application server.

If you are not sorting by the primary key ( E.g. using the ORDER BY PRIMARY key statement) but are sorting by another key, it could be better to use the ABAP SORT stament to sort the data in an internal table. Note however that for very large result sets it might not be a feasible solution and you would want to let the datbase server sort it.
Avoid ther SELECT DISTINCT Statement
As with the ORDER BY clause it could be better to avoid using SELECT DISTINCT, if some of the fields are not part of an index. Instead use ABAP SORT + DELETE ADJACENT DUPLICATES on an internal table, to delete duplciate rows.

ABAP - Questions

What is a 'Z' report?
Y or Z report refer to customized abap programs written for modules such as mm, sd, pp or fi/co etc.

Can we create an ABAP program without using Y or Z?
No, this is because all non Yor Z programs are standard SAP programs.

1. How data is stored in cluster table?
Each field of cluster table behaves as tables which contains the no. of entries.

2. What are client dependant objects in abap/sap?
SAP Script layout, text element, and some DDIC objects.

3. On which even we can validate the input fields in module progams?
In PAI (Write field statement on field you want to validate, if you want to validate group of fields put in chain and End chain statement.)

4. In selection screen I have three fields, plant mat no and material group. If I input plant how do I get the mat no and material group based on plant dynamically?
AT SELECTION-SCREEN ON VALUE-REQUEST FOR MATERIAL.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST' to get material and material group for the plant.

5. How do you get output from IDOC?
Data in IDOc is stored in segments, the output from Idoc is obtained by reading the data stored in its respective segments.

6. When top of the page event is triggered?
After excuteing first write statement in start-of-selection event.

7. Can we create field without data element and how?
In SE11 one option is available above the fields strip. Data element/ direct type.

8. How do we debug sapscript?
Go to SE71 give lay set name , go to utilities select debugger mode on.

9. Which transaction code can I used to analyze the performance of ABAP program.
TCode AL21.

10. How can I copy a standard table to make my own z_table.
Go to transaction SE11. Then there is one option to copy table. Press that button. Enter the name of the standard table and in the Target table enter Z table name and press enter.

Following are some of the answers which I gave upto my knowledge.

1. What is the use of 'outerjoin'
Ans. With the use of outer join you can join the tables even there is no entry in all the tables used in the view.
In case of inner join there should be an entry in al the tables use in the view.

2. When to use logical database?
Ans. Advantage of Logical databases:
less coding s required to retrieve data compared to normal internel tables.
Tables used LDB are in hierarchial structure.

3. What is the use of 'table index'?
Ans .Index is used for faster access of data base tables.

4. What is the use of 'FOR ALL ENTRIES'?
Ans. To avoid nested select statements we use SELECT FOR ALL ENTRIES statement.
If there r more than 10000 records SELECT FOR ALL ENTRIES is used.
Performance wise SELECT FOR ALL ENTRIES is better to use.

5. Can you set up background processing using CALL TRANSACTION?
Yes,Using No Screen Mode.

6. What are table buffers?

Table buffers reside locally on each application server in the system. The data of buffered tables can thus be accessed directly from the buffer of the application server. This avoids the time-consuming process of accessing the database. Buffering is useful if table needs to be accessed more no. of times in a program.

1. How do I set a flag for a field in any table?
Create a char field of length 1. for example field STAS-LKENZ is Deletion Indicator. It means that if the value in the field is 'X' then that record has been deleted.

2. Can I execute user exits? If yes, how?
Yes you can. after finding the user exit, you need to use, goto CMOD add ur user-exit to your project. Then activate the FM which you require. Now go into that function module there will be a Include program wit name ZX* . Double click on it, it will ask to create an object, answer it Yes and then write your code in it.

3. How do I find the output type of a table or a program?
Table TNAPR / NAST

4. How to execute a program step by step on the ABAP editor?

First test your code with '/h' type in command window which shall take you to debug or by putting break points with F8. You test your program from code and then go to se30 performance analysis transaction and there you can know what are the drawbacks. Then go to SLIN transaction and do extended syntax check or from code in menu options where you have debugging -> extended check and the program id ready without error.

Tips by : Harichand Chandunair

Testing your code.

As mentioned above after doing syntax check and extended syntax check you have to create a TEST PLAN. You have to test all possible Postive & Negative test cases.

Test for division by zero if it involves calculation or code accordingly.

Try to test for field overflows. If it involves sap script or smart forms try to print outputs which have single page and also multiple page and which does not have any output at all.

Test by leaving all parameters in selection screen blank.

Test by entering wrong values in selection screen and display a pop-up if the user enters wrong selection screen values.

You can also do ABAP trace and SQL trace to make sure that your program is efficient.

Debugging code/program.

As mentioned above type /h in command line and try to execute the program. Another way is to set break-point at the function module or the required line and do single step execute or execute. Once you finished debugging, you can select Delete to clear all the break points.

5) What are dml statements in sap?

Ans: Insert, Update, Delete.

What is the difference between open sql & native sql?

Ans: Open SQL allows you to access all database tables known to the SAP system, regardless of the database manufacturer. Sometimes, however, we may want to use database-specific SQL statements called Native SQL in your ABAP/4 program. To avoid incompatibilities between different database tables and also to make ABAP/4 programs independent of the database system in use, SAP has created a set of separate SQL statements called Open SQL. Open SQL contains a subset of standard SQL statements as well as some enhancements which are specific to SAP.

A database interface translates SAP's Open SQL statements into SQL commands specific to the database in use. Native SQL statements access the database directly

What is Primary key, foreign key ? what is primary index? secondary index?

Ans: Primary index: the primary index contains key fiels of a table and a pointer to non-key fields of the table. The primary index is created automatically when a table is created in database and moreover you can further define reference to the primary index which are known as Secondary index.

How many indexes can be created for a table?

Ans: 9.

What is data class?

Ans: The data class specifies in which table space the table is created in database.

Give few names of cluster tables in sap?

Ans: sorry i dont know

Give few names of pooled tables in sap?

Ans: A pool table has many to one relation with the table in the database. For one table in the database there are many tables in the dictionary. Tha table in the database has a diff name than in the table in the data dict, it has diff no of fields and field names are different. A pooled table is stored in the pool at the database level. A table pool is a databse table with a special struct that enables the data of many R3 tables to be stored in it. It can hold only pooled tables.
Sorry I dont know table names

Give few names of transparent tables?

Ans: A transparent table has a one to one relataionship in the database. The table in the dictionary has the same name, same no of fields, and the fields have the same name as in the R3 table defn. A transparent tabel has application data (Master and Transaction). sorry i dont know table names

What is a buffer and how many types?

Ans: Buffer is othing but which stores data temporarily. there are two types of buffers. they are Roll and Page areas.
Pages : it stores the application data.
Roll area: it stores the data of previous pages.Data areas of used programs are created in roll areas for each internal session.

What is table maintenance generator and how to create that? What is the transaction code?

Ans: Table maintanence generator is nothing but making a table available for adding records and deleting records.
The transaction code used is SM30.

How to add new fields to a standard sap table?

Ans: 1. Appended structures 2. Customizing tables

What are lock objects?

Ans: Lock objects are nothing but which holds a data for particular field value until you remove a lock..

Diff betwn inner & outer join?

Ans:

What is the use of start-of-selection event?

Ans: Start-of-selection is called implicity even it is not used in the program. start-of-selection is triggered after the standard selection screen has been displayed.

What is the difference between end-of-page and end-of-selection?

Ans: End-of-page : is footer of the page. End-of-selection: is triggered At the end of the processing block.

If you write a write statement after end-of-selection, will that be triggered?

Ans: Yes

How to create a button in selection screen?

Ans: Using parametres

How to add a gui status in a selection screen?

Ans: sorry i dont know i thik using set pf.

How to create a check box/option button in a list?

Ans:

For this...

Create an Internal table as :

data: Begin itab occurs 0,
cb_field type char1,
matnr like mara-matnr,
.....
end of itab.

Now you fetch the data into the internal table of itab using
some query...

select * ......

Now you are going to display it as....

Loop at itab.
write:/ cb_field as checkbox...
......
at this time only write the Hide statement.... as...

HIDE: values.... u want...

Endloop..

Now capturing of selected data process...

This can be done by clicking on some USER Command button...

for suppose you're clicking F8 means...

AT pf8.
IF SY-LSIND = 1.
describe table itab lines VARIABLE NAME.
cnt = 3. " Initiate value for Count 3 if you're including page header.
do VARIABLE NAME times.
read line cnt. " Above counter....
if sy-lisel(1) = 'X'.
WRITE:/ 'SELECTED RECORDS:', itab-cb_field,.....
endif.
COUNTER = COUNTER - 1.
cnt = cnt + 1.
enddo.
ENDIF.

Can you call a bdc program from a report? how?

Ans: Yes through Submit and return

Can you call a transaction from a report? how?

Ans: Yes Using Call transaction and leave to.

What are ALV reports? how they are different from normal reports?
Ans: these reports are used to find subtotals and totals in a report. If you want i'll give you an example program

What are the main events that are used in an ALV report?
Ans: sorry i dont know

What is the use of SLIS type pool in alv reports?

Ans: Slis type pool is a global defination of pooltypes of catalog structure, table and layout which we use in ALV reports

Difference between top-of-page and top-of-page during at-line- selection?

Ans: Top-of-page is a header on primary list. Top-of-page during line-selection is a header on secondary lists

In an interactive report, after going to 5th list, can you come back to 2nd list? how?

How many type of internal tables are there?

Ans: Standard, Hashed, Sorted tables

What is the difference between hashed & sorted internal tables?

Ans: Sorted internal table works on Binary Search and Hashed internal tables works on hashed alogorthim through indexes.

What is the difference between standard and sorted internal tables? (in performance wise)

Ans: Sorted table improve the performance in case of a huge table which has no: of records

What is the use of at new statement?

Ans:sorry i dont know

When do you need to create an internal table with header line? and with out a header line? line?

Ans: If we don't want to use any explicit work area then its better to go for an internal table with header line.

What does it mean occurs 0 while creating an internal table?

Ans: sorry i dont know

Which of these methods can be best used in background process?

Ans : Batch Input method.

What is direct input method?

What does an EXEC SQL stmt do in ABAP? What is the disadvantage of using it?

Ans: Exec Sql[Performing [Native sql statements]
endexec.
The above is the syntax for the native sql statements.

Disadvantages:

. Syntax check is not done to statements written inside the EXEC SQL statements.

What is the meaning of ABAP/4 editor integrated with ABAP/4 data dictionary?

What transactions do you use for data analysis?

ANs: Sorry i dont know but for runtime analysis we use transaction code : se30.

What are selection texts?

Ans: in the selection screen you can change the name of the field,title etc using selection texts. go to text--> text elemets---> selection texts in the menu bar to set selection texts.

What is the client concept in SAP? What is the meaning of client independent?

How to find the return code of a statement in ABAP programs?

Ans: Through functions.

What are steps you follow to improve the performance of a report?

Ans: 1) USe select fields statements (not select *)
2) Use views rather than tables
3) Don't use nested Select.

What is the role of secondary index in performance?

Ans: sorry i dont know

What is the role of ST05 in performance tuning?

Ans: SQL trace

What is the role of extended syntax check in performance tuning?

Ans: sorry i dont know

Will join conditions in sql queries affect perfomance? how?

Ans : Yes

Will sorted internal tables help in performance?

Ans: Yes

Will where conditions in a sql query help improve performance?

Ans: No Not at all

ABAP - Interview Questions 3

1. What is the typical structure of an ABAP/4 program?
HEADER ,BODY,FOOTER.

2. What are field symbols and field groups.?
Have you used "component idx of structure" clause with field groups?

Field symbols:-

Field groups :-

Can any body explain me what is field group?

Field groups are groups similar fields together into one name. Field group works in conjuction with

INSERT f1 f2 INTO fg
EXTRACT fg
SORT BY fg
LOOP ... ENDLOOP

INSERT f1 f2 INTO fg
---------------------

The insert statement is used to create a field group dynamically by inserting the field into it. Only global data fields can be inserted and not local data fields eg : in form modules.

EXTRACT fg
----------

This will combine all the fields in the fieldgroup and write them to a sequential dataset as a single record.

SORT BY fg
----------

Sorting of sequential dataset by field group.

LOOP AND ENDLOOP
---------------

LOOP.
AT ***
......
....
ENDAT.
AT ***
.....
....
ENDAT.
ENDLOOP. *-- Chinmaya

3. What should be the approach for writing a BDC program?
ANS:-
STEP 1: CONVERTING THE LEGACY SYSTEM DATA TO A FLAT FILE to internal table CALLED "CONVERSION".
STEP 2: TRANSFERING THE FLAT FILE INTO SAP SYSTEM CALLED "SAP DATA TRANSFER".
STEP 3: DEPENDING UPON THE BDC TYPE i)call transaction(Write the program explicity)
ii) create sessions (sessions are created and processed.if success data will transfer).

4. What is a batch input session?
ANS:-
BATCH INPUT SESSION is an intermediate step between internal table and database table.
Data along with the action is stored in session ie data for screen fields, to which screen it is passed,program name behind it, and how next screen is processed.

5. What is the alternative to batch input session?
ANS:-
Call transaction.

6. A situation: An ABAP program creates a batch input session.
We need to submit the program and the batch session in back ground. How to do it?
ANS:-
go to SM36 and create background job by giving
job name,job class and job steps (JOB SCHEDULING)

8. What are the problems in processing batch input sessions?
How is batch input process different from processing online?
ANS:-
PROBLEMS:-
i) If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually.
ii)if session processing fails data will not be transferred to SAP database table.

10. What are the different types of data dictionary objects?
ans:-
tables, structures, views, domains, data elements, lock objects, Matchcode objects.

11. How many types of tables exists and what are they in data dictionary?
ans :-
4 types of tables
i)Transparent tables - Exists with the same structure both in dictionary as well as in database exactly with the same data and fields. Both Opensql and Nativesql can be used.

ii)Pool tables & iii)Cluster tables -
These are logical tables that are arranged as records of transparent tables.one cannot use native sql on these tables
(only opensql).They are not managable directly using database system tools.

iv)Internal tables - .

12. What is the step by step process to create a table in data dictionary?
ans:-
step 1: creating domains(data type,field length,range).
step 2: creating data elements(properties and type for a table
field).
step 3: creating tables(SE11).

13. Can a transparent table exist in data dictionary but not in the data base physically?
ANS:- NO.
TRANSPARENT TABLE DO EXIST WITH THE SAME STRUCTURE BOTH IN THE DICTIONARY AS WELL AS IN THE DATABASE,EXACTLY WITH THE SAME DATA AND FIELDS.

14. What are the domains and data elements?
ANS:-
DOMAINS : FORMAL DEFINITION OF THE DATA TYPES.THEY SET ATTRIBUTES SUCH AS DATA TYPE,LENGTH,RANGE.
DATA ELEMENT : A FIELD IN R/3 SYSTEM IS A DATA ELEMENT.

15. Can you create a table with fields not referring to data elements?
ANS:-
YES. eg:- ITAB LIKE SPFLI.here we are referening to a data object(SPFLI) not data element.

16. What is the advantage of structures? How do you use them in the ABAP programs?
ANS:-
Adv:- GLOBAL EXISTANCE(these could be used by any other program without creating it again).

17. What does an extract statement do in the ABAP program?
ANS:-
Once you have declared the possible record types as field groups and defined their structure, you can fill the extract dataset using the following statements:
EXTRACT .

When the first EXTRACT statement occurs in a program, the system creates the extract dataset and adds the first extract record to it. In each subsequent EXTRACT statement, the new extract record is added to the dataset

EXTRACT HEADER.

When you extract the data, the record is filled with the current values of the corresponding fields.

As soon as the system has processed the first EXTRACT statement for a field group , the structure of the corresponding extract record in the extract dataset is fixed. You can no longer insert new fields into the field groups and HEADER. If you try to modify one of the field groups afterwards and use it in another EXTRACT statement, a runtime error occurs.

By processing EXTRACT statements several times using different field groups, you fill the extract dataset with records of different length and structure. Since you can modify field groups dynamically up to their first usage in an EXTRACT statement, extract datasets provide the advantage that you need not determine the structure at the beginning of the program.

18. What is a collect statement? How is it different from append?
ANS:-
If an entry with the same key already exists, the COLLECT statement does not append a new line, but adds the contents of the numeric fields in the work area to the contents of the numeric fields in the existing entry.

19. What is open sql vs native sql?
ANS:- by Madhukar
Open SQL , native SQL are the interfaces to create the database applicatons.
Open SQL is consistant across different types of existing Databases.
Native SQL is the database language specific to database.Its API is specific to the databse.
Open SQL API is consistent across all vendors

20. What does an EXEC SQL stmt do in ABAP? What is the disadvantage of using it?
ANS:-

21. What is the meaning of ABAP/4 editor integrated with ABAP/4 data dictionary?
ANS:-

22. What are the events in ABAP/4 language?
ANS:-
Initialization, At selection-screen,Start-of-selection,end-of-selection,top-of-page,end-of-page, At line-selection,At user-command,At PF,Get,At New,At LAST,AT END, AT FIRST.

23. What is an interactive report?
What is the obvious diff of such report compared with classical type reports?
ANS:-
An Interactive report is a dynamic drill down report that produces the list on users choice.
diff:-
a) THE LIST PRODUCED BY CLASSICAL REPORT DOESN'T allow user to interact with the system
the list produced by interactive report allows the user to interact with the system.
b) ONCE A CLASSICAL REPORT EXECUTED USER LOOSES CONTROL.IR USER HAS CONTROL.
c) IN CLASSICAL REPORT DRILLING IS NOT POSSIBLE.IN INTERACTIVE DRILLING IS POSSIBLE.

24. What is a drill down report?
ANS:-
Its an Interactive report where in the user can get more relavent data by selecting explicitly.

25. How do you write a function module in SAP? describe.
ANS:-
creating function module:-
called program - se37-creating funcgrp,funcmodule by assigning attributes,importing,exporting,tables,exceptions.
calling program - SE38-in pgm click pattern and write function name- provide export,import,tables,exception values.

26. What are the exceptions in function module?
ANS:-
COMMUNICATION_FAILURE
SYSTEM_FAILURE

27. What is a function group?
ANS:-
GROUP OF ALL RELATED FUNCTIONS.

28. How are the date and time field values stored in SAP?
ANS:-
DD.MM.YYYY. HH:MM:SS

30. Name a few data dictionary objects? //rep//
ANS:-
TABLES,VIEWS,STRUCTURES,LOCK OBJECTS,MATCHCODE OBJECTS.

31. What happens when a table is activated in DD?
ANS:-
It is available for any insertion,modification and updation of records by any user.

32. What is a check table and what is a value table?
Check table will be at field level checking.
Value table will be at domain level checking ex: scarr table is check table for carrid.

33. What are match codes? describe?
ans:-
It is a similar to table index that gives list of possible values for either primary keys or non-primary keys.

34. What transactions do you use for data analysis?
ANS:-

35. What is table maintenance generator?
ANS:-

36. What are ranges? What are number ranges?
ANS:-
max,min values provided in selection screens.

37. What are select options and what is the diff from parameters?
ANS:-
select options provide ranges where as parameters do not.

SELECT-OPTIONS declares an internal table which is automatically filled with values or ranges
of values entered by the end user. For each SELECT-OPTIONS , the system creates a selection table.

SELECT-OPTIONS FOR .

A selection table is an internal table with fields SIGN, OPTION, LOW and HIGH.
The type of LOW and HIGH is the same as that of .
The SIGN field can take the following values: I Inclusive (should apply) E Exclusive (should not apply)
The OPTION field can take the following values: EQ Equal GT Greater than NE Not equal BT Between LE Less
than or equal NB Not between LT Less than CP Contains pattern GE Greater than or equal NP No pattern.
diff:-
PARAMETERS allow users to enter a single value into an internal field within a report.
SELECT-OPTIONS allow users to fill an internal table with a range of values.

For each PARAMETERS or SELECT-OPTIONS statement you should define text elements by choosing
Goto - Text elements - Selection texts - Change.

Eg:- Parameters name(30).
when the user executes the ABAP/4 program,an input field for 'name' will appear on the selection screen.You can change the comments on the left side of the input fields by using text elements as described in Selection Texts.

38. How do you validate the selection criteria of a report?
And how do you display initial values in a selection screen?
ANS:-
validate :- by using match code objects.
display :- Parameters default 'xxx'.
select-options for spfli-carrid.

39. What are selection texts?
ANS:-

40. What is CTS and what do you know about it?
ANS:-

The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems and clients in your system landscape.
This documentation provides you with an overview of how to manage changes with the CTS and essential information on setting up your system and client landscape and deciding on a transport strategy. Read and follow this documentation when planning your development project.
For practical information on working with the Change and Transport System, see Change and Transport Organizer and Transport Management System.

41. When a program is created and need to be transported to prodn does selection texts always go with it? if not how do you make sure? Can you change the CTS entries? How do you do it?
ANS:-

42. What is the client concept in SAP? What is the meaning of client independent?
ANS:-

43. Are programs client dependent?
ANS:-
Yes.Group of users can access these programs with a client no.

44. Name a few system global variables you can use in ABAP programs?
ANS:-
SY-SUBRC,SY-DBCNT,SY-LILLI,SY-DATUM,SY-UZEIT,SY-UCOMM,SY-TABIX.....
SY-LILLI IS ABSOLUTE NO OF LINES FROM WHICH THE EVENT WAS TRIGGERED.

45. What are internal tables? How do you get the number of lines in an internal table?
How to use a specific number occurs statement?
ANS:-
i)It is a standard data type object which exists only during the runtime of the program.
They are used to perform table calculations on subsets of database tables and for re-organising the contents of database tables according to users need.
ii)using SY-DBCNT.
iii)The number of memory allocations the system need to allocate for the next record population.

46. How do you take care of performance issues in your ABAP programs?
Performance of ABAPs can be improved by minimizing the amount of data to be transferred.
The data set must be transferred through the network to the applications, so reducing the amount OF time and also reduces the network traffic.

Some measures that can be taken are:

- Use views defined in the ABAP/4 DDIC (also has the advantage of better reusability).
- Use field list (SELECT clause) rather than SELECT *.
- Range tables should be avoided (IN operator)
- Avoid nested SELECTS.

i)system tools

ii)field symbols and field groups.
ans:-
Field Symbols : Field symbols are placeholders for existing fields. A Field Symbol does not physically reserve space for a field,but points to a field which is not known until runtime of the program.
eg:- FIELD-SYMBOL [].

Field groups : A field group combines several fields under one name.At runtime,the INSERT command is used to define which data fields are assigned to which field group.
There should always be a HEADER field group that defines how the extracted data will be sorted,the data is sorted by the fields grouped under the HEADER field group.

47. What are datasets?
ANS:-
The sequential files(ON APPLICATION SERVER) are called datasets. They are used for file handling in SAP.

48. How to find the return code of a statement in ABAP programs?
ANS:-
Using function modules.

49. What are interface/conversion programs in SAP?
ANS :
CONVERSION : LEGACY SYSTEM TO FLAT FILE.
INTERFACE : FLAT FILE TO SAP SYSTEM.

51. What are the techniques involved in using SAP supplied programs?
Do you prefer to write your own programs to load master data? Why?

52. What are logical databases? What are the advantages/disadvantages of logical databases?
ANS:-
To read data from a database tables we use logical database.
A logical database provides read-only access to a group of related tables to an ABAP/4 program.

adv:-
The programmer need not worry about the primary key for each table.Because Logical database knows how the different tables relate to each other,and can issue the SELECT command with proper where clause to retrieve the data.
i)An easy-to-use standard user interface.
ii)check functions which check that user input is complete,correct,and plausible.
iii)meaningful data selection.
iv)central authorization checks for database accesses.
v)good read access performance while retaining the hierarchical data view determined by the application logic.

disadv:-
i)If you donot specify a logical database in the program attributes,the GET events never occur.
ii)There is no ENDGET command,so the code block associated with an event ends with the next event
statement (such as another GET or an END-OF-SELECTION).

53. What specific statements do you using when writing a drill down report?
ans:-
AT LINE-SELECTION,AT USER-COMMAND,AT PF.

54. What are different tools to report data in SAP? What all have you used?
ans:-

55. What are the advantages and disadvantages of ABAP/4 query tool?

56. What are the functional areas? User groups? and how does ABAP/4 query work in relation to these?

57. Is a logical database a requirement/must to write an ABAP/4 query?

59. What are Change header/detail tables? Have you used them?

60. What do you do when the system crashes in the middle of a BDC batch session?
ans:-
we will look into the error log file (SM35).

61. What do you do with errors in BDC batch sessions?
ANS:-
We look into the list of incorrect session and process it again. To correct incorrect session we analyize the session to determine which screen and value produced the error.For small errors in data we correct them interactively otherwise
modify batch input program that has generated the session or many times even the datafile.

62. How do you set up background jobs in SAP? What are the steps? What are the event driven batch jobs?
ans:-
go to SM36 and create background job by giving job name,job class and job steps(JOB SCHEDULING)

63. Is it possible to run host command from SAP environment? How do you run?

64. What kind of financial periods exist in SAP? What is the relavent table for that?

65. Does SAP handle multiple currencies? Multiple languages?
ans:-
Yes.

66. What is a currency factoring technique?

67. How do you document ABAP/4 programs? Do you use program documentation menu option?

68. What is SAPscript and layout set?
ans:-
The tool which is used to create layout set is called SAPscript. Layout set is a design document.

69. What are the ABAP/4 commands that link to a layout set?
ans:-
control commands,system commands,

70. What is output determination?

71. What are IDOCs?
ans:-
IDOCs are intermediate documents to hold the messages as a container.

72. What are screen painter? menu painter? Gui status? ..etc.
ans:-
dynpro - flow logic + screens.
menu painter -
GUI Status - It is subset of the interface elements(title bar,menu bar,standard tool bar,push buttons) used for a certain screen.
The status comprises those elements that are currently needed by the transaction.

73. What is screen flow logic? What are the sections in it? Explain PAI and PBO.
ans:-
The control statements that control the screen flow.
PBO - This event is triggered before the screen is displayed.
PAI - This event is responsible for processing of screen after the user enters the data and clicks the pushbutton.

74. Overall how do you write transaction programs in SAP?
ans:-
Create program-SE93-create transcode-Run it from command field.

75. Does SAP has a GUI screen painter or not? If yes what operating systems is it available on? What is the other type of screen painter called?

76. What are step loops? How do you program pagedown pageup in step loops?
ans:-
step loops are repeated blocks of field in a screen.

77. Is ABAP a GUI language?
ANS:-
Yes.
ABAP IS AN EVENT DRIVEN LANGUAGE.

78. Normally how many and what files get created when a transaction program is written?
What is the XXXXXTOP program?
ans:-
ABAP/4 program.
DYNPRO

79. What are the include programs?
ANS:-
When the same sequence of statements in several programs are to be written repeadly they are coded in include programs (External programs) and are included in ABAP/4 programs.

80. Can you call a subroutine of one program from another program?
ans:- Yes- only external subroutines Using 'SUBMIT' statement.

81. What are user exits? What is involved in writing them? What precations are needed?

82. What are RFCs? How do you write RFCs on SAP side?

83. What are the general naming conventions of ABAP programs?
ANS:-
Should start with Y or Z.

84. How do you find if a logical database exists for your program requrements?
ans:-
SLDB-F4.

85. How do you find the tables to report from when the user just tell you the transaction he uses? And all the underlying data is from SAP structures?
ans:-
Transcode is entered in command field to open the table.Utilities-Table contents-display.

86. How do you find the menu path for a given transaction in SAP?
ans:-

87. What are the different modules of SAP?
ans:-
FI,CO,SD,MM,PP,HR.

89. How do you get help in ABAP?
ans:-
HELP-SAP LIBRARY,by pressing F1 on a keyword.

90. What are different ABAP/4 editors? What are the differences?
ans:-

91. What are the different elements in layout sets?
ans:-
PAGES,Page windows,Header,Paragraph,Character String,Windows.

92. Can you use if then else, perform ..etc statements in sap script?
ans:-
yes.

93. What type of variables normally used in sap script to output data?

94. How do you number pages in sapscript layout outputs?

95. What takes most time in SAP script programming?
ANS:-
LAYOUT DESIGN AND LOGO INSERTION.

96. How do you use tab sets in layout sets?

97. How do you backup sapscript layout sets? Can you download and upload? How?

98. What are presentation and application servers in SAP?
ANS:-
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.

99. In an ABAP/4 program how do you access data that exists on a presentation server vs on an application server?
ans:-
i)using loop statements.
ii)flat

100. What are different data types in ABAP/4?
ans:-
Elementary -
predefined C,D,F,I,N,P,T,X.
userdefined TYPES.
ex: see in intel book page no 35/65

Structured -
predefined TABLES.
userdefined Field Strings and internal tables.

101. What is difference between session method and Call Transaction?
ans:-

102. Setting up a BDC program where you find information from?
ans:-

103. What has to be done to the packed fields before submitting to a BDC session.
ans:-
fields converted into character type.

104. What is the structure of a BDC sessions.
ans:-
BDCDATA (standard structure).

105. What are the fields in a BDC_Tab Table.
ans:-
program,dynpro,dynbegin,fnam,fval.

106. What do you define in the domain and data element.
Technical details like

107. What is the difference between a pool table and a transparent table and how they are stored at the database level.
ans:-
ii)Pool tables is a logical representation of transparent tables .Hence no existence at database level. Where as transparent tables are physical tables and exist at database level.

108. What is cardinality?
For cardinality one out of two (domain or data element) should be the same for Ztest1 and Ztest2 tables. M:N
Cardinality specifies the number of dependent(Target) and independent (source) entities which can be in a relationship.

TRANSACTION CODES - OTHERS

Config Related

OLE	OLE demo transaction
OLI0	C Plant Maintenance Master Data
OLI1	Set Up INVCO for Material Movements
OLI8	Set Up SIS for Deliveries
OLIA	C Maintenance Processing
OLIP	C Plant Maintenance Planning
OLIQ	New set-up of QM info system
OLIX	Set Up Copying/Deleting of Versions
OLIY	Set Up Deletion of SIS/Inter.Storage
OLIZ	Stat Set Up INVCO: Invoice Verif
OLM2	Customizing: Volume-Based Rebates
OLMB	C RM-MAT Inventory Management Menu
OLMD	C RM-MAT MRP Menu
OLME	C MM Menu: Purchasing
OLML	C MM Menu for Warehouse Management
OLMR	C RM-MAT Menu: Invoice Verification
OLMS	C RM-MAT Master Data Menu
OLMW	C RM-MAT Valuation/Acct. Assgt. Menu
OLPA	SOP Configuration
OLPE	Sales order value
OLPK	Customizing for capacity planning
OLPR	Project System Options
OLPS	Customizing Basic Data
OLPV	Customizing: Std. Value Calculation
OLQB	C QM QM in Procurement
OLQI	Analysis
OLQM	Customizing QM Quality Notifications
OLQS	C QM Menu Basic Data
OLQW	C QM Inspection Management
OLQZ	Quality Certificates
OLS1	Customizing for Rebates
OLSD	Customizing: SD
OLVA	C SD Sales Menu
OLVD	C SD Shipping Menu
OLVF	C SD Billing Menu
OLVS	C SD Menu for Master Data
SPRO	Start SAP IMG (Implementation Guide). (from john.omeara@syskoplan.ie)