Please enable JavaScript.

Coggle requires JavaScript to display documents.

7.3 Events (7.3.1 Program Constructor Events (The LOAD-OF-PROGRAM event…

- - - - When you run an executable program, a series of events are triggered, one after the other, by the ABAP runtime environment.
  - - - the first reporting event triggered when an executable program is running
      - has a LOAD-OF-PROGRAM event block
        
        executed immediately after the LOAD-OF-PROGRAM event block
      - has a selection screen defined
        
        called after the ABAP selection screen code has been processed, before the selection screen is displayed to the user
        
        to initialize input fields of the selection or change the default values of these at runtime before the user gets to enter data into them
        
        PARAMETERS p_carrid TYPE s_carr_id DEFAULT 'LH'. INITIALIZATION. p_carrid = 'AA'.
      - is triggered only once per program execution
    - - is called after the INITIALIZATION event
      - has a selection screen defined
        
        is the first event that is triggered after all selection screen processing has been completed (after executing all selection screen events)
      - put all the data selection logic of ABAP program within the START-OF-SELECTION event
    - - when the executable program uses a logical database for data selection
        
        A logical database is a special ABAP program that retrieves data from the database and makes it available to the application program.
      - The GET event is triggered when the logical database has read a line from the table mentioned in the event keyword and made it available to the program in the work area declared using the TABLES <table> or NODES <table> statement.
        
        NODES: SPFLI. GET SPFLI. SKIP. WRITE: / 'FROM:' , SPFLI-CITYFROM. 'TO:' , SPFLI-CITYTO.
    - - Once all of the data records for a node of the logical database have been read, the ABAP runtime environment triggers the GET<table> LATE event.
        
        can process the steps that should be executed at the end of the block
    - - is used to mark the end of selection
        
        If you report isn't using a logical database, then this event is used after a START-OF-SELECTION event to mark the end of selection and to continue with further processing of the selected data.
        
        If your report is linked to a logical database, this event is called after the logical database has completely transferred all the records to the application program.
- - - - consists of the input/output fields and the screen flow logic
  - - - triggered before the screen is shown to the user and can be used to modify the screen
    - - triggered when the user performs an action on the screen, used to evaluate user actions
    - - triggered when the user select F1 help on the screen field
        used to show field documentation to help the user learn more about a field
    - - triggered when the user selects F4 help on the screen field
        used to show the possible entries for a field (a value list)