ABAP - Advanced Business Application Programming

COMPLETE ALV DOCUMENTATION

noreply@blogger.com (A S Chakrapani) — Tue, 03 Jun 2008 10:38:00 +0000

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

noreply@blogger.com (A S Chakrapani) — Tue, 03 Jun 2008 10:35:00 +0000

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.

Performance Tuning

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 12:13:00 +0000

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

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 11:59:00 +0000

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

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 11:57:00 +0000

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

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:14:00 +0000

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)

TRANSACTION CODES - MM configuration transactions

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:13:00 +0000

OLMB-	Inventory management/Physical Inventory

OLMD-	MM Consumption-Based Planning

OLME-	MM Purchasing

OLML-	Warehouse Management

OLMR-	Invoice Verification

OLMS	Material Master data

OLMW-	MM Valuation/Account Assignment

TRANSACTION CODES - Material Management (MM)

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:12:00 +0000

MM06	Flag material for deletion. (from john.omeara@syskoplan.ie)

OLMS-	materials management configuration menu, most of the stuff under this menu is not under the implementation guide

TRANSACTION CODES - FI Financial Management

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:11:00 +0000

FGRP	Report Writer screen

FM12	View blocked documents by user

FST2	Insert language specific name for G/L account. (from john.omeara@syskoplan.ie)

FST3	Display G/L account name. (from john.omeara@syskoplan.ie)

KEA0	Maintain operating concern. (from john.omeara@syskoplan.ie)

KEKE	Activate CO-PA. (from john.omeara@syskoplan.ie)

KEKK	Assign operating concern. (from john.omeara@syskoplan.ie)

KL04	Delete activity type. (from john.omeara@syskoplan.ie)

KS04	Delete a cost centre. (from john.omeara@syskoplan.ie)

KSH2	Change cost centre group - delete. (from john.omeara@syskoplan.ie)

OBR2	Deletion program for customers, vendors, G/L accounts. (from john.omeara@syskoplan.ie)

OKC5	Cost element/cost element group deletion. (from john.omeara@syskoplan.ie)

OKE1	Delete transaction data. (from john.omeara@syskoplan.ie)

OKE2	Delete a profit centre. (from john.omeara@syskoplan.ie)

OKI1	Determine Activity Number: Activity Types (Assignment of material number/service to activity type) (from john.omeara@syskoplan.ie)

OMZ1	Definition of partner roles. (from john.omeara@syskoplan.ie)

OMZ2	Language dependent key reassignment for partner roles. (from john.omeara@syskoplan.ie)

TRANSACTION CODES - SAP OFFICE

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:09:00 +0000

SO00 send a note through SAP, can be sent to internet, X400, etc

TRANSACTION CODES - Sales and Distribution (SD)

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:08:00 +0000

OLSD	Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data

VA01	Create Sales/Returns Order:Initial Screen

VB21	Transaction for Volume Lease Purchases (done as a sales deal)

VK15	Transaction used to enter multiple sales conditions (most will be entered here)

TRANSACTION CODES - Human Resources (HR)

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:08:00 +0000

PA03	Change Payroll control record

PA20	Display PA Infotypes

PA30	Create/Change PA Infotypes

PP02	Quick Entry for PD object creation

PU00	Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.

TRANSACTION CODES - Basis / ABAP

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:02:00 +0000

You can execute the following commands in the transaction code (tcode) field with Enter. You will find some useful transaction codes below to work in tandem with the following commands:
To call a transaction - In the same session (window) Enter: /nxxxx (xxxx = transaction code). - In an additional session, Enter: /oxxxx (xxxx = transaction code).
If you enter this function before any of the tcodes below, you are able to break out of your current screen/business and begin a completely new session. Otherwise, the current business process has to be terminated, and return to the initial user screen (the main menu) has to be initiated before entering tcode spro). /o tcode saves you the effort of having to do this.
To end the current transaction Enter: /n. Caution: Unsaved changes are lost without warning
To delete the current session. Enter: /i.
To generate a session list Enter: /o.
To log off from the system Enter: /nend.
From John O'Meara
OSS Note 0026171 has additional information on OKCodes in SAP, and is a very useful read

BASIS/ABAP

USMM	Pressing F8 will display all hotpacks applied.

SEARCH_SAP_MENU	Show the menu path to use to execute a given tcode. You can search by transaction code or menu text.

DI02	ABAP/4 Repository Information System: Tables.

LSMW	Legacy System Migration Workbench. An addon available from SAP that can make data converstion a lot easier. Thanks to Serge Desland for this one.

OSS1	SAP Online Service System

OY19	Compare Tables

SM13	Update monitor. Will show update tasks status. Very useful to determine why an update failed.

S001	ABAP Development Workbench

S001	ABAP/4 Development Weorkbench. (from john.omeara@syskoplan.ie)

S002	System Administration. (from john.omeara@syskoplan.ie)

SA38	Execute a program. (from john.omeara@syskoplan.ie)

SCAT	Computer Aided Test Tool

SCU0	Compare Tables

SE01	Old Transport & Corrections screen

SE03	Groups together most of the tools that you need for doing transports. In total, more than 20 tools can be reached from this one transaction.

SE09	Workbench Organizer

SE10	New Transport & Correction screen

SE11	ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)

SE12	Dictionary: Initial Screen - enter object name. (from john.omeara@syskoplan.ie)

SE13	Access tables in ABAP/4 Dictionary. (from john.omeara@syskoplan.ie)

SE14	Utilities for Dictionary Tables

SE15	ABAP/4 Repository Information System

SE16	Data Browser: Initial Screen. (from john.omeara@syskoplan.ie)

SE16N	Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.

SE17	General Table Display

SE24	Class Builder

SE30	ABAP/4 Runtime Analysis

SE32	ABAP/4 Text Element Maintenance

SE35	ABAP/4 Dialog Modules

SE36	ABAP/4: Logical Databases

SE37	ABAP/4 Function Modules

SE38	ABAP Editor

SE39	Splitscreen Editor: Program Compare

SE41	Menu Painter

SE43	Maintain Area Menu

SE48	Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.

SE49	Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.

SE51	Screen Painter: Initial Screen. (from john.omeara@syskoplan.ie)

SE54	Generate View Maintenance Module

SE61	R/3 Documentation

SE62	Industry utilities

SE63	Translation

SE64	Terminology

SE65	R/3 document. short text statistics SE66 R/3 Documentation Statistics (Test!)

SE68	Translation Administration

SE71	SAPscript layout set

SE71	SAPScript Layouts Create/Change

SE72	SAPscript styles

SE73	SAPscript font maintenance (revised)

SE74	SAPscript format conversion

SE75	SAPscript Settings

SE76	SAPscript Translation Layout Sets

SE77	SAPscript Translation Styles

SE80	ABAP/4 Development Workbench

SE81	SAP Application Hierarchy

SE82	Customer Application Hierarchy

SE83	Reuse Library. Provided by Smiho Mathew.

SE84	ABAP/4 Repository Information System

SE85	ABAP/4 Dictionary Information System

SE86	ABAP/4 Repository Information System

SE87	Data Modeler Information System

SE88	Development Coordination Info System

SE91	Maintain Messages

SE92	Maintain system log messages

SE93	Maintain Transaction. (from john.omeara@syskoplan.ie)

SEARCH_SAP_MENU	From the SAP Easy Access screen, type it in the command field and you will be able to search the standard SAP menu for transaction codes / keywords. It will return the nodes to follow for you.

SEU	Object Browser

SHD0	Transaction variant maintenance

SM04	Overview of Users (cancel/delete sessions)

SM12	Lock table entries (unlock locked tables)

SM21	View the system log, very useful when you get a short dump. Provides much more info than short dump

SM30	Maintain Table Views. (from john.omeara@syskoplan.ie)

SM31	Table Maintenance

SM32	Table maintenance

SM35	View Batch Input Sessions

SM37	View background jobs

SM50	Process Overview. (from john.omeara@syskoplan.ie)

SM51	Delete jobs from system (BDC)

SM62	Display/Maintain events in SAP, also use function BP_EVENT_RAISE

SMEN	Display the menu path to get to a transaction

SMOD/CMOD	Transactions for processing/editing/activating new customer enhancements.

SNRO	Object browser for number range maintenance. (from john.omeara@syskoplan.ie)

SPRO	Start SAP IMG (Implementation Guide). (from john.omeara@syskoplan.ie)

SQ00	ABAP/4 Query: Start Queries

SQ01	ABAP/4 Query: Maintain Queries

SQ02	ABAP/4 Query: Maintain Funct. Areas

SQ03	ABAP/4 Query: Maintain User Groups

SQ07	ABAP/4 Query: Language Comparison

ST05	Trace SQL Database Requests. (from john.omeara@syskoplan.ie)

ST22	ABAP Dump analysis

SU53	Display Authorization Values for User. (from john.omeara@syskoplan.ie)

WEDI	EDI Menu. IDOC and EDI base.

WE02	Display an IDOC

WE07	IDOC Statistics

TRANSACTION CODES - Production Planning (PP)

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 05:01:00 +0000

C001 Create Production Order
C005N Collective Release
C011N Time Ticket
C012 Confirmation - Collective
C013 Confirmation - Cancel
C00IS Production order information system
C0GI Reprocess Goods Movements
C223 Maintain production version

TRANSACTION CODES - Plant Maintenance (PM)

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 04:59:00 +0000

IW31 Create Plant Maintenance Order
IW32 Change Plant Maintenance Order
IW33 Display Plant Maintenance Order
IW34 Create Notification Order
IW51 Create Service Notification
IW52 Change Service Notification
IW53 Display Service Notification
IW54 Create Service Notification :Problem notification
IW55 Create Service Notification :Activity Request
IW56 Create Service Notification :Service Request
IW57 Assign deletion Flag to Completed Service Notifications
IW58 Change Service Notifications: Selection of Notification
IW59 Display Service Notifications: Selection of Notification

ABAP - Interview Questions - 2

noreply@blogger.com (A S Chakrapani) — Mon, 26 May 2008 03:05:00 +0000

1. What is an ABAP data dictionary?

ABAP 4 data dictionary describes the logical structures of the objects used in application development and shows how they are mapped to the underlying relational database in tables/views.

2. What are domains and data element?

Domains:Domain is the central object for describing the technical characteristics of an attribute of an business objects. It describes the value range of the field. Data Element: It is used to describe the semantic definition of the table fields like description the field. Data element describes how a field can be displayed to end-user.

3. What is foreign key relationship?

A relationship which can be defined between tables and must be explicitly defined at field level. Foreign keys are used to ensure the consistency of data. Data entered should be checked against existing data to ensure that there are now contradiction. While defining foreign key relationship cardinality has to be specified. Cardinality mentions how many dependent records or how referenced records are possible.

4. Describe data classes.

Master data: It is the data which is seldomly changed. Transaction data: It is the data which is often changed. Organization data: It is a customizing data which is entered in the system when the system is configured and is then rarely changed. System data:It is the data which R/3 system needs for itself.

5. What are indexes?

Indexes are described as a copy of a database table reduced to specific fields. This data exists in sorted form. This sorting form ease fast access to the field of the tables. In order that other fields are also read, a pointer to the associated record of the actual table are included in the index. Yhe indexes are activated along with the table and are created automatically with it in the database.

6. Difference between transparent tables and pooled tables

Transparent tables: Transparent tables in the dictionary has a one-to-one relation with the table in database. Its structure corresponds to single database field. Table in the database has the same name as in the dictionary. Transparent table holds application data. Pooled tables. Pooled tables in the dictionary has a many-to-one relation with the table in database. Table in the database has the different name as in the dictionary. Pooled table are stored in table pool at the database level.

SAP System - Fields

noreply@blogger.com (A S Chakrapani) — Thu, 15 May 2008 08:33:00 +0000

ABCDE	Constant: Alphabet (A,B,C,...)
APPLI	SAP applications
BATCH	Background active (X) IF SY-BATCH EQ SPACE. WRITE: / 'Report was started on-line'. WRITE: / 'Using variant:', SY-SLSET. ELSE. WRITE: / 'Report was started in background'. ENDIF.
BATZD	Background SUBMIT: Daily
BATZM	Background SUBMIT: Monthly
BATZO	Background SUBMIT: Once
BATZS	Background SUBMIT: Immediately
BATZW	Background SUBMIT: Weekly
BINPT	Batch input active (X) This field indicates if the transaction was called in a Batch Input session or by an online user. To test it, a batch input session must be created. From Release 3.1g the next procedure can be used. o Create a report which displays this system field o Create a Transaction code for this report o Use transaction SHDB to record a the previous transaction o Press the Overview button and choose the 'generate program' function. o Running the previously generated program it will create a Batch Input session o Now call transaction SM35 and process the created Batch Input in foreground. It should display an 'X' for system field SY-BINPT.
BREP4	Background SUBMIT: Root name of request report
BSPLD	Background SUBMIT: List output to spool
CALLD	CALL mode active (X) This field indicates if the transaction was called from another transaction. o Create a report which displays this system field o Create a Transaction code for this report o Create a new report containing the next ABAP command: CALL TRANSACTION tcode. Where tcode is the Transaction code you created. When you run this report, it should display an 'X' for system field SY-CALLD.
CALLR	Print: ID for print dialog function
CCURS	Rate specification/result field (CURRENCY CONVERT)
CCURT	Table rate from currency conversion
CDATE	Date of rate from currency conversion
COLNO	Current column during list creation WRITE: SY-COLNO, ',', SY-LINNO, 'Cursor position (column, row).'.
CPAGE	Current page number WRITE: / 'SY-CPAGE:', SY-CPAGE LEFT-JUSTIFIED.
CPROG	Runtime: Main program WRITE: /5 'Main program:' RIGHT-JUSTIFIED, 40 SY-CPROG.
CTABL	Exchange rate table from currency conversion
CTYPE	Exchange rate type 'M','B','G' from CURRENCY CONVERSION
CUCOL	Cursor position (column) WRITE: / 'SY-CUCOL:', SY-CUCOL LEFT-JUSTIFIED.
CUROW	Cursor position (line) WRITE: / 'SY-CUROW:', SY-CUROW LEFT-JUSTIFIED.
DATAR	Flag: Data received In transaction programming this field indicates the change of data on the screen. In the PBO part you may set default values of the input fields of the dynpro. In the PAI part you can check if they were changed. If SY-DATAR is set, then the user has modified or entered new data on the screen.
DATLO	Local date for user
DATUM	System: Date
DATUT	Global date related to UTC (GMT)
DAYST	Summertime active ? ('daylight saving time')
DBCNT	Number of elements in edited dataset with DB operations WRITE: /12 'Number of selected records:', SY-DBCNT CENTERED.
DBNAM	Logical database for ABAP/4 program
DBSYS	System: Database system
DCSYS	System: Dialog system
DSNAM	Runtime: Name of dataset for spool output
DYNGR	Screen group of current screen
DYNNR	Number of current screen
FDAYW	Factory calendar weekday
FDPOS	Location of a string SEARCH T FOR 're'. READ TABLE T INDEX SY-TABIX. WRITE: / SY-TABIX, T-FIELD. SKIP. WRITE: /9 'At the example of sy-tabix, Row', (3) SY-TABIX, ',' , 'keyword ''re'' found at off-set position:', (3) SY-FDPOS.
FMKEY	Current function code menu
HOST	Host
INDEX	Number of loop passes DO 5 TIMES. WRITE: SY-INDEX. ENDDO.
LANGU	SAP logon language key
LDBPG	Program: ABAP/4 database program for SY-DBNAM
LILLI	Number of current list line AT LINE-SELECTION. DETAIL. * SY-LSIND is the index of the current list WRITE: / 'SY-LSIND:', SY-LSIND LEFT-JUSTIFIED. * SY-LISTI is the index of the previous list WRITE: / 'SY-LISTI:', SY-LISTI LEFT-JUSTIFIED. * SY-LILLI is the number of the selected line in the absolute list WRITE: / 'SY-LILLI:', SY-LILLI LEFT-JUSTIFIED.
LINCT	Number of list lines WRITE: / SY-LINCT, 'line and', (3) SY-LINSZ, 'column is a page'.
LINNO	Current line for list creation WRITE: SY-COLNO, ',', SY-LINNO, 'Cursor position (column, row).'.
LINSZ	Line size of list WRITE: SY-COLNO, ',', SY-LINNO, 'Cursor position (column, row).'.
LISEL	Interact.: Selected line * contents of the selected line WRITE: / 'SY-LISEL:', SY-LISEL.
LISTI	Number of current list line * SY-LISTI is the index of the previous list WRITE: / 'SY-LISTI:', SY-LISTI LEFT-JUSTIFIED.
LOCDB	Local database exists
LOCOP	Local database operation
LOOPC	Number of LOOP lines at screen step loop
LSIND	Number of secondary list * SY-LSIND is the index of the current list WRITE: / 'SY-LSIND:', SY-LSIND LEFT-JUSTIFIED.
LSTAT	Interact.: Status information for each list level
MACDB	Program: Name of file for matchcode access
MACOL	Number of columns from SET MARGIN
MANDT	Client number from SAP logon
MARKY	Current line character for MARK
MAROW	No. of lines from SET MARGIN statement
MODNO	Number of alternative modi
MSGID	Message ID
MSGLI	Interact.: Message line (line 23)
MSGNO	Message number
MSGTY	Message type (E,I.W,...)
MSGV1	Message variable
MSGV2	Message variable
MSGV3	Message variable
MSGV4	Message variable
OPSYS	System: Operating system
PAART	Print: Format
PAGCT	Page size of list from REPORT statement
PAGNO	Runtime: Current page in list
PDEST	Print: Output device
PEXPI	Print: Spool retention period
PFKEY	Runtime: Current F key status
PLIST	Print: Name of spool request (list name)
PRABT	Print: Department on cover sheet
PRBIG	Print: Selection cover sheet
PRCOP	Print: Number of copies
PRDSN	Print: Name of spool dataset
PREFX	ABAP/4 prefix for background jobs
PRIMM	Print: Print immediately
PRNEW	Print: New spool request (list)
PRREC	Print: Recipient
PRREL	Print: Delete after printing
PRTXT	Print: Text for cover sheet
REPID	Program: Name of ABAP/4 program
RTITL	Print: Report title of program to be printed
SAPRL	System: SAP Release
SCOLS	Columns on screen
SLSET	Name of selection set
SPONO	Runtime: Spool number for list output
SPONR	Runtime: Spool number from TRANSFER statement
SROWS	Lines on screen
STACO	Interact.: List displayed from column
STARO	Interact.: Page displayed from line
STEPL	Number of LOOP line at screen step
SUBRC	Return value after specific ABAP/4 statements
SUBTY	ABAP/4: Call type for SUBMIT
SYSID	System: SAP System ID
TABIX	Runtime: Current line of an internal table SEARCH T FOR 're'. READ TABLE T INDEX SY-TABIX.
TCODE	Session: Current transaction code
TFDSN	Runtime: Dataset for data extracts
TFILL	Current number of entries in internal table
TIMLO	Local time for user
TIMUT	Global time related to UTC (GMT)
TITLE	Title of ABAP/4 program
TLENG	Line width of an internal table
TMAXL	Maximum number of entries in internal table (?)
TNAME	Name of internal table after an access (?)
TOCCU	OCCURS parameter with internal tables
TPAGI	Flag indicating roll-out of internal table to paging area (?)
TSTLO	Timestamp (date and time) for user
TSTUT	Timestamp (date and time) related to UTC (GMT)
TTABC	Number of line last read in an internal table (?)
TTABI	Offset of internal table in roll area (?)
TVAR0	Runtime: Text variable for ABAP/4 text elements
TVAR1	Runtime: Text variable for ABAP/4 text elements
TVAR2	Runtime: Text variable for ABAP/4 text elements
TVAR3	Runtime: Text variable for ABAP/4 text elements
TVAR4	Runtime: Text variable for ABAP/4 text elements
TVAR5	Runtime: Text variable for ABAP/4 text elements
TVAR6	Runtime: Text variable for ABAP/4 text elements
TVAR7	Runtime: Text variable for ABAP/4 text elements
TVAR8	Runtime: Text variable for ABAP/4 text elements
TVAR9	Runtime: Text variable for ABAP/4 text elements
TZONE	Time difference from 'Greenwich Mean Time' (UTC) in seconds
UCOMM	Interact.: Command field function entry
ULINE	Constant: Underline (---------...)
UNAME	Session: SAP user from SAP logon
UZEIT	System: Time
VLINE	Constant: Vertical bar
WAERS	T001: Company code currency after reading B segment
WILLI	Number of current window line
WINCO	Cursor position in window (column)
WINDI	Index of current window line
WINRO	Cursor position in window (line)
WINSL	Interact.: Selected window line
WINX1	Window coordinate (column left)
WINX2	Window coordinate (column right)
WINY1	Window coordinate (line left)
WINY2	Window coordinate (line right)
WTITL	Standard page header indicator
XCODE	Extended command field
ZONLO	Time zone of user

ABAP - Interview Questions - 1

noreply@blogger.com (A S Chakrapani) — Thu, 15 May 2008 08:20:00 +0000

1. Preparation of the data records by the L.D.B and reading of the data records in the actual
report are accomplished with the command pair Put and Get.

2. The three main elements of LDB are Structure, Selections, and Database Program.

3. In LDB what determines hierarchy of the tables? Structure.

4. In general what are the two ways in which one can retrieve data from tables?

Using Select statements, Database Program.

5. With LDB one can modify the pre-generated selection screen to their needs (T/F).
Yes.

6. Logical databases are programs that read data from Database tables (Dictionary Structures).

7. The event Get LATE process all tables that are hierarchically superior to the

. (True/False)

False. It processes all tables that are hierarchically inferior to the

.

8. The Database Program of LDB is a collection of SUBROUTINES, which selects data and passes it to the report.

9. The layout of the Database program is determined by both Structure and Selections.
10. The order in which data is made available to the report depends on Structure of the LDB.

11. Apart from the structure and selections of the LDB the GET statements in the report
determines the behavior of the database at runtime.

12. Node at the highest level in the structure is known as Root.

13. There can be more than one node at the highest level in the structure. (T/F)
False.
One can define only one node at the highest level in the structure on LDB.

14. All nodes in the structure of LDB need not be defined in the ABAP/4 Dictionary (T/F).
False.

One has to define all nodes in the Dictionary or one has to select all nodes that are defined in
the Dictionary.

15. It is not possible to use ABAP/4 Dictionary Structures without an underlying database using LDB. (T/F)

True. One can use additionally related tables, along with the tables defined in the structure of LDB.

16. Dynamic selections allow the user to define further selections for database access in addition to the selection criteria already defined in the LDB selections.

17. Check statement can be used along with the event GET in the report for checking the selections, which are not table-specific values.

18. In sense of Database Management System (DBMS) LOGICAL DATABASE is a database Structure. (T/F).

False.

19. It is not necessary to maintain the Parent-Child relationship between the tables in Logical Database Structure. (T/F)

False. One has to maintain the Parent-Child relationship.

20. Is it possible to extract data from tables without using the event ‘GET’ in the report with an appropriate LDB. (T/F).

False. One can extract data from tables using Select statements in a report, though the report is having a LDB attribute.

21. What sorts of tables one can se in designing the hierarchy of a LDB?

Tables, which are having Foreign Key relations.

22. A report program, which uses only SELECT statements, is called SQL Report.

23. One cannot use SELECT statements in a report program linked to a Logical Database (T/F). False.

24. Is it true that the Logical Database reads the data from the database tables using Select Statements (T/F).

Yes. We are coding that in Database part of LDB.

25. In a report with an LDB attribute, you do not have to define how the information should be retrieved from the database tables, but only how the data should be represented on the screen. (T/F).

True.

26. One can use the event GET in a report without LDB attribute. (T/F).

False.

27. The last character of the LDB name denotes Application.

28. The structure of Logical Databases reflects the Foreign Key dependencies of hierarchical tables in the SAP system.

29. It is mandatory that for each table in the LDB hierarchy there should exist one GET statement in the report. (T/F).

False. It is not necessary.

30. What happens if a report does not contain a GET statement for a particular node of a Logical Database.

Process will transfer to the next event.

31. In a Logical Database, one can define input fields on the selection screen with Select-Options and Parameters statements.

32. Suppose a logical database program contains the following lines:

SELECT-OPTIONS CONNID FOR SPFLI-CONNID.

PARAMETERS CARRID LIKE SFLIGHT-CARRID FOR TABLE SFLIGHT.

What will be the output, for the above two statements?

Only select-options connid for spfli-carrid will be displayed on the screen.

33. Consider a report with F1S attribute, what will be the output for the following code. Whether you will get the data from spfli and sflight or not, with corresponding tables statement,

GET SPFLI.

GET SFLIGHT.

Write:/ spfli-carrid, spfli-connid, sflight-fldate, sbook-bookid.

Yes, you will get the data from spfli and sflight.

34. Consider a report with F1S attribute, what will be the output of the following code. Whether you will get the data from sbook or not, with corresponding tables statement.

GET SPFLI.

GET SFLIGHT.

Write:/ spfli-carrid, spfli-connid, sflight-fldate, sbook-bookid.

You cannot extract data from sbook.

35. Identify any errors in the following code and correct the same, and what will be the output. If there exists corresponding tables statement, for spfli, sflight, sbook.

GET SPFLI.

GET SBOOK.

Write:/ spfli-carrid, spfli-connid, sflight-fldate, sbook-bookid, sbook-class.

No syntax errors. You will get data from all the three tables.

36. Does the following two statements do the same task? If so which one takes less time and which one is recommended.

Select * from spfli where spfli-carrid = ‘LH’ and spfli-connid = ‘400’.

Endselect.

Select * from spfli. Check: spfli-carrid = ‘LH’ and spflid-connid = ‘400’.

Endselect.

-Yes they will do the same task. Second Select statement takes less time and is recommended.

37. If you want to improve the response time (time to access data) Logical Databases permits you to achieve this using VIEWS.

38. Is there any upper limit (max) to the possible number of nodes in a logical database structure? If so what is the limit?

Yes, there is an upper limit for defining number of nodes in a Logical Database Structure.

Maximum nodes = 1200 / length where length = max. Length of name in the structure.

39. In the structure of Logical Database nodes at different levels are displayed in the same columns. (T/F) If false what types of nodes are displayed in the same columns. If true what type of nodes are not displayed in the same columns.

False. Nodes at same levels are displayed in the same columns.

40. What are the advantages of Logical Databases?

It offers an easy-to-use selection screens. You can modify the pre-generated selection screen to your needs. It offers check functions to check whether user input is complete, correct, and plausible. It offers reasonable data selections. It contains central authorization checks for data base accesses. Enhancements such as improved performance immediately apply to all report programs that use the logical database.

41. Though all the ABAP/4 Dictionary Structures that exists in the structure of the LDB, being defined in Database Program, we are defining the Dictionary Structures in the Report. What is the reason for such declaration?

By declaring so we are providing work areas for data passing between Logical Database and Report. In addition, the logical database configures the selection screen depending on the selection of database tables.

42. Is it mandatory to declare all the tables in Report by the key word tables for all the tables that exist in the structure of LDB, and are being defined in the Database part of LDB.

No, It is not mandatory to declare all tables in report.

43. If one wants to access data using Logical Database, the use of events is unavoidable. (T/F).
True.

ABAP - Performance tuning

noreply@blogger.com (A S Chakrapani) — Thu, 15 May 2008 07:00:00 +0000

For all entries
Nested selects
Select using JOINS
Use the selection criteria
Use the aggregated functions
Select with view
Select with index support
Select … Into table
Select with selection list
Key access to multiple lines
Copying internal tables
Modifying a set of lines
Deleting a sequence of lines
Linear search vs. binary
Comparison of internal tables
Modify selected components
Appending two internal tables
Deleting a set of lines
Tools available in SAP to pin-point a performance problem
Optimizing the load of the database
Other General Tips & Tricks for Optimization

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

TIPS & TRICKS FOR OPTIMIZATION

Use the GET RUN TIME command to help evaluate performance. It's hard to know whether that optimization technique REALLY helps unless you test it out. Using this tool can help you know what is effective, under what kinds of conditions. The GET RUN TIME has problems under multiple CPUs, so you should use it to test small pieces of your program, rather than the whole program.
Generally, try to reduce I/O first, then memory, then CPU activity. I/O operations that read/write to hard disk are always the most expensive operations. Memory, if not controlled, may have to be written to swap space on the hard disk, which therefore increases your I/O read/writes to disk. CPU activity can be reduced by careful program design, and by using commands such as SUM (SQL) and COLLECT (ABAP/4).
Avoid 'SELECT *', especially in tables that have a lot of fields. Use SELECT A B C INTO instead, so that fields are only read if they are used. This can make a very big difference.
Field-groups can be useful for multi-level sorting and displaying. However, they write their data to the system's paging space, rather than to memory (internal tables use memory). For this reason, field-groups are only appropriate for processing large lists (e.g. over 50,000 records). If you have large lists, you should work with the systems administrator to decide the maximum amount of RAM your program should use, and from that, calculate how much space your lists will use. Then you can decide whether to write the data to memory or swap space.
Use as many table keys as possible in the WHERE part of your select statements.
Whenever possible, design the program to access a relatively constant number of records (for instance, if you only access the transactions for one month, then there probably will be a reasonable range, like 1200-1800, for the number of transactions inputted within that month). Then use a SELECT A B C INTO TABLE ITAB statement.
Get a good idea of how many records you will be accessing. Log into your productive system, and use SE80 -> Dictionary Objects (press Edit), enter the table name you want to see, and press Display. Go To Utilities -> Table Contents to query the table contents and see the number of records. This is extremely useful in optimizing a program's memory allocation.
Try to make the user interface such that the program gradually unfolds more information to the user, rather than giving a huge list of information all at once to the user.
Declare your internal tables using OCCURS NUM_RECS, where NUM_RECS is the number of records you expect to be accessing. If the number of records exceeds NUM_RECS, the data will be kept in swap space (not memory).
Use SELECT A B C INTO TABLE ITAB whenever possible. This will read all of the records into the itab in one operation, rather than repeated operations that result from a SELECT A B C INTO ITAB... ENDSELECT statement. Make sure that ITAB is declared with OCCURS NUM_RECS, where NUM_RECS is the number of records you expect to access.
If the number of records you are reading is constantly growing, you may be able to break it into chunks of relatively constant size. For instance, if you have to read all records from 1991 to present, you can break it into quarters, and read all records one quarter at a time. This will reduce I/O operations. Test extensively with GET RUN TIME when using this method.
Know how to use the 'collect' command. It can be very efficient.
Use the SELECT SINGLE command whenever possible.
Many tables contain totals fields (such as monthly expense totals). Use these avoid wasting resources by calculating a total that has already been calculated and stored.

ABAP/4 Development Code Efficiency Guidelines

ABAP/4 (Advanced Business Application Programming 4GL) language is an "event-driven",

"top-down", well-structured and powerful programming language. The ABAP/4 processor controls the execution of an event. Because the ABAP/4

language incorporates many "event" keywords and these keywords need not be in any specific order in the code, it is wise to implement in-house

ABAP/4 coding standards.

SAP-recommended customer-specific ABAP/4 development guidelines can

be found in the SAP-documentation.

This page contains some general guidelines for efficient

ABAP/4 Program Development that should be considered to improve the systems performance on the following areas:-

Physical I/O - data must be read from and written into I/O devices. This can be a potential bottle neck. A well

configured system always runs 'I/O-bound' - the performance of the I/O dictates the overall performance.

Memory consumption of the database resources eg. buffers, etc.

CPU

consumption on the database and application servers

Network communication - not critical for

little data volumes, becomes a bottle neck when large volumes are transferred.

Policies and

procedures can also be put into place so that every SAP-customer development object is thoroughly reviewed (quality – program correctness as well

as code-efficiency) prior to promoting the object to the SAP-production system. Information on the SAP R/3 ABAP/4 Development Workbench

programming tools and its features can be found on the SAP Public Web-Server.

--------------------------------------------------------------------------------

CLASSIC GOOD 4GL PROGRAMMING CODE-PRACTICES GUIDELINES

Avoid dead-code

Remove unnecessary code and redundant processing

Spend time documenting and adopt good change control practices

Spend adequate time

anayzing business requirements, process flows, data-structures and data-model

Quality

assurance is key: plan and execute a good test plan and testing methodology

Experience

counts

--------------------------------------------------------------------------------

SELECT * FROM

CHECK:
ENDSELECT

vs.

SELECT * FROM

WHERE
ENDSELECT

In order to keep the amount of data which is relevant to the query the hit set small, avoid

using SELECT+CHECK statements wherever possible. As a general rule of thumb, always specify all known conditions in the WHERE clause (if

possible). If there is no WHERE clause the DBMS has no chance to make optimizations. Always specify your conditions in the Where-clause instead

of checking them yourself with check-statements. The database system can also potentially make use a database index (if possible) for greater

efficiency resulting in less load on the database server and considerably less load on the network traffic as well.

Also, it is important to use EQ (=) in the WHERE clause wherever possible, and analyze the SQL-statement for the

optimum path the database optimizer will utilize via SQL-trace when necessary.

Also, ensure

careful usage of "OR", "NOT" and value range tables (INTTAB) that are used inappropriately in Open SQL statements.

--------------------------------------------------------------------------------

SELECT *

vs.

SELECT SINGLE *

If you are interested in exactly one row of a database table or view,

use the SELECT SINGLE statement instead of a SELECT * statement. SELECT SINGLE requires one communication with the database system whereas

SELECT * requires two.

--------------------------------------------------------------------------------

SELECT

* FROM

INTO
APPEND
ENDSELECT

vs.

SELECT * FROM

INTO TABLE

It is usually faster to use the INTO TABLE version of a SELECT statement than to use APPEND

statements

--------------------------------------------------------------------------------

SELECT ... WHERE + CHECK

vs.

SELECT using aggregate function

If you want to

find the maximum, minimum, sum and average value or the count of a database column, use a select list with aggregate functions instead of

computing the aggregates within the program. The RDBMS is responsible for aggregated computations instead of transferring large amount of data

to the application. Overall Network, Application-server and Database load is also considerably less.

--------------------------------------------------------------------------------

SELECT INTO TABLE + LOOP AT T
…………
SELECT * FROM

INTO TABLE .
LOOP AT .
ENDLOOP.

vs.

SELECT * FROM

……….
ENDSELECT

If you process your data only once, use a SELECT-ENDSELECT loop instead of collecting data in

an internal table with SELECT ... INTO TABLE. Internal table handling takes up much more space

--------------------------------------------------------------------------------

Nested

SELECT statements:
SELECT * FROM
SELECT * FROM
……..
ENDSELECT.
ENDSELECT

vs.

Select with view
SELECT * FROM
ENDSELECT

To process a join, use a view wherever possible instead of nested SELECT

statements.
Using nested selects is a technique with low performance. The inner select statement is executed several times which might be an overhead. In

addition, fewer data must be transferred if another technique would be used eg. join implemented as a view in ABAP/4 Repository.

· SELECT ... FORM ALL ENTRIES
· Explicit cursor handling (for more information, goto Transaction SE30 – Tips & Tricks)

--------------------------------------------------------------------------------

Nested

select:
SELECT * FROM pers WHERE condition.
SELECT * FROM persproj WHERE person = pers-persnr.
... process ...
ENDSELECT.
ENDSELECT.

vs.

SELECT persnr FROM pers

INTO TABLE ipers WHERE cond. ……….
SELECT * FROM persproj FOR ALL ENTRIES IN ipers
WHERE person = ipers-persnr
………... process .……………
ENDSELECT.

In the lower version the new Open SQL statement FOR ALL ENTRIES is used. Prior to

the call, all interesting records from 'pers' are read into an internal table. The second SELECT statement results in a call looking like this

(ipers containing: P01, P02, P03):
(SELECT * FROM persproj WHERE person = 'P01')
UNION
(SELECT * FROM persproj WHERE person = 'P02')
UNION
(SELECT * FROM persproj WHERE person = 'P03')

In case of large statements, the R/3's database

interface divides the statement into several parts and recombines the resulting set to one. The advantage here is that the number of transfers

is minimized and there is minimal restrictions due to the statement size (compare with range tables).

--------------------------------------------------------------------------------

SELECT * FROM

vs.

SELECT FROM

Use a select list or a view instead of SELECT *, if you are only interested in specific columns of the

table. If only certain fields are needed then only those fields should be read from the database. Similarly, the number of columns can also be

restricted by using a view defined in ABAP/4 Dictionary. Overall database and network load is considerably less.

--------------------------------------------------------------------------------

SELECT without table buffering support

vs.

SELECT with table buffering support

For all

frequently used, read-only(few updates) tables, do attempt to use SAP-buffering for eimproved performance response times. This would reduce the

overall Database activity and Network traffic.

--------------------------------------------------------------------------------

Single-line inserts
LOOP AT
INSERT INTO

VALUES
ENDLOOP

vs.

Array inserts

Whenever possible, use array operations instead of single-row operations to modify the database tables.

Frequent communication between the application program and database system produces

considerable overhead.

--------------------------------------------------------------------------------

Single-line updates
SELECT * FROM

UPDATE

ENDSELECT

vs.

Column updates
UPDATE

SET

Wherever possible, use column

updates instead of single row updates to update your database tables

--------------------------------------------------------------------------------

DO....ENDDO loop with Field-Symbol

vs.

Using CA operator

Use the special operators CO, CA, CS instead of programming the

operations yourself
If ABAP/4 statements are executed per character on long strings, CPU consumprion can rise substantially

--------------------------------------------------------------------------------

Use of a CONCATENATE function module

vs.

Use of a CONCATENATE statement

Some function modules for string manipulation have

become obsolete, and should be replaced by ABAP statements or functions

STRING_CONCATENATE... ---> CONCATENATE
STRING_SPLIT... ---> SPLIT
STRING_LENGTH... ---> strlen()
STRING_CENTER... ---> WRITE..TO. ..CENTERED
STRING_MOVE_RIGHT ---> WRITE...TO...RIGHT-JUSTIFIED

--------------------------------------------------------------------------------

Moving

with offset

vs.

Use of the CONCATENATE

statement

Use the CONCATENATE statement instead of programming a string concatenation of

your own

--------------------------------------------------------------------------------

Use of SEARCH and MOVE with offset

vs.

Use of SPLIT statement

Use the SPLIT statement instead of programming a string split yourself

--------------------------------------------------------------------------------

Shifting by SY-FDPOS places

Using SHIFT...LEFT DELETING LEADING...

If you want ot delete

the leading spaces in a string use the ABAP/4 statements SHIFT...LEFT DELETING LEADING... Other constructions (with CN and SHIFT... BY SY-FDPOS

PLACES, with CONDENSE if possible, with CN and ASSIGN CLA+SY-FDPOS(LEN) ...) are not as fast

--------------------------------------------------------------------------------

Get a

check-sum with field length

Get a

check-sum with strlen ()

Use the strlen () function to restrict the DO loop to the relevant part of the field, eg.

when determinating a check-sum

ALV

noreply@blogger.com (A S Chakrapani) — Thu, 15 May 2008 06:52:00 +0000

1) ALV GRID CONTROL

2) SAP List Viewer

ABAP - REPORT GENERATION - FORMATTING

noreply@blogger.com (A S Chakrapani) — Thu, 15 May 2008 06:45:00 +0000

REPORT GENERATION – FORMATTING

1. The alignment of a type ‘c’ field in a report is left Aligned.
2. In the statement Write:/15(10) Ofal-lifnr. what do the number 15 and 10 stand for
15 stand for the offset on the screen and 10 stands for the field length displayed.

3. Specify the default alignment for the following field types:
‘D’ – Left, ‘F’-Right, ‘N’-Left, ‘I’-Right, ‘T’-Left.

4. If s_time has the value ‘123456’ how would you get an output of 12:34:56 with a single
‘Write:’ statement. Write:s_time using edit mask’--:--:--‘.

5. In order to suppress the leading zeroes of a number field the keywords used are NO-ZERO.

6. The total no of date formats that can be used to display a date during output is MM/DD/YY, DD/MM/YY, DD/MM/YYYY, MM/DD/YYYY, MMDDYY, DDMMYY, YYMMDD.

7. The UNDER Command allows for vertical alignment of fields one below the other.

8. In order to concatenate strings only for output purposes the command NO-GAP can be used in conjunction with the ‘Write’ statement.

9. The no of decimal places for output can be defines within a write statement. (T/F).

TRUE. Write:/ decimals 2.

10.

Data can be moved from one field to another using a ‘Write:’ Statement and stored in the desired format. (T/F).

TRUE. Write: Date_1 to Date_2 format DD/MM/YY.

11.

In the statement Write:/15(10) lfa1-lifnr. The values 15 and 11 can also be defined by variables (T/F). False.
12.

Differentiate between the following two statements if any.

ULINE.

Write: sy-uline.

No-difference. Except that uline is used outside the ‘Write’ Statement.

13.

In order to skip a single line the number of lines need not be given as an assignment (T/F)

TRUE.

14.

The “SKIP TO LINE line number” is dependent on the LINE-COUNT statement included in the report statement of the program.
15.

In order to skip columns the command used is POSITION .
16.

In order to have boldfaced text as output the command used is Write:INTENSIFIED.
17.

Background and foreground colors can be interchanged using the command Format Inverse.
18.

In order to restore the system defaults for all changes made with the format statement is Format Reset.
19.

Like ULINE the statement VLINE is used to insert vertical lines. (T/F).

False.

20. Suppressing the number signs (+/-) is carried out using the addition NO-SIGNS to the Write statement. (T/F). False.

21.

If SY-UZEIT has the value 6:34:45 it can be displayed as 063445 using No Edit Mask.
22.

If the variable “Text” has the value ‘ABCDEF’ the output for the statement “Write:/Text+2(3)” will be “CDE”
23.

The fields specified by select-options and parameters statement cannot be grouped together in the selection screen. (T/F). False.
24.

When calling an external report the parameters or select-options specified in the external report cannot be called. (T/F)

FALSE.

25.

Selection Texts in the text elements of the program helps in changing the displayed names of variables in the parameters statement.
26.

Type F datatype cannot be used to define parameters.

27. Rounding off of values can be carried out using the write statement. (T/F). TRUE

28.

How would you define the exponents for a type ‘f’ field?

Exponent .

29.

How would you format the output as left, centered or right-justified using the write statement.

Left-justified, Centered, Right-justified.

30.

If the same formatting options were used for a WRITE statement that follows the FORMAT statement, which settings would take precedence.

The settings in the Write Statement.

31.

For each new event, the system resets all formatting options to their default values (T/F)

TRUE.

32.

All formatting options have the default value OFF. (T/F).

TRUE.

33.

How would you set the formatting options statically and dynamically within a report? Statically: FORMAT [ON|OFF]….

Dynamically: FORMAT = =….

34.

The page footer is defined using the statement END-OF-PAGE.
35.

The processing block following END-OF-PAGE is processed only if you reserve lines for the footer in the LINE-COUNT option of the REPORT statement. (T/F)

TRUE.

36.

To execute a page break under the condition that less than a certain number of lines is left on a page is achieved by RESERVE n lines.
37.

The RESERVE statement only takes effect if output is written to the subsequent page. No blank pages are created and it defines a block of lines that must be output as a whole. (T/F). TRUE.
38.

To set the next output line to the first line of a block of lines defined with the RESERVE statement the statement BACK is used.
39.

What is the limit for the length of a page if the page length is not specified in the report statement. 60,000 lines.
40.

How would you start the printing process from within the program while creating a list?

NEW-PAGE PRINT ON.

41.

You can change the width of pages within list levels triggered by page breaks. (T/F).

FALSE.

42.

Hotspots are special areas of an output list used to trigger events. (T/F) TRUE.
43.

To designate fields as hotspots at runtime, use FORMAT HOTSPOT = .
44.

Horizontal lines created with ULINE and blank lines created with SKIP can be formatted as hotspots. (T/F). FALSE.
45.

How would you suppress the display of a parameter on the selection screen?

Parameters

………..No-Display.

46.

Can you assign a matchcode object to a parameter? If so how?

Yes. PARAMETERS

……..MATCHCODE OBJECT ……..

47.

For each SELECT-OPTIONS statement, the system creates a selection table. (T/F)

TRUE.

48.

To position a set of parameters or comments on a single line on the selection screen, you must declare the elements in a block enclosed by

SELECTION-SCREEN BEGIN OF LINE.

……..

SELECTION-SCREEN END OF LINE.

49.

How can Symbols or R/3 icons be output on the screen?

WRITE AS SYMBOL.

WRITE AS ICON.

50.

In the standard setting, you cannot create empty lines with the WRITE statement alone. (T/F). TRUE.

REPORTING – GENERAL

1.

The system field, which indicates success or failure of a SQL operation, is SY-SUBRC.
2.

What is the syntax for specifying database table name at runtime in SELECT statement.

NAME = ‘SPFL1’.

SELECT * FROM (NAME).

……………….

……………….

ENDSELECT.

3.

How do you read selected lines of database table into an internal table in packages of predefined size.

SELECT * FROM INTO TABLE PACKAGE SIZE.

Where n is variable.

4.

Name the WILDCARD characters which are used for comparisons with character strings & numeric strings. ‘%’ and ‘-‘.
5.

In SELECT statements can you specify a variable in WHERE condition or a part of the condition, if so what is the syntax.

SELECT * FROM

WHERE . 6. Name the ABAP/4 key words, which are used to change the contents of database table. UPDATE or MODIFY. 7. How to specify a client for database table processing. TABLES SPFLI. SELECT * FROM SPFLI CLIENT SPECIFIED WHERE MANDT BETWEEN ‘001’ AND ‘003’. …….. ENDSELECT. 8. How do you write a DATA object from ABAP/4 program to ABAP/4 memory and restore the same from memory to program. EXPORT [FROM ][FROM ]…. TO MEMORY ID . The ID , which can be up to 32 characters long, identifies the data in memory. 9. What are DATA CLUSTERS? You can group any complex internal data objects of an ABAP/4 program together in data clusters and store them temporarily in ABAP/4 memory or for longer periods in databases. You can store data clusters in special databases of the ABAP/4 Dictionary. These databases are known as ABAP/4 cluster databases and have a predefined structure. Storing a data cluster is specific to ABAP/4. Although you can also access cluster databases using SQL statements, only ABAP/4 statements are able to decode the structure of the stored data cluster. 10. Statements used to delete data objects in ABAP/4 memory FREE MEMORY [ID ]. 11. How will you create a file on application server. Open dataset for output. 12. ABAP/4 statement for opening a file on application server for reading Open dataset for input. 13. How will you transfer data into a file in application server? Data fname(60) value ‘mYFILE’. Data num type i. Open dataset fname for output. Do 10 times. Num = Num +1. Transfer num to fname. Enddo. …….etc. 14. Name the function modules to write data from an Internal Table to the Presentation Server. DOWNLOAD and WS_DOWNLOAD. 15. Name the function module that can be used to give information about files on Presentation Server and about its Operating System. WS_QUERY. 16. Name the ABAP/4 key word, which is used to clear the Headerline of an Internal Table. CLEAR. 17. Name the function modules to read data from Presentation Server into an Internal Table. UPLOAD and WS_UPLOAD. 18. Name the ABAP/4 keywords to initialize an Internal Table with and without headerline. REFRESH . 19. How to determine the attributes of an internal table? DESCRIBE TABLE [LINES ] [OCCURS ]. 20. Name the ABAP/4 key word for searching a string in an Internal Table. SEARCH FOR . The different options () for the search in an internal table are: ABBREVIATED Searches tablefor a word containing the character string specified in , where other characters might separate the characters. The first letter of the word and the string must be the same. STARTING AT Searches table for , starting at line . <\lin1> can be a variable. ENDING AT Searches table for upto line. can be a variable. AND MARK If the search string is found, all the characters in the search string (and all the characters in between when using ABBREVIATED) are converted to upper case. 21. What are the different attributes that can be assigned to a variant? The different attributes that can be assigned to a variant are…. Description Enter a short, meaningful description of the variant. This may be upto 30 characters long. Background only Specify whether you want to use the variant in background processing only, or in online environment as well. Protected variant. Mark the field if you want to protect your variant against being changed by other users. Do not display variant. Mark this field if you want the variant name to be displayed in the catalog only, but not in the F4 value list. For the selections you cover in a variant, you can enter the following attributes: Type The system displays whether the field is a parameter or a select option. Protected Mark this field for each field on the selection screen you want to protect from being overwritten. Values that you mark this way are displayed to the users, but they cannot change them, that are they are not ready to accept input. Invisible If you mark this column, the system will not display the corresponding field on the selection screen the user sees when starting the report program. Variable Mark this column if you want to set the value for this field at runtime. 22. Is it possible to create new dynamic programs during runtime of an ABAP/4 program? If so how? To create new dynamic programs during the runtime of an ABAP/4 program, you must use an internal table. For this purpose, you should create this internal table with one character type column and a line width of 72. You can use any method you like from Filling Internal Tables to write the code of your new program into the internal table. Especially, you can use internal fields in which contents are dependent on the flow of the program that you use to create a new one, to influence the coding of the new program dynamically. The following example shows how to proceed in principal: DATA CODE (72) OCCURS 10. APPEND ‘REPORT ZDYN1.’ TO CODE. APPEND ‘WRITE/”Hello, I am dynamically created!”.’ TO CODE. Two lines of a very simple program are written into the internal table CODE. In the next step you have to put the new module, in the above example it is a report, into the library. For this purpose you can use the following statement: Syntax INSERT REPORT FROM . The program is inserted in your present development class in the R/3 Repository. If a program with this name does not already exists, it is newly created with the following attributes: Title: none, Type: 1 (Reporting), Application: S (Basis). You can specify the name of the program explicitly within single quotation marks or you can write the name of a character field, which contains the program name. The name of the program must not necessarily be the same as given in the coding, but it is recommended to do so. is the internal table containing the source code. For the above example you could write: INSERT REPORT ‘ZDYN1’ FROM CODE. Or DATA REP (8). REP = ‘ZDYN1’ INSERT REPORT REP FROM CODE. 23. Data types can be elementary or structured (T/F). TRUE. 24. The amount of memory associated with a data type is ZERO. 25. Data objects are the physical units a program uses at runtime. (T/F). TRUE. 26. The data object does not occupy any space in memory. (T/F) FALSE. 27. What are the three hierarchical levels of data types and objects? Program-independent data, defined in the ABAP/4 Dictionary. Internal data used globally in one program. Data used locally in a procedure (subroutine, function module) 28. How would you find the attributes of a data type or data object? DESCRIBE FIELD [LENGTH [COMPONENTS ]] [OUTPUT-LENGTH ] [DECIMALS ] [EDIT MASK ]. 29. The components of a field string cannot have different data types. (T/F). FALSE. 30. Field strings are also called as Record or Structures. 31. If a field string is aligned (Left, centered, right justified etc.), the filler fields are also added to the length of the type C field. (T/F). TRUE. 32. You cannot assign a local data object defined in a subroutine or function module to a field group. (T/F) TRUE. 33. Field group reserves storage space for the fields, and does not contain pointers to existing fields (T/F). False. 34. Defining a field group as ‘HEADER’ is optional (T/F) FALSE. 35. How would you define a field symbol? FIELD-SYMBOLS. 36. Which function module would you use to check the user’s authorization to access files before opening a file? AUTHORITY_CHECK_DATASET 37. Name the function module used to convert logical file names to physical file names in ABAP/4 programs. FILE_GET_NAME. 38. Parameters, which are defined during the definition of a subroutine with the FORM statement, are called Formal Parameters. 39. Parameters which are specified during the call of a subroutine with the PERFORM statement are called Actual Parameters. 40. In subroutines internal tables that are passed by TABLES, are always called by value and result. (T/F) FALSE. They are called by reference. INTERACTIVE REPORTING 1. What is interactive reporting? It helps you to create easy-to-read lists. You can display an overview list first that contains general information and provide the user with the possibility of choosing detailed information that you display on further lists. 2. What are the uses of interactive reporting? The user can actively control data retrieval and display during the session. Instead of an extensive and detailed list, you create a basic list with condensed information from which the user can switch to detailed displays by positioning the cursor and entering commands. The detailed information appears in secondary lists. 3. What are the event key words in interactive reporting? Event Keyword Event AT LINE-SELECTION Moment at which the user selects a line by double clicking on it or by positioning the cursor on it and pressing F2. AT USER-COMMAND Moment at which the user presses a function key. TOP-OF-PAGE DURING Moment during list processing of a LINE-SELECTION secondary list at which a new page starts. 4. What is secondary list? It allows you to enhance the information presented in the basic list. The user can, for example, select a line of the basic list for which he wants to see more detailed information. You display these details on a secondary list. Secondary lists may either overlay the basic list completely or you can display them in an extra window on the screen. The secondary lists can themselves be interactive again. 5. How to select valid lines for secondary list? To prevent the user from selecting invalid lines, ABAP/4 offers several possibilities. At the end of the processing block END-OF-SELECTION, delete the contents of one or more fields you previously stored for valid lines using the HIDE statement. At the event AT LINE-SELECTION, check whether the work area is initial or whether the HIDE statement stored field contents there. After processing the secondary list, clear the work area again. This prevents the user from trying to create further secondary lists from the secondary list displayed. 6. How to create user interfaces for lists? The R/3 system automatically, generates a graphical user interface (GUI) for your lists that offers the basic functions for list processing, such as saving or printing the list. If you want to include additional functionality, such as pushbuttons, you must define your own interface status. To create a new status, the Development Workbench offers the Menu Painter. With the Menu Painter, you can create menus and application toolbars. And you can assign Function Keys to certain functions. At the beginning of the statement block of AT END-OF-SELECTION, active the status of the basic list using the statement: SET PF-STATUS ‘STATUS’. 7. What is interactive reporting? A classical non-interactive report consists of one program that creates a single list. Instead of one extensive and detailed list, with interactive reporting you create basic list from which the user can call detailed information by positioning the cursor and entering commands. Interactive reporting thus reduces information retrieval to the data actually required. 8. Can we call reports and transactions from interactive reporting lists? Yes. It also allows you to call transactions or other reports from lists. These programs then use values displayed in the list as input values. The user can, for example, call a transaction from within a list of change the database table whose data is displayed in the list. 9. What are system fields for secondary lists? SY-LSIND Index of the list created during the current event (basic list = 0) SY-LISTI Index of the list level from which the event was triggered. SY-LILLI Absolute number of the line from which the event was triggered. SY-LISEL Contents of the line from which the event was triggered. SY-CUROW Position of the line in the window from which the event was triggered (counting starts with 1) SY-CUCOL Position of the column in the window from which the event was triggered (counting starts with 2). SY-CPAGE Page number of the first displayed page of the list from which the event was triggered. SY-STARO Number of the first line of the first page displayed of the list from which the event was triggered (counting starts with 1). Possibly, a page header occupies this line. SY-STACO Number of the first column displayed in the list from which the event was triggered (counting starts with 1). SY-UCOMM Function code that triggered the event. SY-PFKEY Status of the displayed list. 10. How to maintain lists? To return from a high list level to the next-lower level (SY-LSIND), the user chooses Back on a secondary list. The system then releases the currently displayed list and activates the list created one step earlier. The system deletes the contents of the released list. To explicitly specify the list level, into which you want to place output, set the SY-lsind field. The system accepts only index values, which correspond to existing list levels. It then deletes all existing list levels whose index is greater or equal to the index specify. For example, if you set SY-LSIND to 0, the system deletes all secondary lists and overwrites the basic list with the current secondary list. 11. What are the page headers for secondary lists? On secondary lists, the system does not display a standard page header and it does not trigger the event. TOP-OF-PAGE. To create page headers for secondary list, you must enhance TOP-OF-PAGE: Syntax TOP-OF-PAGE DURING LINE-SELECTION. The system triggers this event for each secondary list. If you want to create different page headers for different list levels, you must program the processing block of this event accordingly, for example by using system fields such as SY-LSIND or SY-PFKEY in control statements (IF, CASE). 12. How to use messages in lists? ABAP/4 allows you to react to incorrect or doubtful user input by displaying messages that influence the program flow depending on how serious the error was. Handling messages is mainly a topic of dialog programming. You store and maintain messages in Table T100. Messages are sorted by language, by a two-character ID, and by a three-digit number. You can assign different message types to each message you output. The influence of a message on the program flow depends on the message type. In our program, use the MESSAGE statement to output messages statically or dynamically and to determine the message type. Syntax:REPORT MESSAGE-ID . 13. What are the types of messages? A message can have five different types. These message types have the following effects during list processing: .A (=Abend): .E (=Error) or W (=Warning): .I (=Information): .S (=Success): 14. What are the user interfaces of interactive lists? If you want the user to communicate with the system during list display, the list must be interactive. You can define specific interactive possibilities in the status of the list’s user interface (GUI). To define the statuses of interfaces in the R/3 system, use the Menu Painter tool. In the Menu Painter, assign function codes to certain interactive functions. After an user action occurs on the completed interface, the ABAP/4 processor checks the function code and, if valid, triggers the corresponding event. 15. What are the drill-down features provided by ABAP/4 in interactive lists? ABAP/4 provides some interactive events on lists such as AT LINE-SELECTION (double click) or AT USER-COMMAND (pressing a button). You can use these events to move through layers of information about individual items in a list. 16. What is meant by stacked list? A stacked list is nothing but secondary list and is displayed on a full-size screen unless you have specified its coordinates using the window command. 17. Is the basic list deleted when the new list is created? No. It is not deleted and you can return back to it using one of the standard navigation functions like clicking on the back button or the cancel button. 18. What is meant by hotspots? A Hotspot is a list area where the mouse pointer appears as an upright hand symbol. When a user points to that area (and the hand cursor is active), a single click does the same thing as a double-click. Hotspots are supported from R/3 release 3.0c. 19. What is the length of function code at user-command? Each menu function, push button, or function key has an associated function code of length FOUR (for example, FREE), which is available in the system field SYUCOMM after the user action. 20. Can we create a gui status in a program from the object browser? Yes. You can create a GUI STATUS in a program using SET PF-STATUS. 21. In which system field does the name of current gui status is there? The name of the current GUI STATUS is available in the system field SY-PFKEY. 22. Can we display a list in a pop-up screen other than full-size stacked list? Yes, we can display a list in a pop-up screen using the command WINDOW with the additions starting at X1 Y1 and ending at X2 Y2 to set the upper-left and the lower-right corners where x1 y1 and x2 y2 are the coordinates. 23. What is meant by hide area? The hide command temporarily stores the contents of the field at the current line in a system-controlled memory called the HIDE AREA. At an interactive event, the contents of the field are restored from the HIDE AREA. 24. When the get cursor command used in interactive lists? If the hidden information is not sufficient to uniquely identify the selected line, the command GET CURSOR is used. The GET CURSOR command returns the name of the field at the cursor position in a field specified after the addition field, and the value of the selected field in a field specified after value. 25. How can you display frames (horizontal and vertical lines) in lists? You can display tabular lists with horizontal and vertical lines (FRAMES) using the ULINE command and the system field SY-VLINE. The corners arising at the intersection of horizontal and vertical lines are automatically drawn by the system. 26. What are the events used for page headers and footers? The events TOP-OF-PAGE and END-OF-PAGE are used for pager headers and footers. 27. How can you access the function code from menu painter? From within the program, you can use the SY-UCOMM system field to access the function code. You can define individual interfaces for your report and assign them in the report to any list level. If you do not specify self-defined interfaces in the report but use at least one of the three interactive event keywords. AT LINE-SELECTION, AT PF, OR AT USER-COMMAND in the program, the system automatically uses appropriate predefined standard interfaces. These standard interfaces provide the same functions as the standard list described under the standard list. 28. How the at-user command serves mainly in lists? The AT USER-COMMAND event serves mainly to handle own function codes. In this case, you should create an individual interface with the Menu Painter and define such function codes. 29. How to pass data from list to report? ABAP/4 provides three ways of passing data: ---Passing data automatically using system fields ---Using statements in the program to fetch data ---Passing list attributes 30. How can you manipulate the presentation and attributes of interactive lists? ---Scrolling through Interactive Lists. ---Setting the Cursor from within the Program. ---Modifying List Lines. 31. How to call other programs? Report Transaction Call and return SUBMIT AND RETURN CALL TRANSACTION Call without return SUBMIT LEAVE TO TRANSACTION You can use these statements in any ABAP/4 program. 32. What will exactly the hide statement do? For displaying the details on secondary lists requires that you have previously stored the contents of the selected line from within the program. To do this, ABAP/4 provides the HIDE statement. This statement stores the current field contents for the current list line. When calling a secondary list from a list line for which the HIDE fields are stored, the system fills the stored values back into the variables in the program. In the program code, insert the HIDE statement directly after the WRITE statement for the current line. Interactive lists provide the user with the so-called ‘INTERACTIVE REPORTING’ facility. For background processing the only possible method of picking the relevant data is through ‘NON INTERACTIVE REPORT’ . After starting a background job, there is no way of influencing the program. But whereas for dialog sessions there are no such restrictions. 33. How many lists can a program can produce? Each program can produce up to 21 lists: one basic list and 20 secondary lists. If the user creates a list on the next level (that is, SY-LSIND increases), the system stores the previous list and displays the new one. Only one list is active, and that is always the most recently created list. FALSE.

ABAP - ABAP SYNTAX

noreply@blogger.com (A S Chakrapani) — Thu, 15 May 2008 03:28:00 +0000

ABAP - Creating and Changing ABAP Programs

noreply@blogger.com (A S Chakrapani) — Sun, 11 May 2008 14:27:00 +0000

ABAP programs are objects of the R/3 Repository. Like all other Repository objects, you maintain them using an ABAP Workbench - in this case, the ABAP Editor. This section provides a brief description of the ABAP Workbench and an overview of how to create and edit ABAP programs. It describes the different ways of starting the ABAP Editor. In the text below, 'open a program' always means 'start the ABAP Editor and use it to open a program'.

Starting the ABAP Editor : To start the ABAP Editor to create or change ABAP programs, the R/3 system offers three possibilities:

Using the Repository Browser : The Repository Browser in the ABAP Workbench (transaction SE80) offers a hierarchical overview of all R/3 Repository objects, ordered by development class, user name of the programmer, object type, and so on. If you enter a program name, you can directly access all of its components, such as the main program, subroutines, and global data. If you select a program object in the Repository Browser and choose Change, the system automatically opens the appropriate tool; in this case, the ABAP Editor. This method is suitable for complex programs, since the Repository Browser always provides you with an overview of all of the program components.

Using the ABAP Editor : You can open a program directly by choosing ABAP Editor from the initial screen of the ABAP Workbench (Transaction SE38). If you want to change a program using this method, you must already know its name and environment. This procedure is suited for maintaining or creating relatively simple or short programs, which have few or no additional components.

Using Forward Navigation : In any of the tools in the ABAP Workbench, you can open a different Repository object by positioning the cursor on it and double-clicking. The system automatically opens the object using the correct tool. This also applies to ABAP programs. Forward navigation by double-clicking is possible wherever an ABAP program is called from another object, such as screen flow logic or another program.

Naming ABAP Programs : The name of an ABAP program can be between 1 and 30 characters long.

ABAP - ABAP Statements

noreply@blogger.com (A S Chakrapani) — Sun, 11 May 2008 14:15:00 +0000

ABAP statements always begin with an ABAP keyword and are always concluded with a period (.) . Statements can be several lines long; conversely, a line may contain more than one statement.

Comments are distinguished by the preceding signs * (at the beginning of a line) and “ (at any
position in a line).

ABAP statements use ABAP data types and objects.

Statements and Keywords : The first element of an ABAP statement is the ABAP keyword. This determines the category of the statements. The different statement categories are as follows:

Declarative Statements :
These statements define data types or declare data objects which are used by the other statements in a program or routine. The collected declarative statements in a program or routine make up its declaration part.

Examples of declarative keywords: TYPES, DATA, TABLES

Modularization Statements :

1) Event Keywords : You use statements containing these keywords to define event blocks. There are no special statements to conclude processing blocks - they end when the next processing block is introduced.
Examples of event keywords are: AT SELECTION SCREEN, START-OF-SELECTION, AT USER-COMMAND

2) Defining keywords : You use statements containing these keywords to define subroutines, function modules, dialog modules and methods. You conclude these processing blocks using the ENDstatements.

Examples of definitive keywords:
FORM ..... ENDFORM, FUNCTION ... ENDFUNCTION,
MODULE ... ENDMODULE.

Control Statements :
You use these statements to control the flow of an ABAP program within a processing block
according to certain conditions.

Examples of control keywords: IF, WHILE, CASE

Call Statements :
You use these statements to call processing blocks that you have already defined using modularization statements. The blocks you call can either be in the same ABAP program or in a
different program.
Examples of call keywords: PERFORM, CALL, SET USER-COMMAND, SUBMIT, LEAVE TO

Operational Statements : These keywords process the data that you have defined using declarative statements.
Examples of operational keywords: WRITE, MOVE, ADD

Database Statements :
These statements use the database interface to access the tables in the central database system. There are two kinds of database statement in ABAP: Open SQL and Native SQL.

Open SQL : Open SQL is a subset of the standard SQL92 language. It contains only Data Manipulation Language (DML) statements, such as SELECT, IINSERT, and DELETE. It does not contain any Data Definition Language (DDL) statements (such as CREATE TABLE or CREATE INDEX). Functions of this type are contained in the ABAP Dictionary. Open SQL contains all of the DML functions from SQL92 that are common to all of the database systems supported by SAP. It also contains a few SAP-specific functions. ABAP programs that use only Open SQL statements to access the database are fully portable. The database interface converts the OPEN SQL commands into commands of the relevant database.

Native SQL : Native SQL statements are passed directly from the database interface to the database without first being converted. It allows you to take advantage of all of your database’s characteristics in your programs. In particular, it allows you to use DDL operations. The ABAP Dictionary uses Native SQL for tasks such as creating database tables. In ordinary ABAP programs, it is not worth using DDL statements, since you cannot then take advantage of the central administration functions of thie ABAP Dictionary. ABAP programs that use Native SQL statements are database-specific, because there is no standardized programming interface for SQL92.

ABAP - Program Types and Execution

noreply@blogger.com (A S Chakrapani) — Sun, 11 May 2008 14:02:00 +0000

In the R/3 System, there are various types of ABAP program. The program type determines the
basic technical attributes of the program, and you must set it when you create it. The main difference between the different program types is the way in which the runtime environment calls its processing blocks. When you run an application program, you must call at least the first processing block from outside the program, that is, from the runtime environment. This processing block can then either call further processing blocks or return control to the runtime environment. When you start an ABAP program, the runtime environment starts a processor (dependent on the program type), which calls the first ABAP processing block. An ABAP program can be started either by the user or by the system (for example, in background processing), or through an external interface (for example, Remote Function Call). There are two ways of allowing users to execute programs - either by entering the program name or by entering a transaction code. You can assign a transaction code to any program. Users can then start that program by entering the code in the command field. Transaction codes are also usually linked to a menu path within the R/3 System.

The following program types are relevant to application programming:

Type 1 :
Type 1 programs have the important characteristic that they do not have to be controlled using
user-defined screens. Instead, they are controlled by the runtime environment, which calls a series of processing blocks (and selection screens and lists where necessary) in a fixed sequence. User actions on screens can then trigger further processing blocks. You can start a type 1 program and the corresponding processor in the runtime environment using the SUBMIT statement in another ABAP program. There are also various ways of starting a type1 program by entering its program name. This is why we refer to type 1 programs as executable programs.
When you run a type 1 program, a series of processors run in a particular order in the runtime environment. The process flow allows the user to enter selection parameters on a selection screen. The data is them selected from the database and processed. Finally, an output list is displayed. At no stage does the programmer have to define his or her own screens. The runtime
environment also allows you to work with a logical database. A logical database is a special ABAP program which combines the contents of certain database tables. The flow of a type 1 program is oriented towards reporting, whose main tasks are to read data from the database, process it, and display the results. This is why executable programs (type 1) in the R/3 System are often referred to as reports, and why running an executable program is often called reporting. Since it is not compulsory to define event blocks, you can yourself determine the events to which your ABAP program should react. Furthermore, you can call your own screens or processing blocks at any time, leaving the prescribed program flow. You can use this, for example, to present data in a table on a dialog screen instead of in a list. The simplest executable program (report) contains only one processing block (START-OF-SELECTION). Executable programs do not require any user dialog. You can fill the selection screen using a variant and output data directly to the spool system instead of to a list. This makes executable programs (reports) the means of background processing in the R/3 System. You can also assign a transaction code to an executable program. Users can then start it using the transaction code and not the program name. The reporting-oriented runtime environment is also called when you run a report using a transaction code. This kind of transaction is called a report transaction. It is appropriate to use executable programs (reports) when the flow of your program corresponds either wholly or in part to the pre-defined flow of the runtime environment. Until Release 4.5A, the only way to use a logical database was to use an executable program. However, from Release 4.5A, it is also possible to call logical databases on their own.

Type M : The most important technical attribute of a type M program is that it can only be controlled using screen flow logic. You must start them using a transaction code, whcih is linked to the program and one of its screens (initial screen). Another feature of these programs is that you must define your own screens in the Screen Painter (although the intial screen can be a selection screen). When you start a program using a transaction code, the runtime environment starts a processor that calls the initial screen. This then calls a dialog module in the corresponding ABAP program. The remainder of the program flow can take any form. For example, the dialog module can: return control to the screen, after which, the processing passes to a subsequent screen. Each screen has a following screen, set either statically or dynamically. call other sequences of screens, selection screens or lists, from which further processing blocks in the ABAP program are started. call other processing blocks itself, either internally or externally. call other application programs using CALL TRANSACTION (type M program) or SUBMIT (type 1 program). ABAP programs with type M contain the dialog modules belonging to the various screens. They are therefore known as module pools. It is appropriate to use module pools when you write dialog-oriented programs using a large number of screens whose flow logic largely determines the program flow.

Type F : Type F programs are containers for function modules, and cannot be started using a transaction code or by entering their name directly. Function modules are special procedures that you can call from other ABAP programs. Type F programs are known as function groups. Function modules may only be programmed in function groups. The Function Builder is a tool in the ABAP Workbench that you can use to create function groups and function modules. Apart from function modules, function groups can contain global data declarations and subroutines. These are visible to all function modules in the group. They can also contain event blocks for screens in function modules.

Type K : You cannot start type K programs using a transaction code or by entering the program name. They are containers for global classes in ABAP Objects . Type K programs are known as class definitions. The Class Builder is a tool in the ABAP Workbench that you can use to create
class definitions.

Type J : You cannot start type J programs using a transaction code or by entering the program name. They are containers for global interface in ABAP Objects . Type J programs are known as
interface definitions. Like class definitions, you create interface definitions in the Class Builder.

Type S : You cannot start a type S program using a transaction code or by entering the program name. Instead, they are containers for subroutines, which you can call externally from other ABAP programs. Type S programs are known as subroutine pools. They cannot contain screens.

Type I: Type I programs - called includes - are a means of dividing up program code into smaller, more manageable units. You can insert the coding of an include program at any point in another ABAP program using the INCLUDE statement. There is no technical relationship between include programs and processing blocks. Includes are more suitable for logical programming units, such as data declarations, or sets of similar processing blocks. The ABAP Workbench has a mechanism for automatically dividing up module pools and function groups into include programs.

ABAP - Advanced Business Application Programming

COMPLETE ALV DOCUMENTATION

OOPS AT A GLANCE

Performance Tuning

ABAP - Questions

ABAP - Interview Questions 3

TRANSACTION CODES - OTHERS

TRANSACTION CODES - MM configuration transactions

TRANSACTION CODES - Material Management (MM)

TRANSACTION CODES - FI Financial Management

TRANSACTION CODES - SAP OFFICE

TRANSACTION CODES - Sales and Distribution (SD)

TRANSACTION CODES - Human Resources (HR)

TRANSACTION CODES - Basis / ABAP

TRANSACTION CODES - Production Planning (PP)

TRANSACTION CODES - Plant Maintenance (PM)

ABAP - Interview Questions - 2

SAP System - Fields

ABAP - Interview Questions - 1

ABAP - Performance tuning

Using tablebuffering

Use the ABAP SORT Clause Instead of ORDER BY

Avoid ther SELECT DISTINCT Statement

ALV

ABAP - REPORT GENERATION - FORMATTING

ABAP - ABAP SYNTAX

ABAP - Creating and Changing ABAP Programs

ABAP - ABAP Statements

ABAP - Program Types and Execution

Using table

buffering