Please enable JavaScript.

Coggle requires JavaScript to display documents.

List Screens (13.1 Program Types (13.1.4 Class Pools (loaded when the…

- - - - enter the program name in Transaction SA38
      - executed directly from ABAP Editor SE38
  - - - A function group can use all processing blocks in ABAP, except reporting events.
  - - - A transaction code can be created for a method of the global class so that an object of the class can be created implicitly when the method is used.
- - - - The sequence of events triggered by the ABAP runtime environment is as follows
        
        LOAD-OF-PROGRAM
        
        INITIALIZATION
        
        AT SELECTION-SCREEN
        
        START-OF-SELECTION
        
        GET
        
        END-OF-SELECTION
  - - - The transaction code links the program with one of its screens, which becomes the initial screen.
        
        From this initial screen, dialog modules and other screens are called.
    - - LOAD-OF-PROGRAM
        
        PROCESS BEFORE OUTPUT (PBO)
        
        PROCESS AFTER INPUT (PAI)
  - - - Executable programs are called internally using the SUBMIT statement with the program name, whereas module pool programs are called using CALL TRANSACTION or LEAVE TO TRANSACTION statements terminate the calling program
- - - - The line count is set using the LINE-COUNT statement in the program introductory statement.
  - - - DATA: column TYPE string, row TYPE I. AT LINE-SELECTION. GET CURSOR FIELD column. GET CURSOR LINE row.
        
        the column name will be transferred to the column field and the row number will be transferred to the row field
  - - - Under this event, we can maintain the functionality to perform various actions based on the button selected by the user on the list screen.
      - The function code of the GUI menu item or button is transferred to the sy-ucomm system field, which can be checked to identify the user action.
- - - - These additional lists are called detail lists (or secondary lists)
      - One basic list can have up to 19 detail lists.
  - - - FORM output. LOOP AT it_sflight INTO wa_sflight. WRITE: / wa_sflight-carrid, wa_sflight-connid, wa_sflight-fldate. HIDE: wa_sflight-carrid, wa_sflight-connid. ENDLOOP. ENDFORM.
- - - - only the basic list to display the report output
- - - - Once a record is written to the basic list using the WRITE statement, the HIDE statement is used immediately to store the record in the hide area.
        
        When the user selects the record from the list, it's automatically copied to the data object in the program for which the value was written in the output.
  - - - Using the READ LINE statement, you can read any line by supplying the row number.
        
        use the GET CURSOR statement to dynamically identify the row on which the user double-clicked and use that row number with the READ LINE statement to get the field value
      - To read the line in succession, use the READ CURRENT LINE statement.
      - DATA row TYPE sy-index. GET CURSOR LINE row. READ LINE row FIELD VALUE wa_vbrk-vbeln. READ CURRENT LINE FIELD VALUE wa_vbrk-vbeln.
        
        the READ LINE statement reads the field value of the supplied row number
        
        the READ CURRENT LINE statement automatically reads the line where the cursor is currently positioned
  - - - fetch row number
        
        DATA row TYPE sy-index. GET CURSOR LINE row.
      - fetch column (field) name
        
        DATA field TYPE string. GET CURSOR FIELD field.
  - - - retrieve information such as the number of lines or number of pages of a list, get the page number of a particular line number, or get the properties of the particular page
    - - the last_page field will contain the total number of pages generated
      - the line field will contain the number of lines in the last page